Google Git
Sign in
bazel / rules_cc / 262ebec3c2296296526740db4aefce68c80de7fa
commit262ebec3c2296296526740db4aefce68c80de7fa[log] [tgz]
authorGoogler <hlopko@google.com>Thu Oct 24 07:01:01 2019 -0700
committerCopybara-Service <copybara-worker@google.com>Thu Oct 24 07:01:25 2019 -0700
tree5f2f55804d800b6c417cdc886c0f09cea70710e2
parent0e66ef31d611b9fe5b762bc7b363e15134c53c85 [diff]
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
41 files changed
tree: 5f2f55804d800b6c417cdc886c0f09cea70710e2
  1. .bazelci/
  2. cc/
  3. distro/
  4. examples/
  5. third_party/
  6. tools/
  7. .gitignore
  8. BUILD
  9. CODEOWNERS
  10. CONTRIBUTING.md
  11. internal_deps.bzl
  12. internal_setup.bzl
  13. ISSUE_TEMPLATE.md
  14. LICENSE
  15. README.md
  16. renovate.json
  17. WORKSPACE
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: