commit | 2e79abf8ca80f51e0928a7728f08f87a9a7c5854 | [log] [tgz] |
---|---|---|
author | hlopko <hlopko@google.com> | Mon Feb 18 05:16:03 2019 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Mon Feb 18 05:16:18 2019 -0800 |
tree | ef70cca8bab950de2f1faadc80492b481c5089fd | |
parent | 5743a325d13e110177014cc5c16badc4484be54a [diff] |
Flip --incompatible_disable_expand_if_all_available_in_flag_set FlagSets in the CROSSTOOL no longer accept expand_if_all_available field Fixes #7008 RELNOTES: `--incompatible_disable_expand_if_all_available_in_flag_set` has been flipped (https://github.com/bazelbuild/bazel/issues/7008) PiperOrigin-RevId: 234466411
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