Google Git
Sign in
bazel / rules_cc / 0b8e7b5940e0f1ed21fec09ea1bea918b0ac5935
commit0b8e7b5940e0f1ed21fec09ea1bea918b0ac5935[log] [tgz]
authorhlopko <hlopko@google.com>Thu Mar 07 00:01:43 2019 -0800
committerCopybara-Service <copybara-worker@google.com>Thu Mar 07 00:02:00 2019 -0800
treed3972f14d314fa90f972c78d5c98da9c6a5ddd4e
parent2d3bc12294953888a091a7f49fcf72239d3a8ca3 [diff]
Use is_using_fission in legacy_fields_migrator

Since unknown commit is submitted, the principled variable to use in per_object_debug_info is is_using_fission, not per_object_debug_info_file (in case of thinlto build, the former is present also for thinlto bitcode compile, the latter only for backend compile).

RELNOTES: None.
PiperOrigin-RevId: 237192121
2 files changed
tree: d3972f14d314fa90f972c78d5c98da9c6a5ddd4e
  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. 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: