Google Git
Sign in
bazel / rules_cc / 5b9a7090ce7bd4c55bd3080798a7d68f7cd288f8
commit5b9a7090ce7bd4c55bd3080798a7d68f7cd288f8[log] [tgz]
authorGoogler <ilist@google.com>Thu Oct 02 01:57:15 2025 -0700
committerCopybara-Service <copybara-worker@google.com>Thu Oct 02 01:57:44 2025 -0700
tree6292d8f62f30b105ee45adb41ea1020ad48b00e5
parente5f57cf6e3415efbbe65422f70f5212ebb827235 [diff]
Remove `propagateModuleMapAsActionInput` from `CcCompilationContext`.

This field was always set to `true` in all call sites, making it effectively a constant. The logic in `CcCompilationContext.addAdditionalInputs` is simplified to always include the module map artifact if it exists. The corresponding Starlark parameter `propagate_module_map_to_compile_action` is also removed from `cc_common.bzl` and related files.

Works towards Starlarkification of CcCompilationContext.

PiperOrigin-RevId: 814131436
Change-Id: Iae39e9552e84ff8b028d5ed9686cbcd4178b2728
1 file changed
tree: 6292d8f62f30b105ee45adb41ea1020ad48b00e5
  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: