t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 63d5f3d..4303c25 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 14)
-set(CMake_VERSION_PATCH 20190520)
+set(CMake_VER
Hi, I am building CMake (on x64 linux) with custom OpenSSL and wondering if there are any CMake requirements on how OpenSSL should be compiled. Specifically, I'm interested to know if it is valid to link CMake with single-threaded OpenSSL library (configured with "no-threads" option). May be it is
Hello,
On 20.05.19 16:01, hex wrote:
What means command1 [args1...]]? Or, should this read
*add_custom_target(Name [ALL] [COMMAND command1 [args1...]]**
** [COMMAND command2 [args2...] ...]*
I believe this is due to backward compatibility (pre 2.6) reasons so
that you could still write:
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 e025495b8500f9aaf6745571ffdb48a6218e7929 (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 28ee31149030c75c32ebbf134502a9d020dbd54b (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 9860b4c5e8756cb58c4cdfc27a14194f823aa0ab (commit)
via
The function is defined as
*add_custom_target(Name [ALL] [command1 [args1...]]**
** [COMMAND command2 [args2...] ...]**
** [DEPENDS depend depend depend ... ]**
** [BYPRODUCTS [files...]]**
** [WORKING_DIRECTORY dir]**
** [COMMENT comment]**
** [VERBATIM] [USES_TERMINAL]**
**
