Home > Archive > Visual Studio > February 2006 > VS 2005 lunresolved external symbols on linked external DLL
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
VS 2005 lunresolved external symbols on linked external DLL
|
|
| JM Lynn 2006-02-22, 7:00 pm |
| Help!
I finally upgraded my Visual Studio V6 to Visual Studion 2005. When I
open the VS V6 C++ project, VS 2005 asked if I want to convert into VS
2005. I clicked "Yes to all" and it seemed to be fine. But when I
start to build the project, I got "unresolved external symbol errors.
Upon close inspection, the required LIB files have been defined and
their paths were specified. But the linker just complained. The
following is a sample error on linking to Xerces C++ DLL.
CXMLNode.obj : error LNK2019: unresolved external symbol
"__declspec(dllimport) public: static char * __cdecl
xercesc_2_7::XMLString::transcode(wchar_
t const * const)"
(__imp_? transcode@XMLString@xercesc_2_7@@SAPADQB
_W@Z) referenced in
function "protected: void __thiscall CXMLNode::parseNode(class
xercesc_2_7::DOMNode *)"
(? parseNode@CXMLNode@@IAEXPAVDOMNode@xerce
sc_2_7@@@Z)
The project build fine under VS V6 and nothing had been changed other
than upgrading to VS 2005.
Any suggestion?
jml
| |
| Jeff Lynn 2006-02-22, 9:57 pm |
| More info, I set the "Linker - General - Additional Library Directories"
property to the proper additional Lib path, as well as the "Linker - Input -
Additional Dependencies" property to the proper lib file.
Since it work under VS V6, then it must be VS 2005 changed the default way
of external Library reference.
Can someone show me the proper configuration so I can call external Library?
Thanks!
JML
"JM Lynn" wrote:
> Help!
>
> I finally upgraded my Visual Studio V6 to Visual Studion 2005. When I
> open the VS V6 C++ project, VS 2005 asked if I want to convert into VS
> 2005. I clicked "Yes to all" and it seemed to be fine. But when I
> start to build the project, I got "unresolved external symbol errors.
>
> Upon close inspection, the required LIB files have been defined and
> their paths were specified. But the linker just complained. The
> following is a sample error on linking to Xerces C++ DLL.
>
> CXMLNode.obj : error LNK2019: unresolved external symbol
> "__declspec(dllimport) public: static char * __cdecl
> xercesc_2_7::XMLString::transcode(wchar_
t const * const)"
> (__imp_? transcode@XMLString@xercesc_2_7@@SAPADQB
_W@Z) referenced in
> function "protected: void __thiscall CXMLNode::parseNode(class
> xercesc_2_7::DOMNode *)"
> (? parseNode@CXMLNode@@IAEXPAVDOMNode@xerce
sc_2_7@@@Z)
>
> The project build fine under VS V6 and nothing had been changed other
> than upgrading to VS 2005.
>
> Any suggestion?
>
> jml
>
| |
|
| On Thu, 23 Feb 2006 04:27:04 +0200, Jeff Lynn =
<JeffLynn@discussions.microsoft.com> wrote:
> More info, I set the "Linker - General - Additional Library Directorie=
s"
> property to the proper additional Lib path, as well as the "Linker - =
> Input -
> Additional Dependencies" property to the proper lib file.
>
> Since it work under VS V6, then it must be VS 2005 changed the default=
=
> way
> of external Library reference.
>
> Can someone show me the proper configuration so I can call external =
> Library?
>
> Thanks!
try to recompile Xercesc first.
-- =
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
|
|
|
|
|