[Cmake-commits] CMake branch, master, updated. v3.9.2-721-g90b6186

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

[cmake-developers] [ANNOUNCE] CMake 3.9.2 available for download

We are pleased to announce that CMake 3.9.2 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.9.2 since 3.9.1: Brad

[CMake] [ANNOUNCE] CMake 3.9.2 available for download

We are pleased to announce that CMake 3.9.2 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.9.2 since 3.9.1: Brad

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

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.9.2 has been created at 4743855ac0c5e3811dd92bc68e35d7ef0ddf76c8 (tag) tagging

[Cmake-commits] CMake branch, master, updated. v3.9.1-758-gb7b9bae

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

[Cmake-commits] CMake branch, master, updated. v3.9.1-755-g25ac91a

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

[Cmake-commits] CMake branch, release, updated. v3.9.1-37-g80420d3

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, release has been updated via 80420d3c019715c256759d427f3c4cad1acab2d8 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.9.1-753-g10a3835

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

Re: [CMake] Adding compile and build type tests to CMake/CTest

On 9/7/2017 10:34 AM, paul via CMake wrote: On Thu, 2017-09-07 at 02:58 -0400, Edward Diener wrote: On 9/6/2017 11:39 PM, P F via CMake wrote: The `add_test` function can run whatever command you want it to, including compiling a target: add_library(foo_compile_test STATIC EXCLUDE_FROM_ALL

Re: [CMake] Adding compile and build type tests to CMake/CTest

On Thu, 2017-09-07 at 02:58 -0400, Edward Diener wrote: > On 9/6/2017 11:39 PM, P F via CMake wrote: > > > > The `add_test` function can run whatever command you want it to, including > > compiling a target: > > > > add_library(foo_compile_test STATIC EXCLUDE_FROM_ALL foo_compile_test.cpp) > >

Re: [CMake] Adding compile and build type tests to CMake/CTest

Yes, exactly. I think so… On 07/09/2017, 16:04, "CMake on behalf of Edward Diener" wrote: On 9/7/2017 3:32 AM, CHEVRIER, Marc wrote: > Rather than building a STATIC library, you can build an OBJECT library. In this

Re: [CMake] Adding compile and build type tests to CMake/CTest

On 9/7/2017 3:32 AM, CHEVRIER, Marc wrote: Rather than building a STATIC library, you can build an OBJECT library. In this case only compilation step is done. So your are saying that: add_library(foo_compile_test OBJECT EXCLUDE_FROM_ALL foo_compile_test.cpp) add_test(NAME foo_compile_test

Re: [CMake] CMake 3.9.x Visual Studio CUDA PDB/compiler flags issues

Okay I have opened an issue on CMake for handling multiple gencode with multiple code targets. On Wed, Sep 6, 2017 at 3:19 PM, Mueller-Roemer, Johannes Sebastian < johannes.sebastian.mueller-roe...@igd.fraunhofer.de> wrote: > Yes > > > From: Robert Maynard

Re: [CMake] configuration packages, IMPORTED targets, and global scope

Thanks, I am watching that discussion and will try to contribute where I can. On Thu, Sep 7, 2017 at 4:02 AM, Deniz Bahadir wrote: > Am 06.09.2017 um 20:24 schrieb Robert Dailey: >> >> So it took me a while to figure out why find_package() calls I was >> making (with CONFIG)

Re: [CMake] configuration packages, IMPORTED targets, and global scope

Am 06.09.2017 um 20:24 schrieb Robert Dailey: So it took me a while to figure out why find_package() calls I was making (with CONFIG) option were not accessible outside of the directory in which it was invoked. I realized that all targets seem to be global by default except IMPORTED targets

Re: [CMake] Adding compile and build type tests to CMake/CTest

Rather than building a STATIC library, you can build an OBJECT library. In this case only compilation step is done. On 07/09/2017, 08:59, "CMake on behalf of Edward Diener" wrote: On 9/6/2017 11:39 PM, P F via CMake

Re: [CMake] Adding compile and build type tests to CMake/CTest

On 9/6/2017 11:39 PM, P F via CMake wrote: The `add_test` function can run whatever command you want it to, including compiling a target: add_library(foo_compile_test STATIC EXCLUDE_FROM_ALL foo_compile_test.cpp) add_test(NAME foo_compile_test COMMAND ${CMAKE_COMMAND} --build . --target