[cmake-developers] [CMake 0015802]: CMake crashes in creating build files for JsonCpp

The following issue has been SUBMITTED. == http://public.kitware.com/Bug/view.php?id=15802 == Reported By:Lukas Pioch Assigned To:

[cmake-developers] [CMake 0015804]: FindPkgConfig pkg_check_modules command should return full path to shared libraries in _LIBRARIES variable

The following issue has been SUBMITTED. == https://cmake.org/Bug/view.php?id=15804 == Reported By:Sam Thursfield Assigned To:

Re: [CMake] Creating relocatable packages

Yes, that was exactly what I needed. Now my installed targets file has IMPORTED_LINK_INTERFACE_LIBRARIES "PCAP" instead of an absolute path, and the FindPCAP.cmake module kicks in and does what I would expect. Thanks again for your time - much appreciated. Zac On Tue, Oct 20, 2015 at 9:25 AM,

[CMake] CMake string REGEX REPLACE and environment variables

Hi all, Does anybody know why I can't evaluate environment variable inside "REGEX REPLACE"? Example, I have a value: set(value "LD_LIBRARY_PATH=my_path:$LD_LIBRARY_PATH") I expect: value = "LD_LIBRARY_PATH=my_path:some_system_path_from_env" What I'm doing: string(REGEX REPLACE

Re: [CMake] Creating relocatable packages

I think I'm on the right track now. I was definitely missing the add_library(PCAP IMPORTED) section. Could you elaborate on the last part? I thought target_link_libraries() is the reason I'm getting absolute paths. Should I be using the FindDependency macro instead of target_link_libraries()?

Re: [CMake] CMake string REGEX REPLACE and environment variables

On 10/20/2015 01:49 PM, Oleg Trenkin wrote: Hi all, Does anybody know why I can't evaluate environment variable inside "REGEX REPLACE"? Example, I have a value: set(value "LD_LIBRARY_PATH=my_path:$LD_LIBRARY_PATH") I expect: value = "LD_LIBRARY_PATH=my_path:some_system_path_from_env" What

[cmake-developers] [CMake 0015803]: FindCUDA.cmake should propagate value of COMPILE_PDB_OUTPUT_DIRECTORY{_CONFIG} to NVCC

The following issue has been SUBMITTED. == https://cmake.org/Bug/view.php?id=15803 == Reported By:tomwar Assigned To:

[Cmake-commits] CMake branch, master, updated. v3.4.0-rc1-303-g9afbb73

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 9afbb733ec2a55424e6c25c6afa7fdd14219d6b1 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-727-gb440006

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, next has been updated via b440006bcad4df6916b90b7505352cc866bf8b96 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.4.0-rc1-261-g1fcc01f

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 1fcc01f2074cc5fd56489ccab90457b51082e10e (commit) via

Re: [cmake-developers] Filesystem timestamp checks

On Tue, Oct 20, 2015 at 04:56:47 +0600, Ruslan Baratov via cmake-developers wrote: > * I don't want to patch every script. To be precise I prefer to "Fix > something in one place so it works 100% and forget about it" then "Every > time I start creating script I should remember that..." The

[Cmake-commits] CMake branch, master, updated. v3.4.0-rc1-266-g5ec8064

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 5ec8064b76aca89b6e0274e53c272f298655b992 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.4.0-rc1-259-gfca389e

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 fca389e78ca8d5fe377a4116dedf8b9307126380 (commit) via

Re: [CMake] linking hared libraries

> > On Mon, Oct 19, 2015 at 8:43 PM, Owen Alanzo Hogarth > wrote: > > Also you said the PROJECT() should only be defined once, but shouldn't > each > > cmakelists.txt contain a project() or else cmake complains at me. > > > According to the last paragraph of: > >

Re: [CMake] cmake_check_build_system is causing a rebuild at "make install"

The cpp file dependency is generator specific. CMake supports cpp file dependency for Makefiles only. The solution we have works for any generator. The dependencies could be generated at configure time, and I have a local version used internally where I work that does this, but it's not a

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-725-g1fe5b92

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, next has been updated via 1fe5b927e070f42067487b7dd0c3cac720d879bf (commit) via

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-719-g846d838

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, next has been updated via 846d838c55836073bb97d4589a20885af9328079 (commit) via

Re: [cmake-developers] Filesystem timestamp checks

On 21-Oct-15 03:25, Ben Boeckel wrote: On Wed, Oct 21, 2015 at 01:53:42 +0600, Ruslan Baratov wrote: On 20-Oct-15 21:42, Ben Boeckel wrote: On Tue, Oct 20, 2015 at 04:56:47 +0600, Ruslan Baratov via cmake-developers wrote: * I don't want to patch every script. To be precise I prefer to "Fix

Re: [cmake-developers] Filesystem timestamp checks

On 20-Oct-15 21:42, Ben Boeckel wrote: On Tue, Oct 20, 2015 at 04:56:47 +0600, Ruslan Baratov via cmake-developers wrote: * I don't want to patch every script. To be precise I prefer to "Fix something in one place so it works 100% and forget about it" then "Every time I start creating script I

[cmake-developers] [CMake 0015805]: pkg_get_variable from FindPkgConfig should honour search path from CMAKE_PREFIX_PATH

The following issue has been SUBMITTED. == https://cmake.org/Bug/view.php?id=15805 == Reported By:Sam Thursfield Assigned To:

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-733-g03c0c9c

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, next has been updated via 03c0c9cc4098108010dc115bbdde4158fe423a40 (commit) via

[cmake-developers] [Patch] Documentation file(GLOB): ordering note

Add a note that order of files is not defined >From 9cd9fbb12ef73b72526190573cba0392ead5fd9f Mon Sep 17 00:00:00 2001 From: Ruslan Baratov Date: Wed, 21 Oct 2015 02:53:37 +0600 Subject: [PATCH] Documentation: file(GLOB*) order is not guaranteed Since this command use

Re: [cmake-developers] Filesystem timestamp checks

On Wed, Oct 21, 2015 at 01:53:42 +0600, Ruslan Baratov wrote: > On 20-Oct-15 21:42, Ben Boeckel wrote: > > On Tue, Oct 20, 2015 at 04:56:47 +0600, Ruslan Baratov via cmake-developers > > wrote: > >> * I don't want to patch every script. To be precise I prefer to "Fix > >> something in one place

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-735-gc8286a5

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, next has been updated via c8286a5ff5e2c7843a0ee33376dd3b0032317d48 (commit) via

[cmake-developers] [CMake 0015806]: The Xcode generator consumes all arguments beginning with "-g"

The following issue has been SUBMITTED. == https://cmake.org/Bug/view.php?id=15806 == Reported By:Ching Ping Sun Assigned To:

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-765-g9407f97

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, next has been updated via 9407f9732a9c7b32b5689094cbd29a3a74a0d6a5 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-767-gd06f93a

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, next has been updated via d06f93ac425f3fc61720fb2752111457e4b56431 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-743-ga3de829

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, next has been updated via a3de829edbb478a949ae9877e6a1541657869305 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-747-g657b36f

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, next has been updated via 657b36f08e5329c2fdcd6f299685796dc8abfbd0 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-753-g7fcccb9

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, next has been updated via 7fcccb9f7b854319c23febac9c9280c271e8740c (commit) via

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-776-gedb7311

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, next has been updated via edb731113d63696ae691dfca207c2155129ff27c (commit) via

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-741-g1bc5bbf

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, next has been updated via 1bc5bbf165a5d818d9589d5b6599727af47afaa3 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-780-g2fc8bee

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, next has been updated via 2fc8bee548c8d15d34ae9357523e0d5423026c03 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-778-ga174f7e

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, next has been updated via a174f7e14b464be73a4282f9d1ade942f1476b5c (commit) via

[Cmake-commits] CMake branch, master, updated. v3.4.0-rc1-304-g893a7fc

_VERSION_MINOR 4) -set(CMake_VERSION_PATCH 20151020) +set(CMake_VERSION_PATCH 20151021) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

Re: [CMake] Creating relocatable packages

Hi Zac, target_link_libraries will work with either full library paths or target names including imported targets. You need to use target_link_libraries in your CMakeLists.txt and find_dependency in your PackageConfig.cmake. Like so: in CMakeLists.txt: target_link_libraries(mylib