bazel
/
rules_cc
mirror of https://github.com/bazelbuild/rules_cc
2
0
Fork 0
Code Issues Releases Activity
C++ Rules for Bazel
189 Commits 15 Branches 20 Tags 1.9 MiB
Starlark 83.1%
C++ 7.5%
Smarty 4.9%
Shell 4.4%
Batchfile 0.1%
Go to file
Philipp Wollermann 6ecee7ec8f
Example config for using Bazel HEAD on CI 		2019-11-12 15:00:34 +01:00
.bazelci Example config for using Bazel HEAD on CI 2019-11-12 15:00:34 +01:00
cc Fix codebase in preparation for incompatible_use_cc_configure_from_rules_cc 2019-11-12 04:35:10 -08:00
distro Fix buildifier warnings in @rules_cc 2019-10-24 07:01:25 -07:00
examples C++: Checks in prototype of cc_shared_libraryA 2019-11-12 05:06:44 -08:00
third_party Fix buildifier warnings in @rules_cc 2019-10-24 07:01:25 -07:00
tools Fix buildifier warnings in @rules_cc 2019-10-24 07:01:25 -07: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 Add badge for incompatible flag pipeline 2019-11-04 12:38:06 +01:00
WORKSPACE Fix call in WORKSPACE 2019-11-01 16:39:47 +01: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: