Google Git
Sign in
bazel/rules_cc/6c1531cd5f17951f6bf574f542fce5a1fb41260e
commit
6c1531cd5f17951f6bf574f542fce5a1fb41260e
[log]
author
Lukasz Anforowicz <lukasza@google.com>
Wed Sep 02 18:47:37 2026 -0700
committer
Copybara-Service <copybara-worker@google.com>
Wed Sep 02 18:48:57 2026 -0700
tree
576e9dca545a0c34977b9bd4d5396969cc7e06f0
parent
4dfe8a328d92b6eb2fdf301b66aaedfb5c42320c [diff]
Add `ACTION_NAMES.cpp_header_analysis` to `ALL_CPP_COMPILE_ACTION_NAMES`.

`c++-header-analysis` actions parse and analyze C++ header files and
require the standard C++ compiler/preprocessor flags (include
directories, language standard, sysroot, defines) like other C++
compilation actions.  In addition to being desirable in general, this
specifically ensures that Crubit (`rs_bindings_from_cc`) actions work
out of the box with all expected C/C++ compilation flags.

This change:
* Adds `ACTION_NAMES.cpp_header_analysis` to
  `ALL_CPP_COMPILE_ACTION_NAMES` in `rules_cc`.
* Ensures `ACTION_NAME_GROUPS.all_cpp_compile_actions` and
  `all_cc_compile_actions` include header analysis by default.
* Re-exports `ACTION_NAMES.rs_bindings_from_cc` in
  `tools/build_defs/cc/action_names.bzl` as an alias of
  `CPP_HEADER_ANALYSIS_ACTION_NAME`.
* Cleans up `devtools/crosstool/ndk/crosstool.bzl` to inherit header
  analysis via `ACTION_NAME_GROUPS`.

Startblock:
  * // Put other blockers before this line to avoid churning.
  * has lgtm
  * is approved
  * and then
  * all comments are resolved
  * and then
  *[] allows unknown commit
PiperOrigin-RevId: 975444194
Change-Id: I4a2a08bdb391b7cdbec9ae2fa91214d8b74f1cc4
1 file changed
tree: 576e9dca545a0c34977b9bd4d5396969cc7e06f0
  1. .bazelci/
  2. .bcr/
  3. .github/
  4. cc/
  5. docs/
  6. examples/
  7. tests/
  8. .bazelignore
  9. .bazelrc
  10. .gitignore
  11. AUTHORS
  12. BUILD
  13. CODEOWNERS
  14. CONTRIBUTING.md
  15. googletest.patch
  16. ISSUE_TEMPLATE.md
  17. LICENSE
  18. local_bazel.bzl
  19. MODULE.bazel
  20. README.md
  21. WORKSPACE
  22. WORKSPACE.bzlmod
README.md

C++ rules for Bazel

  • Postsubmit Build status

This repository contains C, C++, and Objective-C language support for the Bazel build system.

For this module's main reference, see the Bazel documentation.

Get Started

Install Bazel

Follow the official instructions to Install Bazel.

Add rules_cc to your MODULE.bazel

Add the latest release to your MODULE.bazel project file.

Declare a build target

In a BUILD.bazel file, import and use the rules:

load("@rules_cc//cc:cc_binary.bzl", "cc_binary")

cc_binary(
    name = "hello_world",
    srcs = ["hello_world.cc"],
)

Build and run your project

Build and run your C/C++ binary with one command:

$ bazel run hello_world

To build the project without running the binary, use Bazel's build subcommand:

$ bazel build hello_world

Toolchains

Default autoconfigured toolchain

rules_cc includes an auto-configured toolchain that uses the local compiler installed on the host machine.

You can disable the autoconfigured C/C++ toolchain by adding the following Bazel flag to your project's .bazelrc file:

--repo_env=BAZEL_DO_NOT_DETECT_CPP_TOOLCHAIN=1

Hermetic toolchains

Configuring a hermetic toolchain makes your build more deterministic. rules_cc itself does not yet offer a hermetic toolchain distribution. Other community owned and maintained projects offer hermetic C/C++ toolchains:

Contributing

Bazel and rules_cc are the work of many contributors. We appreciate your help!

To contribute, please read the contribution guidelines: CONTRIBUTING.md.

Note that the rules_cc use the GitHub issue tracker for bug reports and feature requests only. For asking questions see: