| commit | 04195ada1783263b561bbd98d03ad167a559c43b | [log] [tgz] |
|---|---|---|
| author | hlopko <hlopko@google.com> | Tue Jan 15 02:09:04 2019 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Jan 15 02:09:19 2019 -0800 |
| tree | 51020fcbf8874166aeacd8f12c486114ac76015d | |
| parent | 5a13c618589282a86eaa54f539ed5d9bfd0d3f1e [diff] |
Fix legacy_fields_migrator Another round of fixes: * if the toolchain contains legacy_compile_flags or legacy_link_flags, replace the feature with default_compile_flags or default_link_flags. This is to ensure the location of the flags stays intact. * it fixes the order of compilation flags, the correct order is: 1) compiler_flag 2) compilation_mode_flags.compiler_flag 3) cxx_flag 4) compilation_mode_flags.cxx_flag * We don't add cxx_flags to assemble and preprocess-assemble actions * We don't add sysroot to assemble action https://github.com/bazelbuild/bazel/issues/6861 https://github.com/bazelbuild/bazel/issues/5883 RELNOTES: None. PiperOrigin-RevId: 229336027
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