Google Git
Sign in
bazel / rules_cc / 96eb170c6e3e272a794975147028bcdc9bdcd016
commit96eb170c6e3e272a794975147028bcdc9bdcd016[log] [tgz]
authorCopybara-Service <copybara-worker@google.com>Fri May 24 06:17:43 2019 -0700
committerCopybara-Service <copybara-worker@google.com>Fri May 24 06:17:43 2019 -0700
treed62a7cf27a577d70f78c9d3ac68f03533f683e7a
parentf25bda7e0d59079bd87653772d0b73c5959dedef [diff]
parent6cd7e75fc4ee81923db1b6733e48909a05eba683 [diff]
Merge pull request #15 from hlopko:fix_examples_for_platforms

PiperOrigin-RevId: 249821791
Change-Id: I61b10b87731a9f5a892c58b8ea4c7158e35a943e
tree: d62a7cf27a577d70f78c9d3ac68f03533f683e7a
  1. .bazelci/
  2. cc/
  3. examples/
  4. third_party/
  5. tools/
  6. .gitignore
  7. BUILD
  8. CODEOWNERS
  9. CONTRIBUTING.md
  10. ISSUE_TEMPLATE.md
  11. LICENSE
  12. README.md
  13. renovate.json
  14. 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:rules.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: