[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-109-g095fc6d9d9

2019-10-16 Thread Kitware Robot via Cmake-commits
t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index 4edadd8e06..c15eda7281 100644 --- a/Source/CMakeVersion.cmake +++ b/Source/CMakeVersion.cmake @@ -1,7 +1,7 @@ # CMake version number components. set(CMake_VERSION_MAJOR 3) set(CMake_VERSION_MINOR 16) -set(CMake_VERSION_PATCH 2019

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc1-41-gc2a7729

2019-10-16 Thread Kitware Robot via Cmake-commits
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 c2a7729177fa62a4a8eb3e2f7385f3f517c42f91 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-108-ge60412b

2019-10-16 Thread Kitware Robot via Cmake-commits
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 e60412b63ed4665559c89e4f39a71973dd41a61a (commit) via

Re: [cmake-developers] CTest load balancing

2019-10-16 Thread Brad King via cmake-developers
On 10/16/19 10:05 AM, Wouter Klouwen wrote: > Is the intent for CTest to specifically manage CPU load or system load > overall? I don't think a careful distinction was made at the time. If Linux needs some updates to be consistent with other platforms then that would be fine with me. -Brad --

[cmake-developers] CTest load balancing

2019-10-16 Thread Wouter Klouwen
Hi all, CTest has a very useful feature that performs load balancing. This works by comparing the current system load to a target load. The current implementation defers to SystemInformationImplementation::GetLoadAverage() to return a value. This is implemented on the platforms that have

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-104-g96a93a7

2019-10-16 Thread Kitware Robot via Cmake-commits
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 96a93a7f6436681d1d196de84b95ad38d88a8aaa (commit) via

[Cmake-commits] CMake branch, release, updated. v3.16.0-rc1-39-g3658f44

2019-10-16 Thread Kitware Robot via Cmake-commits
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 3658f4425a8ba10761682b5db323ab45650f230b (commit) via

[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-99-g0e5a3ae

2019-10-16 Thread Kitware Robot via Cmake-commits
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 0e5a3ae7a9161628ff0de65a31cc1a870803fc17 (commit) via

Re: [CMake] using `install()` with EXPORT and COMPONENT

2019-10-16 Thread Craig Scott
On Mon, Sep 30, 2019 at 4:09 AM Stefan Seefeld wrote: > Hi Craig, > > thanks for the detailed explanation ! > On 2019-09-29 5:13 a.m., Craig Scott wrote: > > > If all of your headers should be installed to a single directory, then you > can list the headers in the target's PUBLIC_HEADER or