I have a situation where I've created a custom command to generate .cpp
files to be compiled (in my case running bison/flex).
I'm using CMake 3.13.4
However, I have to compile this code in two different ways for two
different targets. I am seeing the Visual Studio generator re-running
t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 2582bf5..c9707e1 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 20190313)
+set(CMake_VER
I see now the generators are part of CMake sources on gitlab...
that answers my questions.
thank you, Zan Lynx.
On March 11, 2019 6:03:24 PM MDT, hex wrote:
Another question, I didn't know there is a generator for sublime text 2:
Hi,
CMake had hardcoded default support for high-dpi screens in the applications it
generated for Apple's desktop OS at some point, but that was removed very
quickly in 286c75f7f034c5fdcd43bcb755da74d09c809642.
It is my understanding that you don't actually need to set the high-dpi key
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 80b761b9244d5ab9047082be40ebeee256be95ef (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 1b6a3047c6c2fc01afbcdba596bbbcaca8d7b43f (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 1b8c5a0c35bdc8e7004a56fca356f6c917e31a15 (commit)
via
