commit | d485e267a559030434158bee69141d182db60dd4 | [log] [tgz] |
---|---|---|
author | hlopko <hlopko@google.com> | Wed Feb 13 05:40:32 2019 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Wed Feb 13 05:40:50 2019 -0800 |
tree | 07f70bd93e55a55c9c082ee1a5a940d52ab249a2 | |
parent | 49a6c21b32f53d7439a3c3dfb9669873f5ebcb96 [diff] |
Enable features that were previously enabled by Bazel in legacy_fields_migrator https://github.com/bazelbuild/bazel/issues/6861 RELNOTES: None. PiperOrigin-RevId: 233735389
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