[Cmake-commits] CMake branch, master, updated. v3.9.0-425-g7c7a57c

2017-08-04 Thread Kitware Robot
_VERSION_MINOR 9) -set(CMake_VERSION_PATCH 20170804) +set(CMake_VERSION_PATCH 20170805) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

Re: [CMake] Interest in adding to CMake the CMakeGet module to get dependencies

2017-08-04 Thread Craig Scott
TLDR: There may be other work already covering similar capabilities (e.g. hunter and WIP that I'm uncloaking here). This response is mostly about providing broader discussion. Paul it seems you've been busy since you first asked about cget

Re: [CMake] Not able to find boost with cmake

2017-08-04 Thread ??????
Actually I have built boost from source with the version I downloaded, and I've run the install script given by boost. However, I just cannot let CMake find it. [ D:/Program Files/CMake/share/cmake-3.9/Modules/FindBoost.cmake:1450 ] _boost_LIBRARY_SEARCH_DIRS_RELEASE = D:/Program Files/PCL

Re: [CMake] CMake 3.9 change to dependencies of object compilation

2017-08-04 Thread Robert Maynard
I see no reason that we couldn't provide a TARGET_OBJ_DIR:tgt generator expression that states where the objects reside. Opening TARGET_OBJ_DIR and TARGET_OBJECTS to be evaluated for any target would require some work, and an interested CMake developer. FYI Due to XCode limitations we can't allow

[CMake] Interest in adding to CMake the CMakeGet module to get dependencies

2017-08-04 Thread paul via CMake
Hi, I have a written a cmake module to get dependencies using the cget protocol here: https://github.com/pfultz2/cmake-get This is different than `ExternelProject`: * `ExternelProject` happens only during build, which allows this module to work in both in config and script mode.  * In config

Re: [CMake] CMake 3.9 change to dependencies of object compilation

2017-08-04 Thread Puetz Kevin A
> -Original Message- > From: Ben Boeckel [mailto:ben.boec...@kitware.com] > Sent: Friday, August 04, 2017 12:55 PM > To: Puetz Kevin A > Cc: cmake@cmake.org; Robert Maynard > Subject: Re: CMake 3.9 change to dependencies of object

Re: [CMake] CMake 3.9 change to dependencies of object compilation

2017-08-04 Thread Puetz Kevin A
> -Original Message- > From: Robert Maynard [mailto:robert.mayn...@kitware.com] > Sent: Friday, August 04, 2017 1:03 PM > To: Ben Boeckel > Cc: Puetz Kevin A ; cmake@cmake.org > Subject: Re: CMake 3.9 change to dependencies of object

Re: [CMake] CMake 3.9 change to dependencies of object compilation

2017-08-04 Thread Puetz Kevin A
Thanks for the reply, questions/clarifications below. > -Original Message- > From: Ben Boeckel [mailto:ben.boec...@kitware.com] > Sent: Thursday, August 03, 2017 10:59 AM > To: cmake@cmake.org > Cc: Robert Maynard ; Puetz Kevin A > >

Re: [CMake] CMake 3.9 change to dependencies of object compilation

2017-08-04 Thread Robert Maynard
You can find the location for object files by using $. This can be used as the DEPENDS of a custom command. I would not try using OBJECT_OUTPUTS as IIRC that is only used by the makefile generator. On Fri, Aug 4, 2017 at 1:55 PM, Ben Boeckel

Re: [CMake] CMake 3.9 change to dependencies of object compilation

2017-08-04 Thread Ben Boeckel
On Fri, Aug 04, 2017 at 17:35:53 +, Puetz Kevin A wrote: > Thanks for the reply, questions/clarifications below. > > requests that that be fixed as well (though that is backwards compatible > > since the solution will likely involve ). > > Sentence cut off? I assume you meant "will likely

[Cmake-commits] CMake branch, master, updated. v3.9.0-424-geed33ad

2017-08-04 Thread Kitware Robot
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 eed33adc6a65581a47b552020432a618ed5b9cdf (commit) via

[Cmake-commits] CMake branch, release, updated. v3.9.0-22-g8fb12ce

2017-08-04 Thread Kitware Robot
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 8fb12ce7a22ffe21cb9dfc20ffaf111d0897a34a (commit) via

[Cmake-commits] CMake branch, master, updated. v3.9.0-419-gc2cc764

2017-08-04 Thread Kitware Robot
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 c2cc7645820ba762bdaaba62fa860bd00b909a39 (commit) via

Re: [CMake] What is the default build type?

2017-08-04 Thread Mueller-Roemer, Johannes Sebastian
Exactly. Also, CMAKE_CONFIGURATION_TYPES uses the CamelCase Versions by default, so if your CMake code breaks with that spelling, your CMakeLists.txt can be considered broken anyways... Fraunhofer-Institut für Graphische Datenverarbeitung IGD Fraunhoferstr. 5  |  64283 Darmstadt  |  Germany Tel

Re: [CMake] Change LTO Type in CMake 3.9 with Clang?

2017-08-04 Thread Clément Gregoire
Not yet, but it is a known issue : https://gitlab.kitware.com/cmake/cmake/issues/16808 Le ven. 4 août 2017 à 06:03, Breannan Smith a écrit : > Testing the new LTO support in CMake 3.9, it appears that > setting INTERPROCEDURAL_OPTIMIZATION to TRUE causes CMake to pass >