[Cmake-commits] CMake branch, master, updated. v3.12.0-386-g708dcbf
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 708dcbfdf587a2a84c4fdfc64f80d358e6efffb0 (commit) from d7a52f8c24a29ff7f64b00566b646f2d125d4ac0 (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=708dcbfdf587a2a84c4fdfc64f80d358e6efffb0 commit 708dcbfdf587a2a84c4fdfc64f80d358e6efffb0 Author: Kitware Robot AuthorDate: Wed Aug 8 00:01:06 2018 -0400 Commit: Kitware Robot CommitDate: Wed Aug 8 00:01:06 2018 -0400 CMake Nightly Date Stamp diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake index 842ce28..8b5f738 100644 --- a/Source/CMakeVersion.cmake +++ b/Source/CMakeVersion.cmake @@ -1,5 +1,5 @@ # CMake version number components. set(CMake_VERSION_MAJOR 3) set(CMake_VERSION_MINOR 12) -set(CMake_VERSION_PATCH 20180807) +set(CMake_VERSION_PATCH 20180808) #set(CMake_VERSION_RC 1) --- 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
Re: [cmake-developers] Experiments in CMake support for Clang (header & standard) modules
On Mon, Aug 6, 2018 at 2:37 PM Stephen Kelly wrote: > Stephen Kelly wrote: > >> The build.sh script shows the commands required to build it (though I > >> haven't checked the exact fmodule-file dependencies to check that > they're > >> all necessary, etc) - and with current Clang top-of-tree it does build > >> and run the example dinnerparty program. > > > > Ok. I tried with my several-weeks-old checkout and it failed on the first > > command with -modules-ts in it (for AbstractFruit.cppm - the simplest > > one). > > > > I'll update my build and try again, but that will take some time. > > I have locally tried your modifications. Aside from the content of my > previous email, I updated my clone (force push) to clean up the commits, > and > to modify your build.sh script to maintain the different libraries in the > repo. > > https://github.com/steveire/ModulesExperiments/commits/master > > I am still interested in what the C++ code (and build.sh) look like in the > case of one-module-per-library. > Oh, sure - that's easy enough, in terms of rolling together any modules in the same library. Mash all the code in any cppm interface files that are part of the same library into a single cppm file & build that into a single module. > It is obvious from looking at build.sh as it is that the buildsystem needs > to be changed when adding a new import to a c++ file, as I have described. > Though potentially not manually - and some of those lines would be added when the new module was added (as would be done when a new .cpp file is added today) - rather than when the import occurred. The 'worst' part is for intra-library module dependencies. For inter-library module dependencies, a coarse-grained solution would be to only build a library once all of the BMIs (.pcm files) for dependent libraries are built - and all of those are passed to libraries that depend on them. But, yeah, having the build system trying to figure out the dependency between modules within a library (which isn't explicit in the build files, unlike the inter-module dependency) is awkward. (& honestly, for maximum build parallelism, you wouldn't want the coarse-grained solution I described above - because then if something in library A depended on only module B.1 but not module B.2, you'd want to start building that part of A when B.1's BMI was built, without waiting for B.2's BMI to be finished) So, yes, if you have more than one module per library, then both for the intra-library module dependency problem and the minimal-cross-library dependency issue, you'd need the build system to either be told by the compiler as its going (ala the proposed build server/oracle system that's implemented in GCC) or by pre-scanning with a semi-aware scanner (doesn't have to know all of C++ - modules are notionally well defined to be able to scan a short preamble with limited syntax... but I'm not fully up on all the nuance there & retro #include-to-import legacy support might complicate things) (I guess, technically, even in the one-module-per-library, arguably your library dependency courld be a purely implementation dependency, in which case you'd still want to be able to build your 'dependent' BMI without waiting for the dependency's BMI to finish, since they don't depend on each other - so if your build system doesn't differentiate between external and internal dependencies, then again you'd need the kind of discovery phase if you want maximal build parallelism... ) > see the commit adding Grape separately and the changes required to the > buildsystem which were not required in the non-modules world: > > https://github.com/steveire/ModulesExperiments/commit/428bea53fc6 > > I will see if I can get a recent GCC build for comparison and to determine > whether the callback-to-the-buildsystem used in GCC makes a difference in > that respect. > > I'm still interested in a response to my previous email in that respect. > Yep, coming back to that now. > > Thanks, > > Stephen. > > > -- > > 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 > -- 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:
Re: [CMake] simple find_package example
Am Dienstag, 7. August 2018, 14:48:26 CEST schrieb Randy Heiland: > Hmm, well if that's the case, how does one generate the HelloConfig.cmake > file? The official documentation is here: https://cmake.org/cmake/help/latest/manual/cmake-packages.7.html > Although, for my particular situation, my question about wanting to > generate a "Find" file still remains, I think. I have a library which is, > potentially, useful to several projects. I assume there's some sort of > "Find" template for any such lib, i.e., a project needs to be able to > locate a lib (static or dynamic) and headers, cross-platform. Im almost positively sure that you don't want a FindXYZ.cmake, but a XYZConfig.cmake file instead. These are the main differences between Find- module packages and config-file packages: Find-Module packages: - are written and maintained independently of the "consumed" project (usually because the project does not support CMake) - are usually shipped by the consuming project - are hard to get right (they have to deal with strange installations, or old versions of the software, etc.) Config-file packages: - are generated by the "consumed" project - are shipped by the consumed project - have tooling to ensure correctness For the consuming project, there's no visible difference between both (you call "find_package(XYZ)" and cmake uses whatever it finds. In principle, it's even possible to use both together (note: please don't). That said, the official documentation can be a bit overwhelming at first. You probably can write some kind of cmake-2.6-style Find-Module package in less time, but the time to do it "right" is worth your effort. Just start by reading the documentation and don't hesitate to ask when you hit a problem… Cheers, Johannes -- 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
Re: [CMake] Boost + CMake + Windows + Sanity -> Possible?
On 7 August 2018 at 18:15, Wheeler, Gavin wrote:
> [...]
> 1. Look in C:\Program
> Files\CMake\share\cmake-3.9\Modules\FindBoost.cmake
Rule #1: never use CMake older than the latest release!
Rule #2: if you die hard for old CMake, force use of the latest FindBoost.cmake
if (CMAKE_VERSION VERSION_LESS 3.12)
if (NOT EXISTS "${CMAKE_BINARY_DIR}/cmake/FindBoost.cmake")
message(STATUS "You are using CMake older than 3.10")
message(STATUS "FindBoost.cmake has likely been updated to detect
newer or even not yet released Boost")
message(STATUS "Downloading FindBoost.cmake from
https://gitlab.kitware.com/cmake/ release branch")
message(STATUS "The auto-download can be disabled with
GIL_DISABLE_FINDBOOST_DOWNLOAD=ON")
file(DOWNLOAD
"https://gitlab.kitware.com/cmake/cmake/raw/release/Modules/FindBoost.cmake;
"${CMAKE_BINARY_DIR}/cmake/FindBoost.cmake")
endif()
list(INSERT CMAKE_MODULE_PATH 0 ${CMAKE_BINARY_DIR}/cmake)
endif()
The rules work most of the time, unless a lil' bug sneaks in eg.
https://gitlab.kitware.com/cmake/cmake/merge_requests/1731
https://gitlab.kitware.com/cmake/cmake/issues/17701
Remember, FindBoost.cmake is *always* a step or two behind CMake release.
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
--
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
Re: [CMake] Boost + CMake + Windows + Sanity -> Possible?
Hi,
Thanks for the suggestions and apologies for my tardiness in getting back on
this issue. I'm replying with my experiences for other to use as a future
reference, hopefully they can avoid some of the frustration I've encountered.
I spent half a day on this with two colleagues who are well versed in using
CMake, and we found a simple solution.
DON'T BOTHER!
"Windows + CMake + source boost "build seems intractable, or at the very least
intractable enough to basically be impossible, or at any rate just not worth
bothering with.
If are using Windows and you rate your sanity and time higher than you rate the
ability to use CMake and a source build of boost together I suggest you do the
following...
1. Look in C:\Program Files\CMake\share\cmake-3.9\Modules\FindBoost.cmake
2. Search for _Boost_KNOWN_VERSIONS
3. Download the binary build of the newest version listed from
https://sourceforge.net/projects/boost/files/boost-binaries/
4. If Windows Defender has a wobbly and your IT policy won't allow you to
ignore the wobble then move back thorugh older versions until one works
5. Install the boost to the default location and default settings
6. Run CMake with the following sort of thing...
find_package(Boost REQUIRED COMPONENTS system filesystem thread date_time
iostreams)
include_directories(${Boost_INCLUDE_DIRS})
link_directories(${Boost_LIBRARY_DIRS})
7. ...relax and make a nice cup of tea
Best Regards,
Gavin
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Dvir Yitzchaki
Sent: 15 July 2018 08:27
To: Innokentiy Alaytsev ; cmake@cmake.org
Subject: Re: [CMake] Boost + CMake + Windows + Sanity -> Possible?
I recommend using Hunter package manager:
https://docs.hunter.sh/en/latest/quick-start/boost-components.html
Regards,
Dvir
-Original Message-
From: CMake mailto:cmake-boun...@cmake.org>> On Behalf
Of Innokentiy Alaytsev
Sent: Thursday, July 12, 2018 13:29
To: cmake@cmake.org
Subject: Re: [CMake] Boost + CMake + Windows + Sanity -> Possible?
Hello!
First of all, I suggest you use Boost imported targets instead of
Boost_INCLUDE_DIRS and Boost_LIBRARY_DIRS and the
target_include_directories() and target_link_libraries() functions. Al this is
to better support exporting CMake package if you need it. If you do not produce
CMake package for use in some other projects, then just ignore this advice.
Second, just use pre-built Boost binaries
>
. They are just fine. If your Windows Defender finds something in them then
it's the problem in Windows Defender.
Best regards,
Innokentiy Alaytsev
--
Sent from:
http://cmake.3232098.n2.nabble.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:
[Cmake-commits] CMake branch, master, updated. v3.12.0-385-gd7a52f8
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 d7a52f8c24a29ff7f64b00566b646f2d125d4ac0 (commit)
via 496d22b8cc5b503537841892c0a630b264de146b (commit)
from 8f0b3d2da61ef5d0322f3886e1ed0629f1673a9c (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=d7a52f8c24a29ff7f64b00566b646f2d125d4ac0
commit d7a52f8c24a29ff7f64b00566b646f2d125d4ac0
Merge: 8f0b3d2 496d22b
Author: Craig Scott
AuthorDate: Tue Aug 7 13:17:15 2018 +
Commit: Kitware Robot
CommitDate: Tue Aug 7 09:17:26 2018 -0400
Merge topic 'productbuild-merge-output'
496d22b8cc productbuild: Capture stderr too in CPackProductBuild logs
Acked-by: Kitware Robot
Merge-request: !2257
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=496d22b8cc5b503537841892c0a630b264de146b
commit 496d22b8cc5b503537841892c0a630b264de146b
Author: Muhammad Ismail Soboute
AuthorDate: Thu Aug 2 05:56:49 2018 +0430
Commit: Craig Scott
CommitDate: Mon Aug 6 21:27:51 2018 +1000
productbuild: Capture stderr too in CPackProductBuild logs
Stdout and stderr will be merged.
Fixes: #18234
diff --git a/Source/CPack/cmCPackProductBuildGenerator.cxx
b/Source/CPack/cmCPackProductBuildGenerator.cxx
index 4ca0fa8..76b3275 100644
--- a/Source/CPack/cmCPackProductBuildGenerator.cxx
+++ b/Source/CPack/cmCPackProductBuildGenerator.cxx
@@ -144,10 +144,10 @@ bool cmCPackProductBuildGenerator::RunProductBuild(const
std::string& command)
tmpFile += "/ProductBuildOutput.log";
cmCPackLogger(cmCPackLog::LOG_VERBOSE, "Execute: " << command << std::endl);
- std::string output, error_output;
+ std::string output;
int retVal = 1;
bool res = cmSystemTools::RunSingleCommand(
-command.c_str(), , _output, , nullptr,
+command.c_str(), , , , nullptr,
this->GeneratorVerbose, cmDuration::zero());
cmCPackLogger(cmCPackLog::LOG_VERBOSE, "Done running command" << std::endl);
if (!res || retVal) {
---
Summary of changes:
Source/CPack/cmCPackProductBuildGenerator.cxx | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
hooks/post-receive
--
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
https://cmake.org/mailman/listinfo/cmake-commits
Re: [CMake] simple find_package example
Hmm, well if that's the case, how does one generate the HelloConfig.cmake file? Although, for my particular situation, my question about wanting to generate a "Find" file still remains, I think. I have a library which is, potentially, useful to several projects. I assume there's some sort of "Find" template for any such lib, i.e., a project needs to be able to locate a lib (static or dynamic) and headers, cross-platform. thanks, Randy On Mon, Aug 6, 2018 at 4:09 PM, Alexander Neundorf wrote: > On 2018 M08 2, Thu 10:01:39 CEST Randy Heiland wrote: > > Hi, > > > > I'd like to figure out how to modify the simple "hello" demo ( > > https://cmake.org/examples/) so that the Hello project is a library > with an > > accompanying FindHello.cmake and then the Demo project uses that > > information and "find_package" to discover/use it. > > > > Hopefully that makes sense. Basically, I'm looking for a simple tutorial > on > > how I can make my library easily accessible to a CMake project. > > for that, you don't want a FindHello.cmake (which would typically be > shipped > either by cmake or by the consuming application), instead you want to > generate > and install a HelloConfig.cmake file. > > Alex > > -- 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
[Cmake-commits] CMake branch, master, updated. v3.12.0-383-g8f0b3d2
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 8f0b3d2da61ef5d0322f3886e1ed0629f1673a9c (commit)
via 00a5836a3de046aa910aee7ec3e015b155790422 (commit)
from 90df5f673029ae5a9ca1e88fec9ed3aa67ad36d1 (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=8f0b3d2da61ef5d0322f3886e1ed0629f1673a9c
commit 8f0b3d2da61ef5d0322f3886e1ed0629f1673a9c
Merge: 90df5f6 00a5836
Author: Brad King
AuthorDate: Tue Aug 7 12:25:14 2018 +
Commit: Kitware Robot
CommitDate: Tue Aug 7 08:25:21 2018 -0400
Merge topic 'xerces-version-fix'
00a5836a3d FindXercesC: Correct order of version detection and versioned
library checks
Acked-by: Kitware Robot
Merge-request: !2259
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=00a5836a3de046aa910aee7ec3e015b155790422
commit 00a5836a3de046aa910aee7ec3e015b155790422
Author: Roger Leigh
AuthorDate: Fri Aug 3 07:54:35 2018 +0100
Commit: Roger Leigh
CommitDate: Fri Aug 3 07:54:35 2018 +0100
FindXercesC: Correct order of version detection and versioned library checks
diff --git a/Modules/FindXercesC.cmake b/Modules/FindXercesC.cmake
index 267c164..55db7ae 100644
--- a/Modules/FindXercesC.cmake
+++ b/Modules/FindXercesC.cmake
@@ -73,6 +73,10 @@ find_path(XercesC_INCLUDE_DIR
DOC "Xerces-C++ include directory")
mark_as_advanced(XercesC_INCLUDE_DIR)
+if(XercesC_INCLUDE_DIR)
+ _XercesC_GET_VERSION("${XercesC_INCLUDE_DIR}/xercesc/util/XercesVersion.hpp")
+endif()
+
if(NOT XercesC_LIBRARY)
# Find all XercesC libraries
find_library(XercesC_LIBRARY_RELEASE
@@ -90,10 +94,6 @@ unset(XercesC_VERSION_MAJOR)
unset(XercesC_VERSION_MINOR)
unset(XercesC_VERSION_PATCH)
-if(XercesC_INCLUDE_DIR)
- _XercesC_GET_VERSION("${XercesC_INCLUDE_DIR}/xercesc/util/XercesVersion.hpp")
-endif()
-
include(${CMAKE_CURRENT_LIST_DIR}/FindPackageHandleStandardArgs.cmake)
FIND_PACKAGE_HANDLE_STANDARD_ARGS(XercesC
FOUND_VAR XercesC_FOUND
---
Summary of changes:
Modules/FindXercesC.cmake | 8
1 file changed, 4 insertions(+), 4 deletions(-)
hooks/post-receive
--
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
https://cmake.org/mailman/listinfo/cmake-commits
Re: [cmake-developers] Darwin nightly builds
On 08/07/2018 02:56 AM, Martin Sander wrote: > the last nightly build for Mac in https://cmake.org/files/dev/?C=M;O=D > is dated 2018-07-30, the other systems are there. Thanks. The problem was introduced just before I took time off so the failing entry on our nightly testing dashboard went unnoticed. I've opened an issue for it: * https://gitlab.kitware.com/cmake/cmake/issues/18245 -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] Link flags in CMAKE_CXX_CREATE_STATIC_LIBRARY
Hi,
I'm using CMake on Windows with Ninja and MSVC inside Visual Studio. I'd like
to suppress linker warning 4221. To do so I added the following linker flag:
set_property(TARGET MyTarget APPEND PROPERTY LINK_FLAGS "/ignore:4221")
This however doesn't affect the creation of static libraries. The only
workaround I found is to manipulate the CMAKE_CXX_CREATE_STATIC_LIBRARY
variable:
string(REPLACE "" " /ignore:4221"
CMAKE_CXX_CREATE_STATIC_LIBRARY "${CMAKE_CXX_CREATE_STATIC_LIBRARY}")
Is there a nicer way to do this? Why are the link flags not passed to the
static library creation or - if not possible - why are there no static library
link flag properties?
Regards,
Daniel
--
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
[cmake-developers] Darwin nightly builds
Hi, the last nightly build for Mac in https://cmake.org/files/dev/?C=M;O=D is dated 2018-07-30, the other systems are there. M. -- 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
