Replies: 1 comment
-
Docs:
On Windows, the generated project is using the Visual Studio 2022 generator, which is a multi-config generator. Such generators need the config specified during build. If you wish to use a single-config generator, Ninja is shipped as part of the Visual Studio build tools (and so is CMake fyi): C:\>call "C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\Tools\vsdevcmd.bat" -arch=amd64 -host_arch=amd64 -no_logo
C:\>where ninja | tail -n1
C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\Ninja\ninja.exe
C:\>"C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\Ninja\ninja.exe" --version
1.11.0 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
cmake-init projects on Windows seem to always output to build/Debug even when CMAKE_BUILD_TYPE is set to Release, instead of the expected build/Release
I also noticed that ci-win64 in CMakePresets.json is the only ci-* that does not set
I attempted the above simple modification, and it did not resolve the issue.
Beta Was this translation helpful? Give feedback.
All reactions