I have a C++ VSCode project converted over from 2019 to 2020 that compiles and deploys; however, I continue to see warnings about IncludePath and not being able to open header files, and Intellisense seems to be out to lunch when it comes to WPIlib, Phoenix, and REV.
Again, remember that the code builds and deploys seemingly fine and runs as expected (except for configuring a new Falcon 500/TalonFX to behave as a Follower - running the example code in the docs throws compile errors - that will be help request #2 later). But it would be GREAT for VSCode to stop blasting warnings about include paths, and it would be SWELL if Intellisense would start being a helpful tool.
Anyone have any general troubleshooting ideas? I’ve got all the latest and greatest versions of WPIlib, Phoenix, and REV stuff installed. I’ve done the close all tabs, close VSCode, restart VSCode thing. I’ve tried to refresh Intellisense. No dice.
Please help me graciously slap some sense into this thing. Keep in mind if you tell me to “go into build.gradle and update the paths”, that is insufficient guidance, as my programming experience is limited. I would need actual examples of how to add an arbitrary path. Thanks in advance.
Alas, C++ tooling kind of sucks. I’ve given up on intellisense entirely when writing C++ these days, and just do my editing in notepad++ or the like. That said, @Thad_House might be able to give you some useful advice on how to get it less-broken.
It’s actually not a Gradle issue, it’s just that occasionally the vscode engine gets confused. Follow the following steps to try and reset everything.
Make sure you’re not getting any popups saying you’re in the wrong folder when opening vscode, or any other popups.
Make sure you didn’t accidentally create a c_cpp_properties.json file in the .vscode folder. It breaks everything. If it’s there, delete it.
Close all files in vscode. Leave vscode open.
Run the refresh c++ intellisense command in vscode.
Once that finishes, in the bottom right you should see something that looks like a platform (linuxathena or windowsx86-64 etc). If it’s not linuxathena click it and set it to one of the linuxathena one.
Wait one minute (yes one whole minute don’t skip this)
Open your main cpp file (not a header file). Intellisense should now be working.
Not closing vscode while doing this is key, closing it will reset the process. You just have to close all the tabs.
I gave up on using vscode. Instead I added the visual-studio plugin to gradle which allows me to generate a solution that I can open in vs community. You have to regenerate whenever you add a new file but it works reaaallllyyy well compared to vscode.