Gitiles
Code Review Sign In
android-review.linaro.org / platform / external / bazelbuild-rules_cc / refs/heads/simpleperf-release
commit8c87ef785486d8c098d20cd5d2007786fd3a6cab[log] [tgz]
authorAndroid Build Coastguard Worker <android-build-coastguard-worker@google.com>Fri Feb 02 23:46:17 2024 +0000
committerAndroid Build Coastguard Worker <android-build-coastguard-worker@google.com>Fri Feb 02 23:46:17 2024 +0000
treec75dabb560288e11786211bdc61ba40dde4b8674
parent4b1592503ce058be5047e244cbdf859cb03459c2 [diff]
parent9a4853f0327e0266818c8d6b4967e2e8f36b1a88 [diff]
Snap for 11400057 from 9a4853f0327e0266818c8d6b4967e2e8f36b1a88 to simpleperf-release

Change-Id: Idaa5482750963a8964710731bdb1d816f542fbed
tree: c75dabb560288e11786211bdc61ba40dde4b8674
  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. METADATA
  16. MODULE.bazel
  17. MODULE_LICENSE_APACHE2
  18. OWNERS
  19. README.md
  20. renovate.json
  21. 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: