t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index b2be3c0..60b7a9b 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 13)
-set(CMake_VERSION_PATCH 20181005)
+set(CMake_VER
Module mode is only selected if there is a Find.cmake
file available. Otherwise Config mode is used anyway. For a given
project's call only one of the modes can be used: the find module
is either present or it is not. If the find module is available
it is used and becomes responsible for
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 3261e18f0379321e9bd77bfb48a320051f9de56f (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, master has been updated
via 02a1dbbb6c41aeab2d6a491629329a7f6ef47eef (commit)
via
On 10/04/2018 02:36 PM, Joachim Wuttke wrote:
> What then about user code that ought to check
> for version compatibility? Module mode only offers a check
> for an EXACT version string, and does not terminate if
> that condition is not met [3].
Module mode is only selected if there is a
