Google Git
Sign in
pigweed / third_party / github / bazelbuild / rules_cc / 2e5f7b7e5aeb51313d1e40ff712d1b158d2bb385
commit2e5f7b7e5aeb51313d1e40ff712d1b158d2bb385[log] [tgz]
authorDavid Zbarsky <dzbarsky@gmail.com>Fri Dec 12 06:49:08 2025 -0800
committerCopybara-Service <copybara-worker@google.com>Fri Dec 12 06:49:46 2025 -0800
tree1e2349c6981c3a936496dd110d99e515f5a4c3ae
parent506289b872e76e0e1b42e131dc8e4dfc2cef17d9 [diff]
Make archiver_flags public

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

BEGIN_PUBLIC
Make archiver_flags public (#547)

Downstream toolchains need to use these to align the AR tool with the flags.

Closes #547
END_PUBLIC

COPYBARA_INTEGRATE_REVIEW=https://github.com/bazelbuild/rules_cc/pull/547 from dzbarsky:zbarsky/vis 2185ebaac6d1fcf0a849027ce5e91d99d82ede2f
PiperOrigin-RevId: 843669849
Change-Id: Iab961f19ffb8a25485c7f07bd31c96564e0613be
1 file changed
tree: 1e2349c6981c3a936496dd110d99e515f5a4c3ae
  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: