commit | 7f0992b0bd47d5b24076c2d022ba1819cc8641e4 | [log] [tgz] |
---|---|---|
author | Googler <gnish@google.com> | Tue May 02 06:19:19 2023 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Tue May 02 06:19:53 2023 -0700 |
tree | 4cc327d92180e6072696a12c8751d03f2dfdc030 | |
parent | 2e4313aeba18bb350f77bcbe22bc0fe14b5d8c03 [diff] |
Remove `cc_host_toolchain_alias` target. Right now there should be no difference between `cc_host_toolchain_alias` and `cc_toolchain_alias` rules. This is a potentially breaking change for Bazel, if something was depending on `current_cc_host_toolchain` try depending on `current_cc_toolchain` instead. PiperOrigin-RevId: 528762965 Change-Id: Id2d211c61fa06a578a838c054682c3507aa48261
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/refs/tags/<VERSION>.tar.gz"], sha256 = "...", )
Then, in your BUILD
files, import and use the rules:
load("@rules_cc//cc:defs.bzl", "cc_library") cc_library( ... )
If you'd like to use the cc toolchain defined in this repo add this to your WORKSPACE after you include rules_cc:
load("@rules_cc//cc:repositories.bzl", "rules_cc_dependencies", "rules_cc_toolchains") rules_cc_dependencies() rules_cc_toolchains()
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
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:
rules_cc
mailing list#cc
on slack.bazel.build