Linking problems with latest coreLibrary_300 on windows

A place to discuss everything related to Newton Dynamics.

Moderators: Sascha Willems, walaber

Linking problems with latest coreLibrary_300 on windows

Postby Bird » Thu Feb 09, 2012 9:52 am

I'm getting some multiple definition errors while trying to link my vc2008 project to the very latest SVN version of lib_300

1>core.lib(dgThreadHive.obj) : error LNK2005: "public: void __thiscall dgThreadHive::GetIndirectLock(int * const,unsigned int)const " (?GetIndirectLock@dgThreadHive@@QBEXQAHI@Z) already defined in newton_d.lib(Newton.obj)
1>core.lib(dgThreadHive.obj) : error LNK2005: "public: void __thiscall dgThreadHive::ReleaseIndirectLock(int * const)const " (?ReleaseIndirectLock@dgThreadHive@@QBEXQAH@Z) already defined in newton_d.lib(Newton.obj)
1>core.lib(dgThreadHive.obj) : error LNK2005: "public: void __thiscall dgThreadHive::GetLock(unsigned int)const " (?GetLock@dgThreadHive@@QBEXI@Z) already defined in newton_d.lib(Newton.obj)
1>core.lib(dgThreadHive.obj) : error LNK2005: "public: void __thiscall dgThreadHive::ReleaseLock(void)const " (?ReleaseLock@dgThreadHive@@QBEXXZ) already defined in newton_d.lib(Newton.obj)


The Newton SDK demo compiles ok, so I assume I'm doing something wrong on my end but I can't figure out what. I noticed that the SDK demo doesn't link to Newton.lib but I don't do that, I get all sorts of other linker errors.

Also the debug Win32 version of dJointLibrary does not compile cleanly using vc2008

1>------ Build started: Project: dJointLibrary, Configuration: debug Win32 ------
1>Compiling...
1>CustomWheelVehicle.cpp
1>..\..\dCustomJoints\CustomWheelVehicle.cpp(64) : error C2065: 'SERIALIZE_ID_COMPOUND_ARTICULATED_SKELETON' : undeclared identifier
1>..\..\dCustomJoints\CustomWheelVehicle.cpp(64) : error C3861: 'NewtonCollisionGetType': identifier not found
1>Build log was saved at "file://e:\Depenencies\NewtonTrunk\packages\projects\visualStudio_2008\Win32\dJointLibrary\de


-Bird
Bird
 
Posts: 636
Joined: Tue Nov 22, 2011 1:27 am

Re: Linking problems with latest coreLibrary_300 on windows

Postby Julio Jerez » Thu Feb 09, 2012 10:06 am

I remember having that problem, and I fix it but maybe I forget to apply teh fix to other solution.
what project are you building. can you print teh path to whe the VS project is?
Julio Jerez
Moderator
Moderator
 
Posts: 12426
Joined: Sun Sep 14, 2003 2:18 pm
Location: Los Angeles

Re: Linking problems with latest coreLibrary_300 on windows

Postby Bird » Thu Feb 09, 2012 10:25 am

Julio Jerez wrote:I remember having that problem, and I fix it but maybe I forget to apply teh fix to other solution.
what project are you building. can you print teh path to whe the VS project is?

I'm trying to build a win32 debug version Here's the Newton paths that I'm providing to vs2008

LIBS += E:/Depenencies/NewtonTrunk/coreLibrary_300/projets/windows/project_vs2008/Win32/core/debug/core.lib
LIBS += E:/Depenencies/NewtonTrunk/coreLibrary_300/projets/windows/project_vs2008/Win32/newton/debug/newton_d.lib
LIBS += E:/Depenencies/NewtonTrunk/coreLibrary_300/projets/windows/project_vs2008/Win32/physics/debug/physics.lib
LIBS += E:/Depenencies/NewtonTrunk/packages/Win32/debug/dMath_d.lib
LIBS += E:/Depenencies/NewtonTrunk/packages/Win32/debug/dJointLibrary_d.lib
LIBS += E:/Depenencies/NewtonTrunk/packages/Win32/debug/dContainers_d.lib
LIBS += E:/Depenencies/NewtonTrunk/packages/Win32/debug/dScene_d.lib
LIBS += E:/Depenencies/NewtonTrunk/packages/Win32/debug/tinyxml_d.lib

-Bird
Bird
 
Posts: 636
Joined: Tue Nov 22, 2011 1:27 am

Re: Linking problems with latest coreLibrary_300 on windows

Postby Julio Jerez » Thu Feb 09, 2012 11:16 am

I just build all teh project and they compile fine.

nmake sure you delete the newton.h file from an alder dowload.

I deleted the part do publich teh heder file form the core enge to the SDK tool forder, you most have an older version there.
I have to do that because Buggey VI2010 does no supports post build even anymore, therfore I can not copy the file afte copimled.

to make uniform for 2008 and 2010, I remove the batch copy form VS 2008 and I us eteh headers form where there are originally created.
Julio Jerez
Moderator
Moderator
 
Posts: 12426
Joined: Sun Sep 14, 2003 2:18 pm
Location: Los Angeles

Re: Linking problems with latest coreLibrary_300 on windows

Postby Bird » Thu Feb 09, 2012 1:18 pm

Julio Jerez wrote:I just build all teh project and they compile fine.

nmake sure you delete the newton.h file from an alder dowload.

I deleted the part do publich teh heder file form the core enge to the SDK tool forder, you most have an older version there.
I have to do that because Buggey VI2010 does no supports post build even anymore, therfore I can not copy the file afte copimled.

to make uniform for 2008 and 2010, I remove the batch copy form VS 2008 and I us eteh headers form where there are originally created.

I started over with a new SVN sync and now it works fine. Thanks for the help!

-Bird
Bird
 
Posts: 636
Joined: Tue Nov 22, 2011 1:27 am


Return to General Discussion

Who is online

Users browsing this forum: No registered users and 1 guest

cron