Skip to content
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

The logic of the feature —— "select CMakeLists.txt" #3170

Closed
SAquarius opened this issue May 10, 2023 · 1 comment · May be fixed by #3646
Closed

The logic of the feature —— "select CMakeLists.txt" #3170

SAquarius opened this issue May 10, 2023 · 1 comment · May be fixed by #3646
Labels
documentation related to documentation of the extension
Milestone

Comments

@SAquarius
Copy link

Brief Issue Summary

CMake extension has a program logic that confuses me. When I open a folder that contains a project folder organized by CMake and many other folders, I don't want to use the CMake extension to initialize or process the directory. I just want to browse or modify other files. However, the CMake extension always automatically pops up a prompt window to select the CMakeLists.txt file. As shown in the following figure:
GLHCVWSZFOWN270GDTBBG$X
As shown in the above figure: I opened the "code" folder, which contains multiple subfolders. The CMake directory is a project I created to learn CMake syntax, and there are also several other independent folders included. However, as I was browsing and editing Python files, the CMake plugin popped up a prompt window, which obviously does not conform to the user's logical use.

CMake Tools Diagnostics

No response

Debug Log

No response

Additional Information

No response

@gcampbell-msft
Copy link
Collaborator

@SAquarius Thanks for the issue!

Please enable the cmake.ignoreCMakeListsMissing setting, at the user level, and this should fix your issue!

We will also take an action to update the docs to document this setting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation related to documentation of the extension
Projects
Status: Completed
Development

Successfully merging a pull request may close this issue.

2 participants