commit | de2791648512e8bf2f898b2af9ae1c56c03f2931 | [log] [tgz] |
---|---|---|
author | rosica <rosica@google.com> | Wed Feb 06 08:41:06 2019 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Wed Feb 06 08:41:22 2019 -0800 |
tree | ddca3087a7a090202e4819507e2b7bbc9e90346c | |
parent | 9432a5a6e891d19531cfe7df0167d808459c1715 [diff] |
Fix action_config names If an action_config's name doesn't appear in the action_names.bzl, eg action-a.b+c, in it's assignments statement we would declare it as: action_a.b+c_action = action_config( ... This cl fixes it to create the action_config variable with the +, - and . It also adds tests for action_config Issue #5380 PiperOrigin-RevId: 232681355
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