You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CMake Tools 1.7.1 was released today and it contains a fix for this issue. Upgrade the extension in VSCode and let us know if you encounter any other problems.
https://github.com/microsoft/vscode-cmake-tools/blob/develop/docs/cmake-presets.md#supported-cmake-and-cmakepresetsjson-versions says "CMake Tools reads and evaluates CMakePresets.json and CMakeUserPresets.json, and does not invoke CMake directly with the --preset option.", unfortunately with CMake Tools 1.7.0 the evaluation is not equivalent to the one done by CMake.
https://cmake.org/cmake/help/latest/manual/cmake-presets.7.html#macro-expansion says "All macros are evaluated in the context of the preset being used, even if the macro is in a field that was inherited from another preset.". And when using
and using the "Complete" preset CMake Tools uses
build/Base
as binaryDir while CMake usesbuild/Complete
.The text was updated successfully, but these errors were encountered: