dll hell

[markw at mohawksoft.com (markw at mohawksoft.com)]

Yes, you are right that you need a file, *.lib" to link with to use a
*.dll file.

I believe that the program to create this file is implib (or at least it
was at one time).

The -L option on the linker works like on gcc in that it specifies a
directory in which to look for libraries.

Libraries can just be added at the end of the link line, the linker knows
what they are (you don't use -lfoo as people would with gcc)

DLLs on Windows do not have to begin with lib, i.e. libfoo.so, they would
just be foo.dll.

DLLs are found in the Windows execution path, there is no LD_LIBRARY_PATH
equivalent.

The Windows execution path ALWAYS starts with the current working
directory, so if you execute a program within its directory and the DLL is
present, it will be found regardless of whether or not it is in the "path"
environment.


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.