Google Git
Sign in
pigweed/third_party/github/bazelbuild/rules_cc/d02965274841a27e85156d3b417c7c178bb4eaf1
commit
d02965274841a27e85156d3b417c7c178bb4eaf1
[log]
author
David Zbarsky <dzbarsky@gmail.com>
Sun Jul 12 17:55:29 2026 -0700
committer
Copybara-Service <copybara-worker@google.com>
Sun Jul 12 17:55:54 2026 -0700
tree
766d28cac91681e6b3d0ce4450cc970017919f58
parent
0cc41d6d652bfb6fca57b2f22db9b6d965727b39 [diff]
Cache rule feature lists

Copybara Import from https://github.com/bazelbuild/rules_cc/pull/767

BEGIN_PUBLIC
Cache rule feature lists (#767)

## Summary

`ctx.features` and `ctx.disabled_features` allocate a new list on every access. Cache those lists in `cc_binary`, `cc_library`, `objc_library`, and `objc_import`, then pass the cached lists through the existing feature-configuration helpers.

This reduces `ctx.features` accesses from up to five to one for `cc_binary`/`cc_test`, from up to four to one for `cc_library`, and reduces both property accesses from four to one for `objc_library` and from two to one for `objc_import`. Optional helper arguments preserve behavior for existing external callers.

## Validation

- `buildifier -mode=check` on all changed Starlark files
- `bazel test --jobs=4 --test_output=errors //tests/cc/common:cc_common_tests //tests/cc/common:cc_binary_configured_target_tests //tests/cc/common:cc_objc_library_configured_target_tests`

Closes #767
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/767 from dzbarsky:codex/cache-rule-feature-lists bb77beecd459b49f9cd3843aabff75c1dbe139bc
PiperOrigin-RevId: 946714345
Change-Id: Id2e333dc8935c6b11e78327992dc79da22780f8b
6 files changed
tree: 766d28cac91681e6b3d0ce4450cc970017919f58
  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: