Google Git
Sign in
bazel / rules_cc / 02a9a1c5b4c8e9664df76604d20a7b5918bcf286
commit02a9a1c5b4c8e9664df76604d20a7b5918bcf286[log] [tgz]
authorGoogler <hvd@google.com>Thu Aug 21 03:06:35 2025 -0700
committerCopybara-Service <copybara-worker@google.com>Thu Aug 21 03:07:09 2025 -0700
tree517731179af6dfb3cb6a6e600c9149f3d766e7b5
parent8827fd4a8a91d0258f25add3d91e5470eb05b49b [diff]
Prepare for Starlark `CcToolchainConfigInfo`

 - Make all starlark accessible members struct fields. This is necessary because the config is written to a file via `proto.encode_text` which errors out on functions for `StarlarkInfo`. (`NativeInfo` is special-cased to ignore methods)
 - Stop converting tool paths and make variables to pairs/tuples to match the eventual Starlark implementation.
 - Update tests to access `CcToolchainConfigInfo` via the provider type instance instead of the provider key. This will allow using a `StarlarkProviderWrapper` for the Starlarkified provider.

PiperOrigin-RevId: 797683393
Change-Id: Icbc8d6c9b115a576bde3b1c3a9f2e753738969b3
1 file changed
tree: 517731179af6dfb3cb6a6e600c9149f3d766e7b5
  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. ISSUE_TEMPLATE.md
  16. LICENSE
  17. MODULE.bazel
  18. README.md
  19. renovate.json
  20. WORKSPACE
  21. 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: