commit | ddc0791fa66deaf3d70925fbc8048e5b0e2fe999 | [log] [tgz] |
---|---|---|
author | Googler <plf@google.com> | Tue Oct 05 09:12:49 2021 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Tue Oct 05 09:13:17 2021 -0700 |
tree | 2accc6c631e84477a5320c367cdcfd4780933777 | |
parent | dd2758b96dc8f9f4add81eaa4154b7e3d8be6873 [diff] |
Remove dependency on rules_pkg from rules_cc This helps with getting rules_cc back to green. The distro package doesn't seem critical and it can be added back in a later CL once we figure out what is wrong with the rules_pkg dependency. RELNOTES:none PiperOrigin-RevId: 401001290 Change-Id: I94304c7df3597c84633952fb6013bd074c350122
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( ... )
If you'd like to use the cc toolchain defined in this repo add this to your WORKSPACE after you include rules_cc:
load("@rules_cc//cc:repositories.bzl", "rules_cc_dependencies", "rules_cc_toolchains") rules_cc_dependencies() rules_cc_toolchains()
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