Hi all -
Is there a way to get the "go to definition" command to exclude the IDF components? On my system, if my application uses a symbol name that is also found in the IDF, it finds those instead of the one in my own code.
Thanks...
VS Code "go to definition" includes IDF
-
- Posts: 229
- Joined: Wed May 02, 2018 12:12 pm
Re: VS Code "go to definition" includes IDF
You should update the <project-directory/.vscode/c_cpp_properties.json file as shown in c_cpp_configuration documentation. The best configuration is usually the one using the compile_commands.json but you could remove/update those browse paths in ESP-IDF components.
EDIT: Apologies, wrong url formatting.
EDIT: Apologies, wrong url formatting.
Re: VS Code "go to definition" includes IDF
Thanks, bignacio. Does the file compile_commands.json have to reside in the build directory? I'd like it to be a bit more permanent.
Re: VS Code "go to definition" includes IDF
There's something about the build process I still don't understand. If I do a clean, I get build errors when I try to build from within the IDE. Running idf.py build fixes that, but it also wipes out my compile_commands.json file, and replaces it with about 4800 lines including a ton of files from the IDE. Do you have any idea why this is happening?
Thanks...
Thanks...
Who is online
Users browsing this forum: No registered users and 35 guests