Google Git
Sign in
bazel / rules_cc / eeed2a9ab71625938674e91137dfd1d9a1e65a83
commiteeed2a9ab71625938674e91137dfd1d9a1e65a83[log] [tgz]
authorGoogler <ilist@google.com>Tue Oct 08 05:34:58 2024 -0700
committerCopybara-Service <copybara-worker@google.com>Tue Oct 08 05:35:42 2024 -0700
treed36ef9c447289e300e5f73fe7d08d9ce33956339
parentb96ca297634becaec06123b21a2ba7eab384418a [diff]
Remove crostool migration tools

The migration to .bzl configured toolchains happened a long time ago and the conversion tools from proto files are not needed anymore.

This also cleans up rules_cc dependencies to build those tools. And unblock me around the import of py_proto_library, which is not needed anymore.

PiperOrigin-RevId: 683582749
Change-Id: I9a56d9e3f9089f7434708a2cfefdd4f12d186658
19 files changed
tree: d36ef9c447289e300e5f73fe7d08d9ce33956339
  1. .bazelci/
  2. .bcr/
  3. cc/
  4. docs/
  5. examples/
  6. tests/
  7. .gitignore
  8. AUTHORS
  9. BUILD
  10. CODEOWNERS
  11. CONTRIBUTING.md
  12. ISSUE_TEMPLATE.md
  13. LICENSE
  14. MODULE.bazel
  15. README.md
  16. renovate.json
  17. WORKSPACE
README.md

C++ rules for Bazel

  • Postsubmit Build status
  • Postsubmit + Current Bazel Incompatible flags 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

There is no need to use rules from this repository just yet. If you want to use rules_cc anyway, 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: