-
Notifications
You must be signed in to change notification settings - Fork 468
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Non-existent build folder used with doubly inheriting configure preset #4023
Comments
@mpayrits We are investigating and I have diagnosed the issue. I hope to have a PR up and merge by tomorrow so that we can get a pre-release version out with a fix for you to use. Thanks for your understanding. |
Could you please test the changes I've made in #4028 by installing this vsix (you'll have to modify the extension from .zip to .vsix) and confirm whether it fixes the issue? Thanks! |
Hi, I've tried out the custom vsix and can confirm it fixes the issue 👍 |
The fix for this issue will be released in the next hour or so in v1.20.2. |
@gcampbell-msft We verified this issue on CMake tools:v1.20.2 (pre-release) and it has been fixed. |
Brief Issue Summary
With a
CMakeUserPresets.json
and noCMakePresets.json
where the active preset inherits from two hidden presets, the CMake vscode tools build step executes with a made-up, non-existent build folder, and consequently fails.The specific setup that fails is included in the Additional Information section.
Adding a
CMakePresets.json
file, even if itsconfigurePresets
field is empty, makes the problem go away, as does moving the specification ofbinaryDir
to thedefault
preset.CMake Tools Diagnostics
Debug Log
Additional Information
The reproducing project consists of these two files.
CMakeUserPresets.json
CMakeLists.txt
Adding the following trivial file makes the problem go away.
CMakePresets.json
The text was updated successfully, but these errors were encountered: