Re: [CMake] Transitive include and link libraries on imported targets ?

target_link_libraries(B INTERFACE A) Regards, Dvir From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of David Jobet Sent: Wednesday, April 5, 2017 18:34 To: cmake@cmake.org Subject: [CMake] Transitive include and link libraries on imported targets ? Hello, Let's say I build some external

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc4-695-g8844af8

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 discards b3aaf1b55addfb1b8593f02df83f1fa6f604f141 (commit) discards

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc4-688-g5d4db33

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 5d4db33e7011e7aa3ada95c1aafb51f2f15d6ec5 (commit) from

[Cmake-commits] CMake branch, nightly-master, updated. v3.8.0-rc4-687-g333ff16

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, nightly-master has been updated via 333ff168eb04e12d5d118a2e9cf50d600c508db5 (commit) via

[Cmake-commits] CMake branch, nightly, updated. v3.8.0-rc4-694-gb3aaf1b

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, nightly has been updated discards dd98e44d61770bf483e7fc4d24aa99f50baa6d1c (commit) discards

Re: [CMake] cmake -E remove -f

Yes, but in both cases the directory foo is still not deleted! At least on OSX any way. On Thu, Apr 6, 2017 at 9:22 AM, Mark Ferry wrote: > Hi Craig > > On Thu, 06 Apr 2017 08:55:58 +1000, Craig Scott wrote: > > Can anyone identify a scenario where the -f option to the

Re: [CMake] cmake -E remove -f

Hi Craig On Thu, 06 Apr 2017 08:55:58 +1000, Craig Scott wrote: > Can anyone identify a scenario where the -f option to the CMake command > mode's "remove" command makes any difference? > How about removing directories: ~/src/cmake-test$ cmake --version cmake version 3.0.2 CMake suite

[CMake] cmake -E remove -f

Can anyone identify a scenario where the -f option to the CMake command mode's "remove" command makes any difference? Testing a range of possibilities has so far yielded no difference for the cases I can think of. The documentation simply says "use -f to force it", which doesn't explain when such

[CMake] Is it possible to detecting if -C was used, and if so which file was passed?

Hi Everyone, I have a simple quandary — I was wondering if -C was used when cmake is run — is it possible to find the name of this file via any cmake state? Thanks! -Cyrus -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at:

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc4-694-gb3aaf1b

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

Re: [CMake] get complete list of compile definitions

Am 04/04/2017 um 11:17 schrieb Magnus Therning: Robert Schwarzelt writes: Hi all, I need to implement a code export function, that will only export code used in a specific project configuration. For this purpose I want to use unifdef (http://dotat.at/prog/unifdef/),

[CMake] Transitive include and link libraries on imported targets ?

Hello, Let's say I build some external libs A and B with B depending on A. B and A do not use cmake, so I build them and install them in a 3rdparty directory. I now have access to includes and libs. I then create some cmake file to describe those libs so I can use them in my project :

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc4-687-g333ff16

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 discards 988dc63683e046fd68ea6915036cc61f94fc8acf (commit) discards

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc4-689-g764b7ec

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 discards 02854fb634fbc1f2401f22d2fbfd00519308423e (commit) discards

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc4-690-g988dc63

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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc4-692-g02854fb

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

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc4-687-g333ff16

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

[Cmake-commits] CMake branch, master, updated. v3.8.0-rc4-685-gd9bd7ad

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

[Cmake-commits] CMake branch, next, updated. v3.8.0-rc4-685-gd9bd7ad

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 discards b5852b59d116886f7fc827f2df097da01f720df7 (commit) discards