Nathan Ridge
Nathan Ridge
The "invalid AST" error is downstream of `error: unknown target CPU 'avr128db48'`. As you observe, clang does not support this exact target. But for code editing purposes, a similar one...
> How can I use the clangd service without upgrading glibc? You could try building it from source. Instructions can be found at https://github.com/llvm/llvm-project/tree/main/clang-tools-extra/clangd#building-and-testing-clangd.
Clangd should still be picking **some** source file from the compilation database to infer compile commands from for a header. The issue in this ticket, is that it sometimes infers...
(Updated issue title to reflect more specifically what this issue is about.)
> I don't have any C++ files in my CDB and still Clangd is trying to parse an external header file as a C++ header with fallback flags. Here are...
@njames93 Yes, I think a heuristic based on actual inclusion relationships would be the "proper" solution here.
> In the case I reported, clangd did find a CDB, but it did not find a rule for the opened file in it, because the opened file was a...
Please share [clangd logs](https://clangd.llvm.org/troubleshooting.html#gathering-logs) for further diagnosis.
> As long as it includes exporting to C++for use, the C source file will complete the C++header file Is the `extern "C" {` rendered at a reduced opacity (or,...
I at least don't see an obvious culprit in the logs, such as a C file being processed with flags taken from a C++ file. (For example the line: ```...