The .lib is just an import library. Linking is a static operation that can't
be performed against a dynamic object (like a Dynamic Link Library), so when
you want to use a DLL, you have to link against an import library.
This is basic Windows programming stuff. You have to do the same thing if
you want to use, say, Winsock. MSVC hides a lot of this stuff by including
link directives in the object files it generates, but whether you know it or
not, you're linking against all kinds of import libraries.
If you want to know more, get a copy of any edition of Petzold, or look for
"import library" on MSDN.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 02, 2001 11: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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
