Google Git
Sign in
bazel / rules_cc / 10f38e16da5c5c9acd02228ffcf0eb2cff0679f4
commit10f38e16da5c5c9acd02228ffcf0eb2cff0679f4[log] [tgz]
authorhlopko <hlopko@google.com>Fri Mar 15 13:24:56 2019 -0700
committerCopybara-Service <copybara-worker@google.com>Fri Mar 15 13:25:11 2019 -0700
tree3a65a851ae44ea5b88eefc0aa92977252ba0ef0a
parentb844e0c4b8e941204cecb76a616e9e81c0102339 [diff]
Fix migrator to correctly migrate dynamic linking mode linker_flags

This would have not introduced the osx crosstool bug in https://github.com/bazelbuild/bazel/commit/2d0e27e8bc7452758e8f50b51fd470efb8111e1f which was then fixed in unknown commit.

RELNOTES: None.
PiperOrigin-RevId: 238699176
2 files changed
tree: 3a65a851ae44ea5b88eefc0aa92977252ba0ef0a
  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: