commit | fe2b13f37af7df09ff66d2dc36067527a67bd976 | [log] [tgz] |
---|---|---|
author | Matt Stark <msta@google.com> | Mon Jun 03 23:40:25 2024 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jun 06 00:11:38 2024 |
tree | fbe59bb119b1583ad89994cc175a622860a92cf7 | |
parent | d7f5cd1fe98930d4c069253bd3325d6f0c4217e5 [diff] | |
parent | 1cf35f02db465731e11c015f84d30ace164d1ac0 [diff] |
Update rules_cc to upstream Cq-Depend: 5599911 Change-Id: Ic3ac3a9d9939486520f8a6381096c47e9f173050 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/rules_cc/+/5595428 Commit-Queue: Matt Stark <msta@google.com> Reviewed-by: Tim Bain <tbain@google.com> Tested-by: Matt Stark <msta@google.com> Auto-Submit: Matt Stark <msta@google.com>
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.
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( ... )
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()
This repository also contains migration tools that can be used to migrate your project for Bazel incompatible changes.
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
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:
rules_cc
mailing list#cc
on slack.bazel.build