bazel/rules_cc
2
0
Fork 0
mirror of https://github.com/bazelbuild/rules_cc synced 2024-11-26 20:02:22 +00:00
Code Issues Releases Activity
C++ Rules for Bazel
154 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
Googler c2790137ae Stop running Buildifier as part of the presubmit 
We now have copies of .bzl files that we have to keep in sync between @rules_cc and @bazel_tools/tools
I propose to re-enable the Buildifier presubmit once this issue is resolved.

*** Original change description ***

Run Buildifier as part of the presubmit.

As a result we will catch some errors already in GitHub, and not later in Critique when it's harder to fix them.

***

PiperOrigin-RevId: 265636234
Change-Id: I10730665134240b3f47950e0e8fa0add8e0bd591
2019-08-27 01:51:17 -07:00
.bazelci Stop running Buildifier as part of the presubmit 2019-08-27 01:51:17 -07:00
cc Update copyright year in BUILD file. 2019-08-26 08:06:40 -07: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 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
internal_deps.bzl Merge pull request #31 from fweikert:merge 2019-08-12 11:19:21 -07:00
internal_setup.bzl Merge pull request #31 from fweikert:merge 2019-08-12 11:19:21 -07: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 Refactor rules_cc to follow https://docs.bazel.build/versions/master/skylark/deploying.html 2019-06-18 00:21:44 -07:00
renovate.json Automated rollback of commit a613d78865. 2019-03-07 02:55:44 -08:00
WORKSPACE C++: Move tools/cpp from bazel_tools to rules_cc 2019-08-21 07:30:04 -07: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: