C++ Rules for Bazel
Go to file
Copybara-Service c003593092 Merge pull request #108 from renovate-bot:renovate/bazel_federation-digest
PiperOrigin-RevId: 384218471
Change-Id: Id1fcdc5c1f97318b178ea15a4a61ee2f90a27658
2021-07-12 06:15:08 -07:00
.bazelci C++: Make permissions check optional in cc_shared_library 2021-03-16 06:45:21 -07:00
cc Add armeabi_cc_toolchain_config.bzl to macOS config 2021-05-27 13:36:41 -07:00
distro BUILD --> BUILD.bazel 2021-05-10 08:35:04 -07:00
examples mv BUILD --> BUILD.bazel 2021-05-14 07:51:14 -07:00
tests Internal change 2020-11-02 13:19:59 -08:00
third_party Add optional tool_path_origin to Tools in C++ crosstool 2020-05-06 06:52:27 -07:00
tools Automatic code cleanup. 2021-02-05 04:30:09 -08:00
.gitignore
AUTHORS Create AUTHORS 2021-03-25 11:49:43 -04:00
BUILD Internal change 2020-11-02 13:19:59 -08:00
CODEOWNERS Update CODEOWNERS 2020-09-22 14:26:08 +02:00
CONTRIBUTING.md
ISSUE_TEMPLATE.md Fix issue template 2019-02-27 01:37:03 -08:00
LICENSE
README.md Add instructions on toolchain use to README 2021-05-27 13:39:22 -07:00
WORKSPACE Update bazel_federation commit hash to 6ad33bc 2021-07-12 08:56:17 +00:00
internal_deps.bzl Fix buildifier warnings in @rules_cc 2019-10-24 07:01:25 -07:00
internal_setup.bzl Fix buildifier warnings in @rules_cc 2019-10-24 07:01:25 -07:00
renovate.json Update renovate.json 2019-11-03 11:40:55 +01:00

README.md

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

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

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

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

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: