commit | 7c0a3bbee1c90c40abaa45274d9abb4fee506e4c | [log] [tgz] |
---|---|---|
author | Googler <noreply@google.com> | Thu Mar 21 15:44:09 2024 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Thu Mar 21 15:45:05 2024 -0700 |
tree | 72dd430a55e8e01c443575da17091574b9b5e672 | |
parent | 17143d150dd4ea0e46775468382683eb0a884450 [diff] |
Refactor action sets for consistency and simplicity BEGIN_PUBLIC Refactor action sets for consistency and simplicity * Remove the "CC" prefix on some of the actions, as we're already within the scope of rules_cc. * Remove the "all" prefix, since the plural "actions" should already imply this. * Ensure all action types sets end with "_actions" * Refactor some action type sets to be constructed from other (eg. link actions = link executables + link dynamic libraries). * Remove the redundant "all_compile_actions", since it was equivalent to "all_cc_compile_actions" END_PUBLIC PiperOrigin-RevId: 617985242 Change-Id: I9a3621a9d613ff604efdc5c86ba52e5c77f06731
This repository contains a 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( ... )
This repo contains an auto-detecting toolchain that expects to find tools installed on your host machine. This is non-hermetic, and may have varying behaviors depending on the versions of tools found.
There are third-party contributed hermetic toolchains you may want to investigate:
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