commit | 8bd6cd75d03c01bb82561a96d9c1f9f7157b13d0 | [log] [tgz] |
---|---|---|
author | Googler <hlopko@google.com> | Fri Nov 08 10:50:13 2019 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Fri Nov 08 10:50:36 2019 -0800 |
tree | ccdb780f9aeaff71c918ccea38d894cd89e2fc7d | |
parent | fe8f0a4cf9f49dfca982620b98220f7ad883fb21 [diff] |
Keep @rules_cc//cc:toolchain_type as fully-qualified label always Labels in toolchains attribute need to include the repository, otherwise the resolution won't work. RELNOTES: None. PiperOrigin-RevId: 279347045 Change-Id: Iba1eb8bb677771e2c089ab6bc1b5e019c4da434e
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