-
Notifications
You must be signed in to change notification settings - Fork 428
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
VSCode C++ IntelliSense bug when adding new files #1187
Comments
Another workaround (besides reloading) is to configure after editing the CMakeLists.txt. Hopefully not that inconvenient before we get to fix this. |
I can try to do it myself, at least if I can get a VSCode development environment working... EDIT: Finally could get this extension in development mode. I would say it's pretty slow to develop extensions for VSCode: I need to wait approx 2 minutes everytime I edit a line of code as there's no immediate recompilation like there is in many other JS framework... |
That would be great. Let us know if you have any questions about the code base or if you encounter any issues during developing the fix for this issue. We'll be happy to review a PR when you send one. |
I've got something working in local where I can add new files, edit my CMake, and right on CMake save it runs CMake configure which then updates intellisense, a pretty quick fix |
CMake Tools 1.4.0 Beta is available on GitHub. Please try it out and let us know if you encounter any issues. |
This fix is available in CMake Tools #1.4.0 which has been released. |
Brief Issue Summary
VSCode C++ tools bugs when adding new files in a project manged by ms-vscode.cmake-tools.
When adding a new hpp/cpp file in the project workspace CMakeLists.txt, the VSCode C++ IntelliSense gets bugged and refuses to process correctly the new hpp/cpp file. It is needed to close VSCode, run cmake .. inside the build folder in a Powershell and then re-open VSCode in order to get it to work.
Expected:
When saving the CMakeLists.txt of a CMake sub-directory, VSCode C++ tools should automatically be refreshed with the new files. That behaviour is already fine under Visual Studio Community 2019.
Apparent Behavior:
VSCode C++ tools IntelliSense does not get refreshed with the new files and requires full editor reload with powershell console in order to rebuild the cmake project.
Platform and Versions
Other Notes/Information
Tested on a projected first initialized with cmake Visual Studio 2019 generator.
The text was updated successfully, but these errors were encountered: