Clone this repo:
  1. 8f861e8 Merge pull request #117 from meteorcloudy:bzlmod by Copybara-Service · 3 weeks ago main
  2. 890aeb2 Modularize rules_cc by Yun Peng · 3 weeks ago
  3. aa7ff81 Make cc_shared_library use the builtin Starlark version by Googler · 3 weeks ago
  4. 8ab61cf Merge pull request #115 from lizan:splitdwarf by Copybara-Service · 3 weeks ago
  5. aa123b8 Merge branch 'main' into splitdwarf by Lizan Zhou · 3 weeks ago

C++ rules for Bazel

  • Postsubmit Build status
  • Postsubmit + Current Bazel Incompatible flags 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")

    name = "rules_cc",
    urls = [""],
    sha256 = "TODO",

Then, in your BUILD files, import and use the rules:

load("@rules_cc//cc:defs.bzl", "cc_library")


Using the rules_cc toolchain

If you'd like to use the cc toolchain defined in this repo add this to your WORKSPACE after you include rules_cc:

load("@rules_cc//cc:repositories.bzl", "rules_cc_dependencies", "rules_cc_toolchains")



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).


bazel run @rules_cc//tools/migration:legacy_fields_migrator -- \
  --input=my_toolchain/CROSSTOOL \


Bazel and rules_cc are the work of many contributors. We appreciate your help!

To contribute, please read the contribution guidelines:

Note that the rules_cc use the GitHub issue tracker for bug reports and feature requests only. For asking questions see: