C++ Rules for Bazel

Go to file

hlopko 281a8bc480 Add BUILD.third_party to rules_cc Only to make //third_party a package RELNOTES: None PiperOrigin-RevId: 228316989		2019-01-09 08:59:30 +01:00
cc	Add initial content of rules_cc repo	2019-01-09 08:58:14 +01:00
third_party	Add BUILD.third_party to rules_cc	2019-01-09 08:59:30 +01:00
tools/migration	Add a script for comparing CToolchian built from different CROSSTOOL/Ctoolchain proto text files	2019-01-09 08:59:20 +01:00
.gitignore	Add things needed for rules_cc to build & test in the open	2019-01-09 08:59:09 +01:00
BUILD	Internal change	2019-01-09 08:56:00 +01:00
CONTRIBUTING.md	Add initial content of rules_cc repo	2019-01-09 08:58:14 +01:00
LICENSE	Internal change	2019-01-09 08:56:00 +01:00
README.md	Add initial content of rules_cc repo	2019-01-09 08:58:14 +01:00
WORKSPACE	Add things needed for rules_cc to build & test in the open	2019-01-09 08:59:09 +01:00

README.md

C++ rules for Bazel

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.