Google Git
Sign in
bazel / rules_cc / refs/heads/main
commit61f75162216266f75304ec04d398115aa20a9219[log] [tgz]
authorXavier Bonaventura <xavibonaventura@gmail.com>Mon Feb 09 19:04:48 2026 -0800
committerCopybara-Service <copybara-worker@google.com>Mon Feb 09 19:05:18 2026 -0800
tree37101461d4d506a6e6e6074f7370e12de9fc8640
parent20bf72d587383f2dc645f957b6ae48bfb9b33202 [diff]
Modify template for generated toolchain to be more buildifier compliant

Copybara Import from https://github.com/bazelbuild/rules_cc/pull/596

BEGIN_PUBLIC
Modify template for generated toolchain to be more buildifier compliant (#596)

There are situations where the user might want to reuse the  generated file for creating their own toolchain.
Making it as much buildifier compliant as possible, it helps for later to see the differences if needed.
It is not always possible or easy to make sure that the generated file is buildifier compliant. However, there are some changes that are quite easy to apply. This commit apply some of these changes.

Closes #596
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/596 from limdor:patch-1 3f786913e0d30ea256fd5d54cc3c5a79acb747c1
PiperOrigin-RevId: 867875010
Change-Id: I0ae778bba94652c2b890f88034f88bf0cab2c9e9
1 file changed
tree: 37101461d4d506a6e6e6074f7370e12de9fc8640
  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: