[Cmake-commits] CMake branch, master, updated. v3.10.1-628-g4549eed

2017-12-14 Thread Kitware Robot
VERSION_MINOR 10) -set(CMake_VERSION_PATCH 20171214) +set(CMake_VERSION_PATCH 20171215) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

Re: [CMake] Configuration under CMake 3.10.1 fails but succeeds with 3.9.6

2017-12-14 Thread Alan W. Irwin
On 2017-12-14 13:51-0500 Michael Jackson wrote: I just tried out the latest CMake release 3.10.1 and it fails to configure (from a clean build directory) our project where CMake 3.9.x and below (down to CMake 3.7.x) configures it completely and correctly. The configure error I get is" --

[CMake] Configuration under CMake 3.10.1 fails but succeeds with 3.9.6

2017-12-14 Thread Michael Jackson
I just tried out the latest CMake release 3.10.1 and it fails to configure (from a clean build directory) our project where CMake 3.9.x and below (down to CMake 3.7.x) configures it completely and correctly. The configure error I get is" -- Configuring done CMake Error in

[cmake-developers] [ANNOUNCE] CMake 3.10.1 available for download

2017-12-14 Thread Robert Maynard
We are pleased to announce that CMake 3.10.1 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.10.1 since 3.10.0:

[CMake] [ANNOUNCE] CMake 3.10.1 available for download

2017-12-14 Thread Robert Maynard
We are pleased to announce that CMake 3.10.1 is now available for download. Please use the latest release from our download page: https://cmake.org/download/ Thanks for your support! - Changes in 3.10.1 since 3.10.0:

[Cmake-commits] CMake branch, master, updated. v3.10.1-598-g1e148ab

2017-12-14 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 1e148aba7078359e2e5b4d7080a6e1cb6592d94a (commit) via

Re: [CMake] CMake fixup_bundle for ubuntu 16.04

2017-12-14 Thread Konstantin Tokarev
13.12.2017, 23:08, "Daniel Schepler" : > You would need to set the INSTALL_RPATH property of the targets to something > like "$ORIGIN/../lib" . > > You might also need to add "-Wl,--disable-new-dtags" to the > CMAKE_*_LINK_FLAGS variables - otherwise, the RPATH

Re: [CMake] Using SET_TARGET_PROPERTIES and IMPORTED_LINK_INTERFACE_LIBRARIES

2017-12-14 Thread CHEVRIER, Marc
I think you can fill a bug about erroneous behaviour when a list is specified with command set_target_properties for property IMPORTED_LINK_INTERFACE_LIBRARIES. Another way to specify the property is to use command set_property which supports multiple values for a property: set_property(TARGET

Re: [CMake] Using SET_TARGET_PROPERTIES and IMPORTED_LINK_INTERFACE_LIBRARIES

2017-12-14 Thread Petr Kmoch
Hi Saad, have you read the docs on IMPORTED_LINK_INTERFACE_LIBRARIES? ( https://cmake.org/cmake/help/latest/prop_tgt/IMPORTED_LINK_INTERFACE_LIBRARIES.html ): "This property is deprecated. Use INTERFACE_LINK_LIBRARIES instead." Setting INTERFACE_LINK_LIBRARIES to "LibA;LibB" should do exactly