Google Git
Sign in
fuchsia / third_party / github.com / bazelbuild / rules_cc / refs/heads/upstream/main
commit6f0ade9d4d0cef4c41e48b115f719f65dd851026[log] [tgz]
authorCorentin Kerisit <corentin.kerisit@gmail.com>Fri Jan 30 10:03:25 2026 -0800
committerCopybara-Service <copybara-worker@google.com>Fri Jan 30 10:04:03 2026 -0800
treee226c5b844bf74484c2dca844d09a0f172f84ae5
parent1fd961973e1c3ea005cb16cbfa1f017258c50f8a [diff]
[rule base toolchains] Set missing none_of field of FeatureConstraint

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

BEGIN_PUBLIC
[rule base toolchains] Set missing none_of field of FeatureConstraint (#372)

Not setting this field crashes in `convert_args` if the feature constraint was provided by a `cc_tool_capability`.

Closes #372
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/372 from cerisier:cerisier/ensure-none-of-depset ed0da73f0e92f6fee6b5945b328b73b1178a0cf5
PiperOrigin-RevId: 863285620
Change-Id: I304e1227e19a1f16c94e1c5c55d791447be121f7
1 file changed
tree: e226c5b844bf74484c2dca844d09a0f172f84ae5
  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: