commit | 903ad72c430c369ca65c49a552fc2f9f43ec2fd0 | [log] [tgz] |
---|---|---|
author | rosica <rosica@google.com> | Thu Feb 07 01:04:39 2019 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Thu Feb 07 01:04:52 2019 -0800 |
tree | 12a7b434a2b94c8286a0705cf534b96585b80bd3 | |
parent | d4fef611196fd572c017f0a3006e8db78f369951 [diff] |
Make CToolchain comparator ignore differences in CToolchain.Tool.tool_path and CToolcain.ToolPath.path when one is "" and the other "NOT_USED" Starlark constructors for tool_path and tool do not allow empty strings for the path field. Therefore the migrator replaces the "" with "NOT_USED". We should ignore this difference when comparing the CToolchains. #5380 PiperOrigin-RevId: 232827179
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