bazel
/
rules_cc
mirror of https://github.com/bazelbuild/rules_cc
2
0
Fork 0
Code Issues Releases Activity
C++ Rules for Bazel
170 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
Googler 262ebec3c2 Fix buildifier warnings in @rules_cc 
Fixes:

* Enabled buildifier on the Bazel CI again
* Added Skydocs where missing
* Moved public files out of .../private/... (e.g. cc_toolchain_config_lib.bzl)
* Reformatted
* Removed unused loads
* Using relative labels for cc_configure related files
* Added development dependency on rules_proto
    * they're not in the federation yet, so hand rolling in rules_cc's WORKSPACE file
* Added development dependency on rules_python (from federation)
* Cleaned up copybara (notable change - not using @rules_cc in labels inside rules_cc repo)
* Made cc_flags_supplier usable internally
* Moved load statements to the top of the bzl file
* Moved runfiles to the tools directory
* Unified toolchain_utils.bzl and find_cc_toolchain.bzl

RELNOTES: None.
PiperOrigin-RevId: 276479521
Change-Id: I3196896061fa2ee61a3efb130c214d288782066a
 		2019-10-24 07:01:25 -07:00
.bazelci Fix buildifier warnings in @rules_cc 2019-10-24 07:01:25 -07:00
cc Fix buildifier warnings in @rules_cc 2019-10-24 07:01:25 -07:00
distro Fix buildifier warnings in @rules_cc 2019-10-24 07:01:25 -07:00
examples Fix buildifier warnings in @rules_cc 2019-10-24 07:01:25 -07: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 Refactor rules_cc to follow https://docs.bazel.build/versions/master/skylark/deploying.html 2019-06-18 00:21:44 -07:00
WORKSPACE Fix buildifier warnings in @rules_cc 2019-10-24 07:01:25 -07: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 Fix buildifier warnings in @rules_cc 2019-10-24 07:01:25 -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: