Clone this repo:
  1. dfd3d34 Update Slack link to use slack.bazel.build by Googler · 2 days ago master
  2. e354fc3 Merge pull request #19 from renovate-bot:renovate/io_bazel_rules_go-0.x by Copybara-Service · 3 days ago
  3. c1b466c Update dependency io_bazel_rules_go to v0.18.6 by Renovate Bot · 4 days ago
  4. 236c6eb Merge pull request #17 from hlopko:add_find_cc_toolchain by Copybara-Service · 3 weeks ago
  5. d991801 Add find_cc_toolchain.bzl to help accessing current C++ toolchain by Marcel Hlopko · 3 weeks ago

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: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

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: