diff options
Diffstat (limited to 'src/main/java/com/google')
10 files changed, 12 insertions, 12 deletions
diff --git a/src/main/java/com/google/devtools/build/docgen/templates/attributes/binary/output_licenses.html b/src/main/java/com/google/devtools/build/docgen/templates/attributes/binary/output_licenses.html index e474e71850..6cf91eb6d0 100644 --- a/src/main/java/com/google/devtools/build/docgen/templates/attributes/binary/output_licenses.html +++ b/src/main/java/com/google/devtools/build/docgen/templates/attributes/binary/output_licenses.html @@ -20,7 +20,7 @@ regular dependency. <p> (For more about the distinction between host and target configurations, -see <a href="../bazel-user-manual.html#configurations">Build +see <a href="../user-manual.html#configurations">Build configurations</a> in the Bazel manual.)</p> <p> diff --git a/src/main/java/com/google/devtools/build/docgen/templates/attributes/common/tags.html b/src/main/java/com/google/devtools/build/docgen/templates/attributes/common/tags.html index 67a87e3006..200fefa59e 100644 --- a/src/main/java/com/google/devtools/build/docgen/templates/attributes/common/tags.html +++ b/src/main/java/com/google/devtools/build/docgen/templates/attributes/common/tags.html @@ -24,7 +24,7 @@ <ul> <li><code>local</code> keyword results in the action or test never being run remotely or inside the - <a href="../bazel-user-manual.html#sandboxing">sandbox</a>. + <a href="../user-manual.html#sandboxing">sandbox</a>. For genrules and tests, marking the rule with the <code>local = 1</code> attribute has the same effect. </li> diff --git a/src/main/java/com/google/devtools/build/docgen/templates/be/common-definitions.vm b/src/main/java/com/google/devtools/build/docgen/templates/be/common-definitions.vm index 9ccae80b55..270a172beb 100644 --- a/src/main/java/com/google/devtools/build/docgen/templates/be/common-definitions.vm +++ b/src/main/java/com/google/devtools/build/docgen/templates/be/common-definitions.vm @@ -118,7 +118,7 @@ labels attribute. Most attributes can be "configured" so their values depend on the flags passed at the command line. This can be used, for example, to declare platform-dependent <code>srcs</code> or custom compiler flags depending on the - <a href="../bazel-user-manual.html#flag--compilation_mode">compilation + <a href="../user-manual.html#flag--compilation_mode">compilation mode</a>. </p> diff --git a/src/main/java/com/google/devtools/build/docgen/templates/be/functions.vm b/src/main/java/com/google/devtools/build/docgen/templates/be/functions.vm index 525459f38a..dc85bebc69 100644 --- a/src/main/java/com/google/devtools/build/docgen/templates/be/functions.vm +++ b/src/main/java/com/google/devtools/build/docgen/templates/be/functions.vm @@ -474,7 +474,7 @@ There are several important limitations and caveats: existence of BUILD files — that is, the same glob expression would include <code>x/y/z.cc</code> if there was no package called <code>x/y</code> or it was marked as deleted using the - <a href="../bazel-user-manual.html#flag--deleted_packages">--deleted_packages</a> + <a href="../user-manual.html#flag--deleted_packages">--deleted_packages</a> flag. </li> diff --git a/src/main/java/com/google/devtools/build/lib/bazel/rules/genrule/BazelGenRuleRule.java b/src/main/java/com/google/devtools/build/lib/bazel/rules/genrule/BazelGenRuleRule.java index 7130e87e18..c2ef057882 100644 --- a/src/main/java/com/google/devtools/build/lib/bazel/rules/genrule/BazelGenRuleRule.java +++ b/src/main/java/com/google/devtools/build/lib/bazel/rules/genrule/BazelGenRuleRule.java @@ -87,7 +87,7 @@ public final class BazelGenRuleRule implements RuleDefinition { <h4>Cross-compilation Considerations</h4> <p> - <em>See <a href="../bazel-user-manual.html#configurations">the user manual</a> for more info about + <em>See <a href="../user-manual.html#configurations">the user manual</a> for more info about cross-compilation.</em> </p> <p> @@ -126,7 +126,7 @@ public final class BazelGenRuleRule implements RuleDefinition { host configuration, because that's where the compiler will run in the other genrule. In this case, the build system does the right thing automatically: it builds the <code>srcs</code> and <code>outs</code> of the first genrule for the host configuration instead of the target - configuration. See <a href="../bazel-user-manual.html#configurations">the user manual</a> for more + configuration. See <a href="../user-manual.html#configurations">the user manual</a> for more info. </p> <p> diff --git a/src/main/java/com/google/devtools/build/lib/bazel/rules/java/BazelJavaRuleClasses.java b/src/main/java/com/google/devtools/build/lib/bazel/rules/java/BazelJavaRuleClasses.java index 73fbf27975..d77acf74b7 100644 --- a/src/main/java/com/google/devtools/build/lib/bazel/rules/java/BazelJavaRuleClasses.java +++ b/src/main/java/com/google/devtools/build/lib/bazel/rules/java/BazelJavaRuleClasses.java @@ -434,7 +434,7 @@ public class BazelJavaRuleClasses { <li><code>stamp = 0</code>: Always replace build information by constant values. This gives good build result caching.</li> <li><code>stamp = -1</code>: Embedding of build information is controlled by the - <a href="../blaze-user-manual.html#flag--stamp">--[no]stamp</a> flag.</li> + <a href="../user-manual.html#flag--stamp">--[no]stamp</a> flag.</li> </ul> <!-- #END_BLAZE_RULE.ATTRIBUTE --> */ // TODO(bazel-team): describe how to access this data at runtime @@ -451,7 +451,7 @@ public class BazelJavaRuleClasses { indicates that you want to use the normal JDK launcher (bin/java or java.exe) as the value for this attribute. This is the default.</p> - <p>The related <a href="../blaze-user-manual.html#flag--java_launcher"><code> + <p>The related <a href="../user-manual.html#flag--java_launcher"><code> --java_launcher</code></a> Bazel flag affects only those <code>java_binary</code> and <code>java_test</code> targets that have <i>not</i> specified a <code>launcher</code> attribute.</p> diff --git a/src/main/java/com/google/devtools/build/lib/bazel/rules/python/BazelPyRuleClasses.java b/src/main/java/com/google/devtools/build/lib/bazel/rules/python/BazelPyRuleClasses.java index 85743d3c18..006b82c660 100644 --- a/src/main/java/com/google/devtools/build/lib/bazel/rules/python/BazelPyRuleClasses.java +++ b/src/main/java/com/google/devtools/build/lib/bazel/rules/python/BazelPyRuleClasses.java @@ -186,7 +186,7 @@ public final class BazelPyRuleClasses { <li><code>stamp = 0</code>: Always replace build information by constant values. This gives good build result caching.</li> <li><code>stamp = -1</code>: Embedding of build information is controlled - by the <a href="../blaze-user-manual.html#flag--stamp">--[no]stamp</a> Blaze + by the <a href="../user-manual.html#flag--stamp">--[no]stamp</a> Blaze flag.</li> </ul> <!-- #END_BLAZE_RULE.ATTRIBUTE --> */ diff --git a/src/main/java/com/google/devtools/build/lib/rules/android/AndroidBinaryOnlyRule.java b/src/main/java/com/google/devtools/build/lib/rules/android/AndroidBinaryOnlyRule.java index 8991bdfe3f..c1b8bd27aa 100644 --- a/src/main/java/com/google/devtools/build/lib/rules/android/AndroidBinaryOnlyRule.java +++ b/src/main/java/com/google/devtools/build/lib/rules/android/AndroidBinaryOnlyRule.java @@ -66,7 +66,7 @@ public final class AndroidBinaryOnlyRule implements RuleDefinition { <li><code>shrink_resources = 1</code>: Turns on Android resource shrinking</li> <li><code>shrink_resources = 0</code>: Turns off Android resource shrinking</li> <li><code>shrink_resources = -1</code>: Shrinking is controlled by the - <a href="../blaze-user-manual.html#flag--android_resource_shrinking"> + <a href="../user-manual.html#flag--android_resource_shrinking"> --android_resource_shrinking</a> flag.</li> </ul> <!-- #END_BLAZE_RULE.ATTRIBUTE --> */ diff --git a/src/main/java/com/google/devtools/build/lib/rules/android/AndroidRuleClasses.java b/src/main/java/com/google/devtools/build/lib/rules/android/AndroidRuleClasses.java index 14fef3ac13..ed17b9725f 100644 --- a/src/main/java/com/google/devtools/build/lib/rules/android/AndroidRuleClasses.java +++ b/src/main/java/com/google/devtools/build/lib/rules/android/AndroidRuleClasses.java @@ -885,7 +885,7 @@ public final class AndroidRuleClasses { <code><uses-permission></code> and <code><uses-permission-sdk-23></code> tags. Performs an attribute-level merge.</li> <li><code>manifest_merger = "auto"</code>: Merger is controlled by the - <a href="../blaze-user-manual.html#flag--android_manifest_merger"> + <a href="../user-manual.html#flag--android_manifest_merger"> --android_manifest_merger</a> flag.</li> </ul> <!-- #END_BLAZE_RULE.ATTRIBUTE --> */ diff --git a/src/main/java/com/google/devtools/build/lib/rules/genrule/GenRuleBaseRule.java b/src/main/java/com/google/devtools/build/lib/rules/genrule/GenRuleBaseRule.java index c6a1f2a0f5..082904ae81 100644 --- a/src/main/java/com/google/devtools/build/lib/rules/genrule/GenRuleBaseRule.java +++ b/src/main/java/com/google/devtools/build/lib/rules/genrule/GenRuleBaseRule.java @@ -95,7 +95,7 @@ public class GenRuleBaseRule implements RuleDefinition { <a href="../build-ref.html#deps">dependencies</a> for more information. <br/> <p> The build system ensures these prerequisites are built before running the genrule command; - they are built using the <a href='../blaze-user-manual.html#configurations'><i>host</i> + they are built using the <a href='../user-manual.html#configurations'><i>host</i> configuration</a>, since these tools are executed as part of the build. The path of an individual <code>tools</code> target <code>//x:y</code> can be obtained using <code>$(location //x:y)</code>. |