bazel
/
rules_cc
mirror of https://github.com/bazelbuild/rules_cc
2
0
Fork 0
Code Issues Releases Activity
C++ Rules for Bazel
57 Commits 15 Branches 20 Tags 1.9 MiB
Starlark 83.1%
C++ 7.5%
Smarty 4.9%
Shell 4.4%
Batchfile 0.1%
Go to file
hlopko 63003094c9 Make cc_embed_data.bzl forward compatible with removal of legacy crosstool fields 
RELNOTES: None
PiperOrigin-RevId: 228301880
 		2019-01-09 08:58:59 +01:00
cc Add initial content of rules_cc repo 2019-01-09 08:58:14 +01:00
third_party/com/github/bazelbuild/bazel/src/main/protobuf Make bazel option --collect_symbol_counts a noop 2019-01-09 08:58:26 +01:00
tools/migration Make cc_embed_data.bzl forward compatible with removal of legacy crosstool fields 2019-01-09 08:58:59 +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 WORKSPACE to rules_cc 2019-01-09 08:58:36 +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.