Google Git
Sign in
bazel / rules_cc / 810a11e77285e97e5a69e6f1be3c8d647286407f
commit810a11e77285e97e5a69e6f1be3c8d647286407f[log] [tgz]
authorGoogler <plf@google.com>Fri Feb 14 06:58:52 2020 -0800
committerCopybara-Service <copybara-worker@google.com>Fri Feb 14 06:59:11 2020 -0800
tree66aa332a5577c6968733d35173c02ab7dae3dc9d
parenta2060ec7c9e574c1e6b703a8b1ca34c0888ae755 [diff]
C++: Allow libraries to be exported by any target

Any library should be exportable by any cc_shared_library target regardless of whether the cc_shared_library target is in the same package or a parent package as long as the library author gives permission.

The library author can now do this by writing tags=["exported_by=//foo,//baz"].

PiperOrigin-RevId: 295137965
Change-Id: I4acffd26981fedd6cb0c505e2691da0c70a7b6b0
3 files changed
tree: 66aa332a5577c6968733d35173c02ab7dae3dc9d
  1. .bazelci/
  2. cc/
  3. distro/
  4. examples/
  5. tests/
  6. third_party/
  7. tools/
  8. .gitignore
  9. BUILD
  10. CODEOWNERS
  11. CONTRIBUTING.md
  12. internal_deps.bzl
  13. internal_setup.bzl
  14. ISSUE_TEMPLATE.md
  15. LICENSE
  16. README.md
  17. renovate.json
  18. WORKSPACE
README.md

C++ rules for Bazel

  • Postsubmit Build status
  • Postsubmit + Current Bazel Incompatible flags Build status

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: