Google Git
Sign in
bazel / rules_cc / 0769eb3cec5ae57b02c1f34709643f7cc872af21
commit0769eb3cec5ae57b02c1f34709643f7cc872af21[log] [tgz]
authorGoogler <hvd@google.com>Wed Jul 30 02:13:47 2025 -0700
committerCopybara-Service <copybara-worker@google.com>Wed Jul 30 02:14:52 2025 -0700
tree5f090060350761f515a1d58addeb0a554917cca4
parent2ba751fe00f86a0d5cb751cd866ff89024a6666d [diff]
Starlarkify parse header action creation and compile build variable construction

Rollforward of unknown commit with fixes:
 - declare and set outputs on `CppCompileActionBuilder` before constructing build variables, the latter requires those - this removes the need to read the fields from the builder)
 - add missing parameters to `_get_copts`
 - fix cpp opts result list construction
 - add missing internal API for per-file copts

PiperOrigin-RevId: 788813137
Change-Id: I552ce2bc40d8a89cfd3577fd7f03d80de3dcca01
1 file changed
tree: 5f090060350761f515a1d58addeb0a554917cca4
  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: