[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-109-g095fc6d9d9
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 095fc6d9d96bf9f12770f85ebf0b75d384a7d5fb (commit) from e60412b63ed4665559c89e4f39a71973dd41a61a (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=095fc6d9d96bf9f12770f85ebf0b75d384a7d5fb commit 095fc6d9d96bf9f12770f85ebf0b75d384a7d5fb Author: Kitware Robot AuthorDate: Thu Oct 17 00:01:09 2019 -0400 Commit: Kitware Robot CommitDate: Thu Oct 17 00:01:09 2019 -0400 CMake Nightly Date Stamp diff --git 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 20191016) +set(CMake_VERSION_PATCH 20191017) #set(CMake_VERSION_RC 0) set(CMake_VERSION_IS_DIRTY 0) --- Summary of changes: Source/CMakeVersion.cmake | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org https://cmake.org/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, release, updated. v3.16.0-rc1-41-gc2a7729
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 a7ef28b9d8b30b7d5249ade425a9cd2e267da68c (commit) from 3658f4425a8ba10761682b5db323ab45650f230b (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - --- Summary of changes: Help/command/LINK_OPTIONS_LINKER.txt | 18 +- Help/command/OPTIONS_SHELL.txt | 4 ++-- 2 files changed, 11 insertions(+), 11 deletions(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org https://cmake.org/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-108-ge60412b
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 4116d5104e9b4aa5ad5ce8ab412d2230a6a62dbf (commit) via c2a7729177fa62a4a8eb3e2f7385f3f517c42f91 (commit) via a7ef28b9d8b30b7d5249ade425a9cd2e267da68c (commit) from 96a93a7f6436681d1d196de84b95ad38d88a8aaa (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e60412b63ed4665559c89e4f39a71973dd41a61a commit e60412b63ed4665559c89e4f39a71973dd41a61a Merge: 4116d51 c2a7729 Author: Brad King AuthorDate: Wed Oct 16 10:24:00 2019 -0400 Commit: Brad King CommitDate: Wed Oct 16 10:24:00 2019 -0400 Merge branch 'release-3.16' https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=4116d5104e9b4aa5ad5ce8ab412d2230a6a62dbf commit 4116d5104e9b4aa5ad5ce8ab412d2230a6a62dbf Merge: 96a93a7 a7ef28b Author: Brad King AuthorDate: Wed Oct 16 14:23:12 2019 + Commit: Kitware Robot CommitDate: Wed Oct 16 10:23:22 2019 -0400 Merge topic 'doc-add_link_options-typos' a7ef28b9d8 Help: Fix typos and style in add_link_options documentation Acked-by: Kitware Robot Merge-request: !3922 --- Summary of changes: Help/command/LINK_OPTIONS_LINKER.txt | 18 +- Help/command/OPTIONS_SHELL.txt | 4 ++-- 2 files changed, 11 insertions(+), 11 deletions(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org https://cmake.org/mailman/listinfo/cmake-commits
Re: [cmake-developers] CTest load balancing
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 -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake-developers
[cmake-developers] CTest load balancing
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 getloadavg() by returning the first value of that. While this function is present on many UNIX platforms, on Linux it means something slightly different than on say Solaris and *BSD. Namely on the former it is representing a "system load" and on the latter it is "CPU load", which is a subtle but rather important distinction. The system load includes processes which are in the uninterruptable state on purpose, a rather interesting blog post by Brendan Gregg has some juicy details: http://www.brendangregg.com/blog/2017-08-08/linux-load-averages.html Now, this has recently become a problem for us, as on some of our systems there are some kernel level processes active that by design are in the uninterruptable state, therefore contributing to the system load average, even if they do not affect the CPU load of the system. The number of processes in this state can easily outnumber the number of cores (i.e. 11 uninterruptable processes vs 4 CPU threads). So an idle system can have a load of > 10, for instance. At present we are working around this by setting a higher load to manage the tests, this as you might imagine is not a perfect solution as the number of uninterruptable processes does vary over time. The implementation of this feature specifically mentions checking for CPU load, which to be consistent on all platforms would require checking slightly different details on Linux. Is the intent for CTest to specifically manage CPU load or system load overall? The original commit message and comments point more towards the former. The Windows implementation of GetLoadAverage() also points towards merely CPU load. A Linux specific implementation would have to, most likely, investigate /proc/stat and derive a CPU load from that. Any ideas/suggestions? Thanks, W This transmission contains information that may be confidential and contain personal views which are not necessarily those of YouView TV Ltd. YouView TV Ltd (Co No:7308805) is a limited liability company registered in England and Wales with its registered address at YouView TV Ltd, 3rd Floor, 10 Lower Thames Street, London, EC3R 6YT. For details see our web site at http://www.youview.com -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: https://cmake.org/mailman/listinfo/cmake-developers
[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-104-g96a93a7
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 3658f4425a8ba10761682b5db323ab45650f230b (commit) via 080163a6574c6fcdcdb1b194dbd85778ff5a0b66 (commit) via c3c751e9ddb06702c9a046ab2c0eda12750d09ed (commit) via c89794feaeec7c7acd22caee9c20252bfc7b33d9 (commit) from 0e5a3ae7a9161628ff0de65a31cc1a870803fc17 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=96a93a7f6436681d1d196de84b95ad38d88a8aaa commit 96a93a7f6436681d1d196de84b95ad38d88a8aaa Merge: 0e5a3ae 3658f44 Author: Brad King AuthorDate: Wed Oct 16 09:53:14 2019 -0400 Commit: Brad King CommitDate: Wed Oct 16 09:53:14 2019 -0400 Merge branch 'release-3.16' --- Summary of changes: hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org https://cmake.org/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, release, updated. v3.16.0-rc1-39-g3658f44
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 466ad466b44561c8d48360fed0e491b3c09313be (commit) via 080163a6574c6fcdcdb1b194dbd85778ff5a0b66 (commit) via c3c751e9ddb06702c9a046ab2c0eda12750d09ed (commit) via c89794feaeec7c7acd22caee9c20252bfc7b33d9 (commit) via f0da223ff0ddd2b1dcc5112d7df920b23515cbd3 (commit) via 9fc87ef2e712eda340457811a1e1ac0af3e70bb5 (commit) via 08f4b5dcf9243754a3b6f88fc61d0c99578b08f6 (commit) via cd6f0ef35a9a7669e95219684f3a8398932a1b4d (commit) from 4041f6a3273f5638c28c7c9ff48f0326088531c7 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - --- Summary of changes: Modules/CMakeFindBinUtils.cmake | 12 Modules/FindCurses.cmake| 6 -- Modules/FindHDF5.cmake | 4 ++-- Source/cmCoreTryCompile.cxx | 3 +++ 4 files changed, 9 insertions(+), 16 deletions(-) hooks/post-receive -- CMake ___ Cmake-commits mailing list Cmake-commits@cmake.org https://cmake.org/mailman/listinfo/cmake-commits
[Cmake-commits] CMake branch, master, updated. v3.16.0-rc1-99-g0e5a3ae
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 93b80638ce9d034e9574c526aa5378ea4fc8801e (commit) via e0e109611a7c22ea4fe80cac38ba495ec19d1e07 (commit) via 4abdb1900aa47d714633f8ec9576d76781ee2f79 (commit) via 2e133ca30b46d0d189d4ced92d2794e2fccf78db (commit) via c11e7c5c3d5c5e682adf761c4b0de734ff68e690 (commit) via 466ad466b44561c8d48360fed0e491b3c09313be (commit) via f0da223ff0ddd2b1dcc5112d7df920b23515cbd3 (commit) via 9fc87ef2e712eda340457811a1e1ac0af3e70bb5 (commit) via 08f4b5dcf9243754a3b6f88fc61d0c99578b08f6 (commit) via cd6f0ef35a9a7669e95219684f3a8398932a1b4d (commit) from 220d5995076f794e222c882963fb634169a6600b (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log - https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=0e5a3ae7a9161628ff0de65a31cc1a870803fc17 commit 0e5a3ae7a9161628ff0de65a31cc1a870803fc17 Merge: 93b8063 c11e7c5 Author: Brad King AuthorDate: Wed Oct 16 13:51:24 2019 + Commit: Kitware Robot CommitDate: Wed Oct 16 09:51:32 2019 -0400 Merge topic 'FindCURL-cmake-package' c11e7c5c3d FindCURL: Try to find CURLConfig.cmake Acked-by: Kitware Robot Merge-request: !3903 https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=93b80638ce9d034e9574c526aa5378ea4fc8801e commit 93b80638ce9d034e9574c526aa5378ea4fc8801e Merge: e0e1096 f0da223 Author: Brad King AuthorDate: Wed Oct 16 13:43:16 2019 + Commit: Kitware Robot CommitDate: Wed Oct 16 09:45:59 2019 -0400 Merge topic 'CMakeFindBinUtils-cleanup' f0da223ff0 CMakeFindBinUtils: Remove unnecessary variable unset calls Acked-by: Kitware Robot Merge-request: !3920 https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=e0e109611a7c22ea4fe80cac38ba495ec19d1e07 commit e0e109611a7c22ea4fe80cac38ba495ec19d1e07 Merge: 4abdb19 466ad46 Author: Brad King AuthorDate: Wed Oct 16 13:43:26 2019 + Commit: Kitware Robot CommitDate: Wed Oct 16 09:45:11 2019 -0400 Merge topic 'swift-cross-compile' 466ad466b4 try_compile: support Swift for cross-compilation Acked-by: Kitware Robot Merge-request: !3921 https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=4abdb1900aa47d714633f8ec9576d76781ee2f79 commit 4abdb1900aa47d714633f8ec9576d76781ee2f79 Merge: 2e133ca 9fc87ef Author: Brad King AuthorDate: Wed Oct 16 13:43:11 2019 + Commit: Kitware Robot CommitDate: Wed Oct 16 09:44:08 2019 -0400 Merge topic 'FindCurses-tinfow' 9fc87ef2e7 FindCurses: use tinfow when wide support is requested Acked-by: Kitware Robot Merge-request: !3915 https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=2e133ca30b46d0d189d4ced92d2794e2fccf78db commit 2e133ca30b46d0d189d4ced92d2794e2fccf78db Merge: 220d599 08f4b5d Author: Brad King AuthorDate: Wed Oct 16 13:43:04 2019 + Commit: Kitware Robot CommitDate: Wed Oct 16 09:43:12 2019 -0400 Merge topic 'FindHDF5-cray' 08f4b5dcf9 FindHDF5: Append hdf5 to hdf5_hl to avoid undefined references cd6f0ef35a FindHDF5: Cray HDF5 Fortran module filename is usually capitalized Acked-by: Kitware Robot Merge-request: !3918 https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=c11e7c5c3d5c5e682adf761c4b0de734ff68e690 commit c11e7c5c3d5c5e682adf761c4b0de734ff68e690 Author: Charles Barto AuthorDate: Thu Oct 10 16:29:00 2019 -0700 Commit: Brad King CommitDate: Tue Oct 15 13:56:28 2019 -0400 FindCURL: Try to find CURLConfig.cmake diff --git a/Help/release/dev/FindCURL-cmake-package.rst b/Help/release/dev/FindCURL-cmake-package.rst new file mode 100644 index 000..67c5bbc --- /dev/null +++ b/Help/release/dev/FindCURL-cmake-package.rst @@ -0,0 +1,7 @@ +FindCURL-cmake-package +-- + +* The :module:`FindCURL` module learned to find CURL using + the ``CURLConfig.cmake`` package configuration file generated by + CURL's cmake buildsystem. It also gained a new ``CURL_NO_CURL_CMAKE`` + option to disable this behavior. diff --git a/Modules/FindCURL.cmake b/Modules/FindCURL.cmake index aeebc84..919babc 100644 --- a/Modules/FindCURL.cmake +++ b/Modules/FindCURL.cmake @@ -37,8 +37,35 @@ This module defines the following variables: ``CURL_VERSION_STRING`` The version of ``curl`` found. + +CURL CMake +^^ + +If CURL was built using the CMake buildsystem then it provides its own +``CURLConfig.cmake`` file for use with the :command:`find_package` command's +config mode. This module looks for this file and, if found, +returns its results
Re: [CMake] using `install()` with EXPORT and COMPONENT
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 PRIVATE_HEADER target
> property, then make sure you add those destinations in the install(TARGETS
> ...) command. For example:
>
> include(GNUInstallDirs)
> install(TARGETS myLib
> EXPORT SomeProj_Targets
> RUNTIME DESTINATION ${CMAKE_INSTALL_BINDIR}
> COMPONENT SomeProj_Runtime
> LIBRARY DESTINATION ${CMAKE_INSTALL_LIBDIR}
> COMPONENT SomeProj_Runtime
> NAMELINK_COMPONENT SomeProj_Development # Requires CMake 3.12
> ARCHIVE DESTINATION ${CMAKE_INSTALL_LIBDIR}
> COMPONENT SomeProj_Development
> PUBLIC_HEADER DESTINATION ${CMAKE_INSTALL_INCLUDEDIR}
> COMPONENT SomeProj_Development
> INCLUDES DESTINATION ${CMAKE_INSTALL_INCLUDEDIR}
> )
>
> I hadn't noticed one can have multiple 'COMPONENT' sections in a single
> `install` call. The CMake documentation could be a bit more clear about
> that.
>
>
> If you need to install headers into more than one directory (i.e. your
> headers have some sort of directory hierarchy), then the above doesn't work
> because it flattens all of the headers into a single location. Instead, you
> have to use install(FILES ...) to install the headers directly for such
> cases. Also, the target_include_directories() command has nothing to do
> with what header files get installed. Rather, it only controls the header
> search paths attached to a target.
>
> Right, true.
>
> FYI, part of my CppCon talk "Deep CMake For Library Authors" from a couple
> of weeks ago has a fair amount of overlap with this topic (specifically
> install components and destinations). I'm waiting for the YouTube clip to
> be made available and then I'll be posting a blog article on my website
> with links and the slides. When it goes up, you'll be able to find it at
> https://crascit.com (hopefully sometime this week, but depends how
> quickly the production people get the video done).
>
> Great, looking forward to reading the slides.
>
The CppCon talk and slides are now available. You can find them here:
https://crascit.com/2019/10/16/cppcon-2019-deep-cmake-for-library-authors/
--
Craig Scott
Melbourne, Australia
https://crascit.com
Get the hand-book for every CMake user: Professional CMake: A Practical
Guide
