Google Git
Sign in
bazel / rules_cc / 4de26b53a6ad892b605e747fbafe256e48d5b56e
commit4de26b53a6ad892b605e747fbafe256e48d5b56e[log] [tgz]
authorGoogler <plf@google.com>Wed Feb 12 08:01:29 2020 -0800
committerCopybara-Service <copybara-worker@google.com>Wed Feb 12 08:01:50 2020 -0800
tree7c003ac1236f444e90c40932f25a158fb043f1fe
parentcd0fa354f63f8c9f036d1101e8eb0da643ee7f55 [diff]
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
12 files changed
tree: 7c003ac1236f444e90c40932f25a158fb043f1fe
  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: