Add "=" to flags in user manual
The usage was inconsistent, with some using "=" and some not.
Fixes #13146
PiperOrigin-RevId: 362157584
diff --git a/site/docs/user-manual.html b/site/docs/user-manual.html
index 142d93c..0072e33 100644
--- a/site/docs/user-manual.html
+++ b/site/docs/user-manual.html
@@ -102,7 +102,7 @@
These options control Bazel's error-checking and/or warnings.
</p>
-<h4 id='flag--check_constraint'><code class='flag'>--check_constraint <var>constraint</var></code></h4>
+<h4 id='flag--check_constraint'><code class='flag'>--check_constraint=<var>constraint</var></code></h4>
<p>
This option takes an argument that specifies which constraint
should be checked.
@@ -131,7 +131,7 @@
checking is done.
</p>
-<h4 id='flag--output_filter'><code class='flag'>--output_filter <var>regex</var></code></h4>
+<h4 id='flag--output_filter'><code class='flag'>--output_filter=<var>regex</var></code></h4>
<p>
The <code class='flag'>--output_filter</code> option will only show build and compilation
warnings for targets that match the regular expression. If a target does not
@@ -167,7 +167,7 @@
These options control which options Bazel will pass to other tools.
</p>
-<h4 id='flag--copt'><code class='flag'>--copt <var>cc-option</var></code></h4>
+<h4 id='flag--copt'><code class='flag'>--copt=<var>cc-option</var></code></h4>
<p>
This option takes an argument which is to be passed to the compiler.
The argument will be passed to the compiler whenever it is invoked
@@ -201,7 +201,7 @@
<code class='flag'>--linkopt</code>, not in <code class='flag'>--copt</code>.
</p>
-<h4 id='flag--host_copt'><code class='flag'>--host_copt <var>cc-option</var></code></h4>
+<h4 id='flag--host_copt'><code class='flag'>--host_copt=<var>cc-option</var></code></h4>
<p>
This option takes an argument which is to be passed to the compiler for source files
that are compiled in the host configuration. This is analogous to
@@ -209,7 +209,7 @@
host configuration.
</p>
-<h4 id='flag--host_cxxopt'><code class='flag'>--host_cxxopt <var>cc-option</var></code></h4>
+<h4 id='flag--host_cxxopt'><code class='flag'>--host_cxxopt=<var>cc-option</var></code></h4>
<p>
This option takes an argument which is to be passed to the compiler for C++ source files
that are compiled in the host configuration. This is analogous to
@@ -217,7 +217,7 @@
host configuration.
</p>
-<h4 id='flag--conlyopt'><code class='flag'>--conlyopt <var>cc-option</var></code></h4>
+<h4 id='flag--conlyopt'><code class='flag'>--conlyopt=<var>cc-option</var></code></h4>
<p>
This option takes an argument which is to be passed to the compiler when compiling C source files.
</p>
@@ -231,7 +231,7 @@
will be placed on the compiler command line <em>after</em> these options.
</p>
-<h4 id='flag--cxxopt'><code class='flag'>--cxxopt <var>cc-option</var></code></h4>
+<h4 id='flag--cxxopt'><code class='flag'>--cxxopt=<var>cc-option</var></code></h4>
<p>
This option takes an argument which is to be passed to the compiler when compiling C++ source
files.
@@ -250,7 +250,7 @@
will be placed on the compiler command line <em>after</em> these options.
</p>
-<h4 id='flag--linkopt'><code class='flag'>--linkopt <var>linker-option</var></code></h4>
+<h4 id='flag--linkopt'><code class='flag'>--linkopt=<var>linker-option</var></code></h4>
<p>
This option takes an argument which is to be passed to the compiler when linking.
</p>
@@ -299,7 +299,7 @@
<code class='flag'>--linkopt=-Wl,--strip-all</code>, so you should only set one or the other.
</p>
-<h4 id='flag--stripopt'><code class='flag'>--stripopt <var>strip-option</var></code></h4>
+<h4 id='flag--stripopt'><code class='flag'>--stripopt=<var>strip-option</var></code></h4>
<p>
An additional option to pass to the <code>strip</code> command when generating
a <a href="be/c-cpp.html#cc_binary_implicit_outputs"><code>*.stripped</code>
@@ -311,7 +311,7 @@
binary with <code><a href='#flag--strip'>--strip</a>=(always|sometimes)</code>.
</p>
-<h4 id='flag--fdo_instrument'><code class='flag'>--fdo_instrument <var>profile-output-dir</var></code></h4>
+<h4 id='flag--fdo_instrument'><code class='flag'>--fdo_instrument=<var>profile-output-dir</var></code></h4>
<p>
The <code class='flag'>--fdo_instrument</code> option enables the generation of
FDO (feedback directed optimization) profile output when the
@@ -337,7 +337,7 @@
</p>
-<h4 id='flag--fdo_optimize'><code class='flag'>--fdo_optimize <var>profile-zip</var></code></h4>
+<h4 id='flag--fdo_optimize'><code class='flag'>--fdo_optimize=<var>profile-zip</var></code></h4>
<p>
The <code class='flag'>--fdo_optimize</code> option enables the use of the
per-object file profile information to perform FDO (feedback
@@ -429,7 +429,7 @@
</p>
-->
-<h4 id='flag--jvmopt'><code class='flag'>--jvmopt <var>jvm-option</var></code></h4>
+<h4 id='flag--jvmopt'><code class='flag'>--jvmopt=<var>jvm-option</var></code></h4>
<p>
This option allows option arguments to be passed to the Java VM. It can be used
with one big argument, or multiple times with individual arguments. For example:
@@ -442,7 +442,7 @@
startup heap size for the VM to 256 MB.
</p>
-<h4 id='flag--javacopt'><code class='flag'>--javacopt <var>javac-option</var></code></h4>
+<h4 id='flag--javacopt'><code class='flag'>--javacopt=<var>javac-option</var></code></h4>
<p>
This option allows option arguments to be passed to javac. It can be used
with one big argument, or multiple times with individual arguments. For example:
@@ -535,7 +535,7 @@
</li>
</ul>
-<h4 id='flag--cpu'><code class='flag'>--cpu <var>cpu</var></code></h4>
+<h4 id='flag--cpu'><code class='flag'>--cpu=<var>cpu</var></code></h4>
<p>
This option specifies the target CPU architecture to be used for
the compilation of binaries during the build.
@@ -625,13 +625,13 @@
--experimental_extra_action_filter=.*/bar/.*
</pre>
-<h4 id='flag--host_cpu'><code class='flag'>--host_cpu <var>cpu</var></code></h4>
+<h4 id='flag--host_cpu'><code class='flag'>--host_cpu=<var>cpu</var></code></h4>
<p>
This option specifies the name of the CPU architecture that should be
used to build host tools.
</p>
-<h4 id='flag--fat_apk_cpu'><code class='flag'>--fat_apk_cpu <var>cpu[,cpu]*</var></code></h4>
+<h4 id='flag--fat_apk_cpu'><code class='flag'>--fat_apk_cpu=<var>cpu[,cpu]*</var></code></h4>
<p>
The CPUs to build C/C++ libraries for in the transitive <code>deps</code> of
<code>android_binary</code>
@@ -674,7 +674,7 @@
<var>[+-]regex[,[+-]regex]...@option[,option]...</var></code></h4>
</p>
-<h4 id='flag--per_file_copt'><code class='flag'>--per_file_copt
+<h4 id='flag--per_file_copt'><code class='flag'>--per_file_copt=
<var>[+-]regex[,[+-]regex]...@option[,option]...</var></code></h4>
<p>
When present, any C++ file with a label or an execution path matching one of the inclusion regex
@@ -723,7 +723,7 @@
line of the C++ compiler for all <code>.cc</code> files in <code>//foo/</code> except
<code>file.cc</code>.
</p>
-<h4 id='flag--dynamic_mode'><code class='flag'>--dynamic_mode <var>mode</var></code></h4>
+<h4 id='flag--dynamic_mode'><code class='flag'>--dynamic_mode=<var>mode</var></code></h4>
<p>
Determines whether C++ binaries will be linked dynamically, interacting with
the <a href='be/c-cpp.html#cc_binary.linkstatic'>linkstatic
@@ -793,14 +793,14 @@
android_binary rules; see the documentation for that rule for further details. Defaults to off.
</p>
-<h4 id='flag--custom_malloc'><code class='flag'>--custom_malloc <var>malloc-library-target</var></code></h4>
+<h4 id='flag--custom_malloc'><code class='flag'>--custom_malloc=<var>malloc-library-target</var></code></h4>
<p>
When specified, always use the given malloc implementation, overriding all
<code>malloc="target"</code> attributes, including in those targets that use the
default (by not specifying any <code>malloc</code>).
</p>
-<h4 id='flag--crosstool_top'><code class='flag'>--crosstool_top <var>label</var></code></h4>
+<h4 id='flag--crosstool_top'><code class='flag'>--crosstool_top=<var>label</var></code></h4>
<p>
This option specifies the location of the crosstool compiler suite
to be used for all C++ compilation during a build. Bazel will look in that
@@ -810,21 +810,21 @@
<code class='flag'>--compiler</code>.
</p>
-<h4 id='flag--host_crosstool_top'><code class='flag'>--host_crosstool_top <var>label</var></code></h4>
+<h4 id='flag--host_crosstool_top'><code class='flag'>--host_crosstool_top=<var>label</var></code></h4>
<p>
If not specified, bazel uses the value of <code class='flag'>--crosstool_top</code> to compile
code in the host configuration, i.e., tools run during the build. The main purpose of this flag
is to enable cross-compilation.
</p>
-<h4 id='flag--apple_crosstool_top'><code class='flag'>--apple_crosstool_top <var>label</var></code></h4>
+<h4 id='flag--apple_crosstool_top'><code class='flag'>--apple_crosstool_top=<var>label</var></code></h4>
<p>
The crosstool to use for compiling C/C++ rules in the transitive <code>deps</code> of
objc_*, ios__*, and apple_* rules. For those targets, this flag overwrites
<code class='flag'>--crosstool_top</code>.
</p>
-<h4 id='flag--android_crosstool_top'><code class='flag'>--android_crosstool_top <var>label</var></code></h4>
+<h4 id='flag--android_crosstool_top'><code class='flag'>--android_crosstool_top=<var>label</var></code></h4>
<p>
The crosstool to use for compiling C/C++ rules in the transitive <code>deps</code> of
<code>android_binary</code> rules. This is useful if other targets in the
@@ -832,7 +832,7 @@
generated by the <code>android_ndk_repository</code> rule in the WORKSPACE file.
See also <a href='#flag--fat_apk_cpu'><code class='flag'>--fat_apk_cpu</code></a>.
</p>
-<h4 id='flag--compiler'><code class='flag'>--compiler <var>version</var></code></h4>
+<h4 id='flag--compiler'><code class='flag'>--compiler=<var>version</var></code></h4>
<p>
This option specifies the C/C++ compiler version (e.g. <code>gcc-4.1.0</code>)
to be used for the compilation of binaries during the build. If you want to
@@ -844,7 +844,7 @@
and target CPU are allowed.
</p>
-<h4 id='flag--android_sdk'><code class='flag'>--android_sdk <var>label</var></code></h4>
+<h4 id='flag--android_sdk'><code class='flag'>--android_sdk=<var>label</var></code></h4>
<p>
This option specifies the Android SDK/platform toolchain
and Android runtime library that will be used to build any Android-related
@@ -854,20 +854,20 @@
rule is defined in the WORKSPACE file.
</p>
-<h4 id='flag--java_toolchain'><code class='flag'>--java_toolchain <var>label</var></code></h4>
+<h4 id='flag--java_toolchain'><code class='flag'>--java_toolchain=<var>label</var></code></h4>
<p>
This option specifies the label of the java_toolchain used to compile Java
source files.
</p>
-<h4 id='flag--host_java_toolchain'><code class='flag'>--host_java_toolchain <var>label</var></code></h4>
+<h4 id='flag--host_java_toolchain'><code class='flag'>--host_java_toolchain=<var>label</var></code></h4>
<p>
If not specified, bazel uses the value of <code class='flag'>--java_toolchain</code> to compile
code in the host configuration, i.e., tools run during the build. The main purpose of this flag
is to enable cross-compilation.
</p>
-<h4 id='flag--javabase'><code class='flag'>--javabase (<var>label</var>)</code></h4>
+<h4 id='flag--javabase'><code class='flag'>--javabase=(<var>label</var>)</code></h4>
<p>
This option sets the <i>label</i> of the base Java installation to use for <i>bazel run</i>,
<i>bazel test</i>, and for Java binaries built by <code>java_binary</code> and
@@ -875,7 +875,7 @@
<a href='be/make-variables.html'>"Make" variables</a> are derived from this option.
</p>
-<h4 id='flag--host_javabase'><code class='flag'>--host_javabase <var>label</var></code></h4>
+<h4 id='flag--host_javabase'><code class='flag'>--host_javabase=<var>label</var></code></h4>
<p>
This option sets the <i>label</i> of the base Java installation to use in the host configuration,
for example for host build tools including JavaBuilder and Singlejar.
@@ -895,7 +895,7 @@
speed of the build.
</p>
-<h4 id='flag--spawn_strategy'><code class='flag'>--spawn_strategy <var>strategy</var></code></h4>
+<h4 id='flag--spawn_strategy'><code class='flag'>--spawn_strategy=<var>strategy</var></code></h4>
<p>
This option controls where and how commands are executed.
</p>
@@ -939,7 +939,7 @@
strategies and their effects.
</p>
-<h4 id='flag--strategy_regexp'><code class='flag'>--strategy_regexp <var><filter,filter,...>=<strategy></var></code></h4>
+<h4 id='flag--strategy_regexp'><code class='flag'>--strategy_regexp=<var><filter,filter,...>=<strategy></var></code></h4>
<p>
This option specifies which strategy should be used to execute commands that have descriptions
matching a certain <code>regex_filter</code>. See
@@ -965,13 +965,13 @@
</li>
</ul>
-<h4 id='flag--genrule_strategy'><code class='flag'>--genrule_strategy <var>strategy</var></code></h4>
+<h4 id='flag--genrule_strategy'><code class='flag'>--genrule_strategy=<var>strategy</var></code></h4>
<p>
This is a deprecated short-hand for
<code class='flag'>--strategy=Genrule=<var>strategy</var></code>.
</p>
-<h4 id='flag--jobs'><code class='flag'>--jobs <var>n</var></code> (-j)</h4>
+<h4 id='flag--jobs'><code class='flag'>--jobs=<var>n</var></code> (-j)</h4>
<p>
This option, which takes an integer argument, specifies a limit on
the number of jobs that should be executed concurrently during the
@@ -987,7 +987,7 @@
the <code class='flag'>--local_ram_resources</code> option.
</p>
-<h4 id='flag--progress_report_interval'><code class='flag'>--progress_report_interval <var>n</var></code></h4>
+<h4 id='flag--progress_report_interval'><code class='flag'>--progress_report_interval=<var>n</var></code></h4>
<p>
Bazel periodically prints a progress report on jobs that are not
@@ -1200,7 +1200,7 @@
setting is high enough.
</p>
-<h4 id='flag--build_tag_filters'><code class='flag'>--build_tag_filters <var>tag[,tag]*</var></code></h4>
+<h4 id='flag--build_tag_filters'><code class='flag'>--build_tag_filters=<var>tag[,tag]*</var></code></h4>
<p>
If specified, Bazel will build only targets that have at least one required tag
(if any of them are specified) and does not have any excluded tags. Build tag
@@ -1214,7 +1214,7 @@
test targets using <code class='flag'>--test_tag_filters</code> or by explicitly excluding them.
</p>
-<h4 id='flag--test_size_filters'><code class='flag'>--test_size_filters <var>size[,size]*</var></code></h4>
+<h4 id='flag--test_size_filters'><code class='flag'>--test_size_filters=<var>size[,size]*</var></code></h4>
<p>
If specified, Bazel will test (or build if <code class='flag'>--build_tests_only</code>
is also specified) only test targets with the given size. Test size filter
@@ -1236,7 +1236,7 @@
By default, test size filtering is not applied.
</p>
-<h4 id='flag--test_timeout_filters'><code class='flag'>--test_timeout_filters <var>timeout[,timeout]*</var></code></h4>
+<h4 id='flag--test_timeout_filters'><code class='flag'>--test_timeout_filters=<var>timeout[,timeout]*</var></code></h4>
<p>
If specified, Bazel will test (or build if <code class='flag'>--build_tests_only</code>
is also specified) only test targets with the given timeout. Test timeout filter
@@ -1250,7 +1250,7 @@
</p>
-<h4 id='flag--test_tag_filters'><code class='flag'>--test_tag_filters <var>tag[,tag]*</var></code></h4>
+<h4 id='flag--test_tag_filters'><code class='flag'>--test_tag_filters=<var>tag[,tag]*</var></code></h4>
<p>
If specified, Bazel will test (or build if <code class='flag'>--build_tests_only</code>
is also specified) only test targets that have at least one required tag
@@ -1275,7 +1275,7 @@
this manner.
</p>
-<h4 id='flag--test_lang_filters'><code class='flag'>--test_lang_filters <var>lang[,lang]*</var></code></h4>
+<h4 id='flag--test_lang_filters'><code class='flag'>--test_lang_filters=<var>lang[,lang]*</var></code></h4>
<p>
Specifies a comma-separated list of test languages for languages with an official <code>*_test</code> rule the
(see <a href="be/overview.html">build encyclopedia</a> for a full list of these). Each
@@ -1330,7 +1330,7 @@
These options control the verbosity of Bazel's output,
either to the terminal, or to additional log files.
-<h4 id='flag--explain'><code class='flag'>--explain <var>logfile</var></code></h4>
+<h4 id='flag--explain'><code class='flag'>--explain=<var>logfile</var></code></h4>
<p>
This option, which requires a filename argument, causes the
dependency checker in <code>bazel build</code>'s execution phase to
@@ -1369,7 +1369,7 @@
<code class='flag'>--verbose_explanations</code> has no effect.
</p>
-<h4 id='flag--profile'><code class='flag'>--profile <var>file</var></code></h4>
+<h4 id='flag--profile'><code class='flag'>--profile=<var>file</var></code></h4>
<p>
This option, which takes a filename argument, causes Bazel to write
profiling data into a file. The data then can be analyzed or parsed using the
@@ -1389,7 +1389,7 @@
default. When disabled, progress messages are suppressed.
</p>
-<h4 id='flag--show_progress_rate_limit'><code class='flag'>--show_progress_rate_limit
+<h4 id='flag--show_progress_rate_limit'><code class='flag'>--show_progress_rate_limit=
<var>n</var></code></h4>
<p>
This option causes bazel to display only
@@ -1399,7 +1399,7 @@
0.03 seconds.
</p>
-<h4 id='flag--show_result'><code class='flag'>--show_result <var>n</var></code></h4>
+<h4 id='flag--show_result'><code class='flag'>--show_result=<var>n</var></code></h4>
<p>
This option controls the printing of result information at the end
of a <code>bazel build</code> command. By default, if a single
@@ -1489,7 +1489,7 @@
<code>genrule</code>, <code>cc_binary</code>, and more.
</p>
-<h4 id='flag--workspace_status_command'><code class='flag'>--workspace_status_command <var>program</var></code></h4>
+<h4 id='flag--workspace_status_command'><code class='flag'>--workspace_status_command=<var>program</var></code></h4>
<p>
This flag lets you specify a binary that Bazel runs before each build. The program can report
information about the status of the workspace, such as the current source control revision.
@@ -1620,18 +1620,18 @@
<a href="platforms.html">Platforms</a> and <a href="toolchains.html">Toolchains</a>.
</p>
-<h4 id="flag--platforms"><code class='flag'>--platforms <var>labels</var></code></h4>
+<h4 id="flag--platforms"><code class='flag'>--platforms=<var>labels</var></code></h4>
<p>
The labels of the platform rules describing the target platforms for the
current command.
</p>
-<h4 id="flag--host_platform"><code class='flag'>--host_platform <var>label</var></code></h4>
+<h4 id="flag--host_platform"><code class='flag'>--host_platform=<var>label</var></code></h4>
<p>
The label of a platform rule that describes the host system.
</p>
-<h4 id="flag--extra_execution_platforms"><code class='flag'>--extra_execution_platforms <var>labels</var></code></h4>
+<h4 id="flag--extra_execution_platforms"><code class='flag'>--extra_execution_platforms=<var>labels</var></code></h4>
<p>
The platforms that are available as execution platforms to run actions.
Platforms can be specified by exact target, or as a target pattern. These
@@ -1640,7 +1640,7 @@
register_execution_platforms()</a>.
</p>
-<h4 id="flag--extra_toolchains"><code class='flag'>--extra_toolchains <var>labels</var></code></h4>
+<h4 id="flag--extra_toolchains"><code class='flag'>--extra_toolchains=<var>labels</var></code></h4>
<p>
The toolchain rules to be considered during toolchain resolution. Toolchains
can be specified by exact target, or as a target pattern. These toolchains will
@@ -1658,14 +1658,14 @@
<h3 id='misc_build_options'>Miscellaneous</h3>
-<h4 id='flag--flag_alias'><code class='flag'>--flag_alias <var>alias_name=target_path</var></code></h4>
+<h4 id='flag--flag_alias'><code class='flag'>--flag_alias=<var>alias_name=target_path</var></code></h4>
<p>
A convenience flag used to bind longer Starlark build settings to a shorter name. For more
details, see the
<a href=https://docs.bazel.build/versions/master/skylark/config.html#using-build-setting-aliases">Starlark Configurations</a>.
</p>
-<h4 id='flag--symlink_prefix'><code class='flag'>--symlink_prefix <var>string</var></code></h4>
+<h4 id='flag--symlink_prefix'><code class='flag'>--symlink_prefix=<var>string</var></code></h4>
<p>
Changes the prefix of the generated convenience symlinks. The
default value for the symlink prefix is <code>bazel-</code> which
@@ -1704,7 +1704,7 @@
</li>
</ul>
-<h4 id='flag--platform_suffix'><code class='flag'>--platform_suffix <var>string</var></code></h4>
+<h4 id='flag--platform_suffix'><code class='flag'>--platform_suffix=<var>string</var></code></h4>
<p>
Adds a suffix to the configuration short name, which is used to determine the
output directory. Setting this option to different values puts the files into
@@ -1894,7 +1894,7 @@
<code class='flag'>--keep_going</code>.
</p>
-<h4 id='flag--flaky_test_attempts'><code class='flag'>--flaky_test_attempts <var>attempts</var></code></h4>
+<h4 id='flag--flaky_test_attempts'><code class='flag'>--flaky_test_attempts=<var>attempts</var></code></h4>
<p>
This option specifies the maximum number of times a test should be attempted
if it fails for any reason. A test that initially fails but eventually
@@ -1911,7 +1911,7 @@
a maximum of 10 test attempts in order to prevent abuse of the system.
</p>
-<h4 id='flag--runs_per_test'><code class='flag'>--runs_per_test <var>[regex@]number</var></code></h4>
+<h4 id='flag--runs_per_test'><code class='flag'>--runs_per_test=<var>[regex@]number</var></code></h4>
<p>
This option specifies the number of times each test should be executed. All
test executions are treated as separate tests (e.g. fallback functionality
@@ -1947,7 +1947,7 @@
failing status.
</p>
-<h4 id='flag--test_summary'><code class='flag'>--test_summary <var>output_style</var></code></h4>
+<h4 id='flag--test_summary'><code class='flag'>--test_summary=<var>output_style</var></code></h4>
<p>
Specifies how the test result summary should be displayed.
</p>
@@ -1966,7 +1966,7 @@
</li>
</ul>
-<h4 id='flag--test_output'><code class='flag'>--test_output <var>output_style</var></code></h4>
+<h4 id='flag--test_output'><code class='flag'>--test_output=<var>output_style</var></code></h4>
<p>
Specifies how test output should be displayed:
</p>
@@ -2006,7 +2006,7 @@
be formatted to stay within 80 characters when possible.
</p>
-<h4 id='flag--test_tmpdir'><code class='flag'>--test_tmpdir <var>path</var></code></h4>
+<h4 id='flag--test_tmpdir'><code class='flag'>--test_tmpdir=<var>path</var></code></h4>
<p>
Specifies temporary directory for tests executed locally. Each test will be
executed in a separate subdirectory inside this directory. The directory will
@@ -2017,10 +2017,10 @@
</p>
<h4 id='flag--test_timeout'>
- <code class='flag'>--test_timeout
+ <code class='flag'>--test_timeout=
<var>seconds</var></code>
OR
- <code class='flag'>--test_timeout
+ <code class='flag'>--test_timeout=
<var>seconds</var>,<var>seconds</var>,<var>seconds</var>,<var>seconds</var>
</code>
</h4>
@@ -2049,16 +2049,16 @@
timeout.
</p>
-<h4 id='flag--test_arg'><code class='flag'>--test_arg <var>arg</var></code></h4>
+<h4 id='flag--test_arg'><code class='flag'>--test_arg=<var>arg</var></code></h4>
<p>
Passes command-line options/flags/arguments to each test process. This
option can be used multiple times to pass several arguments, e.g.
<code class='flag'>--test_arg=--logtostderr --test_arg=--v=3</code>.
</p>
-<h4 id='flag--test_env'><code class='flag'>--test_env <var>variable</var>=<i>value</i></code>
+<h4 id='flag--test_env'><code class='flag'>--test_env=<var>variable</var>=<i>value</i></code>
OR
- <code class='flag'>--test_env <var>variable</var></code></h4>
+ <code class='flag'>--test_env=<var>variable</var></code></h4>
<p>
Specifies additional variables that must be injected into the test
environment for each test. If <var>value</var> is not specified it will be
@@ -2624,7 +2624,7 @@
<code class='flag'>--start_app</code> or
<code class='flag'>--debug_app</code> is set, the last value is used.
</p>
-<h4 id='flag--adb'><code class='flag'>--adb <var>path</var></code></h4>
+<h4 id='flag--adb'><code class='flag'>--adb=<var>path</var></code></h4>
<p>
Indicates the <code>adb</code> binary to be used.
@@ -2632,7 +2632,7 @@
<a href='#flag--android_sdk'><code class='flag'>--android_sdk</code></a>.
</p>
-<h4 id='flag--adb_arg'><code class='flag'>--adb_arg <var>serial</var></code></h4>
+<h4 id='flag--adb_arg'><code class='flag'>--adb_arg=<var>serial</var></code></h4>
<p>
Extra arguments to <code>adb</code>. These come before the subcommand in the
command line and are typically used to specify which device to install to.
@@ -2646,7 +2646,7 @@
<pre>
adb -s deadbeef install ...
</pre>
-<h4 id='flag--incremental_install_verbosity'><code class='flag'>--incremental_install_verbosity <var>number</var></code></h4>
+<h4 id='flag--incremental_install_verbosity'><code class='flag'>--incremental_install_verbosity=<var>number</var></code></h4>
<p>
The verbosity for incremental install. Set to 1 for debug logging to be
printed to the console.
@@ -2967,7 +2967,7 @@
</p>
-<h4 id='flag--max_idle_secs'><code class='flag'>--max_idle_secs <var>n</var></code></h4>
+<h4 id='flag--max_idle_secs'><code class='flag'>--max_idle_secs=<var>n</var></code></h4>
<p>
This option specifies how long, in seconds, the Bazel server process
should wait after the last client request, before it exits. The
@@ -3015,7 +3015,7 @@
by another Bazel command in the same client.
</p>
-<h4 id='flag--io_nice_level'><code class='flag'>--io_nice_level <var>n</var></code></h4>
+<h4 id='flag--io_nice_level'><code class='flag'>--io_nice_level=<var>n</var></code></h4>
<p>
Sets a level from 0-7 for best-effort IO scheduling. 0 is highest priority,
7 is lowest. The anticipatory scheduler may only honor up to priority 4.
@@ -3053,7 +3053,7 @@
of the setting of the TERM environment variable.
</p>
-<h4 id='flag--config'><code class='flag'>--config <var>name</var></code></h4>
+<h4 id='flag--config'><code class='flag'>--config=<var>name</var></code></h4>
<p>
Selects additional config section from the rc files; for the current
<code>command</code>, it also pulls in the options from
