|author||Marcel Hlopko <firstname.lastname@example.org>||Mon May 27 10:47:06 2019 +0200|
|committer||Marcel Hlopko <email@example.com>||Mon May 27 10:47:06 2019 +0200|
Add find_cc_toolchain.bzl to help accessing current C++ toolchain This is to help migrating for: * https://github.com/bazelbuild/bazel/issues/7260 * https://github.com/bazelbuild/bazel/issues/7643 It's mostly a copy of the file in `@bazel_tools//tools/cpp:toolchain_utils.bzl`, with a small difference - it depends on `@rules_cc//cc:toolchain_type`, not on `@bazel_tools//tools/cpp:toolchain_type`.
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.
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: