commit | ea5c5422a6b9e79e6432de3b2b29bbd84eb41081 | [log] [tgz] |
---|---|---|
author | Googler <rosica@google.com> | Tue Aug 27 03:33:31 2019 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Tue Aug 27 03:33:52 2019 -0700 |
tree | 47c87b1f1495291444ba09cb903e4ee12d260c9a | |
parent | c2790137aedbdbcabe4858ceff53a7339c0a699a [diff] |
Add support for thin LTO optimization in Bazel Usage: CC=clang bazel build //foo:bar --features=thin_lto -c opt RELNOTES: Bazel now supports ThinLTO builds on Linux for Clang versions >= 6.0. ThinLTO can be enabled through --features=thin_lto PiperOrigin-RevId: 265649618 Change-Id: I68a38b8b8c1480e3b73d8e6f24e9dafece2c7de6
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.
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( ... )
This repository also contains migration tools that can be used to migrate your project for Bazel incompatible changes.
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
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:
#cc
on slack.bazel.build