We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I am using the plug-in for ESP-IDF development and for the most part it works well.
The only issue is that apparently the ESP-IDF toolchain uses some commands not known to clangd:
Unknown argument '-mlongcalls'; did you mean '-mlong-calls'? Unknown argument: '-fno-shrink-wrap' Unknown argument: '-fno-tree-switch-conversion' Unknown argument: '-fstrict-volatile-bitfields'
And of course those show up for every source file.
So I wonder if I could add an ideally project-specific clangd configuration like so:
CompileFlags: Add: -Wno-unknown-warning-option Remove: [-m*, -f*]
The text was updated successfully, but these errors were encountered:
Turns out .clangd in any parent directory of the source file in question will work.
.clangd
Sorry for the noise!
Sorry, something went wrong.
Thanks for this nice plugin!
Turns out .clangd in any parent directory of the source file in question will work. Sorry for the noise!
No worries! I did not know this, that's good info, and glad you got it working.
No branches or pull requests
I am using the plug-in for ESP-IDF development and for the most part it works well.
The only issue is that apparently the ESP-IDF toolchain uses some commands not known to clangd:
And of course those show up for every source file.
So I wonder if I could add an ideally project-specific clangd configuration like so:
The text was updated successfully, but these errors were encountered: