Google GitGoogle Git
Sign in
bazel/rules_cc/refs/heads/main
commit
ebd996fd37eaa710fd5d90e1bfd1bcddafcac067
[log]
author
Googler <noreply@google.com>
Tue Oct 20 01:43:20 2026 -0700
committer
Copybara-Service <copybara-worker@google.com>
Tue Oct 20 01:44:06 2026 -0700
tree
21d53940fa0e7e7e093992109bf6696130c0f165
parent
b50a797b7dea422992b49424440167cd60ef4574 [diff]
Implement target allowlists in addition to package allowlists for disallowed copts policies.

Implement the design changes specified in design_banned_warnings.md and
design_modular_copts_policies.md:
- Update CcDisallowedCoptsInfo to provide package_allowlist, target_allowlist, and policy_label.
- Update cc_copts_policy to accept package_allowlist and target_allowlist.
- Update tools/cpp/policy/banned_warnings/BUILD to use package_allowlist.
- Update third_party/crosstool/v18/stable/crosstool_configuration.bzl and third_party/apple_crosstool/crosstool.bzl to forward package_allowlist, target_allowlist, and policy_label.
- Update cc_helper.bzl to exempt targets matching entries in package_allowlist and target_allowlist, and emit "disallowed by '<policy_label>'" in violation messages.
- Add and update unit tests in tools/cpp/policy/ and third_party/bazel_rules/rules_cc/tests/cc/common/.

Startblock:
  - BTRGuardian allows unknown commit

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: 1002924230
Change-Id: I35d1aefd0e0ecc47c81fa45c62481d534ca95a3f
5 files changed
tree: 21d53940fa0e7e7e093992109bf6696130c0f165
  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. CONTRIBUTING.md
  14. googletest.patch
  15. ISSUE_TEMPLATE.md
  16. LICENSE
  17. local_bazel.bzl
  18. MODULE.bazel
  19. README.md
  20. WORKSPACE
  21. 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: