vscode-clangd VS cmake-init

Thanks for your reply, maybe I should go to vscode-clangd community to try to find out how they implement this:)

But I will say that I am mostly happy with either one of the clangd and ccls plugins. The clangd plugin is nicely packaged with a self-installer. The ccls plugin takes a little more work to set up, but it has loads more features. Both are quite good at working with a proper AST. Both build the AST by actually compiling your code with libclang (llvm's compiler core). Both work reliably for me because I am able to provide a compile_commands.json using my project builder (ninja). Nice as it is, it does not update automatically, and I'm not sure I want it to.

For C# there is https://github.com/muhammadsammy/free-omnisharp-vscode for Python there is https://github.com/Microsoft/pyright (Pylance is the proprietary counterpart) for C++ there is https://github.com/clangd/vscode-clangd

https://github.com/friendlyanon/cmake-init This is how you do CMake properly. If you deviate from its install rules you are highly likely to do something wrong.

CMake itself is as declarative as a build systems need to be. For anything nontrivial, these "declarative" solutions all fall apart. Just use https://github.com/friendlyanon/cmake-init, learn CMake and you won't have any issues.

If you want something with a (mostly) Just Works experience then just use https://github.com/friendlyanon/cmake-init

For CMake basics check out the official "Getting started" tutorial: https://cmake.org/cmake/help/latest/guide/tutorial/index.html, as well as Introduction to Modern CMake. You can also get inspired by the CMake project generator cmake-init

You can just use https://github.com/friendlyanon/cmake-init to get a CMake + Conan C project ready to go with a short little command: cmake-init --c -e -p conan coolio