Google Git
Sign in
pigweed/third_party/github/bazelbuild/rules_cc/640996472ed33723ce71347f99509b52f84118b2
commit
640996472ed33723ce71347f99509b52f84118b2
[log]
author
Keith Smiley <keithbsmiley@gmail.com>
Tue Dec 16 06:57:03 2025 -0800
committer
Copybara-Service <copybara-worker@google.com>
Tue Dec 16 06:57:30 2025 -0800
tree
3e4e47904e9631908b9a7fde04aa3e5c7a75edb8
parent
be107bfeafc5f5ccb35aae9c709625e026f4c965 [diff]
Add additional_compiler_inputs to cc_binary

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

BEGIN_PUBLIC
Add additional_compiler_inputs to cc_binary (#542)

Closes #542
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/542 from keith:ks/add-additional_compiler_inputs-to-cc_binary eff786cf0c9ad5eeb43e4bd1ed1cf25fc9283867
PiperOrigin-RevId: 845251652
Change-Id: I87fc5a4bd2bc72dfe3bf93fcf1858b3f1b3eba1e
3 files changed
tree: 3e4e47904e9631908b9a7fde04aa3e5c7a75edb8
  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: