Dyuti Barma wrote:
On Wed, Dec 10, 2008 at 11:38 PM, David Bertoni <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Dyuti Barma wrote:
Hi,
Another related question :
Can Xalan be built with VC8 using *xerces 2.8 *instead of xerces
3.0 ?
I'm getting the following errors :
1>Linking...
1>ICUResHandler.obj : error LNK2001: unresolved external symbol
"__declspec(dllimport) public: static int __cdecl
xercesc_2_8::XMLString::compareString(wchar_t const *
const,wchar_t const * const)"
([EMAIL PROTECTED]@xercesc_2_8@@[EMAIL PROTECTED])
You will need to make sure the setting for treating wchar_t as a
built-in type is consistent.
If you want to change Xerces-C, you need to modify the project files
such that wchar_t is treated as a built-in type. If you want of
modify Xalan-C, you need to modify the project files so is is _not_
treated as a built-in type.
However, this shouldn't be necessary, since the default for Xerces-C
2.8 with VS2005 is to treat wchar_t as a built-in type. Did you
change the project files for some reason?
Yes, I had initially changed the project files but reverted it now.
Getting the same set of errors with the following config :
Xerces-c 2.8 : Treat wchar_t as Built in type = Yes
Xalan-c : Treat wchar_t as Built in type = No
Yes, because the settings are again inconsistent. Why would you think
this would work?
Also, I changed the MsgCreator.mak file to look for xerces-c_2.lib
instead of xerces-c_3.lib.
Are there any other changes required ?
Not that I know of. Any easy way to do this without having to change
all of the Xerces-C link libraries in the Xalan-C project files is to
copy xerces-c_2.lib to xerces-c_3.lib. The name of the DLL is embedded
in the .lib file, so the name of the .lib file is irrelevant.
Dave