>
>
> And it's mostly wrong, e.g. lib64 is not correct for many systems. If you
> want Unix like subdirectories, use the GnuIntallDirs module.
>
>
Better?
if( WIN32 )
install( TARGETS MatrixSSL RUNTIME DESTINATION bin LIBRARY DESTINATION
bin ARCHIVE DESTINATION lib )
else( WIN32 )
include( GNUInstallDirs )
install( TARGETS MatrixSSL DESTINATION ${CMAKE_INSTALL_LIBDIR ) )
endif( WIN32 )
On Linux; .so and .a go into LIBDIR and executable into BINDIR
on windows I have executable (BINDIR/RUNTIME) and I have .lib that are
(.a) that are static libraries which would be ARCHIVE; but I have interface
libraries (.exp, .dll link libraries which on some compilers are optional,
since the .dll itself contains enough information) which I wold think would
be LIBRARY ( something different than ARCHIVE?) ...
It seems some generators treat LIBRARY for add_library(SHARED) output and
some need RUNTIME... and all use ARCHIVE for export and static library
targets.
in the case of add_executable it's possible that also generates a export
library; would that be LIBRARY DESTINATION? or ARCHIVE?
> HS
>
>
>
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
