[cmake-developers] [ANNOUNCE] CMake 3.9.0-rc5 is ready for testing

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

Re: [cmake-developers] 3.9.0-rc3: CMAKE_ANDROID_NDK_DEPRECATED_HEADERS doesn't work outside of toolchain

On 06/27/2017 11:36 AM, Robert Dailey wrote: > Ok maybe I'm misunderstanding the design intent for toolchain files. Originally they were intended to contain information local to the machine, like `set(CMAKE_ANDROID_NDK /path/on/my/machine/to/ndk)`. In controlled environments that share many

Re: [cmake-developers] 3.9.0-rc3: CMAKE_ANDROID_NDK_DEPRECATED_HEADERS doesn't work outside of toolchain

On Tue, Jun 27, 2017 at 10:22 AM, Brad King wrote: > On 06/27/2017 11:14 AM, Robert Dailey wrote: >> Also at $DAYJOB, we all work on the same code base. Our product is >> tested and verified to work on a distinct set of configurations. Why >> would I ask each user to create

Re: [cmake-developers] 3.9.0-rc3: CMAKE_ANDROID_NDK_DEPRECATED_HEADERS doesn't work outside of toolchain

On 06/27/2017 11:14 AM, Robert Dailey wrote: > Also at $DAYJOB, we all work on the same code base. Our product is > tested and verified to work on a distinct set of configurations. Why > would I ask each user to create their own toolchain file? If you have a toolchain file that works in some

Re: [cmake-developers] 3.9.0-rc3: CMAKE_ANDROID_NDK_DEPRECATED_HEADERS doesn't work outside of toolchain

On Mon, Jun 26, 2017 at 3:32 PM, Brad King wrote: > On 06/26/2017 11:58 AM, Robert Dailey wrote: >> Why does this only work in the toolchain file? > > 1. It needs to be set early. > > 2. It needs to propagate into try_compile projects. > > The toolchain file is sufficient

[cmake-developers] Create target with dependency to all targets similar to 'cmake_check_build_system'

I am wondering why there is no entry to create a target which is a dependency for each target like the `cmake_check_build_system`. It feels bit hacky to overload add_dependencies() to achieve this or am I overlooking something. Would something like this be good to add? If yes I could have a