[Cmake-commits] CMake branch, master, updated. v3.4.0-rc1-249-g764720c

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

[cmake-developers] [CMake 0015797]: PROPERTY CXX_STANDARD does not work with custom arm-none-eabi-g++

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

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-618-g7c38530

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

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-616-g672069c

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

Re: [CMake] Creating relocatable packages

What you are seeing is the expected behavior. You can get a relocatable package if all your dependencies (in your case libcap) have themselves relocatable package config files with exported targets. Then you package should make use of find_dependency macro. On Fri, Oct 16, 2015 at 4:56 PM, Zac

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-639-gc9224a0

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

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-641-gfc64d57

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

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-643-g7427b77

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

[Cmake-commits] CMake branch, next, updated. v3.4.0-rc1-666-g000a87a

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

[CMake] Known issues with Xcode 6.x and CMake

Are there any known issues with Xcode 6.4 and CMake 3.3.x? I ask because in our project when we generate the Xcode project we end up with 2 or 3 executables listed in the drop down combo box. We also end up with lots of duplicate targets in the Xcode project. And the first time I open an Xcode