Folks:
I’ve finally got the trunk xalan code building as a static link
library with Xerces 3.0. I’d be more than happy to pass along (for someone else
to checkin) my changes to the vcproj (etc) files (I’ve only done VC8).
I wonder why this isn’t already supported? There didn’t appear to
even be any #defines or anything to control building a static link library.
What I did was pattern (in terms of #defines) the XALAN library
code after what is done in Xerces for static libraries – I defined a constant
XALAN_STATIC_LIBRARY to mimic the behavior of the xerces define
XERCES_STATIC_LIBRARY.
So far – in my very limited testing – Xalan does appear to work
fine as a static link library.
I also cleaned up the vcproj files slightly – to make supporting
additional configurations easier. I’d recommend using the variable
$(Configuration) instead of an explicit ‘Debug’ or ‘Release’ in path names.
Doing that – made it easier to clone ‘Debug’ configuration into ‘Static Debug’.
Also – I had to fix a path-quoting bug in a custom rule file (to support
‘Static Debug’ – like xerces – as opposed to ‘StaticDebug”).
Lewis.
