I did wonder about that symbol actually... it makes sense and I would have used that feature as we are damn simple folk here...
Why did you need the 'define' though? John Clayton -----Original Message----- From: Dean Roddey [mailto:[EMAIL PROTECTED]] Sent: 19 November 2001 05:44 To: [EMAIL PROTECTED] Subject: Re: Xerces as static Win32 Library SINGLEDLL is there because in theory you can build the system as a set of DLLs and only use the ones that you want. I intended it to be that way in general, and always did my development in that mode, but it was designed to make it one DLL for simplicity. So the SINGLEDLL thing was introduced to tweak the PROJ_XXX values to make them all think that they are part of a single DLL. It would be very nice to keep the ability to build as separate DLLs, the SINGLE/MULTIPLE DLL stuff should be maintained separately. However, somewhere along the line, because I was the only one doing it, the clean layering of the system was broken and you probably can't even really do it anymore, which is unfortunately for folks who want minimal overhead and are only using certain things like SAX and not DOM. -------------------------- Dean Roddey The Charmed Quark Controller Charmed Quark Software [EMAIL PROTECTED] http://www.charmedquark.com "If it don't have a control port, don't buy it!" ----- Original Message ----- From: "Jaco Greeff" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, November 18, 2001 9:37 PM Subject: Re: Xerces as static Win32 Library > This works perfectly for creating a static library on the Win32 > platform. I second the motion to get this included in the main > distrobution ;) > > Greetings, > Jaco > > [EMAIL PROTECTED] wrote: > > > Funny, I need EXACTLY the same thing! > > > > 1. I created a XercesStaticLib project and copied contents from the > > XercesLib into it, reset the default project options to match XercesLib (but > > instruction set is blend *, Multithreaded DLL, no RTTI, no precomp headers). > > > > 2. Then I rebuilt all my libraries and found lots and lots of warnings about > > importing AND exporting symbols in the same compilation, so I changed > > VCPPDefs.hpp a little, the only change I made is to conditionally define the > > exports - ala: > > // > > -------------------------------------------------------------------------- - > > // A define in the build for each project is also used to control whether > > // the export keyword is from the project's viewpoint or the client's. > > // These defines provide the platform specific keywords that they need > > // to do this. > > // > > -------------------------------------------------------------------------- - > > #ifdef XML_SINGLEDLL > > #define PLATFORM_EXPORT __declspec(dllexport) > > #define PLATFORM_IMPORT __declspec(dllimport) > > #else > > // don't bother, assume that without the XML_SINGLEDLL we are building a > > static library > > // and therefore don't want to export symbols (esp. when VC++ complains > > bitterly about > > // havnig imports AND exports if you don't bother losing these > > __declspec()'s) > > #define PLATFORM_EXPORT > > #define PLATFORM_IMPORT > > #endif > > > > I noticed that the XML_SINGLEDLL #define isnt used anywhere else, so thought > > 'heck, why not - lets use that instead of inventing my own!' > > > > 3. Recompiled everything again and ran my project test harnesses - things > > appear to work OK, and I've thrown away my DLL version (shameless plug: ya > > gotta love xtreme programming sometimes)! > > > > Attached is the project, feel free to use. > > > > LIST OWNERS / MODERATOR / SOMEONE: > > Can we add this project and the VCPPDefs.hpp to the distro please (after > > review no doubt)?? > > > > Regards > > John Clayton. > > > > -----Original Message----- > > From: Jaco Greeff [mailto:[EMAIL PROTECTED]] > > Sent: 15 November 2001 05:52 > > To: [EMAIL PROTECTED] > > Subject: Xerces as static Win32 Library > > > > > > Hi, > > > > I've done a bit of searching on the mail archives and couldn't come up > > with a full answer on this one: it is possible to build Xerces as a > > static library so we don't need to distribute the xerces dll along with > > the program? If so, how? > > > > Our full application is componentised and allows for automatic software > > updates. As one of the components, we provide a very light high-level > > wrapper of the Xercer parser and would like this full DLL to actually > > include a static version of Xerces to make our version control a bit better. > > > > Thanks for all replies, > > Jaco > > > > > > ------------------------------------------------------------------------ > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > -- > And there were all the stars, looking remarkably like powered diamonds > spilled on black velvet, the stars that lured and ultimately called the > boldest towards them... > (Colour of Magic) > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ------------------------------------------------------------------------ For more information about Barclays Capital, please visit our web site at http://www.barcap.com. Internet communications are not secure and therefore the Barclays Group does not accept legal responsibility for the contents of this message. Although the Barclays Group operates anti-virus programmes, it does not accept responsibility for any damage whatsoever that is caused by viruses being passed. Any views or opinions presented are solely those of the author and do not necessarily represent those of the Barclays Group. Replies to this email may be monitored by the Barclays Group for operational or business reasons. ------------------------------------------------------------------------ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
