Google Git
Sign in
pigweed/third_party/github/bazelbuild/rules_cc/2993fd1c7472495a39a27e11f6d8807d82046eb8
commit
2993fd1c7472495a39a27e11f6d8807d82046eb8
[log]
author
Keith Smiley <keithbsmiley@gmail.com>
Fri Apr 17 11:13:06 2026 -0700
committer
Copybara-Service <copybara-worker@google.com>
Fri Apr 17 11:13:32 2026 -0700
tree
17ec47ecfbb3c5ff652cda4b7df828e0ccc24718
parent
cab707163687334903cc6d087c823081feebffda [diff]
Remove uses of bazel_features ge

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

BEGIN_PUBLIC
Remove uses of bazel_features ge (#691)

We want to use the cc specific one for this instead, this replaces all our
incorrect uses

Closes #691
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/691 from keith:ks/fix-bazel_features-test-issue 46541c1b8eaffb47124ff26a365df6538445d32c
PiperOrigin-RevId: 901383847
Change-Id: Iaddc952febb1af18538f7e1132d2d74341e1a3f1
2 files changed
tree: 17ec47ecfbb3c5ff652cda4b7df828e0ccc24718
  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: