commit | fe8f0a4cf9f49dfca982620b98220f7ad883fb21 | [log] [tgz] |
---|---|---|
author | Googler <hlopko@google.com> | Thu Nov 07 02:26:50 2019 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Thu Nov 07 02:27:13 2019 -0800 |
tree | 7aa33bed85073cb1a5d1e22b1f49280f619dbddb | |
parent | e7c97c3af74e279a5db516a19f642e862ff58548 [diff] |
Add //cc:srcs filegroup that Bazel can depend on in unittests RELNOTES: None. PiperOrigin-RevId: 279041716 Change-Id: I90ce28031a4f2ac737cffbe57d42030c0d1d862b
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