ccls VS Bear

Then it would just have a dependency on Clang, and you couldn't use Emacs at all (since you can't use Clang).

AFAIK, the only alternative to the clangd language server is ccls: https://github.com/MaskRay/ccls

The base config adds about 15 lines (I have extra settings adding another 15 lines), then each language server adds a few lines per augroup. Example config for ccls.

"" https://github.com/MaskRay/ccls/wiki/vim-lsp if executable('ccls') augroup lsp_ccls ....

Try ccls instead, it has setup instructions for many LSP clients in the wiki: https://github.com/MaskRay/ccls

vim-lsp and ccls, supertab for auto-completion

these days a good lsp plugin will get you 90% of what you need for most languages and codebases. once youve got that set up its just a matter of picking lsp servers. i use ccls for c/c++. if you set it up and its not giving you hints for godot classes you probably have to point ccls at the proper godot-cpp subdirs using a .ccls file in your project root.

I installed ccls using snap for ubuntu.

C++/C language server: ccls

ccls: https://github.com/MaskRay/ccls/issues/798

Have you tried Bear? I used it for several projects and overall it works very well.

An update: I am now able to make everything work by generating `compile_commands.json` using compiledb. I'm aware that there is another tool Bear but for some reason it generates an empty `compile_commands.json` file for me.

Try https://github.com/rizsotto/Bear

Regarding the libraries, you might need to add it to clangd’s configuration. A convenient way is to have a compile_commands.json in your project (this is generated by some build tools like CMake, but if you don’t use them, have a look at bear).

Note that you need to have a compile_commands.json file. That file can easily be generated by CMake, Meson, etc. For other build systems checkout Bear https://github.com/rizsotto/Bear

make a 'gcc' command/executable that do nothing and make it first in your PATH and then run bear with make: https://github.com/rizsotto/Bear/issues/219 It is unfortunate that bear doesn't catch the output of the make command with '--dry-run' as it still prints the compile commands, it seems not that hard to support this and I think many ppl would benefit..

You could try to start with Bear: https://github.com/rizsotto/Bear In worst cases, I had to use strace to catch every gcc/g++ invocation and restructure the compile_commands.json out of the strace logs.

But it sounds like maybe you’re assuming for the purposes of using something like clangd (highly recommended for coding in cpp projects in general, you want to be using this in vscode or whatever else anyway, codelion notwithstanding I suppose) with neovim on a c++ project that you have to use cmake to produce a compilation database to use with neovim plugins (e.g. clangd via nvim-lsp et. al.). In this case, be aware that the https://github.com/rizsotto/Bear tool is a handy way to just tack it on to whatever command you’re using to run a c++ code build step, and it will give you a compile_commands.json, corresponding to the compiler commands it invoked, on a silver platter.

I guess your questionmarks are about installing "bear", he refers to this project: https://github.com/rizsotto/Bear

You just simply go to the root of your project, use bear and just open your C files. That's all.