commit | 3723b4c35f361ba5593d00c1f4183b387402fef5 | [log] [tgz] |
---|---|---|
author | Googler <noreply@google.com> | Mon Mar 25 08:38:55 2019 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Mon Mar 25 08:39:10 2019 -0700 |
tree | 17cf7b8367ffb33e2a2a0a17a4426da76fded3b1 | |
parent | e86b282e6fb72e6c508937f396c4e3b50cb9ad96 [diff] |
Update rules_go to 0.18.1 [Copybara import of https://github.com/bazelbuild/rules_cc/pull/9] Merge 6181c870fcda4ba6bdc9618ee5fdf12c17c9d3e4 into 2312d7213425d868a54983f963c3e3d80b262558 PiperOrigin-RevId: 240145582
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
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 bazelbuild.slack.com (use bazel-slackin to join).