Re: Statically linking Xerces

2004-10-30 Thread Matt Garman
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

Re: Statically linking Xerces

2004-10-26 Thread Hua-Ying Ling
On Tue, 26 Oct 2004 15:29:20 -0400, Jesse Pelton <[EMAIL PROTECTED]> wrote: > Unless you've built a static library, you'll need the DLL at runtime. > It sounds like the library you're linking against is an import library, > which is just a collection of stub routines, not the actual Xerces code. Th

RE: Statically linking Xerces

2004-10-26 Thread Jesse Pelton
Unless you've built a static library, you'll need the DLL at runtime. It sounds like the library you're linking against is an import library, which is just a collection of stub routines, not the actual Xerces code. I think the process of building a static library for Windows has been discussed bef