-
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
Cmake extension does not prompt to select CmakeLists.txt file in 1.17 #3588
Comments
The hypothesis is that this came from a community PR to disable selecting CMakeList.txt when it is not in your root. We need to bring back that dropdown to some degree |
@sinemakinci1 could you please provide any workaround to fix the problem locally on user's PC? |
@YuriL180821 Can you try the following?
Then, reload the window and see if VSC will prompt for youto configure? Once prompted, you should press Yes, and see an option to select a CMakeLists.txt file up top (if embedded in a subdirectory). In general, if you have the CMake Tools extension installed, you should be able to find the CMake: Configure command in the command palette which will fire that option to select a CMakeLists.txt file if detected in a sub-directory. |
Brief Issue Summary
in 1.17, even when there is a CMakeLists.txt file, the Cmake Tools extension does not activate. An example repo I used can be found here: https://github.com/sinemakinci1/basic-cpp-copilot-example/tree/main/my-cmake-project

Since CMakeLists.txt file is embedded not at the top-level, it should prompt me to select a CMakeLists.txt file (this is part of the partial activation experience). Once I downgraded to 1.15, I saw the prompt, selected my CMakeList.txt file and kits, and now 1.16 and 1.17 versions of CMake Tools extension activate with the project.
CMake Tools Diagnostics
No response
Debug Log
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: