bear

bear [options] -- build-command

bear (Build EAR) generates a compilation database (compile_commands.json) by intercepting compiler calls during a build. This database enables tools like clangd, clang-tidy, and IDEs to understand the project structure without custom configuration.The tool works with any build system by recording actual compiler invocations. From version 3 onward, the build command must be separated from bear's own options by a `--`; older 2.4.x packages omit it.

-o file, --output file

Output file (default: compile_commands.json)

Append results to an existing database instead of overwriting it

Read settings (output formatting, compiler/source filters) from a configuration file

Print help information

Print version information

- Build system agnostic- Intercepts compiler calls- Supports parallel builds- Works with make, ninja, etc.- No build system modification needed

Generated compile_commands.json format:

$ [
  {
    "directory": "/path/to/project",
    "command": "gcc -c file.c -o file.o",
    "file": "file.c"
  }
]

Requires running full build. May not capture all compilation units if cached. Some build systems have native support (CMake: -DCMAKEEXPORTCOMPILE_COMMANDS=ON). Different interception methods on different platforms.

bear was created by László Nagy (rizsotto) around 2012 to generate compilation databases for C/C++ projects using any build system. Version 3 introduced the `--` separator syntax, and version 4 rewrote the tool in Rust.

compiledb(1), cmake(1), clangd(1), make(1), ninja(1), clang(1)

Source code · Documentation