commit | dfb180b48691315a8c67245bd42e072632083ea8 | [log] [tgz] |
---|---|---|
author | hlopko <hlopko@google.com> | Fri Feb 08 04:53:38 2019 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Fri Feb 08 04:53:52 2019 -0800 |
tree | 3a0f8b3772631cd37b8665ba728357eb664be569 | |
parent | 903ad72c430c369ca65c49a552fc2f9f43ec2fd0 [diff] |
Migrate repeated expand_if_(all|none)_available into nested flag_groups Crosstool in Starlark assumes these fields as singular, not collections. This cl updates the migration script to prepare crosstool in proto for this. https://github.com/bazelbuild/bazel/issues/6861 https://github.com/bazelbuild/bazel/issues/5883 RELNOTES: None. PiperOrigin-RevId: 233041028
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