Google Git
Sign in
pigweed/third_party/github/bazelbuild/rules_cc/bd5fb786f62442cd7da73cb28ecc53ae950f1c07
commit
bd5fb786f62442cd7da73cb28ecc53ae950f1c07
[log]
author
Googler <hvd@google.com>
Thu Dec 11 07:32:29 2025 -0800
committer
Copybara-Service <copybara-worker@google.com>
Thu Dec 11 07:33:09 2025 -0800
tree
a194db38ee7ff5fe0b5eccfe1c35c0ba369c555c
parent
5ca8dd0385d4c9b272e361e60f72d616ce895966 [diff]
Automated rollback of commit d9f1178c796ee3a83a7bcaf6445601ce617b8fde.

*** Reason for rollback ***

Re-enable testing with latest rolling release

*** Original change description ***

Disable rolling releases

They need to catch up to head, so that we're able to remove cc_common. HEAD at the moment covers everything.

PiperOrigin-RevId: 843215669
Change-Id: I2fe5a958d5518c412a5a5b4d1cb16673e0f12369
1 file changed
tree: a194db38ee7ff5fe0b5eccfe1c35c0ba369c555c
  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: