Linkage Problems

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   We are attempting to migrate from the XTreme Toolkit 4.1 to the XTreme Toolkit Pro 10.4.2.

We are trying to utilize the dynamic CRT library with static linkage to the XTreme Toolkit Pro using ToolkitPro1042vc71DS.lib (release) and ToolkitPro1042vc71DSD.lib (debug).

The first thing noticed besides the linker errors is that the XTreme libraries use the __cdecl calling convention while our applications use the __stdcall calling convention.  Trying to recompile the XTreme Toolkit Pro libraries using the __stdcall calling convention fails.

The second, and more concerning issue, is that we are unable to perform a successful linkage with the new libraries.  We get LNK2001 errors in release mode and LNK2005 errors in debug mode.  

We believe we are using the correct runtime libraries by ignoring (libc.lib;libcmt.lib;msvcrt.lib;libcd.lib;libcmtd.lib) for debug builds and ignorming (libc.lib;libcmt.lib;libcd.lib;libcmtd.lib;msvcrtd.lib) for release builds.

Any help is greatly appreciated.

Thanks greatly...

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
denczek Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 06 August 2004 Status: Offline Points: 27	Post Options Post Reply Quote denczek Report Post Thanks(0) Quote Reply Topic: Linkage Problems Posted: 06 February 2007 at 2:14pm
	We are attempting to migrate from the XTreme Toolkit 4.1 to the XTreme Toolkit Pro 10.4.2. We are trying to utilize the dynamic CRT library with static linkage to the XTreme Toolkit Pro using ToolkitPro1042vc71DS.lib (release) and ToolkitPro1042vc71DSD.lib (debug). The first thing noticed besides the linker errors is that the XTreme libraries use the __cdecl calling convention while our applications use the __stdcall calling convention. Trying to recompile the XTreme Toolkit Pro libraries using the __stdcall calling convention fails. The second, and more concerning issue, is that we are unable to perform a successful linkage with the new libraries. We get LNK2001 errors in release mode and LNK2005 errors in debug mode. We believe we are using the correct runtime libraries by ignoring (libc.lib;libcmt.lib;msvcrt.lib;libcd.lib;libcmtd.lib) for debug builds and ignorming (libc.lib;libcmt.lib;libcd.lib;libcmtd.lib;msvcrtd.lib) for release builds. Any help is greatly appreciated. Thanks greatly...

denczek Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 06 August 2004 Status: Offline Points: 27	Post Options Post Reply Quote denczek Report Post Thanks(0) Quote Reply Posted: 06 February 2007 at 2:43pm
	Here's an example of one of the many linker errors in debug mode: ... error LNK2005: "private: static class CXTPColorManager & __cdecl CXTPColorManager::Instance(void)" (?Instance@CXTPColorManager@@CAAAV1@XZ) already defined in ToolkitPro1042vc71DSD.lib(XTPColorManager.obj)

Oleg Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 21 May 2003 Location: United States Status: Offline Points: 11234	Post Options Post Reply Quote Oleg Report Post Thanks(0) Quote Reply Posted: 07 February 2007 at 1:16am
	Hi, message "already defined in ToolkitPro1042vc71DSD" means that you somehow include this file twice. May be you added this file directly to your application?
	Oleg, Support Team CODEJOCK SOFTWARE SOLUTIONS