[CMake] Shared library OutputFile path for Visual Studio

Philip Lowman philip at yhbt.com
Sat Sep 29 00:03:32 EDT 2007


Neal Meyer wrote:
> Is there any particular reasoning why for a shared library project the
> .dll file is created in the LibraryOutputPath rather then the
> ExecutableOutputPath.  The Import library(.lib) should be placed in
> the LibraryOutputPath, but it doesn't make any sense for the .dll to
> be placed there as well.
> 
> I end up having to copy the .dll output with a post-build step, which
> works but is complete a waste of time and just makes the cmake file
> more complex for what seems like a very simple case.

Here Here!

I've had to add custom post-build rules for this issue before too. 
Other users I know of in the OSG project have resorted to trickery with 
the PREFIX target option to try to work around this problem.

I've filed this as bug #5805 (feature request) in the bugtracker.

Implementing this modification for the Visual Studio generators is 
trivial (I did it two weeks ago by coincidence when I came across this 
issue yet again).  I had a look at the Makefile and Makefile generators 
that same day though and nearly had a stroke :).  Provided someone could 
give me some pointers as to where to start I probably could add the 
support for this.


More information about the CMake mailing list