Google Git
Sign in
bazel / rules_cc / e68ae76a67c3291f66d624dcd164b3a9d3f3af17
commite68ae76a67c3291f66d624dcd164b3a9d3f3af17[log] [tgz]
authorGoogler <rosica@google.com>Fri Aug 09 05:42:58 2019 -0700
committerCopybara-Service <copybara-worker@google.com>Fri Aug 09 05:43:22 2019 -0700
treea31b02778bfcffb11d5d9c0b0d73b26bd7ac896e
parentb7fe9697c0c76ab2fd431a891dbb9a6a32ed7c3e [diff]
Allow the C++ toolchain config rules comparator script to not need toolchain_identifier argument when both --before and --after arguments are CToolchains (coming from Starlark rules instead of CROSSTOOL proto)

We don't need to select a toolchain by the identifier when we get the proto from Starlark rules because in that case the proto contains a single toolchain.
The difference in toolchain_identifier field between the first and the second proto file will be caught as any other field.

RELNOTES: None.
PiperOrigin-RevId: 262543753
Change-Id: I1e66ee302bf551ade883c217f6269f44382393c0
1 file changed
tree: a31b02778bfcffb11d5d9c0b0d73b26bd7ac896e
  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: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: