Nathan Ridge

@thokra1 Another way to integrate with vscode-cmake-tools that you might find interesting is https://github.com/sr-tream/vscode-clangd-cmake. My understanding is that this sends the compile commands of the relevant configuration to the language...

> Generally speaking, would it be feasible to provide an integration of `llvm-vs-code-extensions.vscode-clangd` with `vscode-cmake-tools`? The likelihood that a C/C++ developer using VS Code will use `vscode-cmake-tools` is pretty high,...

> I thought it would be nice to let `llvm-vs-code-extensions.vscode-clangd` talk to `vscode-cmake-tools` directly if both are active. I'd rather the official thing support common use cases than having to...

Please post clangd logs as instructed in the issue template. Also, please share reproducing code in text form.

So is the issue with "go to definition", or "find references"? (It's not clear to me because the issue's title mentions "go to definition" but the video is showing "find...

> you can reproduce by cloning https://github.com/jendrikw/pokeemerald, checking out the clangd branch and opening `include/metatile_behaviour.h` in vscode. You didn't mention anything about generating a `compile_commands.json` file. Please have a look...

Thanks for the added context. Note that if a project's code cannot be compiled with clang, clangd may not work well either, since clangd uses the clang frontend to analyze...

Linking to patch written by @ADKaster: https://reviews.llvm.org/D145843

> The heuristic without additional configuration: use triangular brackets if a header is on either `-i` or `-I` search path, else use double quotes. Yeah, I expect that would align...

Clangd expects to get information about include paths from a `compile_commands.json` file, as described at https://clangd.llvm.org/installation#project-setup. This file is intended to be generated by the build system, and should reflect...