Update documentation of //tools/cpp:current_cc_toolchain to instead…

… refer to `//tools/cpp:toolchain_type`. PiperOrigin-RevId: 693392965 Change-Id: Ic6a3d3bad51574aeb4e15c6ab4f7d4416543c470
katre · Nov 5, 2024 · c79bc21 · c79bc21
1 parent 2ebc759
commit c79bc21
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/src/main/java/com/google/devtools/build/docgen/templates/attributes/common/toolchains.html b/src/main/java/com/google/devtools/build/docgen/templates/attributes/common/toolchains.html
@@ -8,7 +8,7 @@
   include:
 
 <ul>
-    <li><code>@bazel_tools//tools/cpp:current_cc_toolchain</code>
+    <li><code>@bazel_tools//tools/cpp:toolchain_type</code>
   <li><code>@bazel_tools//tools/jdk:current_java_runtime</code>
   </ul>
 

diff --git a/src/main/java/com/google/devtools/build/docgen/templates/be/make-variables.vm b/src/main/java/com/google/devtools/build/docgen/templates/be/make-variables.vm
@@ -411,7 +411,7 @@ instead.
 <p>
   The following are defined in C++ toolchain rules and available to any rule
   that sets <code>toolchains =
-  ["@bazel_tools//tools/cpp:current_cc_toolchain"]</code>
+  ["@bazel_tools//tools/cpp:toolchain_type"]</code>
   Some rules, like <code><a
   href="$expander.expandRef("java_binary")">java_binary</a></code>, implicitly
   include the C++ toolchain in their rule definition. They inherit these variables