From d5509ebacc1bd4426926cfa7c930c8b271455500 Mon Sep 17 00:00:00 2001
From: zdivelbiss <8019570+zdivelbiss@users.noreply.github.com>
Date: Sun, 17 Aug 2025 14:38:39 -0500
Subject: [PATCH] amend documentation style for `host` target specifier
We also rebuilt the manual pages, to ensure they're up-to-date with the changes made in the `host` target specifier PR.
---
src/cargo/util/command_prelude.rs | 2 +-
src/doc/man/generated_txt/cargo-bench.txt | 25 ++++++++++---------
src/doc/man/generated_txt/cargo-build.txt | 25 ++++++++++---------
src/doc/man/generated_txt/cargo-check.txt | 25 ++++++++++---------
src/doc/man/generated_txt/cargo-clean.txt | 25 ++++++++++---------
src/doc/man/generated_txt/cargo-doc.txt | 25 ++++++++++---------
src/doc/man/generated_txt/cargo-fetch.txt | 25 ++++++++++---------
src/doc/man/generated_txt/cargo-fix.txt | 25 ++++++++++---------
src/doc/man/generated_txt/cargo-install.txt | 23 +++++++++--------
src/doc/man/generated_txt/cargo-package.txt | 25 ++++++++++---------
src/doc/man/generated_txt/cargo-publish.txt | 25 ++++++++++---------
src/doc/man/generated_txt/cargo-run.txt | 23 +++++++++--------
src/doc/man/generated_txt/cargo-rustc.txt | 25 ++++++++++---------
src/doc/man/generated_txt/cargo-rustdoc.txt | 25 ++++++++++---------
src/doc/man/generated_txt/cargo-test.txt | 25 ++++++++++---------
src/doc/man/includes/options-target-triple.md | 15 +++++------
src/doc/src/commands/cargo-bench.md | 14 ++++++-----
src/doc/src/commands/cargo-build.md | 14 ++++++-----
src/doc/src/commands/cargo-check.md | 14 ++++++-----
src/doc/src/commands/cargo-clean.md | 14 ++++++-----
src/doc/src/commands/cargo-doc.md | 14 ++++++-----
src/doc/src/commands/cargo-fetch.md | 14 ++++++-----
src/doc/src/commands/cargo-fix.md | 14 ++++++-----
src/doc/src/commands/cargo-install.md | 14 ++++++-----
src/doc/src/commands/cargo-package.md | 14 ++++++-----
src/doc/src/commands/cargo-publish.md | 14 ++++++-----
src/doc/src/commands/cargo-run.md | 14 ++++++-----
src/doc/src/commands/cargo-rustc.md | 14 ++++++-----
src/doc/src/commands/cargo-rustdoc.md | 14 ++++++-----
src/doc/src/commands/cargo-test.md | 14 ++++++-----
src/doc/src/reference/config.md | 10 ++++----
src/etc/man/cargo-bench.1 | 14 ++++++-----
src/etc/man/cargo-build.1 | 14 ++++++-----
src/etc/man/cargo-check.1 | 14 ++++++-----
src/etc/man/cargo-clean.1 | 14 ++++++-----
src/etc/man/cargo-doc.1 | 14 ++++++-----
src/etc/man/cargo-fetch.1 | 14 ++++++-----
src/etc/man/cargo-fix.1 | 14 ++++++-----
src/etc/man/cargo-install.1 | 14 ++++++-----
src/etc/man/cargo-package.1 | 14 ++++++-----
src/etc/man/cargo-publish.1 | 14 ++++++-----
src/etc/man/cargo-run.1 | 14 ++++++-----
src/etc/man/cargo-rustc.1 | 14 ++++++-----
src/etc/man/cargo-rustdoc.1 | 14 ++++++-----
src/etc/man/cargo-test.1 | 14 ++++++-----
tests/testsuite/list_availables.rs | 24 +++++++++---------
46 files changed, 430 insertions(+), 359 deletions(-)
diff --git a/src/cargo/util/command_prelude.rs b/src/cargo/util/command_prelude.rs
index 52c955459..e1d2f9a88 100644
--- a/src/cargo/util/command_prelude.rs
+++ b/src/cargo/util/command_prelude.rs
@@ -670,7 +670,7 @@ pub trait ArgMatchesExt {
bail!(
"\"--target\" takes a target architecture as an argument.
-Run `{cmd}` to see possible targets, or specify `host` for the host architecture."
+Run `{cmd}` to see possible targets."
);
}
Ok(self._values_of("target"))
diff --git a/src/doc/man/generated_txt/cargo-bench.txt b/src/doc/man/generated_txt/cargo-bench.txt
index 44748e3cd..09f742fd8 100644
--- a/src/doc/man/generated_txt/cargo-bench.txt
+++ b/src/doc/man/generated_txt/cargo-bench.txt
@@ -220,30 +220,31 @@ OPTIONS
Compilation Options
--target triple
- Benchmark for the specified target (may be specified multiple times)
- The default is the host architecture. The general format of the
- triple is ---.
+ Benchmark for the specified target architecture. Flag may be
+ specified multiple times. The default is the host architecture. The
+ general format of the triple is ---.
- You may specify the following kinds of targets:
+ Possible values:
- o Any supported target in rustc --print target-list (note: you have
- to install/add the target to use it).
+ o Any supported target in rustc --print target-list.
- o host, which will internally be substituted by the host’s
+ o "host", which will internally be substituted by the host’s
target. This can be particularly useful if you’re
cross-compiling some crates, and don’t want to specify your
host’s machine as a target (for instance, an xtask in a shared
project that may be worked on by many hosts).
- o A path to a custom target specification (further reading here
- ).
+ o A path to a custom target specification. See Custom Target Lookup
+ Path
+
+ for more information.
This may also be specified with the build.target config value
.
- Note: Specifying this flag makes Cargo run in a different mode where
- the target artifacts are placed in a separate directory. See the
- build cache
+ Note that specifying this flag makes Cargo run in a different mode
+ where the target artifacts are placed in a separate directory. See
+ the build cache
documentation for more details.
diff --git a/src/doc/man/generated_txt/cargo-build.txt b/src/doc/man/generated_txt/cargo-build.txt
index dc632cffd..2f8247937 100644
--- a/src/doc/man/generated_txt/cargo-build.txt
+++ b/src/doc/man/generated_txt/cargo-build.txt
@@ -137,30 +137,31 @@ OPTIONS
Compilation Options
--target triple
- Build for the specified target (may be specified multiple times) The
- default is the host architecture. The general format of the triple
- is ---.
+ Build for the specified target architecture. Flag may be specified
+ multiple times. The default is the host architecture. The general
+ format of the triple is ---.
- You may specify the following kinds of targets:
+ Possible values:
- o Any supported target in rustc --print target-list (note: you have
- to install/add the target to use it).
+ o Any supported target in rustc --print target-list.
- o host, which will internally be substituted by the host’s
+ o "host", which will internally be substituted by the host’s
target. This can be particularly useful if you’re
cross-compiling some crates, and don’t want to specify your
host’s machine as a target (for instance, an xtask in a shared
project that may be worked on by many hosts).
- o A path to a custom target specification (further reading here
- ).
+ o A path to a custom target specification. See Custom Target Lookup
+ Path
+
+ for more information.
This may also be specified with the build.target config value
.
- Note: Specifying this flag makes Cargo run in a different mode where
- the target artifacts are placed in a separate directory. See the
- build cache
+ Note that specifying this flag makes Cargo run in a different mode
+ where the target artifacts are placed in a separate directory. See
+ the build cache
documentation for more details.
diff --git a/src/doc/man/generated_txt/cargo-check.txt b/src/doc/man/generated_txt/cargo-check.txt
index 845052a8c..42be19298 100644
--- a/src/doc/man/generated_txt/cargo-check.txt
+++ b/src/doc/man/generated_txt/cargo-check.txt
@@ -134,30 +134,31 @@ OPTIONS
Compilation Options
--target triple
- Check for the specified target (may be specified multiple times) The
- default is the host architecture. The general format of the triple
- is ---.
+ Check for the specified target architecture. Flag may be specified
+ multiple times. The default is the host architecture. The general
+ format of the triple is ---.
- You may specify the following kinds of targets:
+ Possible values:
- o Any supported target in rustc --print target-list (note: you have
- to install/add the target to use it).
+ o Any supported target in rustc --print target-list.
- o host, which will internally be substituted by the host’s
+ o "host", which will internally be substituted by the host’s
target. This can be particularly useful if you’re
cross-compiling some crates, and don’t want to specify your
host’s machine as a target (for instance, an xtask in a shared
project that may be worked on by many hosts).
- o A path to a custom target specification (further reading here
- ).
+ o A path to a custom target specification. See Custom Target Lookup
+ Path
+
+ for more information.
This may also be specified with the build.target config value
.
- Note: Specifying this flag makes Cargo run in a different mode where
- the target artifacts are placed in a separate directory. See the
- build cache
+ Note that specifying this flag makes Cargo run in a different mode
+ where the target artifacts are placed in a separate directory. See
+ the build cache
documentation for more details.
diff --git a/src/doc/man/generated_txt/cargo-clean.txt b/src/doc/man/generated_txt/cargo-clean.txt
index 8cdd693ad..09feaf50b 100644
--- a/src/doc/man/generated_txt/cargo-clean.txt
+++ b/src/doc/man/generated_txt/cargo-clean.txt
@@ -45,30 +45,31 @@ OPTIONS
target in the root of the workspace.
--target triple
- Clean for the specified target (may be specified multiple times) The
- default is the host architecture. The general format of the triple
- is ---.
+ Clean for the specified target architecture. Flag may be specified
+ multiple times. The default is the host architecture. The general
+ format of the triple is ---.
- You may specify the following kinds of targets:
+ Possible values:
- o Any supported target in rustc --print target-list (note: you have
- to install/add the target to use it).
+ o Any supported target in rustc --print target-list.
- o host, which will internally be substituted by the host’s
+ o "host", which will internally be substituted by the host’s
target. This can be particularly useful if you’re
cross-compiling some crates, and don’t want to specify your
host’s machine as a target (for instance, an xtask in a shared
project that may be worked on by many hosts).
- o A path to a custom target specification (further reading here
- ).
+ o A path to a custom target specification. See Custom Target Lookup
+ Path
+
+ for more information.
This may also be specified with the build.target config value
.
- Note: Specifying this flag makes Cargo run in a different mode where
- the target artifacts are placed in a separate directory. See the
- build cache
+ Note that specifying this flag makes Cargo run in a different mode
+ where the target artifacts are placed in a separate directory. See
+ the build cache
documentation for more details.
diff --git a/src/doc/man/generated_txt/cargo-doc.txt b/src/doc/man/generated_txt/cargo-doc.txt
index 865411bc6..bac56fd6c 100644
--- a/src/doc/man/generated_txt/cargo-doc.txt
+++ b/src/doc/man/generated_txt/cargo-doc.txt
@@ -112,30 +112,31 @@ OPTIONS
Compilation Options
--target triple
- Document for the specified target (may be specified multiple times)
- The default is the host architecture. The general format of the
- triple is ---.
+ Document for the specified target architecture. Flag may be
+ specified multiple times. The default is the host architecture. The
+ general format of the triple is ---.
- You may specify the following kinds of targets:
+ Possible values:
- o Any supported target in rustc --print target-list (note: you have
- to install/add the target to use it).
+ o Any supported target in rustc --print target-list.
- o host, which will internally be substituted by the host’s
+ o "host", which will internally be substituted by the host’s
target. This can be particularly useful if you’re
cross-compiling some crates, and don’t want to specify your
host’s machine as a target (for instance, an xtask in a shared
project that may be worked on by many hosts).
- o A path to a custom target specification (further reading here
- ).
+ o A path to a custom target specification. See Custom Target Lookup
+ Path
+
+ for more information.
This may also be specified with the build.target config value
.
- Note: Specifying this flag makes Cargo run in a different mode where
- the target artifacts are placed in a separate directory. See the
- build cache
+ Note that specifying this flag makes Cargo run in a different mode
+ where the target artifacts are placed in a separate directory. See
+ the build cache
documentation for more details.
diff --git a/src/doc/man/generated_txt/cargo-fetch.txt b/src/doc/man/generated_txt/cargo-fetch.txt
index a02e3cadd..91e308f65 100644
--- a/src/doc/man/generated_txt/cargo-fetch.txt
+++ b/src/doc/man/generated_txt/cargo-fetch.txt
@@ -25,30 +25,31 @@ DESCRIPTION
OPTIONS
Fetch options
--target triple
- Fetch for the specified target (may be specified multiple times) The
- default is all architectures. The general format of the triple is
- ---.
+ Fetch for the specified target architecture. Flag may be specified
+ multiple times. The default is all architectures. The general format
+ of the triple is ---.
- You may specify the following kinds of targets:
+ Possible values:
- o Any supported target in rustc --print target-list (note: you have
- to install/add the target to use it).
+ o Any supported target in rustc --print target-list.
- o host, which will internally be substituted by the host’s
+ o "host", which will internally be substituted by the host’s
target. This can be particularly useful if you’re
cross-compiling some crates, and don’t want to specify your
host’s machine as a target (for instance, an xtask in a shared
project that may be worked on by many hosts).
- o A path to a custom target specification (further reading here
- ).
+ o A path to a custom target specification. See Custom Target Lookup
+ Path
+
+ for more information.
This may also be specified with the build.target config value
.
- Note: Specifying this flag makes Cargo run in a different mode where
- the target artifacts are placed in a separate directory. See the
- build cache
+ Note that specifying this flag makes Cargo run in a different mode
+ where the target artifacts are placed in a separate directory. See
+ the build cache
documentation for more details.
diff --git a/src/doc/man/generated_txt/cargo-fix.txt b/src/doc/man/generated_txt/cargo-fix.txt
index b82234952..56e131b45 100644
--- a/src/doc/man/generated_txt/cargo-fix.txt
+++ b/src/doc/man/generated_txt/cargo-fix.txt
@@ -208,30 +208,31 @@ OPTIONS
Compilation Options
--target triple
- Fix for the specified target (may be specified multiple times) The
- default is the host architecture. The general format of the triple
- is ---.
+ Fix for the specified target architecture. Flag may be specified
+ multiple times. The default is the host architecture. The general
+ format of the triple is ---.
- You may specify the following kinds of targets:
+ Possible values:
- o Any supported target in rustc --print target-list (note: you have
- to install/add the target to use it).
+ o Any supported target in rustc --print target-list.
- o host, which will internally be substituted by the host’s
+ o "host", which will internally be substituted by the host’s
target. This can be particularly useful if you’re
cross-compiling some crates, and don’t want to specify your
host’s machine as a target (for instance, an xtask in a shared
project that may be worked on by many hosts).
- o A path to a custom target specification (further reading here
- ).
+ o A path to a custom target specification. See Custom Target Lookup
+ Path
+
+ for more information.
This may also be specified with the build.target config value
.
- Note: Specifying this flag makes Cargo run in a different mode where
- the target artifacts are placed in a separate directory. See the
- build cache
+ Note that specifying this flag makes Cargo run in a different mode
+ where the target artifacts are placed in a separate directory. See
+ the build cache
documentation for more details.
diff --git a/src/doc/man/generated_txt/cargo-install.txt b/src/doc/man/generated_txt/cargo-install.txt
index 2baebd96a..2001a2cd0 100644
--- a/src/doc/man/generated_txt/cargo-install.txt
+++ b/src/doc/man/generated_txt/cargo-install.txt
@@ -186,30 +186,31 @@ OPTIONS
Compilation Options
--target triple
- Install for the specified target The default is the host
- architecture. The general format of the triple is
+ Install for the specified target architecture. The default is the
+ host architecture. The general format of the triple is
---.
- You may specify the following kinds of targets:
+ Possible values:
- o Any supported target in rustc --print target-list (note: you have
- to install/add the target to use it).
+ o Any supported target in rustc --print target-list.
- o host, which will internally be substituted by the host’s
+ o "host", which will internally be substituted by the host’s
target. This can be particularly useful if you’re
cross-compiling some crates, and don’t want to specify your
host’s machine as a target (for instance, an xtask in a shared
project that may be worked on by many hosts).
- o A path to a custom target specification (further reading here
- ).
+ o A path to a custom target specification. See Custom Target Lookup
+ Path
+
+ for more information.
This may also be specified with the build.target config value
.
- Note: Specifying this flag makes Cargo run in a different mode where
- the target artifacts are placed in a separate directory. See the
- build cache
+ Note that specifying this flag makes Cargo run in a different mode
+ where the target artifacts are placed in a separate directory. See
+ the build cache
documentation for more details.
diff --git a/src/doc/man/generated_txt/cargo-package.txt b/src/doc/man/generated_txt/cargo-package.txt
index 032cee263..54c226280 100644
--- a/src/doc/man/generated_txt/cargo-package.txt
+++ b/src/doc/man/generated_txt/cargo-package.txt
@@ -188,30 +188,31 @@ OPTIONS
Compilation Options
--target triple
- Package for the specified target (may be specified multiple times)
- The default is the host architecture. The general format of the
- triple is ---.
+ Package for the specified target architecture. Flag may be specified
+ multiple times. The default is the host architecture. The general
+ format of the triple is ---.
- You may specify the following kinds of targets:
+ Possible values:
- o Any supported target in rustc --print target-list (note: you have
- to install/add the target to use it).
+ o Any supported target in rustc --print target-list.
- o host, which will internally be substituted by the host’s
+ o "host", which will internally be substituted by the host’s
target. This can be particularly useful if you’re
cross-compiling some crates, and don’t want to specify your
host’s machine as a target (for instance, an xtask in a shared
project that may be worked on by many hosts).
- o A path to a custom target specification (further reading here
- ).
+ o A path to a custom target specification. See Custom Target Lookup
+ Path
+
+ for more information.
This may also be specified with the build.target config value
.
- Note: Specifying this flag makes Cargo run in a different mode where
- the target artifacts are placed in a separate directory. See the
- build cache
+ Note that specifying this flag makes Cargo run in a different mode
+ where the target artifacts are placed in a separate directory. See
+ the build cache
documentation for more details.
diff --git a/src/doc/man/generated_txt/cargo-publish.txt b/src/doc/man/generated_txt/cargo-publish.txt
index 2ca84a8f0..c303754b2 100644
--- a/src/doc/man/generated_txt/cargo-publish.txt
+++ b/src/doc/man/generated_txt/cargo-publish.txt
@@ -109,30 +109,31 @@ OPTIONS
Compilation Options
--target triple
- Publish for the specified target (may be specified multiple times)
- The default is the host architecture. The general format of the
- triple is ---.
+ Publish for the specified target architecture. Flag may be specified
+ multiple times. The default is the host architecture. The general
+ format of the triple is ---.
- You may specify the following kinds of targets:
+ Possible values:
- o Any supported target in rustc --print target-list (note: you have
- to install/add the target to use it).
+ o Any supported target in rustc --print target-list.
- o host, which will internally be substituted by the host’s
+ o "host", which will internally be substituted by the host’s
target. This can be particularly useful if you’re
cross-compiling some crates, and don’t want to specify your
host’s machine as a target (for instance, an xtask in a shared
project that may be worked on by many hosts).
- o A path to a custom target specification (further reading here
- ).
+ o A path to a custom target specification. See Custom Target Lookup
+ Path
+
+ for more information.
This may also be specified with the build.target config value
.
- Note: Specifying this flag makes Cargo run in a different mode where
- the target artifacts are placed in a separate directory. See the
- build cache
+ Note that specifying this flag makes Cargo run in a different mode
+ where the target artifacts are placed in a separate directory. See
+ the build cache
documentation for more details.
diff --git a/src/doc/man/generated_txt/cargo-run.txt b/src/doc/man/generated_txt/cargo-run.txt
index e6363d9d5..9f5f3a610 100644
--- a/src/doc/man/generated_txt/cargo-run.txt
+++ b/src/doc/man/generated_txt/cargo-run.txt
@@ -61,30 +61,31 @@ OPTIONS
Compilation Options
--target triple
- Run for the specified target The default is the host architecture.
- The general format of the triple is
+ Run for the specified target architecture. The default is the host
+ architecture. The general format of the triple is
---.
- You may specify the following kinds of targets:
+ Possible values:
- o Any supported target in rustc --print target-list (note: you have
- to install/add the target to use it).
+ o Any supported target in rustc --print target-list.
- o host, which will internally be substituted by the host’s
+ o "host", which will internally be substituted by the host’s
target. This can be particularly useful if you’re
cross-compiling some crates, and don’t want to specify your
host’s machine as a target (for instance, an xtask in a shared
project that may be worked on by many hosts).
- o A path to a custom target specification (further reading here
- ).
+ o A path to a custom target specification. See Custom Target Lookup
+ Path
+
+ for more information.
This may also be specified with the build.target config value
.
- Note: Specifying this flag makes Cargo run in a different mode where
- the target artifacts are placed in a separate directory. See the
- build cache
+ Note that specifying this flag makes Cargo run in a different mode
+ where the target artifacts are placed in a separate directory. See
+ the build cache
documentation for more details.
diff --git a/src/doc/man/generated_txt/cargo-rustc.txt b/src/doc/man/generated_txt/cargo-rustc.txt
index 700fd3f98..763b9b3bb 100644
--- a/src/doc/man/generated_txt/cargo-rustc.txt
+++ b/src/doc/man/generated_txt/cargo-rustc.txt
@@ -128,30 +128,31 @@ OPTIONS
Compilation Options
--target triple
- Build for the specified target (may be specified multiple times) The
- default is the host architecture. The general format of the triple
- is ---.
+ Build for the specified target architecture. Flag may be specified
+ multiple times. The default is the host architecture. The general
+ format of the triple is ---.
- You may specify the following kinds of targets:
+ Possible values:
- o Any supported target in rustc --print target-list (note: you have
- to install/add the target to use it).
+ o Any supported target in rustc --print target-list.
- o host, which will internally be substituted by the host’s
+ o "host", which will internally be substituted by the host’s
target. This can be particularly useful if you’re
cross-compiling some crates, and don’t want to specify your
host’s machine as a target (for instance, an xtask in a shared
project that may be worked on by many hosts).
- o A path to a custom target specification (further reading here
- ).
+ o A path to a custom target specification. See Custom Target Lookup
+ Path
+
+ for more information.
This may also be specified with the build.target config value
.
- Note: Specifying this flag makes Cargo run in a different mode where
- the target artifacts are placed in a separate directory. See the
- build cache
+ Note that specifying this flag makes Cargo run in a different mode
+ where the target artifacts are placed in a separate directory. See
+ the build cache
documentation for more details.
diff --git a/src/doc/man/generated_txt/cargo-rustdoc.txt b/src/doc/man/generated_txt/cargo-rustdoc.txt
index b40b05a4e..da7ee6b6e 100644
--- a/src/doc/man/generated_txt/cargo-rustdoc.txt
+++ b/src/doc/man/generated_txt/cargo-rustdoc.txt
@@ -128,30 +128,31 @@ OPTIONS
Compilation Options
--target triple
- Document for the specified target (may be specified multiple times)
- The default is the host architecture. The general format of the
- triple is ---.
+ Document for the specified target architecture. Flag may be
+ specified multiple times. The default is the host architecture. The
+ general format of the triple is ---.
- You may specify the following kinds of targets:
+ Possible values:
- o Any supported target in rustc --print target-list (note: you have
- to install/add the target to use it).
+ o Any supported target in rustc --print target-list.
- o host, which will internally be substituted by the host’s
+ o "host", which will internally be substituted by the host’s
target. This can be particularly useful if you’re
cross-compiling some crates, and don’t want to specify your
host’s machine as a target (for instance, an xtask in a shared
project that may be worked on by many hosts).
- o A path to a custom target specification (further reading here
- ).
+ o A path to a custom target specification. See Custom Target Lookup
+ Path
+
+ for more information.
This may also be specified with the build.target config value
.
- Note: Specifying this flag makes Cargo run in a different mode where
- the target artifacts are placed in a separate directory. See the
- build cache
+ Note that specifying this flag makes Cargo run in a different mode
+ where the target artifacts are placed in a separate directory. See
+ the build cache
documentation for more details.
diff --git a/src/doc/man/generated_txt/cargo-test.txt b/src/doc/man/generated_txt/cargo-test.txt
index a44a6a0d2..272b5fcaa 100644
--- a/src/doc/man/generated_txt/cargo-test.txt
+++ b/src/doc/man/generated_txt/cargo-test.txt
@@ -242,30 +242,31 @@ OPTIONS
Compilation Options
--target triple
- Test for the specified target (may be specified multiple times) The
- default is the host architecture. The general format of the triple
- is ---.
+ Test for the specified target architecture. Flag may be specified
+ multiple times. The default is the host architecture. The general
+ format of the triple is ---.
- You may specify the following kinds of targets:
+ Possible values:
- o Any supported target in rustc --print target-list (note: you have
- to install/add the target to use it).
+ o Any supported target in rustc --print target-list.
- o host, which will internally be substituted by the host’s
+ o "host", which will internally be substituted by the host’s
target. This can be particularly useful if you’re
cross-compiling some crates, and don’t want to specify your
host’s machine as a target (for instance, an xtask in a shared
project that may be worked on by many hosts).
- o A path to a custom target specification (further reading here
- ).
+ o A path to a custom target specification. See Custom Target Lookup
+ Path
+
+ for more information.
This may also be specified with the build.target config value
.
- Note: Specifying this flag makes Cargo run in a different mode where
- the target artifacts are placed in a separate directory. See the
- build cache
+ Note that specifying this flag makes Cargo run in a different mode
+ where the target artifacts are placed in a separate directory. See
+ the build cache
documentation for more details.
diff --git a/src/doc/man/includes/options-target-triple.md b/src/doc/man/includes/options-target-triple.md
index 336eb21a1..977b52b93 100644
--- a/src/doc/man/includes/options-target-triple.md
+++ b/src/doc/man/includes/options-target-triple.md
@@ -1,18 +1,19 @@
{{#option "`--target` _triple_"}}
-{{actionverb}} for the specified target {{~#if multitarget }} (may be specified multiple times) {{~/if}}
-
+{{actionverb}} for the specified target architecture. {{~#if multitarget }} Flag may be specified multiple times. {{~/if}}
{{~#if target-default-to-all-arch}} The default is all architectures.
{{~else}} The default is the host architecture.
{{~/if}} The general format of the triple is
`---`.
-You may specify the following kinds of targets:
-- Any supported target in `rustc --print target-list` (note: you have to install/add the target to use it).
-- `host`, which will internally be substituted by the host's target. This can be particularly useful if you're cross-compiling some crates, and don't want to specify your host's machine as a target (for instance, an `xtask` in a shared project that may be worked on by many hosts).
-- A path to a custom target specification (further reading [here](https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path)).
+Possible values:
+- Any supported target in `rustc --print target-list`.
+- `"host"`, which will internally be substituted by the host's target. This can be particularly useful if you're cross-compiling some crates, and don't want to specify your host's machine as a target (for instance, an `xtask` in a shared project that may be worked on by many hosts).
+- A path to a custom target specification. See [Custom Target Lookup Path](../../rustc/targets/custom.html#custom-target-lookup-path) for more information.
This may also be specified with the `build.target` [config value](../reference/config.html).
-**Note**: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the [build cache](../reference/build-cache.html) documentation for more details.
+Note that specifying this flag makes Cargo run in a different mode where the
+target artifacts are placed in a separate directory. See the
+[build cache](../reference/build-cache.html) documentation for more details.
{{/option}}
diff --git a/src/doc/src/commands/cargo-bench.md b/src/doc/src/commands/cargo-bench.md
index d88e92963..98a7bc9d3 100644
--- a/src/doc/src/commands/cargo-bench.md
+++ b/src/doc/src/commands/cargo-bench.md
@@ -256,16 +256,18 @@ be specified multiple times, which enables all specified features.
--target
triple
-- Benchmark for the specified target (may be specified multiple times) The default is the host architecture. The general format of the triple is
+
- Benchmark for the specified target architecture. Flag may be specified multiple times. The default is the host architecture. The general format of the triple is
<arch><sub>-<vendor>-<sys>-<abi>
.
-You may specify the following kinds of targets:
+Possible values:
-- Any supported target in
rustc --print target-list
(note: you have to install/add the target to use it).
-host
, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an xtask
in a shared project that may be worked on by many hosts).
-- A path to a custom target specification (further reading here).
+- Any supported target in
rustc --print target-list
.
+"host"
, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an xtask
in a shared project that may be worked on by many hosts).
+- A path to a custom target specification. See Custom Target Lookup Path for more information.
This may also be specified with the build.target
config value.
-Note: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the build cache documentation for more details.
+
Note that specifying this flag makes Cargo run in a different mode where the
+target artifacts are placed in a separate directory. See the
+build cache documentation for more details.
--profile
name
diff --git a/src/doc/src/commands/cargo-build.md b/src/doc/src/commands/cargo-build.md
index 0a3752b2a..643875515 100644
--- a/src/doc/src/commands/cargo-build.md
+++ b/src/doc/src/commands/cargo-build.md
@@ -171,16 +171,18 @@ be specified multiple times, which enables all specified features.
--target
triple
-- Build for the specified target (may be specified multiple times) The default is the host architecture. The general format of the triple is
+
- Build for the specified target architecture. Flag may be specified multiple times. The default is the host architecture. The general format of the triple is
<arch><sub>-<vendor>-<sys>-<abi>
.
-You may specify the following kinds of targets:
+Possible values:
-- Any supported target in
rustc --print target-list
(note: you have to install/add the target to use it).
-host
, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an xtask
in a shared project that may be worked on by many hosts).
-- A path to a custom target specification (further reading here).
+- Any supported target in
rustc --print target-list
.
+"host"
, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an xtask
in a shared project that may be worked on by many hosts).
+- A path to a custom target specification. See Custom Target Lookup Path for more information.
This may also be specified with the build.target
config value.
-Note: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the build cache documentation for more details.
+Note that specifying this flag makes Cargo run in a different mode where the
+target artifacts are placed in a separate directory. See the
+build cache documentation for more details.
-r
diff --git a/src/doc/src/commands/cargo-check.md b/src/doc/src/commands/cargo-check.md
index f0a280703..a80c70453 100644
--- a/src/doc/src/commands/cargo-check.md
+++ b/src/doc/src/commands/cargo-check.md
@@ -167,16 +167,18 @@ be specified multiple times, which enables all specified features.
--target
triple
-- Check for the specified target (may be specified multiple times) The default is the host architecture. The general format of the triple is
+
- Check for the specified target architecture. Flag may be specified multiple times. The default is the host architecture. The general format of the triple is
<arch><sub>-<vendor>-<sys>-<abi>
.
-You may specify the following kinds of targets:
+Possible values:
-- Any supported target in
rustc --print target-list
(note: you have to install/add the target to use it).
-host
, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an xtask
in a shared project that may be worked on by many hosts).
-- A path to a custom target specification (further reading here).
+- Any supported target in
rustc --print target-list
.
+"host"
, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an xtask
in a shared project that may be worked on by many hosts).
+- A path to a custom target specification. See Custom Target Lookup Path for more information.
This may also be specified with the build.target
config value.
-Note: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the build cache documentation for more details.
+Note that specifying this flag makes Cargo run in a different mode where the
+target artifacts are placed in a separate directory. See the
+build cache documentation for more details.
-r
diff --git a/src/doc/src/commands/cargo-clean.md b/src/doc/src/commands/cargo-clean.md
index 6694d7d55..1eb9881e7 100644
--- a/src/doc/src/commands/cargo-clean.md
+++ b/src/doc/src/commands/cargo-clean.md
@@ -59,16 +59,18 @@ Defaults to target
in the root of the workspace.
--target
triple
-- Clean for the specified target (may be specified multiple times) The default is the host architecture. The general format of the triple is
+
- Clean for the specified target architecture. Flag may be specified multiple times. The default is the host architecture. The general format of the triple is
<arch><sub>-<vendor>-<sys>-<abi>
.
-You may specify the following kinds of targets:
+Possible values:
-- Any supported target in
rustc --print target-list
(note: you have to install/add the target to use it).
-host
, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an xtask
in a shared project that may be worked on by many hosts).
-- A path to a custom target specification (further reading here).
+- Any supported target in
rustc --print target-list
.
+"host"
, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an xtask
in a shared project that may be worked on by many hosts).
+- A path to a custom target specification. See Custom Target Lookup Path for more information.
This may also be specified with the build.target
config value.
-Note: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the build cache documentation for more details.
+Note that specifying this flag makes Cargo run in a different mode where the
+target artifacts are placed in a separate directory. See the
+build cache documentation for more details.
diff --git a/src/doc/src/commands/cargo-doc.md b/src/doc/src/commands/cargo-doc.md
index de562a1bf..6b5db3a6d 100644
--- a/src/doc/src/commands/cargo-doc.md
+++ b/src/doc/src/commands/cargo-doc.md
@@ -146,16 +146,18 @@ be specified multiple times, which enables all specified features.
--target
triple
-- Document for the specified target (may be specified multiple times) The default is the host architecture. The general format of the triple is
+
- Document for the specified target architecture. Flag may be specified multiple times. The default is the host architecture. The general format of the triple is
<arch><sub>-<vendor>-<sys>-<abi>
.
-You may specify the following kinds of targets:
+Possible values:
-- Any supported target in
rustc --print target-list
(note: you have to install/add the target to use it).
-host
, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an xtask
in a shared project that may be worked on by many hosts).
-- A path to a custom target specification (further reading here).
+- Any supported target in
rustc --print target-list
.
+"host"
, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an xtask
in a shared project that may be worked on by many hosts).
+- A path to a custom target specification. See Custom Target Lookup Path for more information.
This may also be specified with the build.target
config value.
-Note: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the build cache documentation for more details.
+Note that specifying this flag makes Cargo run in a different mode where the
+target artifacts are placed in a separate directory. See the
+build cache documentation for more details.
-r
diff --git a/src/doc/src/commands/cargo-fetch.md b/src/doc/src/commands/cargo-fetch.md
index d76391409..443762465 100644
--- a/src/doc/src/commands/cargo-fetch.md
+++ b/src/doc/src/commands/cargo-fetch.md
@@ -29,16 +29,18 @@ you plan to use Cargo without a network with the `--offline` flag.
--target
triple
-- Fetch for the specified target (may be specified multiple times) The default is all architectures. The general format of the triple is
+
- Fetch for the specified target architecture. Flag may be specified multiple times. The default is all architectures. The general format of the triple is
<arch><sub>-<vendor>-<sys>-<abi>
.
-You may specify the following kinds of targets:
+Possible values:
-- Any supported target in
rustc --print target-list
(note: you have to install/add the target to use it).
-host
, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an xtask
in a shared project that may be worked on by many hosts).
-- A path to a custom target specification (further reading here).
+- Any supported target in
rustc --print target-list
.
+"host"
, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an xtask
in a shared project that may be worked on by many hosts).
+- A path to a custom target specification. See Custom Target Lookup Path for more information.
This may also be specified with the build.target
config value.
-Note: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the build cache documentation for more details.
+Note that specifying this flag makes Cargo run in a different mode where the
+target artifacts are placed in a separate directory. See the
+build cache documentation for more details.
diff --git a/src/doc/src/commands/cargo-fix.md b/src/doc/src/commands/cargo-fix.md
index 0bf919a33..5a0dfccc9 100644
--- a/src/doc/src/commands/cargo-fix.md
+++ b/src/doc/src/commands/cargo-fix.md
@@ -247,16 +247,18 @@ be specified multiple times, which enables all specified features.
--target
triple
-- Fix for the specified target (may be specified multiple times) The default is the host architecture. The general format of the triple is
+
- Fix for the specified target architecture. Flag may be specified multiple times. The default is the host architecture. The general format of the triple is
<arch><sub>-<vendor>-<sys>-<abi>
.
-You may specify the following kinds of targets:
+Possible values:
-- Any supported target in
rustc --print target-list
(note: you have to install/add the target to use it).
-host
, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an xtask
in a shared project that may be worked on by many hosts).
-- A path to a custom target specification (further reading here).
+- Any supported target in
rustc --print target-list
.
+"host"
, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an xtask
in a shared project that may be worked on by many hosts).
+- A path to a custom target specification. See Custom Target Lookup Path for more information.
This may also be specified with the build.target
config value.
-Note: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the build cache documentation for more details.
+Note that specifying this flag makes Cargo run in a different mode where the
+target artifacts are placed in a separate directory. See the
+build cache documentation for more details.
-r
diff --git a/src/doc/src/commands/cargo-install.md b/src/doc/src/commands/cargo-install.md
index 27b11e083..8e272a80e 100644
--- a/src/doc/src/commands/cargo-install.md
+++ b/src/doc/src/commands/cargo-install.md
@@ -212,16 +212,18 @@ be specified multiple times, which enables all specified features.
--target
triple
-- Install for the specified target The default is the host architecture. The general format of the triple is
+
- Install for the specified target architecture. The default is the host architecture. The general format of the triple is
<arch><sub>-<vendor>-<sys>-<abi>
.
-You may specify the following kinds of targets:
+Possible values:
-- Any supported target in
rustc --print target-list
(note: you have to install/add the target to use it).
-host
, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an xtask
in a shared project that may be worked on by many hosts).
-- A path to a custom target specification (further reading here).
+- Any supported target in
rustc --print target-list
.
+"host"
, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an xtask
in a shared project that may be worked on by many hosts).
+- A path to a custom target specification. See Custom Target Lookup Path for more information.
This may also be specified with the build.target
config value.
-Note: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the build cache documentation for more details.
+Note that specifying this flag makes Cargo run in a different mode where the
+target artifacts are placed in a separate directory. See the
+build cache documentation for more details.
--target-dir
directory
diff --git a/src/doc/src/commands/cargo-package.md b/src/doc/src/commands/cargo-package.md
index 01d26e1e4..5c75c0048 100644
--- a/src/doc/src/commands/cargo-package.md
+++ b/src/doc/src/commands/cargo-package.md
@@ -202,16 +202,18 @@ single quotes or double quotes around each pattern.
--target
triple
-- Package for the specified target (may be specified multiple times) The default is the host architecture. The general format of the triple is
+
- Package for the specified target architecture. Flag may be specified multiple times. The default is the host architecture. The general format of the triple is
<arch><sub>-<vendor>-<sys>-<abi>
.
-You may specify the following kinds of targets:
+Possible values:
-- Any supported target in
rustc --print target-list
(note: you have to install/add the target to use it).
-host
, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an xtask
in a shared project that may be worked on by many hosts).
-- A path to a custom target specification (further reading here).
+- Any supported target in
rustc --print target-list
.
+"host"
, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an xtask
in a shared project that may be worked on by many hosts).
+- A path to a custom target specification. See Custom Target Lookup Path for more information.
This may also be specified with the build.target
config value.
-Note: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the build cache documentation for more details.
+Note that specifying this flag makes Cargo run in a different mode where the
+target artifacts are placed in a separate directory. See the
+build cache documentation for more details.
--target-dir
directory
diff --git a/src/doc/src/commands/cargo-publish.md b/src/doc/src/commands/cargo-publish.md
index 86b37f115..6b6081d82 100644
--- a/src/doc/src/commands/cargo-publish.md
+++ b/src/doc/src/commands/cargo-publish.md
@@ -122,16 +122,18 @@ single quotes or double quotes around each pattern.
--target
triple
-- Publish for the specified target (may be specified multiple times) The default is the host architecture. The general format of the triple is
+
- Publish for the specified target architecture. Flag may be specified multiple times. The default is the host architecture. The general format of the triple is
<arch><sub>-<vendor>-<sys>-<abi>
.
-You may specify the following kinds of targets:
+Possible values:
-- Any supported target in
rustc --print target-list
(note: you have to install/add the target to use it).
-host
, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an xtask
in a shared project that may be worked on by many hosts).
-- A path to a custom target specification (further reading here).
+- Any supported target in
rustc --print target-list
.
+"host"
, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an xtask
in a shared project that may be worked on by many hosts).
+- A path to a custom target specification. See Custom Target Lookup Path for more information.
This may also be specified with the build.target
config value.
-Note: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the build cache documentation for more details.
+Note that specifying this flag makes Cargo run in a different mode where the
+target artifacts are placed in a separate directory. See the
+build cache documentation for more details.
--target-dir
directory
diff --git a/src/doc/src/commands/cargo-run.md b/src/doc/src/commands/cargo-run.md
index a9d841618..968dbda00 100644
--- a/src/doc/src/commands/cargo-run.md
+++ b/src/doc/src/commands/cargo-run.md
@@ -88,16 +88,18 @@ be specified multiple times, which enables all specified features.
--target
triple
-- Run for the specified target The default is the host architecture. The general format of the triple is
+
- Run for the specified target architecture. The default is the host architecture. The general format of the triple is
<arch><sub>-<vendor>-<sys>-<abi>
.
-You may specify the following kinds of targets:
+Possible values:
-- Any supported target in
rustc --print target-list
(note: you have to install/add the target to use it).
-host
, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an xtask
in a shared project that may be worked on by many hosts).
-- A path to a custom target specification (further reading here).
+- Any supported target in
rustc --print target-list
.
+"host"
, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an xtask
in a shared project that may be worked on by many hosts).
+- A path to a custom target specification. See Custom Target Lookup Path for more information.
This may also be specified with the build.target
config value.
-Note: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the build cache documentation for more details.
+Note that specifying this flag makes Cargo run in a different mode where the
+target artifacts are placed in a separate directory. See the
+build cache documentation for more details.
-r
diff --git a/src/doc/src/commands/cargo-rustc.md b/src/doc/src/commands/cargo-rustc.md
index 5bdf5c42d..73a168102 100644
--- a/src/doc/src/commands/cargo-rustc.md
+++ b/src/doc/src/commands/cargo-rustc.md
@@ -160,16 +160,18 @@ be specified multiple times, which enables all specified features.
--target
triple
-- Build for the specified target (may be specified multiple times) The default is the host architecture. The general format of the triple is
+
- Build for the specified target architecture. Flag may be specified multiple times. The default is the host architecture. The general format of the triple is
<arch><sub>-<vendor>-<sys>-<abi>
.
-You may specify the following kinds of targets:
+Possible values:
-- Any supported target in
rustc --print target-list
(note: you have to install/add the target to use it).
-host
, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an xtask
in a shared project that may be worked on by many hosts).
-- A path to a custom target specification (further reading here).
+- Any supported target in
rustc --print target-list
.
+"host"
, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an xtask
in a shared project that may be worked on by many hosts).
+- A path to a custom target specification. See Custom Target Lookup Path for more information.
This may also be specified with the build.target
config value.
-Note: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the build cache documentation for more details.
+Note that specifying this flag makes Cargo run in a different mode where the
+target artifacts are placed in a separate directory. See the
+build cache documentation for more details.
-r
diff --git a/src/doc/src/commands/cargo-rustdoc.md b/src/doc/src/commands/cargo-rustdoc.md
index ec1fa0629..8ae1559e7 100644
--- a/src/doc/src/commands/cargo-rustdoc.md
+++ b/src/doc/src/commands/cargo-rustdoc.md
@@ -166,16 +166,18 @@ be specified multiple times, which enables all specified features.
--target
triple
-- Document for the specified target (may be specified multiple times) The default is the host architecture. The general format of the triple is
+
- Document for the specified target architecture. Flag may be specified multiple times. The default is the host architecture. The general format of the triple is
<arch><sub>-<vendor>-<sys>-<abi>
.
-You may specify the following kinds of targets:
+Possible values:
-- Any supported target in
rustc --print target-list
(note: you have to install/add the target to use it).
-host
, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an xtask
in a shared project that may be worked on by many hosts).
-- A path to a custom target specification (further reading here).
+- Any supported target in
rustc --print target-list
.
+"host"
, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an xtask
in a shared project that may be worked on by many hosts).
+- A path to a custom target specification. See Custom Target Lookup Path for more information.
This may also be specified with the build.target
config value.
-Note: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the build cache documentation for more details.
+Note that specifying this flag makes Cargo run in a different mode where the
+target artifacts are placed in a separate directory. See the
+build cache documentation for more details.
-r
diff --git a/src/doc/src/commands/cargo-test.md b/src/doc/src/commands/cargo-test.md
index 8a7fe3648..b76010bf5 100644
--- a/src/doc/src/commands/cargo-test.md
+++ b/src/doc/src/commands/cargo-test.md
@@ -278,16 +278,18 @@ be specified multiple times, which enables all specified features.
--target
triple
-- Test for the specified target (may be specified multiple times) The default is the host architecture. The general format of the triple is
+
- Test for the specified target architecture. Flag may be specified multiple times. The default is the host architecture. The general format of the triple is
<arch><sub>-<vendor>-<sys>-<abi>
.
-You may specify the following kinds of targets:
+Possible values:
-- Any supported target in
rustc --print target-list
(note: you have to install/add the target to use it).
-host
, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an xtask
in a shared project that may be worked on by many hosts).
-- A path to a custom target specification (further reading here).
+- Any supported target in
rustc --print target-list
.
+"host"
, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an xtask
in a shared project that may be worked on by many hosts).
+- A path to a custom target specification. See Custom Target Lookup Path for more information.
This may also be specified with the build.target
config value.
-Note: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the build cache documentation for more details.
+Note that specifying this flag makes Cargo run in a different mode where the
+target artifacts are placed in a separate directory. See the
+build cache documentation for more details.
-r
diff --git a/src/doc/src/reference/config.md b/src/doc/src/reference/config.md
index 7db7ba174..52e1c23c1 100644
--- a/src/doc/src/reference/config.md
+++ b/src/doc/src/reference/config.md
@@ -459,16 +459,16 @@ Sets the executable to use for `rustdoc`.
The default [target platform triples][target triple] to compile to.
-You may specify the following kinds of targets:
-- Any supported target in `rustc --print target-list` (note: you have to install/add the target to use it).
-- `host`, which will internally be substituted by the host's target. This can be particularly useful if you're cross-compiling some crates, and don't want to specify your host's machine as a target (for instance, an `xtask` in a shared project that may be worked on by many hosts).
-- A path to a custom target specification (further reading [here](https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path)).
+Possible values:
+- Any supported target in `rustc --print target-list`.
+- `"host"`, which will internally be substituted by the host's target. This can be particularly useful if you're cross-compiling some crates, and don't want to specify your host's machine as a target (for instance, an `xtask` in a shared project that may be worked on by many hosts).
+- A path to a custom target specification. See [Custom Target Lookup Path](../../rustc/targets/custom.html#custom-target-lookup-path) for more information.
Can be overridden with the `--target` CLI option.
```toml
[build]
-target = ["host", "x86_64-unknown-linux-gnu", "i686-unknown-linux-gnu"]
+target = ["x86_64-unknown-linux-gnu", "i686-unknown-linux-gnu"]
```
#### `build.target-dir`
diff --git a/src/etc/man/cargo-bench.1 b/src/etc/man/cargo-bench.1
index 6cc833890..73e7c64d7 100644
--- a/src/etc/man/cargo-bench.1
+++ b/src/etc/man/cargo-bench.1
@@ -267,26 +267,28 @@ Do not activate the \fBdefault\fR feature of the selected packages.
.sp
\fB\-\-target\fR \fItriple\fR
.RS 4
-Benchmark for the specified target (may be specified multiple times) The default is the host architecture. The general format of the triple is
+Benchmark for the specified target architecture. Flag may be specified multiple times. The default is the host architecture. The general format of the triple is
\fB\-\-\-\fR\&.
.sp
-You may specify the following kinds of targets:
+Possible values:
.sp
.RS 4
-\h'-04'\(bu\h'+03'Any supported target in \fBrustc \-\-print target\-list\fR (note: you have to install/add the target to use it).
+\h'-04'\(bu\h'+03'Any supported target in \fBrustc \-\-print target\-list\fR\&.
.RE
.sp
.RS 4
-\h'-04'\(bu\h'+03'\fBhost\fR, which will internally be substituted by the host\[cq]s target. This can be particularly useful if you\[cq]re cross\-compiling some crates, and don\[cq]t want to specify your host\[cq]s machine as a target (for instance, an \fBxtask\fR in a shared project that may be worked on by many hosts).
+\h'-04'\(bu\h'+03'\fB"host"\fR, which will internally be substituted by the host\[cq]s target. This can be particularly useful if you\[cq]re cross\-compiling some crates, and don\[cq]t want to specify your host\[cq]s machine as a target (for instance, an \fBxtask\fR in a shared project that may be worked on by many hosts).
.RE
.sp
.RS 4
-\h'-04'\(bu\h'+03'A path to a custom target specification (further reading \fIhere\fR ).
+\h'-04'\(bu\h'+03'A path to a custom target specification. See \fICustom Target Lookup Path\fR for more information.
.RE
.sp
This may also be specified with the \fBbuild.target\fR \fIconfig value\fR \&.
.sp
-\fBNote\fR: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the \fIbuild cache\fR documentation for more details.
+Note that specifying this flag makes Cargo run in a different mode where the
+target artifacts are placed in a separate directory. See the
+\fIbuild cache\fR documentation for more details.
.RE
.sp
\fB\-\-profile\fR \fIname\fR
diff --git a/src/etc/man/cargo-build.1 b/src/etc/man/cargo-build.1
index 4f235a21e..dd478a541 100644
--- a/src/etc/man/cargo-build.1
+++ b/src/etc/man/cargo-build.1
@@ -166,26 +166,28 @@ Do not activate the \fBdefault\fR feature of the selected packages.
.sp
\fB\-\-target\fR \fItriple\fR
.RS 4
-Build for the specified target (may be specified multiple times) The default is the host architecture. The general format of the triple is
+Build for the specified target architecture. Flag may be specified multiple times. The default is the host architecture. The general format of the triple is
\fB\-\-\-\fR\&.
.sp
-You may specify the following kinds of targets:
+Possible values:
.sp
.RS 4
-\h'-04'\(bu\h'+03'Any supported target in \fBrustc \-\-print target\-list\fR (note: you have to install/add the target to use it).
+\h'-04'\(bu\h'+03'Any supported target in \fBrustc \-\-print target\-list\fR\&.
.RE
.sp
.RS 4
-\h'-04'\(bu\h'+03'\fBhost\fR, which will internally be substituted by the host\[cq]s target. This can be particularly useful if you\[cq]re cross\-compiling some crates, and don\[cq]t want to specify your host\[cq]s machine as a target (for instance, an \fBxtask\fR in a shared project that may be worked on by many hosts).
+\h'-04'\(bu\h'+03'\fB"host"\fR, which will internally be substituted by the host\[cq]s target. This can be particularly useful if you\[cq]re cross\-compiling some crates, and don\[cq]t want to specify your host\[cq]s machine as a target (for instance, an \fBxtask\fR in a shared project that may be worked on by many hosts).
.RE
.sp
.RS 4
-\h'-04'\(bu\h'+03'A path to a custom target specification (further reading \fIhere\fR ).
+\h'-04'\(bu\h'+03'A path to a custom target specification. See \fICustom Target Lookup Path\fR for more information.
.RE
.sp
This may also be specified with the \fBbuild.target\fR \fIconfig value\fR \&.
.sp
-\fBNote\fR: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the \fIbuild cache\fR documentation for more details.
+Note that specifying this flag makes Cargo run in a different mode where the
+target artifacts are placed in a separate directory. See the
+\fIbuild cache\fR documentation for more details.
.RE
.sp
\fB\-r\fR,
diff --git a/src/etc/man/cargo-check.1 b/src/etc/man/cargo-check.1
index cf32e394b..0fd8d9b3d 100644
--- a/src/etc/man/cargo-check.1
+++ b/src/etc/man/cargo-check.1
@@ -162,26 +162,28 @@ Do not activate the \fBdefault\fR feature of the selected packages.
.sp
\fB\-\-target\fR \fItriple\fR
.RS 4
-Check for the specified target (may be specified multiple times) The default is the host architecture. The general format of the triple is
+Check for the specified target architecture. Flag may be specified multiple times. The default is the host architecture. The general format of the triple is
\fB\-\-\-\fR\&.
.sp
-You may specify the following kinds of targets:
+Possible values:
.sp
.RS 4
-\h'-04'\(bu\h'+03'Any supported target in \fBrustc \-\-print target\-list\fR (note: you have to install/add the target to use it).
+\h'-04'\(bu\h'+03'Any supported target in \fBrustc \-\-print target\-list\fR\&.
.RE
.sp
.RS 4
-\h'-04'\(bu\h'+03'\fBhost\fR, which will internally be substituted by the host\[cq]s target. This can be particularly useful if you\[cq]re cross\-compiling some crates, and don\[cq]t want to specify your host\[cq]s machine as a target (for instance, an \fBxtask\fR in a shared project that may be worked on by many hosts).
+\h'-04'\(bu\h'+03'\fB"host"\fR, which will internally be substituted by the host\[cq]s target. This can be particularly useful if you\[cq]re cross\-compiling some crates, and don\[cq]t want to specify your host\[cq]s machine as a target (for instance, an \fBxtask\fR in a shared project that may be worked on by many hosts).
.RE
.sp
.RS 4
-\h'-04'\(bu\h'+03'A path to a custom target specification (further reading \fIhere\fR ).
+\h'-04'\(bu\h'+03'A path to a custom target specification. See \fICustom Target Lookup Path\fR for more information.
.RE
.sp
This may also be specified with the \fBbuild.target\fR \fIconfig value\fR \&.
.sp
-\fBNote\fR: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the \fIbuild cache\fR documentation for more details.
+Note that specifying this flag makes Cargo run in a different mode where the
+target artifacts are placed in a separate directory. See the
+\fIbuild cache\fR documentation for more details.
.RE
.sp
\fB\-r\fR,
diff --git a/src/etc/man/cargo-clean.1 b/src/etc/man/cargo-clean.1
index 6c2f8f73d..4ca8ed98b 100644
--- a/src/etc/man/cargo-clean.1
+++ b/src/etc/man/cargo-clean.1
@@ -57,26 +57,28 @@ Defaults to \fBtarget\fR in the root of the workspace.
.sp
\fB\-\-target\fR \fItriple\fR
.RS 4
-Clean for the specified target (may be specified multiple times) The default is the host architecture. The general format of the triple is
+Clean for the specified target architecture. Flag may be specified multiple times. The default is the host architecture. The general format of the triple is
\fB\-\-\-\fR\&.
.sp
-You may specify the following kinds of targets:
+Possible values:
.sp
.RS 4
-\h'-04'\(bu\h'+03'Any supported target in \fBrustc \-\-print target\-list\fR (note: you have to install/add the target to use it).
+\h'-04'\(bu\h'+03'Any supported target in \fBrustc \-\-print target\-list\fR\&.
.RE
.sp
.RS 4
-\h'-04'\(bu\h'+03'\fBhost\fR, which will internally be substituted by the host\[cq]s target. This can be particularly useful if you\[cq]re cross\-compiling some crates, and don\[cq]t want to specify your host\[cq]s machine as a target (for instance, an \fBxtask\fR in a shared project that may be worked on by many hosts).
+\h'-04'\(bu\h'+03'\fB"host"\fR, which will internally be substituted by the host\[cq]s target. This can be particularly useful if you\[cq]re cross\-compiling some crates, and don\[cq]t want to specify your host\[cq]s machine as a target (for instance, an \fBxtask\fR in a shared project that may be worked on by many hosts).
.RE
.sp
.RS 4
-\h'-04'\(bu\h'+03'A path to a custom target specification (further reading \fIhere\fR ).
+\h'-04'\(bu\h'+03'A path to a custom target specification. See \fICustom Target Lookup Path\fR for more information.
.RE
.sp
This may also be specified with the \fBbuild.target\fR \fIconfig value\fR \&.
.sp
-\fBNote\fR: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the \fIbuild cache\fR documentation for more details.
+Note that specifying this flag makes Cargo run in a different mode where the
+target artifacts are placed in a separate directory. See the
+\fIbuild cache\fR documentation for more details.
.RE
.SS "Display Options"
.sp
diff --git a/src/etc/man/cargo-doc.1 b/src/etc/man/cargo-doc.1
index 81fb09534..96d237cbd 100644
--- a/src/etc/man/cargo-doc.1
+++ b/src/etc/man/cargo-doc.1
@@ -135,26 +135,28 @@ Do not activate the \fBdefault\fR feature of the selected packages.
.sp
\fB\-\-target\fR \fItriple\fR
.RS 4
-Document for the specified target (may be specified multiple times) The default is the host architecture. The general format of the triple is
+Document for the specified target architecture. Flag may be specified multiple times. The default is the host architecture. The general format of the triple is
\fB\-\-\-\fR\&.
.sp
-You may specify the following kinds of targets:
+Possible values:
.sp
.RS 4
-\h'-04'\(bu\h'+03'Any supported target in \fBrustc \-\-print target\-list\fR (note: you have to install/add the target to use it).
+\h'-04'\(bu\h'+03'Any supported target in \fBrustc \-\-print target\-list\fR\&.
.RE
.sp
.RS 4
-\h'-04'\(bu\h'+03'\fBhost\fR, which will internally be substituted by the host\[cq]s target. This can be particularly useful if you\[cq]re cross\-compiling some crates, and don\[cq]t want to specify your host\[cq]s machine as a target (for instance, an \fBxtask\fR in a shared project that may be worked on by many hosts).
+\h'-04'\(bu\h'+03'\fB"host"\fR, which will internally be substituted by the host\[cq]s target. This can be particularly useful if you\[cq]re cross\-compiling some crates, and don\[cq]t want to specify your host\[cq]s machine as a target (for instance, an \fBxtask\fR in a shared project that may be worked on by many hosts).
.RE
.sp
.RS 4
-\h'-04'\(bu\h'+03'A path to a custom target specification (further reading \fIhere\fR ).
+\h'-04'\(bu\h'+03'A path to a custom target specification. See \fICustom Target Lookup Path\fR for more information.
.RE
.sp
This may also be specified with the \fBbuild.target\fR \fIconfig value\fR \&.
.sp
-\fBNote\fR: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the \fIbuild cache\fR documentation for more details.
+Note that specifying this flag makes Cargo run in a different mode where the
+target artifacts are placed in a separate directory. See the
+\fIbuild cache\fR documentation for more details.
.RE
.sp
\fB\-r\fR,
diff --git a/src/etc/man/cargo-fetch.1 b/src/etc/man/cargo-fetch.1
index 14c911665..726087901 100644
--- a/src/etc/man/cargo-fetch.1
+++ b/src/etc/man/cargo-fetch.1
@@ -25,26 +25,28 @@ you plan to use Cargo without a network with the \fB\-\-offline\fR flag.
.sp
\fB\-\-target\fR \fItriple\fR
.RS 4
-Fetch for the specified target (may be specified multiple times) The default is all architectures. The general format of the triple is
+Fetch for the specified target architecture. Flag may be specified multiple times. The default is all architectures. The general format of the triple is
\fB\-\-\-\fR\&.
.sp
-You may specify the following kinds of targets:
+Possible values:
.sp
.RS 4
-\h'-04'\(bu\h'+03'Any supported target in \fBrustc \-\-print target\-list\fR (note: you have to install/add the target to use it).
+\h'-04'\(bu\h'+03'Any supported target in \fBrustc \-\-print target\-list\fR\&.
.RE
.sp
.RS 4
-\h'-04'\(bu\h'+03'\fBhost\fR, which will internally be substituted by the host\[cq]s target. This can be particularly useful if you\[cq]re cross\-compiling some crates, and don\[cq]t want to specify your host\[cq]s machine as a target (for instance, an \fBxtask\fR in a shared project that may be worked on by many hosts).
+\h'-04'\(bu\h'+03'\fB"host"\fR, which will internally be substituted by the host\[cq]s target. This can be particularly useful if you\[cq]re cross\-compiling some crates, and don\[cq]t want to specify your host\[cq]s machine as a target (for instance, an \fBxtask\fR in a shared project that may be worked on by many hosts).
.RE
.sp
.RS 4
-\h'-04'\(bu\h'+03'A path to a custom target specification (further reading \fIhere\fR ).
+\h'-04'\(bu\h'+03'A path to a custom target specification. See \fICustom Target Lookup Path\fR for more information.
.RE
.sp
This may also be specified with the \fBbuild.target\fR \fIconfig value\fR \&.
.sp
-\fBNote\fR: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the \fIbuild cache\fR documentation for more details.
+Note that specifying this flag makes Cargo run in a different mode where the
+target artifacts are placed in a separate directory. See the
+\fIbuild cache\fR documentation for more details.
.RE
.SS "Display Options"
.sp
diff --git a/src/etc/man/cargo-fix.1 b/src/etc/man/cargo-fix.1
index bfb104395..0e79e99b8 100644
--- a/src/etc/man/cargo-fix.1
+++ b/src/etc/man/cargo-fix.1
@@ -257,26 +257,28 @@ Do not activate the \fBdefault\fR feature of the selected packages.
.sp
\fB\-\-target\fR \fItriple\fR
.RS 4
-Fix for the specified target (may be specified multiple times) The default is the host architecture. The general format of the triple is
+Fix for the specified target architecture. Flag may be specified multiple times. The default is the host architecture. The general format of the triple is
\fB\-\-\-\fR\&.
.sp
-You may specify the following kinds of targets:
+Possible values:
.sp
.RS 4
-\h'-04'\(bu\h'+03'Any supported target in \fBrustc \-\-print target\-list\fR (note: you have to install/add the target to use it).
+\h'-04'\(bu\h'+03'Any supported target in \fBrustc \-\-print target\-list\fR\&.
.RE
.sp
.RS 4
-\h'-04'\(bu\h'+03'\fBhost\fR, which will internally be substituted by the host\[cq]s target. This can be particularly useful if you\[cq]re cross\-compiling some crates, and don\[cq]t want to specify your host\[cq]s machine as a target (for instance, an \fBxtask\fR in a shared project that may be worked on by many hosts).
+\h'-04'\(bu\h'+03'\fB"host"\fR, which will internally be substituted by the host\[cq]s target. This can be particularly useful if you\[cq]re cross\-compiling some crates, and don\[cq]t want to specify your host\[cq]s machine as a target (for instance, an \fBxtask\fR in a shared project that may be worked on by many hosts).
.RE
.sp
.RS 4
-\h'-04'\(bu\h'+03'A path to a custom target specification (further reading \fIhere\fR ).
+\h'-04'\(bu\h'+03'A path to a custom target specification. See \fICustom Target Lookup Path\fR for more information.
.RE
.sp
This may also be specified with the \fBbuild.target\fR \fIconfig value\fR \&.
.sp
-\fBNote\fR: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the \fIbuild cache\fR documentation for more details.
+Note that specifying this flag makes Cargo run in a different mode where the
+target artifacts are placed in a separate directory. See the
+\fIbuild cache\fR documentation for more details.
.RE
.sp
\fB\-r\fR,
diff --git a/src/etc/man/cargo-install.1 b/src/etc/man/cargo-install.1
index e82ae0b78..04c90640e 100644
--- a/src/etc/man/cargo-install.1
+++ b/src/etc/man/cargo-install.1
@@ -242,26 +242,28 @@ Do not activate the \fBdefault\fR feature of the selected packages.
.sp
\fB\-\-target\fR \fItriple\fR
.RS 4
-Install for the specified target The default is the host architecture. The general format of the triple is
+Install for the specified target architecture. The default is the host architecture. The general format of the triple is
\fB\-\-\-\fR\&.
.sp
-You may specify the following kinds of targets:
+Possible values:
.sp
.RS 4
-\h'-04'\(bu\h'+03'Any supported target in \fBrustc \-\-print target\-list\fR (note: you have to install/add the target to use it).
+\h'-04'\(bu\h'+03'Any supported target in \fBrustc \-\-print target\-list\fR\&.
.RE
.sp
.RS 4
-\h'-04'\(bu\h'+03'\fBhost\fR, which will internally be substituted by the host\[cq]s target. This can be particularly useful if you\[cq]re cross\-compiling some crates, and don\[cq]t want to specify your host\[cq]s machine as a target (for instance, an \fBxtask\fR in a shared project that may be worked on by many hosts).
+\h'-04'\(bu\h'+03'\fB"host"\fR, which will internally be substituted by the host\[cq]s target. This can be particularly useful if you\[cq]re cross\-compiling some crates, and don\[cq]t want to specify your host\[cq]s machine as a target (for instance, an \fBxtask\fR in a shared project that may be worked on by many hosts).
.RE
.sp
.RS 4
-\h'-04'\(bu\h'+03'A path to a custom target specification (further reading \fIhere\fR ).
+\h'-04'\(bu\h'+03'A path to a custom target specification. See \fICustom Target Lookup Path\fR for more information.
.RE
.sp
This may also be specified with the \fBbuild.target\fR \fIconfig value\fR \&.
.sp
-\fBNote\fR: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the \fIbuild cache\fR documentation for more details.
+Note that specifying this flag makes Cargo run in a different mode where the
+target artifacts are placed in a separate directory. See the
+\fIbuild cache\fR documentation for more details.
.RE
.sp
\fB\-\-target\-dir\fR \fIdirectory\fR
diff --git a/src/etc/man/cargo-package.1 b/src/etc/man/cargo-package.1
index cac7f2a37..168f3152f 100644
--- a/src/etc/man/cargo-package.1
+++ b/src/etc/man/cargo-package.1
@@ -239,26 +239,28 @@ single quotes or double quotes around each pattern.
.sp
\fB\-\-target\fR \fItriple\fR
.RS 4
-Package for the specified target (may be specified multiple times) The default is the host architecture. The general format of the triple is
+Package for the specified target architecture. Flag may be specified multiple times. The default is the host architecture. The general format of the triple is
\fB\-\-\-\fR\&.
.sp
-You may specify the following kinds of targets:
+Possible values:
.sp
.RS 4
-\h'-04'\(bu\h'+03'Any supported target in \fBrustc \-\-print target\-list\fR (note: you have to install/add the target to use it).
+\h'-04'\(bu\h'+03'Any supported target in \fBrustc \-\-print target\-list\fR\&.
.RE
.sp
.RS 4
-\h'-04'\(bu\h'+03'\fBhost\fR, which will internally be substituted by the host\[cq]s target. This can be particularly useful if you\[cq]re cross\-compiling some crates, and don\[cq]t want to specify your host\[cq]s machine as a target (for instance, an \fBxtask\fR in a shared project that may be worked on by many hosts).
+\h'-04'\(bu\h'+03'\fB"host"\fR, which will internally be substituted by the host\[cq]s target. This can be particularly useful if you\[cq]re cross\-compiling some crates, and don\[cq]t want to specify your host\[cq]s machine as a target (for instance, an \fBxtask\fR in a shared project that may be worked on by many hosts).
.RE
.sp
.RS 4
-\h'-04'\(bu\h'+03'A path to a custom target specification (further reading \fIhere\fR ).
+\h'-04'\(bu\h'+03'A path to a custom target specification. See \fICustom Target Lookup Path\fR for more information.
.RE
.sp
This may also be specified with the \fBbuild.target\fR \fIconfig value\fR \&.
.sp
-\fBNote\fR: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the \fIbuild cache\fR documentation for more details.
+Note that specifying this flag makes Cargo run in a different mode where the
+target artifacts are placed in a separate directory. See the
+\fIbuild cache\fR documentation for more details.
.RE
.sp
\fB\-\-target\-dir\fR \fIdirectory\fR
diff --git a/src/etc/man/cargo-publish.1 b/src/etc/man/cargo-publish.1
index 34dd63644..6d9d3a4a8 100644
--- a/src/etc/man/cargo-publish.1
+++ b/src/etc/man/cargo-publish.1
@@ -132,26 +132,28 @@ single quotes or double quotes around each pattern.
.sp
\fB\-\-target\fR \fItriple\fR
.RS 4
-Publish for the specified target (may be specified multiple times) The default is the host architecture. The general format of the triple is
+Publish for the specified target architecture. Flag may be specified multiple times. The default is the host architecture. The general format of the triple is
\fB\-\-\-\fR\&.
.sp
-You may specify the following kinds of targets:
+Possible values:
.sp
.RS 4
-\h'-04'\(bu\h'+03'Any supported target in \fBrustc \-\-print target\-list\fR (note: you have to install/add the target to use it).
+\h'-04'\(bu\h'+03'Any supported target in \fBrustc \-\-print target\-list\fR\&.
.RE
.sp
.RS 4
-\h'-04'\(bu\h'+03'\fBhost\fR, which will internally be substituted by the host\[cq]s target. This can be particularly useful if you\[cq]re cross\-compiling some crates, and don\[cq]t want to specify your host\[cq]s machine as a target (for instance, an \fBxtask\fR in a shared project that may be worked on by many hosts).
+\h'-04'\(bu\h'+03'\fB"host"\fR, which will internally be substituted by the host\[cq]s target. This can be particularly useful if you\[cq]re cross\-compiling some crates, and don\[cq]t want to specify your host\[cq]s machine as a target (for instance, an \fBxtask\fR in a shared project that may be worked on by many hosts).
.RE
.sp
.RS 4
-\h'-04'\(bu\h'+03'A path to a custom target specification (further reading \fIhere\fR ).
+\h'-04'\(bu\h'+03'A path to a custom target specification. See \fICustom Target Lookup Path\fR for more information.
.RE
.sp
This may also be specified with the \fBbuild.target\fR \fIconfig value\fR \&.
.sp
-\fBNote\fR: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the \fIbuild cache\fR documentation for more details.
+Note that specifying this flag makes Cargo run in a different mode where the
+target artifacts are placed in a separate directory. See the
+\fIbuild cache\fR documentation for more details.
.RE
.sp
\fB\-\-target\-dir\fR \fIdirectory\fR
diff --git a/src/etc/man/cargo-run.1 b/src/etc/man/cargo-run.1
index cf63052b3..f1640ee60 100644
--- a/src/etc/man/cargo-run.1
+++ b/src/etc/man/cargo-run.1
@@ -72,26 +72,28 @@ Do not activate the \fBdefault\fR feature of the selected packages.
.sp
\fB\-\-target\fR \fItriple\fR
.RS 4
-Run for the specified target The default is the host architecture. The general format of the triple is
+Run for the specified target architecture. The default is the host architecture. The general format of the triple is
\fB\-\-\-\fR\&.
.sp
-You may specify the following kinds of targets:
+Possible values:
.sp
.RS 4
-\h'-04'\(bu\h'+03'Any supported target in \fBrustc \-\-print target\-list\fR (note: you have to install/add the target to use it).
+\h'-04'\(bu\h'+03'Any supported target in \fBrustc \-\-print target\-list\fR\&.
.RE
.sp
.RS 4
-\h'-04'\(bu\h'+03'\fBhost\fR, which will internally be substituted by the host\[cq]s target. This can be particularly useful if you\[cq]re cross\-compiling some crates, and don\[cq]t want to specify your host\[cq]s machine as a target (for instance, an \fBxtask\fR in a shared project that may be worked on by many hosts).
+\h'-04'\(bu\h'+03'\fB"host"\fR, which will internally be substituted by the host\[cq]s target. This can be particularly useful if you\[cq]re cross\-compiling some crates, and don\[cq]t want to specify your host\[cq]s machine as a target (for instance, an \fBxtask\fR in a shared project that may be worked on by many hosts).
.RE
.sp
.RS 4
-\h'-04'\(bu\h'+03'A path to a custom target specification (further reading \fIhere\fR ).
+\h'-04'\(bu\h'+03'A path to a custom target specification. See \fICustom Target Lookup Path\fR for more information.
.RE
.sp
This may also be specified with the \fBbuild.target\fR \fIconfig value\fR \&.
.sp
-\fBNote\fR: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the \fIbuild cache\fR documentation for more details.
+Note that specifying this flag makes Cargo run in a different mode where the
+target artifacts are placed in a separate directory. See the
+\fIbuild cache\fR documentation for more details.
.RE
.sp
\fB\-r\fR,
diff --git a/src/etc/man/cargo-rustc.1 b/src/etc/man/cargo-rustc.1
index 09fcc70b7..865e8db4c 100644
--- a/src/etc/man/cargo-rustc.1
+++ b/src/etc/man/cargo-rustc.1
@@ -152,26 +152,28 @@ Do not activate the \fBdefault\fR feature of the selected packages.
.sp
\fB\-\-target\fR \fItriple\fR
.RS 4
-Build for the specified target (may be specified multiple times) The default is the host architecture. The general format of the triple is
+Build for the specified target architecture. Flag may be specified multiple times. The default is the host architecture. The general format of the triple is
\fB\-\-\-\fR\&.
.sp
-You may specify the following kinds of targets:
+Possible values:
.sp
.RS 4
-\h'-04'\(bu\h'+03'Any supported target in \fBrustc \-\-print target\-list\fR (note: you have to install/add the target to use it).
+\h'-04'\(bu\h'+03'Any supported target in \fBrustc \-\-print target\-list\fR\&.
.RE
.sp
.RS 4
-\h'-04'\(bu\h'+03'\fBhost\fR, which will internally be substituted by the host\[cq]s target. This can be particularly useful if you\[cq]re cross\-compiling some crates, and don\[cq]t want to specify your host\[cq]s machine as a target (for instance, an \fBxtask\fR in a shared project that may be worked on by many hosts).
+\h'-04'\(bu\h'+03'\fB"host"\fR, which will internally be substituted by the host\[cq]s target. This can be particularly useful if you\[cq]re cross\-compiling some crates, and don\[cq]t want to specify your host\[cq]s machine as a target (for instance, an \fBxtask\fR in a shared project that may be worked on by many hosts).
.RE
.sp
.RS 4
-\h'-04'\(bu\h'+03'A path to a custom target specification (further reading \fIhere\fR ).
+\h'-04'\(bu\h'+03'A path to a custom target specification. See \fICustom Target Lookup Path\fR for more information.
.RE
.sp
This may also be specified with the \fBbuild.target\fR \fIconfig value\fR \&.
.sp
-\fBNote\fR: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the \fIbuild cache\fR documentation for more details.
+Note that specifying this flag makes Cargo run in a different mode where the
+target artifacts are placed in a separate directory. See the
+\fIbuild cache\fR documentation for more details.
.RE
.sp
\fB\-r\fR,
diff --git a/src/etc/man/cargo-rustdoc.1 b/src/etc/man/cargo-rustdoc.1
index ac5e4e7b4..77f9bc4bf 100644
--- a/src/etc/man/cargo-rustdoc.1
+++ b/src/etc/man/cargo-rustdoc.1
@@ -154,26 +154,28 @@ Do not activate the \fBdefault\fR feature of the selected packages.
.sp
\fB\-\-target\fR \fItriple\fR
.RS 4
-Document for the specified target (may be specified multiple times) The default is the host architecture. The general format of the triple is
+Document for the specified target architecture. Flag may be specified multiple times. The default is the host architecture. The general format of the triple is
\fB\-\-\-\fR\&.
.sp
-You may specify the following kinds of targets:
+Possible values:
.sp
.RS 4
-\h'-04'\(bu\h'+03'Any supported target in \fBrustc \-\-print target\-list\fR (note: you have to install/add the target to use it).
+\h'-04'\(bu\h'+03'Any supported target in \fBrustc \-\-print target\-list\fR\&.
.RE
.sp
.RS 4
-\h'-04'\(bu\h'+03'\fBhost\fR, which will internally be substituted by the host\[cq]s target. This can be particularly useful if you\[cq]re cross\-compiling some crates, and don\[cq]t want to specify your host\[cq]s machine as a target (for instance, an \fBxtask\fR in a shared project that may be worked on by many hosts).
+\h'-04'\(bu\h'+03'\fB"host"\fR, which will internally be substituted by the host\[cq]s target. This can be particularly useful if you\[cq]re cross\-compiling some crates, and don\[cq]t want to specify your host\[cq]s machine as a target (for instance, an \fBxtask\fR in a shared project that may be worked on by many hosts).
.RE
.sp
.RS 4
-\h'-04'\(bu\h'+03'A path to a custom target specification (further reading \fIhere\fR ).
+\h'-04'\(bu\h'+03'A path to a custom target specification. See \fICustom Target Lookup Path\fR for more information.
.RE
.sp
This may also be specified with the \fBbuild.target\fR \fIconfig value\fR \&.
.sp
-\fBNote\fR: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the \fIbuild cache\fR documentation for more details.
+Note that specifying this flag makes Cargo run in a different mode where the
+target artifacts are placed in a separate directory. See the
+\fIbuild cache\fR documentation for more details.
.RE
.sp
\fB\-r\fR,
diff --git a/src/etc/man/cargo-test.1 b/src/etc/man/cargo-test.1
index 2926b557f..2957f891b 100644
--- a/src/etc/man/cargo-test.1
+++ b/src/etc/man/cargo-test.1
@@ -287,26 +287,28 @@ Do not activate the \fBdefault\fR feature of the selected packages.
.sp
\fB\-\-target\fR \fItriple\fR
.RS 4
-Test for the specified target (may be specified multiple times) The default is the host architecture. The general format of the triple is
+Test for the specified target architecture. Flag may be specified multiple times. The default is the host architecture. The general format of the triple is
\fB\-\-\-\fR\&.
.sp
-You may specify the following kinds of targets:
+Possible values:
.sp
.RS 4
-\h'-04'\(bu\h'+03'Any supported target in \fBrustc \-\-print target\-list\fR (note: you have to install/add the target to use it).
+\h'-04'\(bu\h'+03'Any supported target in \fBrustc \-\-print target\-list\fR\&.
.RE
.sp
.RS 4
-\h'-04'\(bu\h'+03'\fBhost\fR, which will internally be substituted by the host\[cq]s target. This can be particularly useful if you\[cq]re cross\-compiling some crates, and don\[cq]t want to specify your host\[cq]s machine as a target (for instance, an \fBxtask\fR in a shared project that may be worked on by many hosts).
+\h'-04'\(bu\h'+03'\fB"host"\fR, which will internally be substituted by the host\[cq]s target. This can be particularly useful if you\[cq]re cross\-compiling some crates, and don\[cq]t want to specify your host\[cq]s machine as a target (for instance, an \fBxtask\fR in a shared project that may be worked on by many hosts).
.RE
.sp
.RS 4
-\h'-04'\(bu\h'+03'A path to a custom target specification (further reading \fIhere\fR ).
+\h'-04'\(bu\h'+03'A path to a custom target specification. See \fICustom Target Lookup Path\fR for more information.
.RE
.sp
This may also be specified with the \fBbuild.target\fR \fIconfig value\fR \&.
.sp
-\fBNote\fR: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the \fIbuild cache\fR documentation for more details.
+Note that specifying this flag makes Cargo run in a different mode where the
+target artifacts are placed in a separate directory. See the
+\fIbuild cache\fR documentation for more details.
.RE
.sp
\fB\-r\fR,
diff --git a/tests/testsuite/list_availables.rs b/tests/testsuite/list_availables.rs
index dc9ff9653..162eadc52 100644
--- a/tests/testsuite/list_availables.rs
+++ b/tests/testsuite/list_availables.rs
@@ -233,7 +233,7 @@ Possible packages/workspace members:
.with_target(str![[r#"
[ERROR] "--target" takes a target architecture as an argument.
-Run `[..]` to see possible targets, or specify `host` for the host architecture.
+Run `[..]` to see possible targets.
"#]])
.build(),
@@ -308,7 +308,7 @@ Possible packages/workspace members:
.with_target(str![[r#"
[ERROR] "--target" takes a target architecture as an argument.
-Run `[..]` to see possible targets, or specify `host` for the host architecture.
+Run `[..]` to see possible targets.
"#]])
.build(),
@@ -344,7 +344,7 @@ Possible packages/workspace members:
.with_target(str![[r#"
[ERROR] "--target" takes a target architecture as an argument.
-Run `[..]` to see possible targets, or specify `host` for the host architecture.
+Run `[..]` to see possible targets.
"#]])
.build(),
@@ -419,7 +419,7 @@ Possible packages/workspace members:
.with_target(str![[r#"
[ERROR] "--target" takes a target architecture as an argument.
-Run `[..]` to see possible targets, or specify `host` for the host architecture.
+Run `[..]` to see possible targets.
"#]])
.build(),
@@ -468,7 +468,7 @@ Possible packages/workspace members:
.with_target(str![[r#"
[ERROR] "--target" takes a target architecture as an argument.
-Run `[..]` to see possible targets, or specify `host` for the host architecture.
+Run `[..]` to see possible targets.
"#]])
.build(),
@@ -543,7 +543,7 @@ Possible packages/workspace members:
.with_target(str![[r#"
[ERROR] "--target" takes a target architecture as an argument.
-Run `[..]` to see possible targets, or specify `host` for the host architecture.
+Run `[..]` to see possible targets.
"#]])
.build(),
@@ -618,7 +618,7 @@ Possible packages/workspace members:
.with_target(str![[r#"
[ERROR] "--target" takes a target architecture as an argument.
-Run `[..]` to see possible targets, or specify `host` for the host architecture.
+Run `[..]` to see possible targets.
"#]])
.build(),
@@ -664,7 +664,7 @@ No binaries available.
.with_target(str![[r#"
[ERROR] "--target" takes a target architecture as an argument.
-Run `[..]` to see possible targets, or specify `host` for the host architecture.
+Run `[..]` to see possible targets.
"#]])
.build(),
@@ -739,7 +739,7 @@ Possible packages/workspace members:
.with_target(str![[r#"
[ERROR] "--target" takes a target architecture as an argument.
-Run `[..]` to see possible targets, or specify `host` for the host architecture.
+Run `[..]` to see possible targets.
"#]])
.build(),
@@ -814,7 +814,7 @@ Possible packages/workspace members:
.with_target(str![[r#"
[ERROR] "--target" takes a target architecture as an argument.
-Run `[..]` to see possible targets, or specify `host` for the host architecture.
+Run `[..]` to see possible targets.
"#]])
.build(),
@@ -856,7 +856,7 @@ Possible packages/workspace members:
.with_target(str![[r#"
[ERROR] "--target" takes a target architecture as an argument.
-Run `[..]` to see possible targets, or specify `host` for the host architecture.
+Run `[..]` to see possible targets.
"#]])
.build(),
@@ -880,7 +880,7 @@ Possible packages/workspace members:
.with_target(str![[r#"
[ERROR] "--target" takes a target architecture as an argument.
-Run `[..]` to see possible targets, or specify `host` for the host architecture.
+Run `[..]` to see possible targets.
"#]])
.build(),