commit | e7f1b2c2e5b6be0052c7815e1fd82f5047b3f3db | [log] [tgz] |
---|---|---|
author | Googler <noreply@google.com> | Mon Mar 09 10:47:51 2020 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Mon Mar 09 10:48:16 2020 -0700 |
tree | 69695554321c87012d858851126c53bbdf2f8e79 | |
parent | b14a82ed1755455bc0c57c861e77bfff9b34b869 [diff] |
Automatic code cleanup. PiperOrigin-RevId: 299879428 Change-Id: I647d3900c2f26b0b9f587cdbd517ad649cb843d7
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:
rules_cc
mailing list#cc
on slack.bazel.build