commit | cfe68f6bc79dea602f2f6a767797f94a5904997f | [log] [tgz] |
---|---|---|
author | Googler <plf@google.com> | Fri Nov 29 04:18:45 2019 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Fri Nov 29 04:19:02 2019 -0800 |
tree | 9980f8290b514c551deff408201267a23aeeb8c7 | |
parent | 03ae87bea3528232327ba4f4d4b544d14b518875 [diff] |
Fix immutable frozen set bug in defs.bzl When adding tags to a native cc_library rule that is created through a macro we were not properly considering the case where the tags came from a different file and therefore were frozen. This caused an error. RELNOTES:none PiperOrigin-RevId: 283039855 Change-Id: Id4cb45675a08ca65196f4f7771abdd5bb0705b79
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:defs.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
Bazel and rules_cc are the work of many contributors. We appreciate your help!
To contribute, please read the contribution guidelines: CONTRIBUTING.md.
Note that the rules_cc use the GitHub issue tracker for bug reports and feature requests only. For asking questions see:
#cc
on slack.bazel.build