Nathan Ridge

> You are in luck, I've started adding it as of the 202407 pack forwards. Please can you give it a quick test on a few arbitrary commits to make...

> FYI [@HighCommander4](https://github.com/HighCommander4) -- [elfshaker/elfshaker#150](https://github.com/elfshaker/elfshaker/pull/150) fixed a bug which means commits which only modified clang-tools-extra would be omitted. From August 2025 onwards they'll be included. Thanks for the heads up...

> If you want to have a go it's in contrib in the elfshaker repo. > > [...] Thanks! I think I got it to work; PR at https://github.com/elfshaker/elfshaker/pull/152.

I haven't looked into the specifics here, but I've seen issues like this caused by an out of date clangd index. It's worth ruling that out by deleting the project's...

Please have a look at [this FAQ entry](https://clangd.llvm.org/troubleshooting#cant-find-standard-library-headers-map-stdioh-etc): > If you’re using an unusual compiler (e.g. a cross-compiler for a different platform, or MinGW on Windows) you may want to...

> But it still fails to do so when I click on the `printf` function. What does happen -- it goes to MSVC headers? Or it does not navigate anywhere?...

This line looks suspicious: > E[21:15:35.989] System include extraction: invalid target "mingw32", ignoring Can you run `C:\MinGW\bin\gcc.exe -E -v -xc -` in a terminal and share its output?

Thanks. Indeed it should have been `-E`, my bad. I don't know much about Windows, but the `Configured with: [...] --target=mingw32`, which leads to the clangd message `invalid target "mingw32",...

Previous discussion of this: https://github.com/clangd/clangd/discussions/1940

See also #966 for another suggestion for customizing how documentation comments near a declaration are discovered