1f87a00b38
We need @rules_cc in front of the toolchain type in cc_shared_library. This is still experimental. More complete test suite is on the way in a separate CL I'm working on. RELNOTES:none PiperOrigin-RevId: 282716323 Change-Id: I797ef08f18987adef82b7c7d484e2838f4e1ba6a |
||
---|---|---|
.bazelci | ||
cc | ||
distro | ||
examples | ||
third_party | ||
tools | ||
.gitignore | ||
BUILD | ||
CODEOWNERS | ||
CONTRIBUTING.md | ||
ISSUE_TEMPLATE.md | ||
LICENSE | ||
README.md | ||
WORKSPACE | ||
internal_deps.bzl | ||
internal_setup.bzl | ||
renovate.json |
README.md
C++ rules for Bazel
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.
Getting Started
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(
...
)
Migration Tools
This repository also contains migration tools that can be used to migrate your project for Bazel incompatible changes.
Legacy fields migrator
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
Contributing
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:
- Stack Overflow
- rules_cc mailing list
- Slack channel
#cc
on slack.bazel.build