Hi Alberto, You are correct. After making the settings match, my MFC program compiled on 7.0. Thank you for your help! Maybe this is worth adding to the FAQ or known issues?
Best regards, Antoan Nikolaev -----Original Message----- From: Alberto Massari [mailto:[EMAIL PROTECTED] Sent: Monday, October 03, 2005 2:00 AM To: [email protected] Subject: Re: unresolved symbols when compiling MFC app with xerces using MSVC7.0 Hi Antoan, can you check if the setting "Treat wchar_t as a built-in type" is set to to different values ("true" in your project, "false" in the Xerces project)? If so, make them equal. Alberto At 18.26 30/09/2005 -0700, Antoan Nikolaev wrote: >I am trying to use xerces-c 2.7 in a MFC application. I am currently >using the 7.0 compiler. > >I did download the source and successfuly built all libraries. > >I can even compile my source successfully but I can never link >properly. I always get errors like this: > >xercesTest1 error LNK2019: unresolved external symbol >"__declspec(dllimport) public: static class >xercesc_2_7::DOMImplementation * __cdecl >xercesc_2_7::DOMImplementationRegistry::getDOMImplementation(wchar_t >const *)" >([EMAIL PROTECTED]@xercesc_2_7@@SAPAVDO [EMAIL PROTECTED]@[EMAIL PROTECTED]) >referenced in function "public: static void __cdecl >Test::doTest(void)" ([EMAIL PROTECTED]@@SAXXZ) > > >xercesTest1 error LNK2019: unresolved external symbol >"__declspec(dllimport) public: static bool __cdecl >xercesc_2_7::XMLString::transcode(char const * const,wchar_t * >const,unsigned int,class xercesc_2_7::MemoryManager * const)" >([EMAIL PROTECTED]@xercesc_2_7@@[EMAIL PROTECTED]@@Z) >referenced in function "public: static void __cdecl >Test::doTest(void)" ([EMAIL PROTECTED]@@SAXXZ) > > > >I thought it was me at first.... > >turns out if I use console application instead of MFC one, things >compile and work just fine. > >In addition I did the same test in VC6.0 and everything compiles and >links just fine. > >Can anyone help me with this? > >Best regards, >Antoan Nikolaev >
