[Cmake-commits] CMake branch, master, updated. v3.11.1-616-g52ae29e

VERSION_MINOR 11) -set(CMake_VERSION_PATCH 20180425) +set(CMake_VERSION_PATCH 20180426) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

[cmake-developers] target_link_libraries not callable from other directory scopes

Hi, this nice post (https://crascit.com/2016/01/31/enhanced-source-file-handling-with-target_sources/) mentions some modern usage of target_sources(), but also shows some discrepancy between target_link_libraries and the remaining target_* functions. In particlar, CMake does not allow

Re: [CMake] swig module add -fPIC flag

swig modules created with command SWIG_ADD_LIBRARY are "standard" CMake targets so, same approach apply. >From convenience, you can use command SWIG_LINK_LIBRARIES (same semantic as >TARGET_LINK_LIBRARIES) to manage custom link flags. Now, regarding specifically flag -fPIC you can manage

[CMake] swig module add -fPIC flag

Hi, I have not found how to add -fPIC link flag to a SWIG module. Regards S.Ancelot -- 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

[Cmake-commits] CMake branch, master, updated. v3.11.1-615-g83e3b14

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via 83e3b1497d4889f8dbb7238a270296377035e40b (commit) via

[Cmake-commits] CMake branch, release, updated. v3.11.1-7-gdc3401d

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, release has been updated via dc3401d5b08ea0c116fd5416c4d7eb5fe22e5835 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.11.1-604-ge5d1584

This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "CMake". The branch, master has been updated via e5d15848ca6cdc52ff44edcde7689518793a5eb6 (commit) via

Re: [CMake] [CMAKE] make package works but ninja package does not

The only difference is about the usage of preinstall target. The Ninja generator does not use it, and it should because it need to build sqlcipher before packaging it... the interesting part of vimdiff of cpack --trace : *Unix Makefiles | Ninja*

[CMake] [CMAKE] make package works but ninja package does not

Hello folks, I ran into an issue today and I think it is an unexpected behaviour. I have a CMake project that build an external project (autotools) and pack it into a .deb. It works when I use the Makefile generator (cmake /my/path) but it does not when I use the Ninja generator (cmake -G Ninja