Google Git
Sign in
bazel / rules_cc / 998319083bf25c9f1acdc2c73bc7cd099a151dff
commit998319083bf25c9f1acdc2c73bc7cd099a151dff[log] [tgz]
authorCopybara-Service <copybara-worker@google.com>Wed Feb 22 10:36:14 2023 -0800
committerCopybara-Service <copybara-worker@google.com>Wed Feb 22 10:36:14 2023 -0800
tree9424ab9a518d12e5f2bdd9a2fd06e8fe42a0eb15
parent42f3259960ba2b7b350bafa50f104567883a49eb [diff]
parentadfbe56c12527d40781ef9a8b8d77fc1b49ceff0 [diff]
Merge pull request #182 from renovate-bot:renovate/rules_proto-digest

PiperOrigin-RevId: 511535003
Change-Id: I4d5847e1339bf8fd882dfcb69140b44efb05072e
tree: 9424ab9a518d12e5f2bdd9a2fd06e8fe42a0eb15
  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: