C++ Rules for Bazel
Go to file
Googler 4de26b53a6 Remove need for exported_by or linked_statically_by
For now we will restrict allowed exports to the same package. At the same time
static_deps should be used to take into account what should be linked into a
shared library.

RELNOTES:none
PiperOrigin-RevId: 294668451
Change-Id: Ia087519106983bfa9a980e471d3102ab391a53eb
2020-02-12 08:01:50 -08:00
.bazelci Adds integration test for cc_shared_library. 2019-11-15 05:36:47 -08:00
cc Remove need for exported_by or linked_statically_by 2020-02-12 08:01:50 -08:00
distro Fix buildifier warnings in @rules_cc 2019-10-24 07:01:25 -07:00
examples Remove need for exported_by or linked_statically_by 2020-02-12 08:01:50 -08:00
tests/load_from_macro Fix immutable frozen set bug in defs.bzl 2019-11-29 04:19:02 -08:00
third_party Remove need for exported_by or linked_statically_by 2020-02-12 08:01:50 -08:00
tools Explicitly export files needed by other packages 2019-11-13 04:27:16 -08:00
.gitignore Add things needed for rules_cc to build & test in the open 2019-01-09 08:59:09 +01:00
BUILD rules_cc: Add top-level BUILD file to distribution. 2019-10-17 08:30:50 -07:00
CODEOWNERS Add CODEOWNERS for rules_cc. 2019-02-05 02:22:15 -08:00
CONTRIBUTING.md Add initial content of rules_cc repo 2019-01-09 08:58:14 +01:00
ISSUE_TEMPLATE.md Fix issue template 2019-02-27 01:37:03 -08:00
LICENSE Internal change 2019-01-09 08:56:00 +01:00
README.md Replace Python with Starlark. 2020-02-03 09:25:33 +03:00
WORKSPACE Remove need for exported_by or linked_statically_by 2020-02-12 08:01:50 -08: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(
    ...
)

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: