commit | 8cded3e3c34cec15b30758b76bc24243df97a8b8 | [log] [tgz] |
---|---|---|
author | Googler <noreply@google.com> | Wed Oct 28 05:26:38 2020 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Wed Oct 28 05:27:07 2020 -0700 |
tree | 5d80ac78b06a1616485067418858b9fbef734d48 | |
parent | b2f6e22c344b095af2d4390e97c4e93537f4cd5e [diff] |
Add constants for common groups of action names. These are used throughout the Crosstool features definitions based on local definitions there. It seems useful to move these to a common location so they are available for other toolchains (and also so that they get updated if new actions are added to the action-name list). The versions of these currently used by Crosstool are defined in //third_party/crosstool/v18/llvm_unstable/crosstool_helpers.bzl starting at line 124. Tested: by inspection PiperOrigin-RevId: 339440647 Change-Id: I3a2b8d37aebd8a0e8450864e079cf5b42d075def
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:defs.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
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