Re: Static xerces lib on Win32

Nevermind the following question---major bonehead mistake on my part! Thanks again to everyone who has helped me! I appreciate it! Matt On Mon, Nov 01, 2004 at 02:30:29PM -0600, Matt Garman wrote: > On Mon, Nov 01, 2004 at 02:31:08PM +0100, Alberto Massari wrote: > > Hi Matt, >

Re: Static xerces lib on Win32

rary I built, but rather has something to do with the way I am building the release version of my application. Any thoughts, suggestions or ideas? Thanks again! Matt -- Matt Garman email at: http://raw-sewage.net/index.php?file=email

Re: Static xerces lib on Win32 - sorry!

Sorry for posting this so many times. I sent this email several days ago, and when it didn't show up on the list right away, I re-sent it several times over. My apologies, Matt On Tue, Oct 26, 2004 at 01:05:27PM -0700, Matt Garman wrote: > I'm trying to link in a static xerces lib

Re: Statically linking Xerces

On Win32, has anyone seen the following kinds of linking errors when trying to link in their static Xerces 2.6.0 library? XercesLib_d.lib(Win32PlatformUtils.obj) : error LNK2005: "void * __cdecl operator new(unsigned int)" ([EMAIL PROTECTED]@Z) already defined in libcpd.lib(newop.obj) XercesLib_d

Static xerces lib on Win32

Hello! I'm trying to link in a static xerces library on Win32 under MS Visual Studio 7.1. I downloaded and unzipped the 2.6.0 source. I changed the build type to static library (in the xerces project settings). I also went into the VCPPDefs.hpp and redefined PLATFORM_EXPORT and PLATFORM_IMPORT

Static xerces lib on Win32

Hello! I'm trying to link in a static xerces library on Win32 under MS Visual Studio 7.1. I downloaded and unzipped the 2.6.0 source. I changed the build type to static library (in the xerces project settings). I also went into the VCPPDefs.hpp and redefined PLATFORM_EXPORT and PLATFORM_IMPORT

specifying a "schema path"?

program config directory (e.g. /etc/my_app/config.xsd, /etc/my_app/data.xsd). Now keep in mind that different people will inevitably install my application in different locations (e.g. /usr versus /usr/local). So how can I specify (perhaps a build time) the paths that should be checked for schemas?

Re: DOMImplementation::createDocument() causing seg fault

t most of the main() function (the part that does the "real work", i.e. actually creates the DOMDocument) is nested in an inner block. Why is this? I did that in my code as well, although the result was no different (still seg faults). Thanks again, Matt -- Matt Garman email at

DOMImplementation::createDocument() causing seg fault

propolice-3.3-7) I'll gladly post my function if anyone would like to see it (but, it's virtually identical to the main() in CreateDOMDocument.cpp). Short of building a debug version of Xerces-C and stepping through createDocument(), does anyone have any ideas what might be causing the cras

xerces "style"???

. Any thoughts here? Is there any existing code that might give me some good ideas on how to best structure my program? E.g., some example programs that are a little more substantial than those distributed with xerces-c? Thanks! Matt -- Matt Garman email at: http://