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
When the field condition is used in a CMake preset, the extension CMake Tools shows a bugged behavior.
Consider the following CMakePresets.json defining two configure presets (Visual Studio 2017 on Windows and Ninja Multi-Config on Linux) with the relative build preset combinations:
Only presets matching the condition are visible in the list presented when the button for selecting the presets in the side bar is clicked.
All presets matching the condition are always visible every time the button for selecting the presets in the side bar is clicked.
Actual behavior:
All presets are visible.
Once a preset is selected, it is no more presented in list shown when the button for selecting the presets in the side bar is clicked. Only restarting Visual Studio Code resets the behavior.
If the condition field is removed form the CMakePresets.json, everything works as expected.
Platform and Versions
Operating System: Windows 10
CMake Version: 3.21.3
VSCode Version: 1.61.1
CMake Tools Extension Version: 1.9.0
C/C++ Extension Version: 1.7.0
Compiler/Toolchain: Visual Studio 2017
The text was updated successfully, but these errors were encountered:
@vdilecce, a fix for this problem was included in the CMake Tools 1.9.1 release. Upgrade your extension in VSCode and let us know if you encounter any other issues.
Brief Issue Summary
When the field
condition
is used in a CMake preset, the extension CMake Tools shows a bugged behavior.Consider the following CMakePresets.json defining two configure presets (Visual Studio 2017 on Windows and Ninja Multi-Config on Linux) with the relative build preset combinations:
Expected behavior:
condition
are visible in the list presented when the button for selecting the presets in the side bar is clicked.condition
are always visible every time the button for selecting the presets in the side bar is clicked.Actual behavior:
If the
condition
field is removed form the CMakePresets.json, everything works as expected.Platform and Versions
The text was updated successfully, but these errors were encountered: