Google Git
Sign in
bazel / rules_cc / 29da92c66c3b36cd2d50b496aa88b270b7842aec
commit29da92c66c3b36cd2d50b496aa88b270b7842aec[log] [tgz]
authorfweikert <fwe@google.com>Fri Sep 13 18:24:56 2019 +0200
committerfweikert <fwe@google.com>Tue Sep 17 18:00:18 2019 +0200
tree9058300b745ad4737f4a95d6f769119a009b6a18
parent42ed56d8acbd9938b4ee8b2066d2c4c898a22504 [diff]
Use rules_pkg for building releases

This commit allows the creation of distributions, with 0.0.1 being the first version.
See distro/README.md for details on how to build a release.

This commit also uses a new version of the Bazel federation that contains rules_pkg 0.2.2 instead of 0.2.1.

There are still some problems with the WORKSPACE stanza that is being printed by the release notes generation script, though:
- It references a //cc:deps.bzl file, which doesn't exist. I have to modify the scripts in rules_pkg to support a flag like 'has_deps'.
- It doesn't support the Bazel federation yet, since it always tells users to download code from the rules_cc repository.
8 files changed
tree: 9058300b745ad4737f4a95d6f769119a009b6a18
  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: