aboutsummaryrefslogtreecommitdiffhomepage
path: root/src
diff options
context:
space:
mode:
authorGravatar Googler <noreply@google.com>2016-12-08 19:04:02 +0000
committerGravatar Irina Iancu <elenairina@google.com>2016-12-09 15:31:25 +0000
commit4d5dc970a9b2616b9c5eb260d089be7c4f17c582 (patch)
tree81178ce36c737cea7abb8adb0adea405330ae7e3 /src
parentdcce3fa3866b3a4af06cec0318dcdfad827bf676 (diff)
Say C and C++, when C and C++ is what we mean.
This document states that $(CC) is the "C compiler". This is incomplete and misleading; per comments at line 1799 of CppConfiguration.java, it is expected to be a binary that will compile both C and C++ code. -- PiperOrigin-RevId: 141459615 MOS_MIGRATED_REVID=141459615
Diffstat (limited to 'src')
-rw-r--r--src/main/java/com/google/devtools/build/docgen/templates/be/make-variables.vm10
1 files changed, 5 insertions, 5 deletions
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
index eeff7dc3c8..e56487d7a0 100644
--- 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
@@ -87,7 +87,7 @@ tests. Simply rely on the PATH.</p>
These tools may not be in the PATH, therefore you must use "Make" variable syntax
in your genrule's cmd attribute.
<ul>
- <li class="harmful"> <code>CC</code>: The C compiler command. The built-in C++
+ <li class="harmful"> <code>CC</code>: The C and C++ compiler command. The built-in C++
rules are much more sophisticated than "run the compiler on it". In order to
support compilation modes as diverse as *SAN, LIPO, ThinLTO, with/without
modules, and carefully optimized binaries at the same time as fast running
@@ -103,7 +103,7 @@ in your genrule's cmd attribute.
combination with <code>CC</code>. Fail to do so at your own risk.
</li>
<li class="harmful"> <code>C_COMPILER</code>:
- The C compiler frontend, e.g. "gcc".
+ The C/C++ compiler identifier, e.g. "gcc".
</li>
<li class="harmful"> <code>JAVA</code>: The "java" command (a Java virtual
machine). Avoid this, and use a <code>java_binary</code> rule instead where
@@ -112,18 +112,18 @@ in your genrule's cmd attribute.
working directory before changing it.
</li>
- <li> <code>STRIP</code>: The strip command from the same suite as the C
+ <li> <code>STRIP</code>: The strip command from the same suite as the C/C++
compiler.</li>
<li> <code>AR</code>: The "ar" command from crosstool. </li>
<li> <code>NM</code>: The "nm" command from crosstool. </li>
- <li> <code>OBJCOPY</code>: The objcopy command from the same suite as the C
+ <li> <code>OBJCOPY</code>: The objcopy command from the same suite as the C/C++
compiler. </li>
</ul>
<p><strong>Tool option Variables</strong></p>
<ul><!-- keep alphabetically sorted -->
- <li class="harmful"><code>CC_FLAGS</code>: A minimal set of flags for the C
+ <li class="harmful"><code>CC_FLAGS</code>: A minimal set of flags for the C/C++
compiler to be used by genrules. In particular, it contains flags to select
the correct architecture if <code>CC</code> supports multiple architectures.
</li>