mirror of
https://github.com/bazelbuild/rules_cc
synced 2024-12-03 02:53:18 +00:00
ca8483971c
*** Reason for rollback ***
Rollforward with fix for b/365154741
*** Original change description ***
Automated rollback of commit 0bc1ba56ef.
*** Reason for rollback ***
TAP failures in Bazel/Blaze, see b/365154741 and discussion at https://chat.google.com/room/AAAAXE3XKrY/_e3TpBFJvus
*** Original change description ***
Add user-facing documentation for cc_tool_map
BEGIN_PUBLIC
Add user-facing documentation for cc_tool_map
Adds user-facing documentation for the cc_tool_map toolchain rule, including an example and higher level analogies.
END_PUBLIC
***
***
PiperOrigin-RevId: 672000172
Change-Id: If7ad64e2378a2016d389a3718944aa04bc5e9759
20 lines
644 B
Python
20 lines
644 B
Python
# This directory contains implementations of starlark functions that contain
|
|
# complex logic. The objective is to keep the rules themselves as simple as
|
|
# possible, so that we can perform very thorough testing on the implementation.
|
|
|
|
# I wanted to call it private / internal, but then buildifier complains about
|
|
# referencing it from the tests directory.
|
|
|
|
load("@bazel_skylib//:bzl_library.bzl", "bzl_library")
|
|
|
|
exports_files(
|
|
["documented_api.bzl"],
|
|
visibility = ["//cc/toolchains:__subpackages__"],
|
|
)
|
|
|
|
bzl_library(
|
|
name = "toolchain_impl_rules",
|
|
srcs = glob(["*.bzl"]),
|
|
visibility = ["//cc/toolchains:__subpackages__"],
|
|
)
|