Google Git
Sign in
bazel / rules_cc / a8f6a9241380a726a9131dc4d2ecc3543d7d6fb8
commita8f6a9241380a726a9131dc4d2ecc3543d7d6fb8[log] [tgz]
authorFabian Meumertzheim <fabian@meumertzhe.im>Mon Nov 03 03:50:09 2025 -0800
committerCopybara-Service <copybara-worker@google.com>Mon Nov 03 03:50:45 2025 -0800
treee1d1e3c41469dc294f72531a3c63f834c7d97062
parent5c3e987e81a1331714014fc133664e1f7a7582f9 [diff]
Fix C++20 module compilation

The merge of C++20 module support in 5c3e987e81a1331714014fc133664e1f7a7582f9 wasn't covered by tests and requires a number of fixes so that the test case in Bazel's `cc_integration_test` can pass.

Closes #511

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/511 from fmeum:c++20-modules 716b9bea37fc6aead69cb6fb812826f192611d71
PiperOrigin-RevId: 827424640
Change-Id: Iff433f2a9ec0b8ad9585805f7df7a86297731b92
3 files changed
tree: e1d1e3c41469dc294f72531a3c63f834c7d97062
  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: