bazel
/
rules_cc
mirror of https://github.com/bazelbuild/rules_cc
2
0
Fork 0
Code Issues Releases Activity
C++ Rules for Bazel
103 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
hlopko 3d5980e5cb Add example writing custom rule that depends and is dependable from rules_cc 
RELNOTES: None.
PiperOrigin-RevId: 235869541
 		2019-02-27 00:37:05 -08:00
.bazelci Add initial bazelci config for rules_cc 2019-01-11 00:05:29 -08:00
.github/ISSUE_TEMPLATE Let's see if this fixes issue template 2019-02-26 04:55:08 -08:00
cc Add initial content of rules_cc repo 2019-01-09 08:58:14 +01:00
examples Add example writing custom rule that depends and is dependable from rules_cc 2019-02-27 00:37:05 -08:00
third_party Automated rollback of commit 2e79abf8ca. 2019-02-20 01:41:00 -08:00
tools/migration Clear dynamic_library_linker_flag in legacy_fields_migrator 2019-02-20 00:25:12 -08:00
.gitignore Add things needed for rules_cc to build & test in the open 2019-01-09 08:59:09 +01:00
BUILD Internal change 2019-01-09 08:56:00 +01: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
LICENSE Internal change 2019-01-09 08:56:00 +01:00
README.md List places to ask questions for rules_cc 2019-02-26 05:11:07 -08:00
WORKSPACE Add a script for converting CROSSTOOL files to Starlark rules 2019-01-24 14:54:38 -08:00

README.md

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: