I'm now trying to statically link to the Xerces lib so that my
application does not require the DLLs.
-- Firstly
It was hard to find the method of compiling Xerces for static
linking. I found a reference in the Release info section dated
2004-11-15 by Alberto saying that a specific build target had been
created. 'build target' unfortunately didn't ring any bells for me -
even though I had built both Debug and Release versions, I've never
needed anything but those standard targets and didn't notice the
extras. There is no other documentation about this.
Can we put a reference on the Build Instructions page almost at the
end of the 'Building Xerces-C++ library (Win VC++), after the
paragraph about DLL which begins "You must make sure that you are
linking your application .."?
I suggest:
"To statically link your application you will first need to build the
StaticDebug and StaticRelease targets provided in the Xerces
configuration manager. You should then link with the xerces-
c_static_2.lib library in the static path of the directory."
Whilst we're changing that, can we also add:
"When linking to Xerces, you will need the project properties > C/C++
> Language > Treat wchar_t as Built-in Type set to No."
-- Secondly
If the user simply selects these configurations, the build will fail
with errors when building the 'all' project. (I couldn't find a
separate project to just build XercesLib.) Most of the included
samples fail with static linking. I solved this by using the
configuration manager to only compile the XercesLib and to omit all
of the other projects for the static version.
Should the Configuration be distributed in the way that I simplified
it, or is there some other error?
D ^ D Andrew E Wilson
< A > AV technology consultant (UK)
D v D Tel +44 7710 727636, or +44 1753 885549
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
