Disable the extension when no CMakeLists is present

[songyang-dev]

Hello! I like this extension but sometimes I am not working on a CMake project in my workspace and this extension starts to search for kits and configurations right away. It would be nice if the extension would not aggressively start on every workspace in VSCode.

[bobbrow]

Thank you for your issue report. I had thought we disabled the extension in cases where there is no CMakeLists.txt found, but we will go back and look at the code to see what is missing.

To help us understand better, are you opening a folder that happens to have a CMakeLists.txt buried in one of the subfolders?

[andreeis]

I vaguely remember that there is some kits searching logic triggered before the project has the chance to first configure. We need to fix that, of course.
@XsongyangX , as a workaround you can select a kit, doesn't matter which one (let's say 'unspecified'), then you should see a popup notifying you that there is no CMakeLists found, with an option button to ignore for the current project. Press that and you should not see any activation happening after that. Let us know how that works.

[songyang-dev]

To help us understand better, are you opening a folder that happens to have a CMakeLists.txt buried in one of the subfolders?

I was in a leaf folder. So no subfolders.

@andreeis I'll try that next time.

[songyang-dev]

I believe this issue is linked with #1564, #1518, #1461

[andreeis]

Fix in PR now. Duplicate of #1007.

[JanHildenbrandBosch]

Can this in any way be disabled over a configuration?
We are having currently the issue that the cmakelist.txt will be created after the extension is loaded. But then the extension bar is never loaded.

[bobbrow]

@JanHildenbrandBosch this issue is closed so I moved your comment to a new issue.