|author||Googler <firstname.lastname@example.org>||Fri May 08 06:35:32 2020 -0700|
|committer||Copybara-Service <email@example.com>||Fri May 08 06:35:54 2020 -0700|
Change cc_shared_library exports logic. Changes in this CL: 1. 'exports' attribute renamed to roots 2. Removed restrictions for exporting a rule in a different repository 3. Kept restrictions for rules in the same repository but not in the same package or subpackages 4. To get around restrictions, instead of the exported_by tag, one can use the cc_shared_library_permissions rule 5. Added exports_filter that will match libraries in the transitive closure of a root. Anything matched by the exports_filter will also be exported. Restrictions as in 4. still apply. RELNOTES:none PiperOrigin-RevId: 310547916 Change-Id: I32d8e0d4dd4bcc9c9e92f4ff3c5b2a01564c31b2
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: