|
Hi. Is one allowed to
build a DLL with all the Xalan and Xerces files in it? We have an
application that statically links to the MSVCRT and MFC libraries. All
support DLLs also statically link any MS library they use to avoid having to
redistribute them with the application. Versioning has always been a
problem with these DLLs so to avoid the problems completely we just
statically link them in. Unfortunately, statically linking MSVCRT to the
Xalan and Xerces DLLs separately does not work because the two share heap
pointers when working together. So the only solution is to package them in
the same DLL. I already have a VC6 project that packages the Xalan and
Xerces files into one DLL and that also statically links the MSVCRT
library. I just want to know if there are any licensing issues with
regards to doing that. This is the first time we're using Xalan and Xerces
so we're unsure of what we can and can't do with it. If there are other
ways of doing what I what I want to do please let me know too.
Thanks.
|
- Re: Packaging Xalan and Xerces into one DLL Jojo Bangit
- Re: Packaging Xalan and Xerces into one... David N Bertoni/Cambridge/IBM
