<!-- Diataxis type: landing (navigation page, not one of the four types) --> <!-- The links below are absolute on purpose. GitHub Pages serves this page for any path that does not exist, including deep ones such as /Bear/recipes/gone/, and mdBook renders Markdown links here as relative URLs, which would then resolve against that missing directory. Keep these as /Bear/... and keep them in step with site-url in book.toml. -->

Page not found

That page does not exist, or it moved. The documentation was reorganized when it moved out of the project wiki, so a link from an older issue, forum post, or search result may point at a page that is now somewhere else.

Where things are now:

• Generate compile_commands.json for any C or C++ build - the home page, and the shortest path to the rest.
• Getting started with Bear - install, run a first build, point clangd at the result.
• Recipes - one page per task: build systems, containers, compiler launchers, and each supported toolchain.
• Bear produces an empty compile_commands.json and Troubleshooting - when the output is wrong.
• How Bear works - the mechanism behind the results.

The complete reference for command-line options and configuration keys is the bear(1) man page. If you followed a link from somewhere and landed here, the issue tracker is the place to report it.