Hi Matt,
if you download the latest code base (for version 2.7) you can use
the solution file for Visual Studio .NET 2003 to build a static library.
If you have to stick with version 2.5, you can search the archives
for the instructions to build static libraries on Windows.
Alberto
At 15.02 22/08/2005 -0500, Matt England wrote:
Hello,
(My apologies in advance for a FAQ; after working with Xerces for
months, my developers don't have an answer for this, so I thought
I'd ask; don't see an immediate answer on the website, either.)
I manage a cross-platform C++ development project that uses Xerces
(and many other tools like MinGW, Boost, ACE, Qt, etc). Amongst all
these tools, Xerces is the one library for which we have yet to
figure out how to eliminate as an external library file. We have to
continually include a xerces-c_2_5_0.dll file in our binary distributions.
How can we avoid this in the future?
Will Xerces support a static-library link (such that the Xerces
module becomes embedded in our executable(s))?
If a static link, I'm concerned about the resulting size of the
executable, for the xerces-c_2_5_0.dll file is 4.5MB big, while our
project's executable is only 3MB big. Is there a way to static-link
only the portions/modules of the library we need?
Is there any other options besides static linking?
Thanks for any help,
-Matt
