cxx-static-shared-example VS ccls

Anyone can create a library using cmake-init. This example goes into a little more detail and while it's for C++, the very same things apply sans a single target property on the library.

Thanks, I noticed a project friendlyanon/cxx-static-shared-example that have feature I didn't used.

https://github.com/friendlyanon/cxx-static-shared-example explains how to do libraries correctly, https://github.com/friendlyanon/cmake-init gives you a template that's ready to go. If something is not clear, ask away.

Here is an example going deeper into how to create a shared library using CMake: https://github.com/friendlyanon/cxx-static-shared-example You'd have to do these regardless of CMake, this just shows how to do it with it.

This example is more focused on explaining on the what and why.

Or if you are also packaging .deb then you're going to need a toolchain anyway, you can put these variables there as well.

To learn how to write a CML that is ideally written to be easy for both consumers building the library, developers developing the library and consumers vendoring the library via add_subdirectory (which will be a very very important thing to do in the near future), please check out this educational example repository https://github.com/friendlyanon/cxx-static-shared-example

This repo will show you how to make your project CML for an easy to (re)use library that supports packaging.

CMake's what you want. You need to know how separation of concerns applies when it comes the lists files. Resources in general suck, the CMake docs are not really discoverable, but are very good otherwise. You can get a handle of how things are supposed to be put together here.

cxx-static-shared-example - 50 lines for requirements + however many for sources + 60 for install rules: now this is a library that builds some artifacts. Still extremely simple and straightforward.

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