Google Git
Sign in
bazel/rules_cc/64024621393c26ff85d11f0d8e46bf92acbfee31
commit
64024621393c26ff85d11f0d8e46bf92acbfee31
[log]
author
Xavier Bonaventura <xavier.bonaventura@bmw.de>
Tue Feb 10 20:24:39 2026 -0800
committer
Copybara-Service <copybara-worker@google.com>
Tue Feb 10 20:25:01 2026 -0800
tree
86c58c16d3316d6d5e985cb348dc8976fbf3842a
parent
61f75162216266f75304ec04d398115aa20a9219 [diff]
Add support to inject cc_feature into legacy toolchains

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

BEGIN_PUBLIC
Add support to inject cc_feature into legacy toolchains (#525)

This adds a parameter to unix cc_toolchain_config and windows cc_toolchain_config to be able to inject a cc_feature. This allows a user to inject a feature (for example for custom warnings) without having to reimplement the full toolchain.

Resolves #517

Closes #525
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/525 from limdor:inject_features_support cbacde6ce16743d05e79824f9d86b0ec0611ccbf
PiperOrigin-RevId: 868449238
Change-Id: I407ece9fc8d308054f3e8dc59ca2cbc34e3d0f6b
3 files changed
tree: 86c58c16d3316d6d5e985cb348dc8976fbf3842a
  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: