commit | 608c7b605fb844a20e96a3eddc9b49ad2542adab | [log] [tgz] |
---|---|---|
author | Googler <plf@google.com> | Tue Mar 16 06:44:51 2021 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Tue Mar 16 06:45:21 2021 -0700 |
tree | d71084aaa7e928850908583bc36604b4c36b6ea6 | |
parent | 9544a3eeacfba706ab6be839af9b4a9a26f0a4bd [diff] |
C++: Make permissions check optional in cc_shared_library The cc_shared_library_permissions mechanism was introduced to add control over which cc_shared_libraries can export a given cc_library. If the repo is big enough, the owner of a cc_library might want to prevent someone else in a different package making their library part of the ABI of a public shared library because that makes it harder to change the cc_library. This does not apply accross repositories because a dependant repository can overwrite anything from a repository dependency anyway. However, it is becoming more apparent than even though this mechanism should exist, it should not be enabled by default since most people don't need it. To enable it pass the flag --//examples:enable_permissions_check=True. RELNOTES:none PiperOrigin-RevId: 363171677 Change-Id: I8afb3294806bb3053ee1279c6e9c5355089bccbb
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:
rules_cc
mailing list#cc
on slack.bazel.build