| commit | b8be74cc4545969dd7a53599d0a0b33ca107b2d6 | [log] [tgz] |
|---|---|---|
| author | hlopko <hlopko@google.com> | Mon Jan 21 02:54:37 2019 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Jan 21 02:54:52 2019 -0800 |
| tree | 263eba5739582ef986f87d6e3e16534115cce724 | |
| parent | da4639bd1f484126677894093c3bcc0b4abc9b72 [diff] |
Change rules_cc badge to only show master branch status RELNOTES: None. PiperOrigin-RevId: 230198892
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