compiledb VS project-cmake

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.

I have tried compiledb as well, but it currently fails to correctly get the backslashes correctly on Windows, as noted in this issue.

There is also this tool which claims to support Windows. However:

There is also compiledb https://github.com/nickdiego/compiledb that works directly with your make file to generate the compile_commands.json.

Have you generated a compile_commands.json? They're necessary for your LSP provider to know which paths to search for headers. They're generated by default if you're using CMake (I believe), otherwise check out compiledb or Bear.

If you can get compiledb to work with your make project and generate the correct file, it should be able to figure out project quite well

You might want to consider this software I wrote https://github.com/juanjosegarciaripoll/project-cmake

If you develop c++ you should use CMake. It handles many aspect of the language such as library dependencies, static checks, etc, very graciously. In that case you can use this https://github.com/juanjosegarciaripoll/project-cmake to handle both the project and clangd

My experience is that eglot identifies properly the project. Indeed, it uses internally Emacs' project package. However, it does not pass information about the project to the language servers. project-cmake's approach is a workaround to complement Eglot's arguments with information that is specific to one language server, but can be extended to others without much difficulty. I have also added a module to project-cmake that defines project-local variables which can help in doing a separate customisation for each project, also of the language servers themselves.