Introduces static_deps attribute to cc_shared_library.

This removes the need for linked_statically_by, although both attributes work for now. The attribute linked_statically_by will disappear from cc_library and instead we will add exported_by which will allow library authors to retain the power of deciding who exports their library.

When a library is linked statically by more than one shared library and this library was only supposed to be linked once, i.e. it contains static initializers, then Bazel will give an error.

PiperOrigin-RevId: 293319906
Change-Id: I3713511e09feffb9429d38ac3ae868498ed4afe6
2 files changed
tree: c5b40805a8c2289432419a5ced4f034d06755da8
  1. .bazelci/
  2. .gitignore
  3. BUILD
  10. cc/
  11. distro/
  12. examples/
  13. internal_deps.bzl
  14. internal_setup.bzl
  15. renovate.json
  16. tests/
  17. third_party/
  18. tools/

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")

    name = "rules_cc",
    urls = [""],
    sha256 = "TODO",

Then, in your BUILD files, import and use the rules:

load("@rules_cc//cc:defs.bzl", "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).


bazel run @rules_cc//tools/migration:legacy_fields_migrator -- \
  --input=my_toolchain/CROSSTOOL \


Bazel and rules_cc are the work of many contributors. We appreciate your help!

To contribute, please read the contribution guidelines:

Note that the rules_cc use the GitHub issue tracker for bug reports and feature requests only. For asking questions see: