Codejock Developer Community : Link Errors with ToolKitPro

Link Errors with ToolKitPro : Thanks. We considered turning...

Tue, 08 Aug 2006 18:58:19 +0000

Author: skemp@docucorp
Subject: 4759
Posted: 08 August 2006 at 6:58pm

Thanks. We considered turning that option off in the ToolkitPro build to see what would happen. But then we figured we might have to change headers or source modules to include the define. And we're trying not to modify your library if possible.

Link Errors with ToolKitPro : see alsohttp://forum.codejoc...

Tue, 08 Aug 2006 14:45:24 +0000

Author: sserge
Subject: 4759
Posted: 08 August 2006 at 2:45pm

see also http://forum.codejock.com/forum_posts.asp?TID=2934 and http://forum.codejock.com/forum_posts.asp?TID=3570

--
WBR,
Serge

Link Errors with ToolKitPro : Well, to answer our own question: It...

Tue, 08 Aug 2006 11:26:37 +0000

Author: skemp@docucorp
Subject: 4759
Posted: 08 August 2006 at 11:26am

Well, to answer our own question:

It appears to be the compile option that says a wchar is a built-in type. Once we turned that on and recompiled all relevant libraries, the link issue was resolved.

Now to see if we can get anything in the framework replaced and working....

Link Errors with ToolKitPro : New customer. We have a rather...

Tue, 08 Aug 2006 10:24:47 +0000

Author: skemp@docucorp
Subject: 4759
Posted: 08 August 2006 at 10:24am

New customer. We have a rather large application where we are trying to replace the existing framework with that from ToolKitPro. Unfortunately, early in the process we have hit a snag.

The application has multiple DLLs, ToolKitPro was built as a separate DLL using the provided wizard. From our DLL, we have instantiated a XTP class. We can apparently call any member function as long as it does not require a CString as a parameter. When we call a member requiring a CString, we get the following type of link error.

DCVCore error LNK2019: unresolved external symbol "__declspec(dllimport) public: int __thiscall CXTPStatusBar::SetPaneText(int,class ATL::CStringTshort,class StrTraitMFC_DLLshort,class ATL::ChTraitsCRT > > const &,int)" (__imp_?SetPaneText@CXTPStatusBar@@QAEHHABV?$CStringT@GV?$StrTraitMFC_DLL@GV?$ChTraitsCRT@G@ATL@@@@@ATL@@H@Z) referenced in function "public: void __thiscall CMainFrame::SetIndicatorText(int,unsigned short const *)" (?SetIndicatorText@CMainFrame@@QAEXHPBG@Z)

This appears to be a name-mangling conflict.

In export file from Toolkit DLL

?SetPaneText@CXTPStatusBar@@QAEHHABV?$CStringT@_WV?$StrTraitMFC_DLL@_WV?$ChTraitsCRT@_W@ATL@@@@@ATL@@H@Z

Link error from our DLL

?SetPaneText@CXTPStatusBar@@QAEHHABV?$CStringT@GV?$StrTraitMFC_DLL@GV?$ChTraitsCRT@G@ATL@@@@@ATL@@H@Z)

You will notice that the CString parameter is not mangled the same way.

Our DLL is compiled for Unicode, just as we (think) selected for the ToolKit DLL.

Anyway, does anyone have a guess as to what will resolve our problem. I'm going to guess it is a compiler or linker option conflict between the DLLs. We'll be looking into that next.

SEK