Re: [CMake] CMake 3.7.2 and parallel builds

On 01/30/2017 02:26 PM, Dave Flogeras wrote: On Sun, Jan 29, 2017 at 9:53 AM, Nils Gladitz > wrote: FWIW I don't think -j does anything when you build the NightlyBuild target given that that make invocation is not the one

Re: [CMake] CMake 3.7.2 and parallel builds

On Sun, Jan 29, 2017 at 9:53 AM, Nils Gladitz wrote: > FWIW I don't think -j does anything when you build the NightlyBuild target > given that that make invocation is not the one directly performing the > actual build. > The only command being run by the NightlyBuild

[CMake] Not being able to create a 'link' interface for an OBJECT library

Dear all, Recently I read the excellent tip of creating a 'link interface' for an OBJECT library in order to overcome the inability to directly link an OBJECT library, see: https://cmake.org/cmake/help/v3.5/manual/cmake-buildsystem.7.html#object-libraries This sounded like a perfect idea, so I

[CMake] Adding cache entries to cmake gui

Using the cmake gui program of the latest cmake 3.7.2 I add a cache entry of CMAKE_CXX_FLAGS to some compile flag value, but as soon as I hit the generate button the cache entry disappears and is no longer retained. Is CMAKE_CXX_FLAGS no longer a valid cmake variable ? If it is not a valid

Re: [CMake] Adding cache entries to cmake gui

On 01/30/2017 12:44 PM, Edward Diener wrote: Using the cmake gui program of the latest cmake 3.7.2 I add a cache entry of CMAKE_CXX_FLAGS to some compile flag value, but as soon as I hit the generate button the cache entry disappears and is no longer retained. Is CMAKE_CXX_FLAGS no longer a

Re: [CMake] Adding cache entries to cmake gui

On 1/30/2017 4:44 AM, Nils Gladitz wrote: On 01/30/2017 12:44 PM, Edward Diener wrote: Using the cmake gui program of the latest cmake 3.7.2 I add a cache entry of CMAKE_CXX_FLAGS to some compile flag value, but as soon as I hit the generate button the cache entry disappears and is no longer

Re: [cmake-developers] Debugger for CMake

On Jan 30, 2017 20:03, "Sylvain Joubert" wrote: > c) What is the best > approach to make this kind of feature appealing to IDE / UI tools which > currently work with CMake? > > If I recall correctly, one of the initial use cases for the server mode was exactly that. The

[Cmake-commits] CMake branch, next, updated. v3.7.2-2403-gfb28d94

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

[Cmake-commits] CMake branch, master, updated. v3.7.2-1213-ge6659f6

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

[Cmake-commits] CMake branch, next, updated. v3.7.2-2405-g6932f84

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

[Cmake-commits] CMake branch, master, updated. v3.7.2-1224-g8df12fc

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

[Cmake-commits] CMake branch, master, updated. v3.7.2-1215-g5c6c766

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

Re: [cmake-developers] CMake 3.8 feature freeze on 2017-02-01

On 01/09/2017 02:10 PM, Brad King wrote: > The feature freeze in 'master' for CMake 3.8 will be on Feb 1, 2017. > I may announce a freeze in 'next' sometime in the preceding week so > that we can get any remaining dashboard trouble cleaned up. In order to get 'master' ready to branch for 3.8,

[Cmake-commits] CMake branch, next, updated. v3.7.2-2411-ga3faf12

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

[Cmake-commits] CMake branch, next, updated. v3.7.2-2407-g6d2ebf5

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

[Cmake-commits] CMake branch, next, updated. v3.7.2-2409-ge715efb

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

[Cmake-commits] CMake branch, next, updated. v3.7.2-2413-ga38022e

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

Re: [cmake-developers] Debugger for CMake

+1 Wish this existed since forever. Cheers, Adam From: cmake-developers [mailto:cmake-developers-boun...@cmake.org] On Behalf Of Justin Berger Sent: Monday, January 30, 2017 11:10 AM To: cmake-developers@cmake.org Subject: [cmake-developers] Debugger for CMake I've made a proof of concept for

[cmake-developers] Debugger for CMake

I've made a proof of concept for a debugger integrated into CMake. The code and notes about the implementation are here: * https://gitlab.kitware.com/cmake/cmake/merge_requests/447 It is still a work in progress and there is still a decent chunk of work to be done. The general approach works

[Cmake-commits] CMake branch, next, updated. v3.7.2-2422-g48381a9

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

[Cmake-commits] CMake branch, next, updated. v3.7.2-2415-g784fe97

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

[Cmake-commits] CMake branch, next, updated. v3.7.2-2417-g91751d6

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

[Cmake-commits] CMake branch, next, updated. v3.7.2-2432-ge2025bc

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

[Cmake-commits] CMake branch, next, updated. v3.7.2-2424-g9c7eecc

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

Re: [cmake-developers] Debugger for CMake

Le 30/01/2017 à 17:09, Justin Berger a écrit : a) Is this feature worthwhile for eventual merge into CMake? No doubt! :-) > c) What is the best approach to make this kind of feature appealing to IDE / UI tools which currently work with CMake? If I recall correctly, one of the initial use

[Cmake-commits] CMake branch, master, updated. v3.7.2-1225-g07d3695

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