Bear
compiledb
Bear | compiledb | |
---|---|---|
52 | 6 | |
4,978 | 1,360 | |
- | - | |
8.6 | 0.0 | |
2 days ago | 3 months ago | |
C++ | Python | |
GNU General Public License v3.0 only | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Bear
- Bear is a tool that generates a compilation database for Clang tooling
-
Visual Studio Code is designed to fracture
There are generators for the compilation databases that work with Makefiles and other build systems, like Bear: https://github.com/rizsotto/Bear
-
emacs lsp-mode with MPLAB X project
Have you tried Bear? I used it for several projects and overall it works very well.
-
Eglot + clangd not working for NetHack code base
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 an existing legacy build system. How do I leverage this with CLion to index my project?
Try https://github.com/rizsotto/Bear
-
New User C Setup Help?
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).
-
vscode alternative for C++ on M1 mac?
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
-
I hope that cscope can make a comeback in the versions after 0.9
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..
-
CLion 2023.1 released
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.
-
Is CMake necessary to set up a C++ "IDE" in neovim?
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.
compiledb
-
Eglot + clangd not working for NetHack code base
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.
-
STM32CubeIDE extract compile_commands.json
I have tried compiledb as well, but it currently fails to correctly get the backslashes correctly on Windows, as noted in this issue.
-
Lsp-mode when I can't generate compile_commands.json
There is also this tool which claims to support Windows. However:
-
clangd beginner problem
There is also compiledb https://github.com/nickdiego/compiledb that works directly with your make file to generate the compile_commands.json.
-
How can I get vim-lsp to recognize OpenCV?
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.
-
CLion users: Is CLion a good choice for development in an old project that can only be built with a complicated mess of makefiles?
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
What are some alternatives?
vscode-cpptools - Official repository for the Microsoft C/C++ extension for VS Code.
conan - Conan - The open-source C and C++ package manager
NvChad - Blazing fast Neovim config providing solid defaults and a beautiful UI, enhancing your neovim experience.
Cython - The most widely used Python to C compiler
scan-build - Clang's scan-build re-implementation in python
gcovr - Generate code coverage reports with gcc/gcov
clangd - clangd language server
coc-clangd - clangd extension for coc.nvim
project-cmake - Emacs extension to the project package for supporting CMake as build system.
ccls - C/C++/ObjC language server supporting cross references, hierarchies, completion and semantic highlighting
pmbuild - A simple, configurable and extendible build system for gamedev.