CMakePresets.json misbehaves, always wants to build a debug build

[Croydon]

CMakePresets.json misbehaves, always wants to build a debug build

[Evelyn-001]

@Croydon, could you please add property "configuration": "release" in buildPresets for release-shared/release-static configuration and verify your issue again? We find that select one of the release- targets and build it in Code, we could get a release build, please see the below video. Thanks.
ENV:
VS code version: 1.88.1
CMake Extension version: v 1.17.17

[Croydon]

Thank you @Evelyn-001!

Adding "configuration": "release" works for VS Code and continues to work for VS.

I am assuming that this difference between VS Code and VS is, that VS prefers the Ninja CMake generator which is single-configuration, while VS Code apparently(?) has no own preferences and uses whatever CMake itself prefers, which is the VS generator on Windows and the VS generator is a multi-generator. So specifying configuration again selects the desired one then.

It is still annoying that "CMAKE_BUILD_TYPE": "Release" from the configuration step is not respected automatically, but I am not sure which component would need to change for that. CMake itself, this extension here, ...?

[Evelyn-001]

@Croydon, we are glad to be hearing your issue has been fixed. This is by design based on CMake upstream commandline. In multi-config scenarios one must define a Build Preset in which they define the configuration field. This matches the command-line cmake behavior where if you simply run cmake --build it will build the debug configuration, you must run cmake --build --config in order to build the correct configuration. This is done in VS by defining a build preset and defining configuration. please refer to this VS feedback ticket. Thanks for your support.