| commit | 0fd5bb9b752e8b9c191530cf6047524d68b9f9ad | [log] [tgz] |
|---|---|---|
| author | hlopko <hlopko@google.com> | Wed Jan 16 01:41:08 2019 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Jan 16 01:41:22 2019 -0800 |
| tree | cf18e3c6fea9914cb6aa36fd8c92e5b9c383d832 | |
| parent | f79b9301fac82626ca4406114c46a91a4f5ec46c [diff] |
Rename/remove fields referencing legacy features in legacy_fields_migrator When renaming legacy_*_flags to default_*_flags, also rename other fields such as requires. We're intentionally not replacing the implies line, just removing it, because default_*_features are enabled by default, so they don't need to be implied (Implied field is older than enabled field, so there are uses of it where enabled would work just fine. The only semantic difference is that implied features cannot be disabled, whereas enabled can. But since the standard style of writing crosstools seems to prefer enabled, I'm doing the same here.) https://github.com/bazelbuild/bazel/issues/6861 https://github.com/bazelbuild/bazel/issues/5883 RELNOTES: None. PiperOrigin-RevId: 229518029
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