t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 07def95..991b9f5 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 15)
-set(CMake_VERSION_PATCH 20190607)
+set(CMake_VER
All,
I am pleased to announce that we are now offering Ubuntu builds of the
CMake release candidates, in addition to the production releases. The
first available release candidate build is 3.15.0~rc1-0kitware2.
If you would like to receive release candidate builds, follow the
instructions at
All,
I am pleased to announce that we are now offering Ubuntu builds of the
CMake release candidates, in addition to the production releases. The
first available release candidate build is 3.15.0~rc1-0kitware2.
If you would like to receive release candidate builds, follow the
instructions at
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 891b5559517b4027147f6d94a139953bdc687668 (commit)
via
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 43316424d0f33d6dc12ae5d1d4528603e8f0fab9 (commit)
via
I found out the problem was an old ninja version. I am closing the bug
report.
El 06/06/19 a las 12:27, Brad King escribió:
GitLab
I tried CMake 3.14.5 and 3.15.0-rc1 on your example. They both behave
the same. Running |ninja bundle| shows incremental output from cpack.
Alternatively
