Re: [CMake] Inconsistency with INSTALL(TARGETS) destinations...

2015-03-11 Thread Rolf Eike Beer
Am Dienstag, 10. März 2015, 17:48:48 schrieb J Decker: 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

Re: [CMake] Inconsistency with INSTALL(TARGETS) destinations...

2015-03-11 Thread Petr Kmoch
Do you even *have* any LIBRARY targets on Windows? Quoting the docs ( http://www.cmake.org/cmake/help/v3.2/command/install.html#installing-targets ): Static libraries are always treated as ARCHIVE targets. Module libraries are always treated as LIBRARY targets. For non-DLL platforms shared

Re: [CMake] Inconsistency with INSTALL(TARGETS) destinations...

2015-03-10 Thread J Decker
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(

[CMake] Inconsistency with INSTALL(TARGETS) destinations...

2015-03-10 Thread J Decker
I recently added cmakelists to a library that didn't support cmake. It started with a simple make system, and was easy to create and use simple cmake support. I was building using visual studio, and this was my install command install( TARGETS MatrixSSL LIBRARY DESTINATION bin

Re: [CMake] Inconsistency with INSTALL(TARGETS) destinations...

2015-03-10 Thread Hendrik Sattler
Am 10. März 2015 23:33:41 MEZ, schrieb J Decker d3c...@gmail.com: I recently added cmakelists to a library that didn't support cmake. It started with a simple make system, and was easy to create and use simple cmake support. I was building using visual studio, and this was my install command