I have a DLL and I would like to use some of its functions.
#include
using namespace std;
extern \"C\" __declspec(dllimport) int Initializ
From your phrasing it is pretty clear you are using Dev Studio some or other version.
In order to implicitly link against a dll, VC++ needs a .lib file, no questions. Without a .lib you can only explicitly load the dll using LoadLibrary and GetProcAddress.
Fortunately import libraries contain nothing other than the dll's exported symbols, so it is perfectly legitimate to simply create a dll project in VC++ that exports the identical symbols, build it, and then use the resulting .lib file to access the target dll.
The trick really is, getting the symbols right: Depending on how the original dll was created there might be some decoration to deal with.
"Initialize" could be exported from a dll in several ways when viewed with dependencywalker
extern "C" __declspec(dllexport) int __cdecl Initialize(...
extern "C" __declspec(dllexport) int __stdcall Initialize(...
The problem really is the first case - if the calling convention isn't __cdecl (and most dll api's are actually __stdcall - all windows dlls are __stdcall) then you must use a .def file to export the undecorated names.
Under visual studio you can't link directly to DLL, you need import library.
So basically you have several options:
Create import library form dll and link to it. There are some tools coming with MinGW that do the job, they may actually work for you, AFAIK there are also some tools for MSVC.
This can be helpful: http://support.microsoft.com/kb/131313, not tested myself
:-)
A good way would be to reconstruct some header that would declare the functions you want to call. For doing this, you must know/discover their exact signatures.
If you have access to the strings
command (available in cygwin), you might run it against the DLL. It will list the sequences of more than 4 consecutive printable characters terminated by a 0 (observe that it is really easy to implement, in the case where you do not want to install cygwin). Among these "strings", you will have garbage and the function signatures, mangled by the C++ compiler (see: http://en.wikipedia.org/wiki/Name_mangling). You will then have to unmangle the ones you are interested in, using undname.exe
(assuming the DLL was built by Microsoft Visual; see: http://msdn.microsoft.com/en-us/library/5x49w699.aspx)
... You might also want to consider DependencyWalker.