[Cmake] Default output name for DLL
Bill Hoffman
bill.hoffman at kitware.com
Thu Jan 17 08:03:19 EST 2002
I am not sure what is going on here...
We use ADD_LIBRARY(something SHARED something_sources) in many places including
the test case for cmake, and it has never generated a .exe file. (the tests would
fail.)
Perhaps you could run with an older version of cmake and the newer one, and
do a diff on the dsp files.
-Bill
At 11:12 AM 1/17/2002 +0000, Geoffrey Cross wrote:
>I just did a cvs update, and have now got a whole range of little
>problems, the most puzzling being:
>
>I am building a bunch of dlls, which worked just fine under my previous
>cmake installation (dating back to around the beginning of December).
>The relevant line in my CMakeLists is:
>
>ADD_LIBRARY(something SHARED something_sources)
>
>In order to get the correct entry point, something_sources also needed
>to include a .def file containing just the line:
>
>EXPORTS entry_point_function_name
>
>However, for some unknown reason, this no longer works and I get the
>standard LNK1561 (entry point not defined) error. Finally, I found that
>the .def file now needs to include the library name:
>
>LIBRARY something
>EXPORTS entry_point_function_name
>
>That's solved, but I'm confused as to why this is necessary now, but
>previously it wasn't (it also makes things slightly less pretty, as I
>used to include the same .def file to generate a whole range of DLLS all
>with the same entry point).
>
>More annoying, however, is that for some reason the DLL generated now
>has a .exe extension! If I rename it to *.dll, everything works just
>fine, but why!???!
>
>Geoff.
>
>_______________________________________________
>Cmake mailing list
>Cmake at public.kitware.com
>http://public.kitware.com/mailman/listinfo/cmake
More information about the CMake
mailing list