Google Git
Sign in
bazel / rules_cc / be9ff3eb412c5781eabd4a4b7b81de8b95da7b84
commitbe9ff3eb412c5781eabd4a4b7b81de8b95da7b84[log] [tgz]
authorCopybara-Service <copybara-worker@google.com>Wed Mar 01 01:22:30 2023 -0800
committerCopybara-Service <copybara-worker@google.com>Wed Mar 01 01:22:30 2023 -0800
tree05ef4be4200554b9bfa3ce8101a2727527cdad65
parent998319083bf25c9f1acdc2c73bc7cd099a151dff [diff]
parent0baf82487f7054cd104a33a882c099f9fa61d18f [diff]
Merge pull request #183 from renovate-bot:renovate/rules_proto-digest

PiperOrigin-RevId: 513165629
Change-Id: Ib58015b1e049cc54a347b86ca781807196a162cf
tree: 05ef4be4200554b9bfa3ce8101a2727527cdad65
  1. .bazelci/
  2. .bcr/
  3. cc/
  4. examples/
  5. tests/
  6. third_party/
  7. tools/
  8. .gitignore
  9. AUTHORS
  10. BUILD
  11. CODEOWNERS
  12. CONTRIBUTING.md
  13. ISSUE_TEMPLATE.md
  14. LICENSE
  15. MODULE.bazel
  16. README.md
  17. renovate.json
  18. WORKSPACE
README.md

C++ rules for Bazel

  • Postsubmit Build status
  • Postsubmit + Current Bazel Incompatible flags Build status

This repository contains 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

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: