| commit | a9932b39398dde579d1c5b9bba84d6eefeb6900a | [log] [tgz] |
|---|---|---|
| author | hlopko <hlopko@google.com> | Wed Jan 23 05:41:57 2019 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Jan 23 05:42:09 2019 -0800 |
| tree | 374498cea1d0e3256f057a06cb568753aef3fd9a | |
| parent | b8be74cc4545969dd7a53599d0a0b33ca107b2d6 [diff] |
Make ctoolchain_compare.bzl more robust by using ctx.label.name as generated files name. This ensures that the generated files will be unique in the package and therefore there won't be action conflict. RELNOTES: None. PiperOrigin-RevId: 230514342
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