Google Git
Sign in
bazel / rules_cc / refs/heads/main
commitf867aea64e0f24a21a7c0e24b6be0d09f6e75ec5[log] [tgz]
authorFabian Meumertzheim <fabian@meumertzhe.im>Fri Nov 07 13:59:12 2025 -0800
committerCopybara-Service <copybara-worker@google.com>Fri Nov 07 13:59:45 2025 -0800
tree2e7075ff97f535cd3e901ce2b0f27be7f6108355
parentf84fadd01175a9c1a421e9f668818c2b6ad9f039 [diff]
Apply `--cxxopt` to C++20 module interfaces

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

BEGIN_PUBLIC
Apply `--cxxopt` to C++20 module interfaces (#520)

C++20 module interfaces are not recognizable by fixed extensions, only by their appearance in the `module_interfaces` attribute.

Closes #520
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/520 from fmeum:c++20-modules-cxxopt 93586edbdacf6c61b886b9565679868a3f1c3660
PiperOrigin-RevId: 829568265
Change-Id: Ib129e67995d14172de54de81b95d7fa050c5ad5f
2 files changed
tree: 2e7075ff97f535cd3e901ce2b0f27be7f6108355
  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: