I did this before no problem, but for some reason when I complile my
project as a .dll the output (in the debug directory) is only the .dll
file and there is no corresponding .lib

Everything on msdn claims that the compiler will generate this lib for
you, but does not explain where the settings are to look at if it does
not generate this lib.

My executable needs this lib in order to use the .dll (implicit
linking)

Any ideas on what settings to look at?

Re: compiling a dependancy .dll, where did the import library go? by David

David
Sat Oct 21 03:00:03 CDT 2006

>I did this before no problem, but for some reason when I complile my
>project as a .dll the output (in the debug directory) is only the .dll
>file and there is no corresponding .lib

Have you exported anything from the DLL yet? I seem to remember that
there is no lib file produced if nothing is exported.

Dave

Re: compiling a dependancy .dll, where did the import library go? by Bruno

Bruno
Sat Oct 21 08:59:27 CDT 2006

> >I did this before no problem, but for some reason when I complile my
>>project as a .dll the output (in the debug directory) is only the .dll
>>file and there is no corresponding .lib
>
> Have you exported anything from the DLL yet? I seem to remember that
> there is no lib file produced if nothing is exported.

Correct.
This typically happens to me when the declaration of the exported functions
is not a 100% match to the function definition, or if I forget to include
the header with the function declarations in the cpp file that contains the
definition of those functions.

Since DLL exports are often top level functions, there will be no compiler
error, but the compiler will also not know that those functions are for
export.

--

Kind regards,
Bruno van Dooren
bruno_nos_pam_van_dooren@hotmail.com
Remove only "_nos_pam"



Re: compiling a dependancy .dll, where did the import library go? by Alex

Alex
Sun Oct 22 06:51:27 CDT 2006

cpisz@austin.rr.com wrote:
> I did this before no problem, but for some reason when I complile my
> project as a .dll the output (in the debug directory) is only the .dll
> file and there is no corresponding .lib
>
> Everything on msdn claims that the compiler will generate this lib for
> you, but does not explain where the settings are to look at if it does
> not generate this lib.
>
> My executable needs this lib in order to use the .dll (implicit
> linking)
>
> Any ideas on what settings to look at?

In addition to other suggestions, check that the project
doesn't contain .EXP file. If .EXP file is used in the
build, then linker doesn't generate import library, too.


HTH
Alex