Google Git
Sign in
bazel / rules_cc / 969186ab940c22bcd7e2a217e427e4f04d8afae5
commit969186ab940c22bcd7e2a217e427e4f04d8afae5[log] [tgz]
authorGoogler <cmita@google.com>Mon Sep 01 09:52:05 2025 -0700
committerCopybara-Service <copybara-worker@google.com>Mon Sep 01 09:52:58 2025 -0700
tree4f74485e0a24fd367ce32c0c6997929fbae708a8
parenta0925f28bb4a70857ffdb0b855b9686eb4c0d0aa [diff]
Starlarkify create_compile_source_action.

We no longer pass around the "compile action builder", instead we
create a fresh one just before calling the "create_cpp_compile_action".
The reasoning is that this builder was often modified or duplicated for
each compilation action anyway and the majority of arguments were
already being passed around so having it created early did not save us
much.

The name of the function is altered to reflect the fact it generates
actions for both PIC and no-PIC compilations. The original name is used
for the "inner" function which generates actions for a given PIC or
no-PIC compile.

_get_compile_output now calls a new internal method to create the output
files. The handling of external repositories is non trivial to implement
in Starlark and there are other subtleties involved, such as never
writing to the genfiles directory.

PiperOrigin-RevId: 801837069
Change-Id: Iffe4ae9b399b4502ac613f264619ee7b0324fb0c
1 file changed
tree: 4f74485e0a24fd367ce32c0c6997929fbae708a8
  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: