Google Git
Sign in
pigweed/third_party/github/bazelbuild/rules_cc/9aad5c688ca8d5bef4b5f14b9cfbb0d829bf0ccd
commit
9aad5c688ca8d5bef4b5f14b9cfbb0d829bf0ccd
[log] [tgz]
author
Googler <noreply@google.com>
Thu Feb 19 10:30:02 2026 -0800
committer
Copybara-Service <copybara-worker@google.com>
Thu Feb 19 10:30:27 2026 -0800
tree
8f2dbfe08b5921c838240e874729519205f7dd6e
parent
447370ac7d5f2830554fcd678c405445f9601a5d [diff]
Fix the behavior of copybara-comment-this-out-please, add a reverse form of it.

On the OSS side this should:
* Comment out a line in an example
* Remove unused comments in //rules_cc/cc/toolchains/actions/BUILD
* add a comment to find_cc_toolchain.bzl but otherwise be a no-op

Right now there's a lot of files with tiny diffs between OSS and Google, this should make refactoring them easier.

PiperOrigin-RevId: 872461034
Change-Id: I6d4dd44ecc92c6a65d8dfa608dc68945a88c63f0
3 files changed
tree: 8f2dbfe08b5921c838240e874729519205f7dd6e
  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. MODULE.bazel
  19. README.md
  20. renovate.json
  21. WORKSPACE
  22. WORKSPACE.bzlmod
README.md

C++ rules for Bazel

  • Postsubmit Build status

This repository contains a Starlark implementation of C++ rules in Bazel.

The rules are being incrementally converted from their native implementations in the Bazel source tree.

For the list of C++ rules, see the Bazel documentation.

Getting Started

Add the following to your WORKSPACE file:

load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")

http_archive(
    name = "rules_cc",
    urls = ["https://github.com/bazelbuild/rules_cc/archive/refs/tags/<VERSION>.tar.gz"],
    sha256 = "...",
)

Then, in your BUILD files, import and use the rules:

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

cc_library(
    ...
)

Using the rules_cc toolchain

This repo contains an auto-detecting toolchain that expects to find tools installed on your host machine. This is non-hermetic, and may have varying behaviors depending on the versions of tools found.

There are third-party contributed hermetic toolchains you may want to investigate:

If you'd like to use the cc toolchain defined in this repo, add this to your WORKSPACE after you include rules_cc:

load("@rules_cc//cc:repositories.bzl", "rules_cc_dependencies", "rules_cc_toolchains")

rules_cc_dependencies()

rules_cc_toolchains()

Migration Tools

This repository also contains migration tools that can be used to migrate your project for Bazel incompatible changes.

Legacy fields migrator

Script that migrates legacy crosstool fields into features (incompatible flag, tracking issue).

TLDR:

bazel run @rules_cc//tools/migration:legacy_fields_migrator -- \
  --input=my_toolchain/CROSSTOOL \
  --inline

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: