On Mon, May 23, 2005 at 09:03:40AM -0500, Jeffrey Holle wrote: >The linker not generating an import library indicates that the DLL module >doesn't have any exported symbols. >Is this because you aren't using >__declspec__(dllimport)/__declspec__(dllexport)? > >While you don't have to use an import library (static linking to the >module), I believe one needs to be generated before you can hope to use >the module by dynamically linking to it at runtime. The DLL itself can be used in place of an import library in many cases. That's why I suggested this. This has nothing to do with static linking. >Christopher Faylor wrote: >>On Sun, May 22, 2005 at 07:45:08PM -0700, Matthew Vanderschaaf wrote: >>>I'm in Windows trying to use a DLL with a program. I don't have an >>>import library, and I can't find any information on how to use it >>>without one. Any information that you may provide on this will help. >> >>Just include the full path to the DLL on the link command line.
