Based on my experience (including reading this list for years), what you've done is no sin. I've used Xerces 1.2 and 2.0 as static libraries on Win32 systems for ages. In addition to the changes you've made, I opted to always use the in-memory message loader. I haven't run into any problems, though my app uses Xerces in fairly simple ways.
> -----Original Message----- > From: Maksim Likharev [mailto:[EMAIL PROTECTED] > Sent: Friday, August 29, 2003 4:07 PM > To: [EMAIL PROTECTED] > Subject: RE: xerces 2.3.0 Win32 static library, possible? > > > OK, > here what I did, ( VC 7.0 ) > 1. New configurations, as Static Library, based on existing > Release/Debug > 2. new define STATIC_LIB in order to switch off all those > #define PLATFORM_EXPORT __declspec(dllexport) > #define PLATFORM_IMPORT __declspec(dllimport) > in VCPPDefs.hpp > basicaly: > > #if !defined(STATIC_LIB) > #define PLATFORM_EXPORT __declspec(dllexport) > #define PLATFORM_IMPORT __declspec(dllimport) > #else > #define PLATFORM_EXPORT > #define PLATFORM_IMPORT > #endif > > As an addition, I checked for any Windows DLL attach/detach depended > code found none, > and I assume that's fairly safe to use Static Lib. > > Again this is only Windows, MS VC 7.0 ( I suppose 6.0 as well ), > do not have any recommendations about other platforms. > > But still I would like to hear something from Core Team, > is it complete sin what I did or ... > > Thanks. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
