t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index c09c1ce..9a4f63e 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -1,7 +1,7 @@
# CMake version number components.
set(CMake_VERSION_MAJOR 3)
set(CMake_VERSION_MINOR 15)
-set(CMake_VERSION_PATCH 20190919)
+set(CMake_VER
Hello,
Perhaps you can start by not using the .bat scripts and using the .exe
instead. You can run cmake from a visual studio environment, and
instead of invoking a visual studio environment for each command.
And to build from your script:
cmake --build .
Regards,
Juan
On 9/19/19 12:59
Now, with this toolchain file:
-start of toolchain file---
set(CMAKE_SYSTEM_NAME Windows)
set(CMAKE_SYSTEM_PROCESSOR "x86")
set(CMAKE_SYSTEM_VERSION 1)
# Microsoft MSVC compiler
#set(CMAKE_C_COMPILER cl.exe)
#set(CMAKE_CXX_COMPILER cl.exe)
set(CMAKE_C_COMPILER
El 17/9/19 a las 16:46, fdk17 escribió:
I personally never seen anyone try to use the Ninja generator via
command line CMake and use the cl.exe compiler.
I've only seen that using Visual Studio to open a CMakeLists.txt file
it can produce a Ninja project. But even MS documentation states
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 e199294673665e01b1cba48625ec1b18c960c90e (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 cca5897318d5c747078f79cd5bb45ba74955102a (commit)
via
