-
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
Update CMake Tools Initial experience [exp] #3732
Conversation
b486118
to
4374c73
Compare
4374c73
to
ac51168
Compare
This does not provide the best experience if the project is supposed to be developed in container. There is no guarantee that configure will succeed while the folder is opened on host, because some of the required tools may only be installed in dev container and not on the host. This can be worked around by setting |
This experimentally address #3588.
The goal of this PR is to make the initial experience of opening a folder that could potentially use the CMake Tools extension better.
This includes making it easier and more obvious to use the
cmake.ignoreCMakeListsMissing
setting. This is done by adding an option in the quick pick to not see the quick pick again. Additionally, it we check to confirm that there is actually a CMakeLists.txt in the folder structure based on the same parameters as our activation events, before popping the quick pick.Lastly, we are experimentally removing the pop-ups that ask "Would you like to configure?", in favor of defaulting
cmake.configureOnOpen
totrue
.