bazel/rules_cc
2
0
Fork 0
mirror of https://github.com/bazelbuild/rules_cc synced 2024-11-25 17:31:30 +00:00
Code Issues Releases Activity
C++ Rules for Bazel
161 commits 15 branches 20 tags 1.9 MiB
Starlark 83.1%
C++ 7.5%
Smarty 4.9%
Shell 4.4%
Batchfile 0.1%
Find a file
Florian Weikert df4a51f42e Use latest federation version 
This version includes rules_pkg 0.2.4, which contains the fix required to cut a first rules_cc release.
2019-09-30 15:10:00 +02:00
.bazelci Stop running Buildifier as part of the presubmit 2019-08-27 01:51:17 -07:00
cc Use rules_pkg for building releases 2019-09-17 18:00:18 +02:00
distro Use rules_pkg for building releases 2019-09-17 18:00:18 +02:00
examples C++: Move tools/cpp from bazel_tools to rules_cc 2019-08-21 07:30:04 -07:00
third_party Replace scrubbing with copybara-comment-this-out-please in copybara 2019-03-14 17:13:28 +01:00
tools/migration Add a cc_toolchain_config_compare_test that compares 2 Starlark C++ toolchain configuration rules 2019-08-09 05:56:16 -07:00
.gitignore
BUILD Use rules_pkg for building releases 2019-09-17 18:00:18 +02:00
CODEOWNERS
CONTRIBUTING.md
internal_deps.bzl Use rules_pkg for building releases 2019-09-17 18:00:18 +02:00
internal_setup.bzl Use rules_pkg for building releases 2019-09-17 18:00:18 +02:00
ISSUE_TEMPLATE.md
LICENSE
README.md Refactor rules_cc to follow https://docs.bazel.build/versions/master/skylark/deploying.html 2019-06-18 00:21:44 -07:00
renovate.json
WORKSPACE Use latest federation version 2019-09-30 15:10:00 +02: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: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: