[Cmake-commits] CMake branch, master, updated. v3.9.1-619-g5eb6d20

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

Re: [cmake-developers] Mini Make

2017-08-28 Thread Brad King
On 08/27/2017 02:24 PM, Taylor Holberton wrote: > I just finished the first release of a cross platform, minimalistic > Make implementation. > > It was made specifically to run CMake generated Makefiles on Linux > and Windows (haven't tested on macOS yet). > > It's on GitHub

[Cmake-commits] CMake branch, master, updated. v3.9.1-618-ga6374b8

2017-08-28 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 a6374b88d96e59e231f3b7679166d1b15a91eece (commit) via

Re: [CMake] Should configuration package files define module package variables?

2017-08-28 Thread Johannes Zarl-Zierl
Hi, On Freitag, 25. August 2017 11:21:50 CEST Robert Dailey wrote: > However, what I'm wondering is even though the import targets should > contain all information about include directories, libraries, etc, > should I still define the typical Foo_INCLUDE_DIRS, Foo_LIBRARIES > variables? This