Google Git
Sign in
bazel / rules_cc / 2ed6b8d1a511ba84fba511aeb66743bd21df4d6b
commit2ed6b8d1a511ba84fba511aeb66743bd21df4d6b[log] [tgz]
authorFabian Meumertzheim <fabian@meumertzhe.im>Fri Aug 22 08:43:40 2025 -0700
committerCopybara-Service <copybara-worker@google.com>Fri Aug 22 08:44:11 2025 -0700
treee53d01d2a55f5614e5a18858020b52636b2570d1
parent02a9a1c5b4c8e9664df76604d20a7b5918bcf286 [diff]
Add `requires-darwin` in default test runner

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

BEGIN_PUBLIC
Add `requires-darwin` in default test runner (#421)

This was missed in 5202ddc05a30742fb0f3c09e354c3e840b636cc1 for parity with the legacy `cc_test` flow.

Closes #421
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/421 from fmeum:test-toolchain-requires-darwin 94ebaa9ea11fe5333ee038b14c7ce2886ccd8ec1
PiperOrigin-RevId: 798224481
Change-Id: Iba80d7fec417293aaf556173d4be637eb6d4c261
1 file changed
tree: e53d01d2a55f5614e5a18858020b52636b2570d1
  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: