Google Git
Sign in
bazel / rules_cc / 475ed28215e8845efe5dd03c9711eb36c2b16173
commit475ed28215e8845efe5dd03c9711eb36c2b16173[log] [tgz]
authorhlopko <hlopko@google.com>Thu Mar 07 02:55:12 2019 -0800
committerCopybara-Service <copybara-worker@google.com>Thu Mar 07 02:55:44 2019 -0800
tree220543792dc93b7f550baf7d44541a020eca96f1
parent0b8e7b5940e0f1ed21fec09ea1bea918b0ac5935 [diff]
Automated rollback of commit a613d7886555b65a8281c48e42fbcb30562c2a04.

*** Reason for rollback ***

And now rolling forward because apparently ospo approved renovate.

*** Original change description ***

Automated rollback of commit 776b274c8a6316cfc7f6b4cdea25a40223b5a831.

*** Reason for rollback ***

Because they use agpl licence.

*** Original change description ***

Enable 'renovate' bot for rules_cc

Fixes https://github.com/bazelbuild/rules_cc/pull/5.

RELNOTES: None.
PiperOrigin-RevId: 237213545
1 file changed
tree: 220543792dc93b7f550baf7d44541a020eca96f1
  1. .bazelci/
  2. cc/
  3. examples/
  4. third_party/
  5. tools/
  6. .gitignore
  7. BUILD
  8. CODEOWNERS
  9. CONTRIBUTING.md
  10. ISSUE_TEMPLATE.md
  11. LICENSE
  12. README.md
  13. renovate.json
  14. 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:rules.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: