C++ Rules for Bazel
Go to file
Copybara-Service 12a2d801f6 Merge pull request #38 from hlopko:update_gtest
PiperOrigin-RevId: 274161434
Change-Id: Ic7cc0802695afff00095d5565496f7db46fe83e4
2019-10-11 06:35:58 -07:00
.bazelci Stop running Buildifier as part of the presubmit 2019-08-27 01:51:17 -07:00
cc Add version number to a dedicated bzl file 2019-10-02 15:25:05 +02:00
distro Merge pull request #35 from fweikert:distro 2019-10-02 08:49:43 -07:00
examples C++: Move tools/cpp from bazel_tools to rules_cc 2019-08-21 07:30:04 -07:00
third_party Replace scrubbing with copybara-comment-this-out-please in copybara 2019-03-14 17:13:28 +01:00
tools/migration Add a cc_toolchain_config_compare_test that compares 2 Starlark C++ toolchain configuration rules 2019-08-09 05:56:16 -07:00
.gitignore
BUILD Add missing bzl files to rules_cc distribution. 2019-10-02 13:25:11 -07:00
CODEOWNERS
CONTRIBUTING.md
ISSUE_TEMPLATE.md
LICENSE
README.md Refactor rules_cc to follow https://docs.bazel.build/versions/master/skylark/deploying.html 2019-06-18 00:21:44 -07:00
WORKSPACE Actually, lets depend on the release archive, not the branch 2019-10-09 15:18:06 +02:00
internal_deps.bzl Use rules_pkg for building releases 2019-09-17 18:00:18 +02:00
internal_setup.bzl Make Buildifier happy 2019-09-30 15:58:14 +02:00
renovate.json

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: