Google Git
Sign in
chromium / chromiumos / third_party / rules_cc / refs/heads/stabilize-15905.B
commitd7f5cd1fe98930d4c069253bd3325d6f0c4217e5[log] [tgz]
authorMatt Stark <msta@google.com>Tue May 21 06:33:33 2024
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed May 22 21:17:49 2024
tree96e449147f4e1ef665d7c9c44de4924e35d590ef
parentbae1f72221f9680b614b957bd29cb71997ced0bb [diff]
Make rules_cc use our hermetic launcher

BUG=b:291840720
TEST=portage/tools/run_tests.sh

Cq-Depend: 5553611
Change-Id: I40ad759b1152eb05f6878c1e84e78cfe3fdfcf55
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/rules_cc/+/5552772
Tested-by: Matt Stark <msta@google.com>
Auto-Submit: Matt Stark <msta@google.com>
Commit-Queue: Matt Stark <msta@google.com>
Reviewed-by: Tim Bain <tbain@google.com>
1 file changed
tree: 96e449147f4e1ef665d7c9c44de4924e35d590ef
  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. DIR_METADATA
  14. ISSUE_TEMPLATE.md
  15. LICENSE
  16. MODULE.bazel
  17. OWNERS
  18. README.md
  19. renovate.json
  20. 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: