Summary

Generate compile_commands.json for any C or C++ build

• Install Bear

Tutorials

• Getting started with Bear
• Build an autotools project under Bear
• Recover compile_commands.json from a build log

Guides

• Recipes
  • Generate compile_commands.json for a Makefile project
  • Generate compile_commands.json for a CMake project
  • Capture a complete dry run for bear parse-sh
  • Bear produces an empty compile_commands.json
  • Set up clangd for a project without CMake
  • clangd has no compile command for a header
  • Use Bear with ccache, distcc, or icecc
  • Run Bear inside a Docker container
  • Generate compile_commands.json when cross-compiling
  • Intercept a 32-bit build on a 64-bit host
  • Generate compile_commands.json for an STM32 or arm-none-eabi project
  • Use Bear with a vendor embedded toolchain
  • Generate compile_commands.json for an Emscripten project
  • Generate compile_commands.json for a CUDA project
  • Use Bear with Intel oneAPI compilers
  • Use Bear with Cray and NVIDIA HPC compilers
  • Generate compile_commands.json for an MPI project
• Troubleshooting

Reference

• Command-line options
• Configure Bear
• Supported compilers
• Exit status

Understanding Bear

• How Bear works

Platform notes

• Bear on Linux, WSL2, and Docker
• Bear on macOS
• Bear on Windows
• Bear on BSD