| commit | ddf13fe1da21df51e21f5fd80f35a579d6f09bb7 | [log] [tgz] |
|---|---|---|
| author | hlopko <hlopko@google.com> | Thu Jan 24 04:55:01 2019 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Jan 24 04:55:15 2019 -0800 |
| tree | 2236de08fb305468fbf69b1eb770c619669719cb | |
| parent | a9932b39398dde579d1c5b9bba84d6eefeb6900a [diff] |
Don't require supports_fission to be set in the crosstool Having a 'per_object_debug_data' feature enabled is giving the same signal as having supports_fission enabled. This is a safe change because all crosstools that have supports_fission: true have per_object_debug_info disabled, and with the legacy crosstool fields migration we will migrate this feature to be enabled by default for these crosstools. https://github.com/bazelbuild/bazel/issues/6861 https://github.com/bazelbuild/bazel/issues/5883 RELNOTES: None. PiperOrigin-RevId: 230701029
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:rules.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