Google Git
Sign in
pigweed/third_party/github/bazelbuild/rules_cc/43ea010aa6070563dc75eb4b1d4cb732425e6a0e
commit
43ea010aa6070563dc75eb4b1d4cb732425e6a0e
[log] [tgz]
author
Googler <bgorshenev@google.com>
Wed Feb 25 07:16:55 2026 -0800
committer
Copybara-Service <copybara-worker@google.com>
Wed Feb 25 07:17:27 2026 -0800
tree
c72b6af00eee2baf9c1d6e48e6d9ad3dd2ee11d8
parent
38517fb1eb1333517b5a4e9bbaa169027b7a5988 [diff]
Cut cc_common dependencies from split build rules.

Once we switch to deferred implementation, this will reduce the impact of changes transitively affecting cc_common and similar files (i.e. a change affecting cc_common will affect java rules importing rules_cc but not affect every cc_binary in the repo).

The rules whose declaration/definition have been split will now no longer transitively depend on cc_common or cc_helper; this requires splitting find_cc toolchain and cc_postmark, as well as moving a function that's used only in cc_shared_library out of cc_helper.
The side of find_cc_toolchain and cc_postmark that still needs cc_common also loads the more lightweight side, making this change a no-op for any files not included in the change.

PiperOrigin-RevId: 875149689
Change-Id: I71b5cf5575b02cf9a8def11fb2a20d1624567979
10 files changed
tree: c72b6af00eee2baf9c1d6e48e6d9ad3dd2ee11d8
  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: