|author||Googler <email@example.com>||Wed Feb 12 08:01:29 2020 -0800|
|committer||Copybara-Service <firstname.lastname@example.org>||Wed Feb 12 08:01:50 2020 -0800|
Remove need for exported_by or linked_statically_by For now we will restrict allowed exports to the same package. At the same time static_deps should be used to take into account what should be linked into a shared library. RELNOTES:none PiperOrigin-RevId: 294668451 Change-Id: Ia087519106983bfa9a980e471d3102ab391a53eb
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
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.
bazel run @rules_cc//tools/migration:legacy_fields_migrator -- \ --input=my_toolchain/CROSSTOOL \ --inline
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: