compiledb
compdb
compiledb | compdb | |
---|---|---|
6 | 4 | |
1,406 | 304 | |
2.1% | 1.3% | |
0.0 | 0.0 | |
5 months ago | 11 months ago | |
Python | Python | |
GNU General Public License v3.0 only | MIT License |
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.
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
compdb
-
Currently working through learncpp.com and clangd doesn't agree with some of the things suggested on the site?
The way to do this is to create a so-called compilation database file which is a json file containing info about the source files in your project. The easiest way to generate such a file is to use CMake and set the CMAKE_EXPORT_COMPILE_COMMANDS variable. Also: cmake won't include header files in this file, so you need to add those manually or by using a tool like compdb.
-
Can't clangd in cmake (already enabled export compile command) work out of the box?
After you generate your compilation database, can you use compdb and see if there is any difference?
-
Working on a header-only library with cmake and clangd
Anyway, the solution is to add a post-processing step that adds the header files to the generated .json using e.g. compdb.
-
Why does indexing the emacs source code repository with clangd have so many errors?
I'm definitely familiar with getting clangd up and running with a compile_commands.json file. I'm just now looking into https://github.com/Sarcasm/compdb. Maybe that'll solve the enormous amount of errors? I have no idea
What are some alternatives?
Bear - Bear is a tool that generates a compilation database for clang tooling.
Aphrodite - Vulkan-based graphics framwork designed for game development and graphics applications on Linux.
conan - Conan - The open-source C and C++ package manager
scan-build - Clang's scan-build re-implementation in python
gcovr - Generate code coverage reports with gcc/gcov
pre-commit-hooks - C/C++ hooks to integrate with pre-commit
run-clang-format - A wrapper script around clang-format, suitable for linting multiple files and to use for continuous integration
bazel-compile-commands-extractor - Goal: Enable awesome tooling for Bazel users of the C language family.
pmbuild - A simple, configurable and extendible build system for gamedev.
codechecker - CodeChecker is an analyzer tooling, defect database and viewer extension for static and dynamic analyzer tools.