Migration to 300

[misho]

I'm trying to migrate to 300 (from 2.24). I have successfully built core, newton and physics. Now, since my code is based on 200, I'd like to build/run tutorialsSDK200. I'm assuming, since they are included in the archive, they can be built using the newest code.

However, I'm running into problems... namely:

File 'E:\newton-dynamics-master\coreLibrary_300\projects\windows\project_vs2008\core.vcproj' was not found.

Indeed, VS2008 don't exist any longer, only VS2010 and onwards. Did I miss a conversion step somewhere? Is it possible to compile the tutorialsSDK200 using the newest version of the code?

thanks,
Misho

[misho]

Anyone, please?

[JoeJ]

I'm assuming, since they are included in the archive, they can be built using the newest code.

Guess they are written on 2.x, so they will not work on 3.x without minor modifications.
You would need to add a new project to tutorialsSDK300 solution for each of the older tutorials that is missing, add the sources and update stuff.
(Tried it but failed on precompiled header stuff - i don't know how this works)


It might be easier to use Sandbox for reference. It's big but it's easy to add your own demo for some testing.

[misho]

Ok, thanks, as long as it is "minor" modifications. When you mention sandbox, you mean:

newton-dynamics-master\applications\demosSandbox, correct?

It would be really helpful if there was some form of a "user guide" as to how the newton-dynamics-master archive is structured and what different components represent. For instance, what's the difference between coreLibrary_300 and packages, namely

newton-dynamics-master\coreLibrary_300\projects\windows
newton-dynamics-master\packages\projects

They both seem to contain projects to build newton.lib, but with different components alongside it.

thanks,
Misho

[JoeJ]

Packages contains additinal stuff, e.g. custom joint lib.
They are seperated so you can select what you wanna use.
Most of it is used by the demoSandox, for the user those two may be most interesting:

dCustomJoints: Joints for ragdolls, doors, bridges etc.
dNewton: C++ Interface if you prefer that over C (if i'm not wrong)

Core is the phyisics library alone. (Personally i've added those files to my project, that way i don't need to build dll or lib files, but i need to reflect Julios changes if he adds or rmoves a file)

applications\demosSandbox is the demo application, it builds all required projects, dlls etc.
So it's good to browse source and see what it's good for, because it contains it all.

[misho]

Thanks again, this cleared up things a bit, and I`ve now modified my code to the latest library. Compiling goes fine, however, linking gives me error for every `Newton...`call:

Code: Select all

...error LNK2001: unresolved external symbol __imp__Newton...

I`ve checked and double checked, I am linking to a correct static MT newton.lib, and dMath.lib - that`s all.

My old code linked to a static 2.24 MT newon.lib and dMath.lib as well, without any problems. Is there anything that I overlooked? It seems that dMath.lib is linking fine since I`m not getting any unresolved external symbol errors there. I did a bit of poking around on what causes LNK2001 (besides obvious) and one of the causes is when the symbols are defined in a C program and used in C++ code... however, I`m assuming, since newton.lib worked in 2.24, it would still be a C++ code and work in the latest release. Is that correct? Any thoughts, anyone?

[Sweenie]

Are you adding the _NEWTON_STATIC_LIB preprocessor definition?

[misho]

Uh... no. I was using _NEWTON_USE_LIB, which I suspect is the obsolete version of _NEWTON_STATIC_LIB... Thanks! I inserted it and the linker errors are gone!

I got a slew of new linker errors, but I figured that I also need physics.lib, core.lib and pthread.lib, and now I get a clean compile. I guess the minimal set of libraries are those five.

Thanks again!

[misho]

And now, I need a double precision versions of libraries, which I think is a whole different topic.