The .lib, in this case, is not a "standard" static library, but an import
library.
Import libraries contain information about exports in other programs (in
this case, the Xerces DLL). The Xerces DLL exports numerous classes that
your application imports... This is pretty typical of Windows DLLs. Check
out what MSDN has to say about import libraries.
Of course, you don't have to include the .lib file with your shipping
application...
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 02, 2001 10:50 AM
To: [EMAIL PROTECTED]
Subject: why include both dll and lib
Xerces C++ version number : 1_5_1
Platform : x86
Operating system and version number : win2k
Compiler and version number : VC6 with latest service pack
The XML document (or excerpt) that failed : N/A
The C++ application code that failed : N/A
Whether you built the Xerces C++ library yourself or used the binary
distribution : distribution
What happened :
we are doing a project using your xml parser, but we are finding it strange
to have to include the library for compilation, and we also have to
distribute your DLL in order to make the app run. It doesn�t make much
sense to statically link the library and also provide the dynamic link
library... are we missing something??
thank you for your help...
regards
neville
Don't just surf the Web ...di-ve right in!
Get the latest on the Maltese Islands at http://www.di-ve.com
---------------------------------------------------------------------
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]
