Google Git
Sign in
bazel / rules_cc / 4a1c578fb0e2fbc06089a3f917e3c3c840c214b4
commit4a1c578fb0e2fbc06089a3f917e3c3c840c214b4[log] [tgz]
authorGoogler <plf@google.com>Wed Aug 21 07:29:46 2019 -0700
committerCopybara-Service <copybara-worker@google.com>Wed Aug 21 07:30:04 2019 -0700
treeeb0a0b8ef4b33b7a0c652c05ddaae1fd37aa1d6f
parent624b5d59dfb45672d4239422fa1e3de1822ee110 [diff]
C++: Move tools/cpp from bazel_tools to rules_cc

Here we are duplicating bazel_tools/tools/cpp. The goal is for the BUILD files in bazel_tools/tools/cpp to have an alias that point to rules_cc. Then later on with the incompatible flag these aliases will no longer be valid.

Working towards #8743

RELNOTES:none
PiperOrigin-RevId: 264604076
Change-Id: I389702793a1a95b0990dce93577de2b7182e2e6b
46 files changed
tree: eb0a0b8ef4b33b7a0c652c05ddaae1fd37aa1d6f
  1. .bazelci/
  2. cc/
  3. examples/
  4. third_party/
  5. tools/
  6. .gitignore
  7. BUILD
  8. CODEOWNERS
  9. CONTRIBUTING.md
  10. internal_deps.bzl
  11. internal_setup.bzl
  12. ISSUE_TEMPLATE.md
  13. LICENSE
  14. README.md
  15. renovate.json
  16. WORKSPACE
README.md

C++ rules for Bazel

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: