| commit | da4639bd1f484126677894093c3bcc0b4abc9b72 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Fri Jan 18 11:20:12 2019 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Jan 18 11:20:25 2019 -0800 |
| tree | 5ae67bfdab9af8a0ef941defb1f6c916ead426e2 | |
| parent | dc71ef6ea677c42c9a861991616d3159094b4512 [diff] |
Actually cause the comparator / test to fail when there is an error reading one of the toolchains. Cosmetic spacing fixes for strings that will be concatenated and fixed a typo. PiperOrigin-RevId: 229961708
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.
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/TODO"],
sha256 = "TODO",
)
Then, in your BUILD files, import and use the rules:
load("@rules_cc//cc:rules.bzl", "cc_library")
cc_library(
...
)
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