[CMake] CMake with VS2015 C++ Build Tools and missing ucrtbased.dll

2016-07-10 Thread Roger Leigh
I'm doing some initial testing of CMake 3.6.0 with the newly-released Visual Studio 2015 Update 3 C++ Build Tools (http://landinghub.visualstudio.com/visual-cpp-build-tools). I.e. the standalone compiler without the IDE. I'm configuring with: cmake -G Ninja

Re: [CMake] Automatic inclusion of import targets found by find_package()?

2016-07-10 Thread Stephen Kelly
Robert Dailey wrote: > Is there more automation here that I'm not seeing? Thanks in advance. Yes, the documentation tells you to include what you need in the config file: https://cmake.org/cmake/help/v3.6/manual/cmake-packages.7.html#creating-a-package-configuration-file Thanks, Steve.

Re: [CMake] Automatic inclusion of import targets found by find_package()?

2016-07-10 Thread Robert Dailey
On Sun, Jul 10, 2016 at 5:11 PM, Stephen Kelly wrote: > Robert Dailey wrote: > >> Is there more automation here that I'm not seeing? Thanks in advance. > > Yes, the documentation tells you to include what you need in the config > file: > > >

[CMake] Why is target installation done in 2 separate steps?

2016-07-10 Thread Robert Dailey
Documentation states, that to export a file that imports your targets, you must do roughly: install(TARGETS fubar EXPORT fubar-targets) install(EXPORT fubar-targets DESTINATION lib/cmake/fubar) Why is this done in two steps? Based on reading the install() documentation, I don't see how the

[CMake] CMake Reports Incorrect HDF5 Libraries on OS X after 3.6.0 Upgrade

2016-07-10 Thread Breannan Smith
After upgrading to CMake 3.6.0 from 3.5.2, CMake fails to find HDF5 on OS X. With 3.5.2, find_package(HDF5 REQUIRED COMPONENTS C) reports the following for HDF5_LIBRARIES. Note the presences of libhdf5.dylib, in this list:

Re: [CMake] Convenience version of CMAKE_INCLUDE_CURRENT_DIR_IN_INTERFACE for INTERFACE_SOURCES

2016-07-10 Thread Robert Dailey
On Sun, Jul 10, 2016 at 1:23 PM, Robert Dailey wrote: > I am exporting/installing a header-only INTERFACE library and I run > into difficulty with target_sources() because I can't use relative > paths to the files. So I do this: > > > > set(project_name fubar) > >

[CMake] Convenience version of CMAKE_INCLUDE_CURRENT_DIR_IN_INTERFACE for INTERFACE_SOURCES

2016-07-10 Thread Robert Dailey
I am exporting/installing a header-only INTERFACE library and I run into difficulty with target_sources() because I can't use relative paths to the files. So I do this: set(project_name fubar) set(source_files myfile.h ) # Include dir for installed targets set(INCLUDE_DIR

[CMake] Automatic inclusion of import targets found by find_package()?

2016-07-10 Thread Robert Dailey
Let's say I have my own upstream library and I export a target for it. This subsequent cmake file (containing my IMPORT target definition) is included with my tarball. When a consuming project wants to find and use my import targets, they currently have to do (consider this pseudocode since i

Re: [CMake] CMAKE_C++_CREATE_SHARED_LIBRARY missing

2016-07-10 Thread Andreas Mohr
Hi, On Sun, Jul 10, 2016 at 12:00:02PM -0400, cmake-requ...@cmake.org wrote: > Message: 1 > Date: Sun, 10 Jul 2016 05:04:35 + > From: Dvir Yitzchaki > To: "'cmake@cmake.org'" > Subject: [CMake] CMAKE_C++_CREATE_SHARED_LIBRARY missing >

[cmake-developers] Don't enclose CMake version to generated files

2016-07-10 Thread Christoph GrĂ¼ninger
Dear CMake develoers, I just updated openSuse's CMake package. We have a patch, that removes the CMake version from generated files. This is aiming to reduce the re-publishing of generated files. Please find the current patch attached. What do you think, can we get this somehow upstreamed? Or are

[Cmake-commits] CMake branch, next, updated. v3.6.0-752-g4328891

2016-07-10 Thread Roger Leigh
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, next has been updated via 4328891e82e4231f513a60aa77afad829c67f8bc (commit) via

[Cmake-commits] CMake branch, next, updated. v3.6.0-754-g83acd62

2016-07-10 Thread Roger Leigh
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, next has been updated via 83acd621676ea63da5d2789300a56ec54494f225 (commit) via

[Cmake-commits] CMake branch, master, updated. v3.6.0-352-g7af4bc6

2016-07-10 Thread Kitware Robot
_VERSION_MINOR 6) -set(CMake_VERSION_PATCH 20160710) +set(CMake_VERSION_PATCH 20160711) #set(CMake_VERSION_RC 1) --- Summary of changes: Source/CMakeVersion.cmake |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/

[cmake-developers] [patch] Fix variable naming in FindTIFF unit test

2016-07-10 Thread Roger Leigh
Straightforward renaming, in https://gitlab.kitware.com/cmake/cmake/merge_requests/33 which is also merged into next for testing. Regards, Roger -- 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

[Cmake-commits] CMake branch, next, updated. v3.6.0-747-g45376cb

2016-07-10 Thread Roger Leigh
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, next has been updated via 45376cb2b6913a96691c36167361459df0d20939 (commit) via

[Cmake-commits] CMake branch, next, updated. v3.6.0-749-g2f77bbd

2016-07-10 Thread Roger Leigh
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, next has been updated via 2f77bbd188fe154580f07070eb10bcec244e494a (commit) via