|author||Yannic Bonenberger <email@example.com>||Wed May 06 06:52:09 2020 -0700|
|committer||Copybara-Service <firstname.lastname@example.org>||Wed May 06 06:52:27 2020 -0700|
Add optional tool_path_origin to Tools in C++ crosstool This change adds an optional field to the C++ crosstool proto that allows configuring the origin tool_path is relative to. For now, the origin can be one of the following: - CROSSTOOL_PACKAGE: If tool_path is a relative path, it's assumed to be relative to the package of the crosstool top. - FILESYSTEM_ROOT: tool_path is an absolute path. This is checked by Bazel. - WORKSPACE_ROOT: tool_path must be a relative path and is assumed to be relative to the exec-root of the workspace (similar to other executables). Updates bazelbuild/bazel#8438 Closes #10967. PiperOrigin-RevId: 310142352 Change-Id: If6316ffa5d7d2713b197840b4aafb2f0cdbb0b96
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
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.
bazel run @rules_cc//tools/migration:legacy_fields_migrator -- \ --input=my_toolchain/CROSSTOOL \ --inline
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: