C++ Rules for Bazel

Go to file

Philipp Wollermann 9d533a919d Add config with bazelversions		2019-01-23 10:53:49 -05:00
.bazelci	Add config with bazelversions	2019-01-23 10:53:49 -05:00
cc	…
third_party	Add BUILD.third_party to rules_cc	2019-01-09 08:59:30 +01:00
tools/migration	Actually cause the comparator / test to fail when there is an error reading one	2019-01-18 11:20:25 -08:00
.gitignore	Add things needed for rules_cc to build & test in the open	2019-01-09 08:59:09 +01:00
BUILD	…
CONTRIBUTING.md	…
LICENSE	…
README.md	Change rules_cc badge to only show master branch status	2019-01-21 02:54:52 -08:00
WORKSPACE	Fix inconsistencies in rules_cc WORKSPACE file	2019-01-11 00:05:36 -08:00

README.md

C++ rules for Bazel

![Build status](https://badge.buildkite.com/f03592ae2d7d25a2abc2a2ba776e704823fa17fd3e061f5103.svg?branch=master

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