Google Git
Sign in
pigweed/third_party/github/bazelbuild/rules_cc/9acfa2faed87ead08a12fc84859a52fc8b4ed4e8
commit
9acfa2faed87ead08a12fc84859a52fc8b4ed4e8
[log]
author
Googler <lberki@google.com>
Tue Jul 14 05:04:45 2026 -0700
committer
Copybara-Service <copybara-worker@google.com>
Tue Jul 14 05:05:44 2026 -0700
tree
1913631e5341a43a2a12a35a7b6d719073e4f3b5
parent
51784080f788bc816242bf1362d76cf14f306107 [diff]
Freeze libraries to link before interning them.

Otherwise, Blaze is susceptible to a race condition:

1. Node A creates a list ["x"] and interns it
2. Node B creates the same list ["x"] and interns it; it gets back a still mutable reference to the list created by node A
3. Node B finishes, freezes its Starlark data structures and puts a reference to the list (which is secretly created by Node A) into a provider
4. Node A adds "y" to the list
5. Now Node C (depending on Node B) will observe the values of the list as ["x", "y"], even though that's totally not what Node B intended

RELNOTES: None.
PiperOrigin-RevId: 947612088
Change-Id: I98fd1dadaaa0e0677577627ce63039599a72f66b
1 file changed
tree: 1913631e5341a43a2a12a35a7b6d719073e4f3b5
  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: