[CMake] dependency in custom command?

King, Steven R steven.r.king at intel.com
Fri Aug 28 16:59:53 EDT 2009


> You don't have to do the copying yourself. Just tell CMake in which
> directory it should create the module by either setting the
> LIBRARY_OUTPUT_DIRECTORY target property or the
> CMAKE_LIBRARY_OUTPUT_DIRECTORY variable.
> 
> AFAIK the LOCATION property is only present for compatibility with
> CMake 2.4, and shouldn't be used in new code.

Hi Mike -- I don't know from which directory my module test will run when using ctest.  So, my test program does not have an easy way to know the relative path to LIBRARY_OUTPUT_DIRECTORY when making the dlopen() call.  Allowing my test program to assume the dll is in its local directory seemed to be the easiest solution.


More information about the CMake mailing list