| commit | 951df6a4964692eed38f267fcd3e3c6b569c8b92 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Thu Mar 28 00:52:04 2019 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Mar 28 00:52:17 2019 -0700 |
| tree | 59c2c0e9424fd17a28b218c9ccb4fdedd6146e6a | |
| parent | 3723b4c35f361ba5593d00c1f4183b387402fef5 [diff] |
Add skylib dependency [Copybara import of https://github.com/bazelbuild/rules_cc/pull/10] Skylib will be used to check minimum supported Bazel version. Merge 2e5b5eb2d04a7a87970f6441c5b782e0954bea14 into 3723b4c35f361ba5593d00c1f4183b387402fef5 PiperOrigin-RevId: 240725578
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).