Skip to content
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

custom clangd configuration? #19

Closed
gknops opened this issue Jul 7, 2024 · 3 comments
Closed

custom clangd configuration? #19

gknops opened this issue Jul 7, 2024 · 3 comments

Comments

@gknops
Copy link

gknops commented Jul 7, 2024

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*]
@gknops
Copy link
Author

gknops commented Jul 7, 2024

Turns out .clangd in any parent directory of the source file in question will work.

Sorry for the noise!

@gknops gknops closed this as completed Jul 7, 2024
@gknops
Copy link
Author

gknops commented Jul 7, 2024

Thanks for this nice plugin!

@logancollins
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants