rules_cc/cc/toolchains/impl/BUILD

# 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 = ["//docs:__pkg__"],
)

bzl_library(
    name = "toolchain_impl_rules",
    srcs = glob(["*.bzl"]),
    visibility = ["//cc/toolchains:__subpackages__"],
)
BEGIN_PUBLIC Implement cc_args. Also change cc_flag_set / cc_flag_group to cc_args / cc_arg_group. This is to lean into the idea that this is roughly equivalent to ctx.actions.args() END_PUBLIC PiperOrigin-RevId: 608804069 Change-Id: I74ea883b14219f904aaafc4eab902b96a1fb3e3d 2024-02-21 01:58:00 +00:00			`# 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.`
Automated rollback of commit 0f352c3497f480bbebc9507a1cfc2cdc9472b827. * Reason for rollback * Rollforward with fix for b/365154741 * Original change description * Automated rollback of commit 0bc1ba56ef2f8e791841bc074376a02ad8608dc2. * 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 2024-09-07 06:05:14 +00:00
			`load("@bazel_skylib//:bzl_library.bzl", "bzl_library")`

			`exports_files(`
			`["documented_api.bzl"],`
Make stardoc a dev dependency Otherwise rules_cc is transitively incompatible with Bazel 6 through the chain stardoc 0.7.0 -> rules_java 7.6.1. `stardoc` targets are not needed by consumers of the ruleset. 2024-10-01 06:32:55 +00:00			`visibility = ["//docs:__pkg__"],`
Automated rollback of commit 0f352c3497f480bbebc9507a1cfc2cdc9472b827. * Reason for rollback * Rollforward with fix for b/365154741 * Original change description * Automated rollback of commit 0bc1ba56ef2f8e791841bc074376a02ad8608dc2. * 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 2024-09-07 06:05:14 +00:00			`)`

			`bzl_library(`
			`name = "toolchain_impl_rules",`
			`srcs = glob(["*.bzl"]),`
			`visibility = ["//cc/toolchains:__subpackages__"],`
			`)`