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
Notification that Configure Failed, Debug with CMake Debugger shows up when you override a Configure with a Build #3343
Comments
There should also be a way to disable the pop-up for legitimate cases. |
@cjdb Thanks for the suggestion. Could you elaborate some on what you mean by "legitimate cases"? It'd be great to understand any and all cases where we should allow this. |
That would be whatever the reason the popup was designed for. |
Agreed 💯, that pop-up is extremely annoying. There should be an option to disable it. |
The same error pops when I cancel configuring (#3472). |
The "Do not show again" button doesn't appear to have any effect. I still get the pop-up even after pressing that button (I've run CMake twice in a row after pressing the button to see if a change in my environment is the culprit, and it is not). |
If you search for Thanks. |
@cjdb Also, what operating system are you on? |
That setting isn't present in my
Arch Linux. I've also run the following, which may be relevant too?
|
Update: I see |
@cjdb It might not be in your settings.json yet, but if you search for it in the global settings UI, you should be able to find it. Could you check there? |
Yep, it's there. Looks like the global settings UI is having difficulty writing to my My guess is that I've got a permissions issue or something, but that's out of scope for the bug. Thank you for your assistance! |
Brief Issue Summary
When a CMake Configure action is running, and you override with a Build action, I get an error that Configure Failed, Debug with CMake Debugger. Ideally, this would not surface to the user, since nothing "failed".
CMake Tools Diagnostics
No response
Debug Log
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: