Is CMake necessary to set up a C++ "IDE" in neovim?

1. YCM-Generator

   1 1 922 10.0 Python

   Discontinued Generates config files for YouCompleteMe (https://github.com/Valloric/YouCompleteMe)

   Back in the days when I used YouCompleteMe there was a plugin called YCM-Generator that could use the output of certain make calls to build the information necessary for YouCompleteMe. Unfortunately, the YCM configuration is different from the configuration clangd wants.

2. Sevalla

   sevalla.com featured

   Deploy and host your apps and databases, now with $50 credit! Sevalla is the PaaS you have been looking for! Advanced deployment pipelines, usage-based pricing, preview apps, templates, human support by developers, and much more!

   

3. nvim-cmp

   2 257 9,069 7.9 Lua

   A completion plugin for neovim coded in Lua.

   

   Right now the standard plugin for autocompletion is https://github.com/hrsh7th/nvim-cmp

4. coc.nvim

   3 322 24,972 9.7 TypeScript

   Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.

   

   I'd say just try to copy that code from nvim-cmp readme as is (unless you're using a different package manager ofc) and see if it works for you. If you decide that you've spent too much time on it, you could give https://github.com/neoclide/coc.nvim a try instead. It has vim support as well, and as far as I know it comes with a lot of stuff included.

5. Bear

   4 53 5,799 8.1 C++

   Bear is a tool that generates a compilation database for clang tooling.

   

   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.

Suggest a related project