doc: mention binary auto-built for build,bench,test,rustc

Author: weihanglo

src/doc/man/cargo-bench.md

@@ -81,6 +81,8 @@ them from being benchmarked by default. Target selection options that take a
 target by name ignore the `bench` flag and will always benchmark the given
 target.
 
+{{> options-targets-bin-auto-built }}
+
 {{> options-targets }}
 
 {{> section-features }}

src/doc/man/cargo-build.md

@@ -23,6 +23,8 @@ When no target selection options are given, `cargo build` will build all
 binary and library targets of the selected packages. Binaries are skipped if
 they have `required-features` that are missing.
 
+{{> options-targets-bin-auto-built }}
+
 {{> options-targets }}
 
 {{> section-features }}

src/doc/man/cargo-rustc.md

@@ -35,6 +35,8 @@ To pass flags to all compiler processes spawned by Cargo, use the `RUSTFLAGS`
 When no target selection options are given, `cargo rustc` will build all
 binary and library targets of the selected package.
 
+{{> options-targets-bin-auto-built }}
+
 {{> options-targets }}
 
 {{> section-features }}

src/doc/man/cargo-test.md

@@ -73,13 +73,7 @@ ignore the `test` flag and will always test the given target.
 Doc tests for libraries may be disabled by setting `doctest = false` for the
 library in the manifest.
 
-Binary targets are automatically built if there is an integration test or
-benchmark. This allows an integration test to execute the binary to exercise
-and test its behavior. The `CARGO_BIN_EXE_<name>`
-[environment variable](../reference/environment-variables.html#environment-variables-cargo-sets-for-crates)
-is set when the integration test is built so that it can use the
-[`env` macro](https://doc.rust-lang.org/std/macro.env.html) to locate the
-executable.
+{{> options-targets-bin-auto-built }}
 
 {{> options-targets }}
 

src/doc/man/generated_txt/cargo-bench.txt

@@ -117,6 +117,15 @@ OPTIONS
        options that take a target by name ignore the bench flag and will always
        benchmark the given target.
 
+       Binary targets are automatically built if there is an integration test
+       or benchmark. This allows an integration test to execute the binary to
+       exercise and test its behavior. The CARGO_BIN_EXE_<name> environment
+       variable
+       <https://doc.rust-lang.org/cargo/reference/environment-variables.html#environment-variables-cargo-sets-for-crates>
+       is set when the integration test is built so that it can use the env
+       macro <https://doc.rust-lang.org/std/macro.env.html> to locate the
+       executable.
+
        Passing target selection flags will benchmark only the specified
        targets.
 

src/doc/man/generated_txt/cargo-build.txt

@@ -51,6 +51,15 @@ OPTIONS
        binary and library targets of the selected packages. Binaries are
        skipped if they have required-features that are missing.
 
+       Binary targets are automatically built if there is an integration test
+       or benchmark. This allows an integration test to execute the binary to
+       exercise and test its behavior. The CARGO_BIN_EXE_<name> environment
+       variable
+       <https://doc.rust-lang.org/cargo/reference/environment-variables.html#environment-variables-cargo-sets-for-crates>
+       is set when the integration test is built so that it can use the env
+       macro <https://doc.rust-lang.org/std/macro.env.html> to locate the
+       executable.
+
        Passing target selection flags will build only the specified targets.
 
        Note that --bin, --example, --test and --bench flags also support common

src/doc/man/generated_txt/cargo-rustc.txt

@@ -42,6 +42,15 @@ OPTIONS
        When no target selection options are given, cargo rustc will build all
        binary and library targets of the selected package.
 
+       Binary targets are automatically built if there is an integration test
+       or benchmark. This allows an integration test to execute the binary to
+       exercise and test its behavior. The CARGO_BIN_EXE_<name> environment
+       variable
+       <https://doc.rust-lang.org/cargo/reference/environment-variables.html#environment-variables-cargo-sets-for-crates>
+       is set when the integration test is built so that it can use the env
+       macro <https://doc.rust-lang.org/std/macro.env.html> to locate the
+       executable.
+
        Passing target selection flags will build only the specified targets.
 
        Note that --bin, --example, --test and --bench flags also support common

src/doc/man/includes/options-targets-bin-auto-built.md

@@ -0,0 +1,7 @@
+Binary targets are automatically built if there is an integration test or
+benchmark. This allows an integration test to execute the binary to exercise
+and test its behavior. The `CARGO_BIN_EXE_<name>`
+[environment variable](../reference/environment-variables.html#environment-variables-cargo-sets-for-crates)
+is set when the integration test is built so that it can use the
+[`env` macro](https://doc.rust-lang.org/std/macro.env.html) to locate the
+executable.

src/doc/src/commands/cargo-bench.md

@@ -138,6 +138,15 @@ them from being benchmarked by default. Target selection options that take a
 target by name ignore the `bench` flag and will always benchmark the given
 target.
 
+Binary targets are automatically built if there is an integration test or
+benchmark. This allows an integration test to execute the binary to exercise
+and test its behavior. The `CARGO_BIN_EXE_<name>`
+[environment variable](../reference/environment-variables.html#environment-variables-cargo-sets-for-crates)
+is set when the integration test is built so that it can use the
+[`env` macro](https://doc.rust-lang.org/std/macro.env.html) to locate the
+executable.
+
+
 Passing target selection flags will benchmark only the specified
 targets. 
 

src/doc/src/commands/cargo-build.md

@@ -66,6 +66,15 @@ When no target selection options are given, `cargo build` will build all
 binary and library targets of the selected packages. Binaries are skipped if
 they have `required-features` that are missing.
 
+Binary targets are automatically built if there is an integration test or
+benchmark. This allows an integration test to execute the binary to exercise
+and test its behavior. The `CARGO_BIN_EXE_<name>`
+[environment variable](../reference/environment-variables.html#environment-variables-cargo-sets-for-crates)
+is set when the integration test is built so that it can use the
+[`env` macro](https://doc.rust-lang.org/std/macro.env.html) to locate the
+executable.
+
+
 Passing target selection flags will build only the specified
 targets.