xerces-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeroen N. Witmond" <...@xs4all.nl>
Subject Re: Re: unresolved symbols (external)
Date Thu, 04 Mar 2004 20:28:18 GMT
I'm sorry, but I cannot help you with this problem. Perhaps somenody on
the list can.

Jeroen.

> I build the dll and lib files first. Copy them into the necessary
> directory (Common\xerces-lib). Added this directory to my link
> tab, then I attempt to build my project.
>
> my project manager and I looked at XMemory.obj file, there are no
> reference to new & delete. We did confirm the file is compiled. (Otherwise
> there wouldn't be the obj file 8-)
>
> in the function where new is called, we tried to put ::new
>
> old code:
>    MemBufInputSource *memBufIS = new MemBufInputSource((const
> XMLByte*)mem, strlen(mem), gMemBufId, false);
>
> new code:
>    MemBufInputSource *memBufIS = ::new MemBufInputSource((const
> XMLByte*)mem, strlen(mem), gMemBufId, false);
>
> We then got one less unknown symbol while linking. My project
> manager thinks this could an issue with namespace. But we are
> not quite sure at this point.
>
> This is currently my linking unresolved symbols...
> Linking...
>    Creating library Release/Engine.lib and object Release/Engine.exp
> lib.lib(ConstraintChecker.obj) : error LNK2001: unresolved external symbol
> "__declspec(dllimport) public: static void __stdcall
> xercesc_2_5::XMemory::operator delete(void *)"
> (__imp_??3XMemory@xercesc_2_5@@SGXPAX@Z)
> lib.lib(ConstraintChecker.obj) : error LNK2001: unresolved external symbol
> "__declspec(dllimport) public: static void __stdcall
> xercesc_2_5::XMLString::release(char * *)"
> (__imp_?release@XMLString@xercesc_2_5@@SGXPAPAD@Z)
> lib.lib(ConstraintChecker.obj) : error LNK2001: unresolved external symbol
> "__declspec(dllimport) public: static char * __stdcall
> xercesc_2_5::XMLString::transcode(unsigned short const * const)"
> (__imp_?transcode@XMLString@xercesc_2_5@@SGPADQBG@Z)
> lib.lib(ConstraintChecker.obj) : error LNK2001: unresolved external symbol
> "public: class ostream & __thiscall ostream::operator<<(int)"
> (??6ostream@@QAEAAV0@H@Z)
> lib.lib(ConstraintChecker.obj) : error LNK2001: unresolved external symbol
> "public: class ostream & __thiscall ostream::operator<<(unsigned char)"
> (??6ostream@@QAEAAV0@E@Z)
> lib.lib(ConstraintChecker.obj) : error LNK2001: unresolved external symbol
> "public: class ostream & __thiscall ostream::operator<<(char const *)"
> (??6ostream@@QAEAAV0@PBD@Z)
> lib.lib(ConstraintChecker.obj) : error LNK2001: unresolved external symbol
> "class ostream_withassign  cout" (?cout@@3Vostream_withassign@@A)
> lib.lib(ConstraintChecker.obj) : error LNK2001: unresolved external symbol
> "__declspec(dllimport) public: static class xercesc_2_5::DOMImplementation
> * __stdcall
> xercesc_2_5::DOMImplementationRegistry::getDOMImplementation(unsigned
> short const *)" (
> __imp_?getDOMImplementation@DOMImplementationRegistry@xercesc_2_5@@SGPAVDOMImplementation@2@PBG@Z)
> lib.lib(ConstraintChecker.obj) : error LNK2001: unresolved external symbol
> "__declspec(dllimport) public: static void __stdcall
> xercesc_2_5::XMLPlatformUtils::Initialize(char const * const,char const *
> c
> onst,class xercesc_2_5::PanicHandler * const,c
> lass xercesc_2_5::MemoryManager * const)"
> (__imp_?Initialize@XMLPlatformUtils@xercesc_2_5@@SGXQBD0QAVPanicHandler@2@QAVMemoryManager@2@@Z)
> lib.lib(ConstraintChecker.obj) : error LNK2001: unresolved external symbol
> "public: class ostream & __thiscall ostream::flush(void)"
> (?flush@ostream@@QAEAAV1@XZ)
> Release/Engine.dll : fatal error LNK1120: 10 unresolved externals
> Error executing link.exe.
>
>
> Any help/hint or things to try would be appreciated.
>
> -- Jimmy
>>
>> From: "Jeroen N. Witmond" <jnw@xs4all.nl>
>> Date: 2004/03/04 Thu AM 11:13:22 PST
>> To: jyu1@verizon.net
>> Subject: Re: unresolved symbols (external)
>>
>> > I have done a sanity check on this in the settings for
>> > the current project.
>> >
>> > If I change my path, add or take out ..\ I would get
>> > xerces-c_2D.lib file not found, but if I keep the path
>> > the same, ..\..\Common\xerces-lib\xerces-c_2D.lib, I
>> > would then get all the unresolved externals.
>> >
>> > If anyone have a hint or further debugging ideas, please
>> > let me know. I have tried with 2.4 and 2.5 version, they
>> > all report the same problem. I build the xerces dll's and
>> > lib's by selecting batch build, all - Win32 Debug and Release. Didn't
>> > change any settings. If this is the wrong way to build
>> > xerces dll's and lib's please let me know, and tell me the right
>> > way to build it.
>>
>> This may have been said before, but just to be sure: Please note that
>> Xerces includes the version number in the C++ namespace name, which the
>> compiler uses in all external names. Therefore the application must be
>> compiled with the same version of Xerces that is used for the dll files.
>>
>> Regards,
>>
>> Jeroen.
>>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org


Mime
View raw message