[Cmake-commits] CMake branch, master, updated. v3.7.0-rc1-16-gaa57f35

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

Re: [cmake-developers] Is there a way in CMake to get a list of all CTest tests added with add_test?

On Mo, 2016-10-03 at 14:25 -0400, Brad King wrote: > > The list we need would thus be built up to contain all COMMAND > > arguments to add_test that are also build targets in CMake. > > The list would also need to include targets mentioned in generator > expressions such as `$`.  This will almost

[CMake] False positives with CheckFunctionExists and dynamic linking

Hello, My laptop is running on Mac OS 10.11 with the latest Xcode 8 release. This version of Xcode ships the Mac OS 10.12 API/SDKs which includes the clock_gettime function which I check for availability using check_function_exists. Even though clock_gettime doesn’t exist on Mac OS 10.11,

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-67-g280cf7a

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

Re: [cmake-developers] [ANNOUNCE] CMake 3.7.0-rc1 now ready for testing!

Robert Maynard wrote: > * The "CodeLite" generator gained a new "CMAKE_CODELITE_USE_TARGETS" > option to change project creation from projects to targets. Something that I have often noticed (and which causes problems) in my refactoring is that per-directory variable definitions are used when

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-65-gfae02d5

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

[Cmake-commits] CMake branch, next, updated. v3.7.0-rc1-63-g74adf4e

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

[cmake-developers] [ANNOUNCE] CMake 3.7.0-rc1 now ready for testing!

I am proud to announce the first CMake 3.7 release candidate. https://cmake.org/download/ Documentation is available at: https://cmake.org/cmake/help/v3.7 Release notes appear below and are also published at https://cmake.org/cmake/help/v3.7/release/3.7.html Some of the more significant

[CMake] [ANNOUNCE] CMake 3.7.0-rc1 now ready for testing!

I am proud to announce the first CMake 3.7 release candidate. https://cmake.org/download/ Documentation is available at: https://cmake.org/cmake/help/v3.7 Release notes appear below and are also published at https://cmake.org/cmake/help/v3.7/release/3.7.html Some of the more significant

[Cmake-commits] CMake annotated tag, v3.7.0-rc1, created. v3.7.0-rc1

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 annotated tag, v3.7.0-rc1 has been created at 4d730d27aa8695ec3ce3608b3f6fefb5685635fb (tag) tagging

[Cmake-commits] CMake branch, next, updated. v3.6.2-1337-g1d6b62a

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

[Cmake-commits] CMake branch, master, updated. v3.6.2-1317-g38642f4

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

[Cmake-commits] CMake branch, next, updated. v3.6.2-1332-g21e9e41

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

[Cmake-commits] CMake branch, master, updated. v3.6.2-1312-g9203691

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

[Cmake-commits] CMake branch, next, updated. v3.6.2-1329-g5fc1dba

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

Re: [cmake-developers] Is there a way in CMake to get a list of all CTest tests added with add_test?

On Mon, Oct 3, 2016 at 2:25 PM, Brad King wrote: > On 10/03/2016 12:14 PM, Clifford Yapp wrote: >> so what we need is not actually the test names themselves, >> but a list of the executables used to run tests that are also defined >> as build targets. > [snip] >> The list

[Cmake-commits] CMake branch, next, updated. v3.6.2-1327-g25ea96c

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

[Cmake-commits] CMake branch, next, updated. v3.6.2-1325-g1db6826

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

[Cmake-commits] CMake branch, next, updated. v3.6.2-1323-g0f847e7

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

[Cmake-commits] CMake branch, next, updated. v3.6.2-1318-gae55ba6

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

[Cmake-commits] CMake branch, next, updated. v3.6.2-1321-g9f041e9

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

[Cmake-commits] CMake branch, master, updated. v3.6.2-1309-g834efe1

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

[CMake] RPATH handling differences

Can anyone confirm whether invoking cpack directly rather than "cmake --build . --target package" would still give the same RPATH handling? Specifically, the install/packaging step rewrites the rpaths in at least some cases (e.g. see the docs for CMAKE_BUILD_WITH_INSTALL_RPATH) and I'm wanting to