mirror of
https://github.com/rust-lang/cargo.git
synced 2025-09-25 11:14:46 +00:00
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.
This commit is contained in:
zdivelbiss
parent
8f66af7194
commit
d5509ebacc
@ -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"))
|
||||
|
||||
@ -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 <arch><sub>-<vendor>-<sys>-<abi>.
|
||||
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:
|
||||
|
||||
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
|
||||
<https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path>).
|
||||
o A path to a custom target specification. See Custom Target Lookup
|
||||
Path
|
||||
<https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path>
|
||||
for more information.
|
||||
|
||||
This may also be specified with the build.target config value
|
||||
<https://doc.rust-lang.org/cargo/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
|
||||
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
|
||||
<https://doc.rust-lang.org/cargo/reference/build-cache.html>
|
||||
documentation for more details.
|
||||
|
||||
|
||||
@ -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 <arch><sub>-<vendor>-<sys>-<abi>.
|
||||
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:
|
||||
|
||||
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
|
||||
<https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path>).
|
||||
o A path to a custom target specification. See Custom Target Lookup
|
||||
Path
|
||||
<https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path>
|
||||
for more information.
|
||||
|
||||
This may also be specified with the build.target config value
|
||||
<https://doc.rust-lang.org/cargo/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
|
||||
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
|
||||
<https://doc.rust-lang.org/cargo/reference/build-cache.html>
|
||||
documentation for more details.
|
||||
|
||||
|
||||
@ -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 <arch><sub>-<vendor>-<sys>-<abi>.
|
||||
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:
|
||||
|
||||
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
|
||||
<https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path>).
|
||||
o A path to a custom target specification. See Custom Target Lookup
|
||||
Path
|
||||
<https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path>
|
||||
for more information.
|
||||
|
||||
This may also be specified with the build.target config value
|
||||
<https://doc.rust-lang.org/cargo/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
|
||||
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
|
||||
<https://doc.rust-lang.org/cargo/reference/build-cache.html>
|
||||
documentation for more details.
|
||||
|
||||
|
||||
@ -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 <arch><sub>-<vendor>-<sys>-<abi>.
|
||||
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:
|
||||
|
||||
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
|
||||
<https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path>).
|
||||
o A path to a custom target specification. See Custom Target Lookup
|
||||
Path
|
||||
<https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path>
|
||||
for more information.
|
||||
|
||||
This may also be specified with the build.target config value
|
||||
<https://doc.rust-lang.org/cargo/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
|
||||
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
|
||||
<https://doc.rust-lang.org/cargo/reference/build-cache.html>
|
||||
documentation for more details.
|
||||
|
||||
|
||||
@ -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 <arch><sub>-<vendor>-<sys>-<abi>.
|
||||
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:
|
||||
|
||||
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
|
||||
<https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path>).
|
||||
o A path to a custom target specification. See Custom Target Lookup
|
||||
Path
|
||||
<https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path>
|
||||
for more information.
|
||||
|
||||
This may also be specified with the build.target config value
|
||||
<https://doc.rust-lang.org/cargo/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
|
||||
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
|
||||
<https://doc.rust-lang.org/cargo/reference/build-cache.html>
|
||||
documentation for more details.
|
||||
|
||||
|
||||
@ -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
|
||||
<arch><sub>-<vendor>-<sys>-<abi>.
|
||||
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:
|
||||
|
||||
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
|
||||
<https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path>).
|
||||
o A path to a custom target specification. See Custom Target Lookup
|
||||
Path
|
||||
<https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path>
|
||||
for more information.
|
||||
|
||||
This may also be specified with the build.target config value
|
||||
<https://doc.rust-lang.org/cargo/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
|
||||
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
|
||||
<https://doc.rust-lang.org/cargo/reference/build-cache.html>
|
||||
documentation for more details.
|
||||
|
||||
|
||||
@ -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 <arch><sub>-<vendor>-<sys>-<abi>.
|
||||
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:
|
||||
|
||||
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
|
||||
<https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path>).
|
||||
o A path to a custom target specification. See Custom Target Lookup
|
||||
Path
|
||||
<https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path>
|
||||
for more information.
|
||||
|
||||
This may also be specified with the build.target config value
|
||||
<https://doc.rust-lang.org/cargo/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
|
||||
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
|
||||
<https://doc.rust-lang.org/cargo/reference/build-cache.html>
|
||||
documentation for more details.
|
||||
|
||||
|
||||
@ -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
|
||||
<arch><sub>-<vendor>-<sys>-<abi>.
|
||||
|
||||
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
|
||||
<https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path>).
|
||||
o A path to a custom target specification. See Custom Target Lookup
|
||||
Path
|
||||
<https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path>
|
||||
for more information.
|
||||
|
||||
This may also be specified with the build.target config value
|
||||
<https://doc.rust-lang.org/cargo/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
|
||||
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
|
||||
<https://doc.rust-lang.org/cargo/reference/build-cache.html>
|
||||
documentation for more details.
|
||||
|
||||
|
||||
@ -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 <arch><sub>-<vendor>-<sys>-<abi>.
|
||||
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:
|
||||
|
||||
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
|
||||
<https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path>).
|
||||
o A path to a custom target specification. See Custom Target Lookup
|
||||
Path
|
||||
<https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path>
|
||||
for more information.
|
||||
|
||||
This may also be specified with the build.target config value
|
||||
<https://doc.rust-lang.org/cargo/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
|
||||
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
|
||||
<https://doc.rust-lang.org/cargo/reference/build-cache.html>
|
||||
documentation for more details.
|
||||
|
||||
|
||||
@ -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 <arch><sub>-<vendor>-<sys>-<abi>.
|
||||
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:
|
||||
|
||||
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
|
||||
<https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path>).
|
||||
o A path to a custom target specification. See Custom Target Lookup
|
||||
Path
|
||||
<https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path>
|
||||
for more information.
|
||||
|
||||
This may also be specified with the build.target config value
|
||||
<https://doc.rust-lang.org/cargo/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
|
||||
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
|
||||
<https://doc.rust-lang.org/cargo/reference/build-cache.html>
|
||||
documentation for more details.
|
||||
|
||||
|
||||
@ -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
|
||||
<arch><sub>-<vendor>-<sys>-<abi>.
|
||||
|
||||
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
|
||||
<https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path>).
|
||||
o A path to a custom target specification. See Custom Target Lookup
|
||||
Path
|
||||
<https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path>
|
||||
for more information.
|
||||
|
||||
This may also be specified with the build.target config value
|
||||
<https://doc.rust-lang.org/cargo/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
|
||||
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
|
||||
<https://doc.rust-lang.org/cargo/reference/build-cache.html>
|
||||
documentation for more details.
|
||||
|
||||
|
||||
@ -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 <arch><sub>-<vendor>-<sys>-<abi>.
|
||||
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:
|
||||
|
||||
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
|
||||
<https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path>).
|
||||
o A path to a custom target specification. See Custom Target Lookup
|
||||
Path
|
||||
<https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path>
|
||||
for more information.
|
||||
|
||||
This may also be specified with the build.target config value
|
||||
<https://doc.rust-lang.org/cargo/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
|
||||
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
|
||||
<https://doc.rust-lang.org/cargo/reference/build-cache.html>
|
||||
documentation for more details.
|
||||
|
||||
|
||||
@ -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 <arch><sub>-<vendor>-<sys>-<abi>.
|
||||
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:
|
||||
|
||||
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
|
||||
<https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path>).
|
||||
o A path to a custom target specification. See Custom Target Lookup
|
||||
Path
|
||||
<https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path>
|
||||
for more information.
|
||||
|
||||
This may also be specified with the build.target config value
|
||||
<https://doc.rust-lang.org/cargo/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
|
||||
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
|
||||
<https://doc.rust-lang.org/cargo/reference/build-cache.html>
|
||||
documentation for more details.
|
||||
|
||||
|
||||
@ -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 <arch><sub>-<vendor>-<sys>-<abi>.
|
||||
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:
|
||||
|
||||
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
|
||||
<https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path>).
|
||||
o A path to a custom target specification. See Custom Target Lookup
|
||||
Path
|
||||
<https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path>
|
||||
for more information.
|
||||
|
||||
This may also be specified with the build.target config value
|
||||
<https://doc.rust-lang.org/cargo/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
|
||||
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
|
||||
<https://doc.rust-lang.org/cargo/reference/build-cache.html>
|
||||
documentation for more details.
|
||||
|
||||
|
||||
@ -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
|
||||
`<arch><sub>-<vendor>-<sys>-<abi>`.
|
||||
|
||||
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}}
|
||||
|
||||
@ -256,16 +256,18 @@ be specified multiple times, which enables all specified features.</dd>
|
||||
<dl>
|
||||
|
||||
<dt class="option-term" id="option-cargo-bench---target"><a class="option-anchor" href="#option-cargo-bench---target"></a><code>--target</code> <em>triple</em></dt>
|
||||
<dd class="option-desc">Benchmark for the specified target (may be specified multiple times) The default is the host architecture. The general format of the triple is
|
||||
<dd class="option-desc">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
|
||||
<code><arch><sub>-<vendor>-<sys>-<abi></code>.</p>
|
||||
<p>You may specify the following kinds of targets:</p>
|
||||
<p>Possible values:</p>
|
||||
<ul>
|
||||
<li>Any supported target in <code>rustc --print target-list</code> (note: you have to install/add the target to use it).</li>
|
||||
<li><code>host</code>, 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 <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
|
||||
<li>A path to a custom target specification (further reading <a href="https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path">here</a>).</li>
|
||||
<li>Any supported target in <code>rustc --print target-list</code>.</li>
|
||||
<li><code>"host"</code>, 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 <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
|
||||
<li>A path to a custom target specification. See <a href="../../rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
|
||||
</ul>
|
||||
<p>This may also be specified with the <code>build.target</code> <a href="../reference/config.html">config value</a>.</p>
|
||||
<p><strong>Note</strong>: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the <a href="../reference/build-cache.html">build cache</a> documentation for more details.</dd>
|
||||
<p>Note that specifying this flag makes Cargo run in a different mode where the
|
||||
target artifacts are placed in a separate directory. See the
|
||||
<a href="../reference/build-cache.html">build cache</a> documentation for more details.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-bench---profile"><a class="option-anchor" href="#option-cargo-bench---profile"></a><code>--profile</code> <em>name</em></dt>
|
||||
|
||||
@ -171,16 +171,18 @@ be specified multiple times, which enables all specified features.</dd>
|
||||
<dl>
|
||||
|
||||
<dt class="option-term" id="option-cargo-build---target"><a class="option-anchor" href="#option-cargo-build---target"></a><code>--target</code> <em>triple</em></dt>
|
||||
<dd class="option-desc">Build for the specified target (may be specified multiple times) The default is the host architecture. The general format of the triple is
|
||||
<dd class="option-desc">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
|
||||
<code><arch><sub>-<vendor>-<sys>-<abi></code>.</p>
|
||||
<p>You may specify the following kinds of targets:</p>
|
||||
<p>Possible values:</p>
|
||||
<ul>
|
||||
<li>Any supported target in <code>rustc --print target-list</code> (note: you have to install/add the target to use it).</li>
|
||||
<li><code>host</code>, 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 <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
|
||||
<li>A path to a custom target specification (further reading <a href="https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path">here</a>).</li>
|
||||
<li>Any supported target in <code>rustc --print target-list</code>.</li>
|
||||
<li><code>"host"</code>, 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 <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
|
||||
<li>A path to a custom target specification. See <a href="../../rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
|
||||
</ul>
|
||||
<p>This may also be specified with the <code>build.target</code> <a href="../reference/config.html">config value</a>.</p>
|
||||
<p><strong>Note</strong>: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the <a href="../reference/build-cache.html">build cache</a> documentation for more details.</dd>
|
||||
<p>Note that specifying this flag makes Cargo run in a different mode where the
|
||||
target artifacts are placed in a separate directory. See the
|
||||
<a href="../reference/build-cache.html">build cache</a> documentation for more details.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-build--r"><a class="option-anchor" href="#option-cargo-build--r"></a><code>-r</code></dt>
|
||||
|
||||
@ -167,16 +167,18 @@ be specified multiple times, which enables all specified features.</dd>
|
||||
<dl>
|
||||
|
||||
<dt class="option-term" id="option-cargo-check---target"><a class="option-anchor" href="#option-cargo-check---target"></a><code>--target</code> <em>triple</em></dt>
|
||||
<dd class="option-desc">Check for the specified target (may be specified multiple times) The default is the host architecture. The general format of the triple is
|
||||
<dd class="option-desc">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
|
||||
<code><arch><sub>-<vendor>-<sys>-<abi></code>.</p>
|
||||
<p>You may specify the following kinds of targets:</p>
|
||||
<p>Possible values:</p>
|
||||
<ul>
|
||||
<li>Any supported target in <code>rustc --print target-list</code> (note: you have to install/add the target to use it).</li>
|
||||
<li><code>host</code>, 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 <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
|
||||
<li>A path to a custom target specification (further reading <a href="https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path">here</a>).</li>
|
||||
<li>Any supported target in <code>rustc --print target-list</code>.</li>
|
||||
<li><code>"host"</code>, 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 <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
|
||||
<li>A path to a custom target specification. See <a href="../../rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
|
||||
</ul>
|
||||
<p>This may also be specified with the <code>build.target</code> <a href="../reference/config.html">config value</a>.</p>
|
||||
<p><strong>Note</strong>: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the <a href="../reference/build-cache.html">build cache</a> documentation for more details.</dd>
|
||||
<p>Note that specifying this flag makes Cargo run in a different mode where the
|
||||
target artifacts are placed in a separate directory. See the
|
||||
<a href="../reference/build-cache.html">build cache</a> documentation for more details.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-check--r"><a class="option-anchor" href="#option-cargo-check--r"></a><code>-r</code></dt>
|
||||
|
||||
@ -59,16 +59,18 @@ Defaults to <code>target</code> in the root of the workspace.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-clean---target"><a class="option-anchor" href="#option-cargo-clean---target"></a><code>--target</code> <em>triple</em></dt>
|
||||
<dd class="option-desc">Clean for the specified target (may be specified multiple times) The default is the host architecture. The general format of the triple is
|
||||
<dd class="option-desc">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
|
||||
<code><arch><sub>-<vendor>-<sys>-<abi></code>.</p>
|
||||
<p>You may specify the following kinds of targets:</p>
|
||||
<p>Possible values:</p>
|
||||
<ul>
|
||||
<li>Any supported target in <code>rustc --print target-list</code> (note: you have to install/add the target to use it).</li>
|
||||
<li><code>host</code>, 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 <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
|
||||
<li>A path to a custom target specification (further reading <a href="https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path">here</a>).</li>
|
||||
<li>Any supported target in <code>rustc --print target-list</code>.</li>
|
||||
<li><code>"host"</code>, 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 <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
|
||||
<li>A path to a custom target specification. See <a href="../../rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
|
||||
</ul>
|
||||
<p>This may also be specified with the <code>build.target</code> <a href="../reference/config.html">config value</a>.</p>
|
||||
<p><strong>Note</strong>: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the <a href="../reference/build-cache.html">build cache</a> documentation for more details.</dd>
|
||||
<p>Note that specifying this flag makes Cargo run in a different mode where the
|
||||
target artifacts are placed in a separate directory. See the
|
||||
<a href="../reference/build-cache.html">build cache</a> documentation for more details.</dd>
|
||||
|
||||
|
||||
</dl>
|
||||
|
||||
@ -146,16 +146,18 @@ be specified multiple times, which enables all specified features.</dd>
|
||||
<dl>
|
||||
|
||||
<dt class="option-term" id="option-cargo-doc---target"><a class="option-anchor" href="#option-cargo-doc---target"></a><code>--target</code> <em>triple</em></dt>
|
||||
<dd class="option-desc">Document for the specified target (may be specified multiple times) The default is the host architecture. The general format of the triple is
|
||||
<dd class="option-desc">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
|
||||
<code><arch><sub>-<vendor>-<sys>-<abi></code>.</p>
|
||||
<p>You may specify the following kinds of targets:</p>
|
||||
<p>Possible values:</p>
|
||||
<ul>
|
||||
<li>Any supported target in <code>rustc --print target-list</code> (note: you have to install/add the target to use it).</li>
|
||||
<li><code>host</code>, 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 <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
|
||||
<li>A path to a custom target specification (further reading <a href="https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path">here</a>).</li>
|
||||
<li>Any supported target in <code>rustc --print target-list</code>.</li>
|
||||
<li><code>"host"</code>, 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 <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
|
||||
<li>A path to a custom target specification. See <a href="../../rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
|
||||
</ul>
|
||||
<p>This may also be specified with the <code>build.target</code> <a href="../reference/config.html">config value</a>.</p>
|
||||
<p><strong>Note</strong>: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the <a href="../reference/build-cache.html">build cache</a> documentation for more details.</dd>
|
||||
<p>Note that specifying this flag makes Cargo run in a different mode where the
|
||||
target artifacts are placed in a separate directory. See the
|
||||
<a href="../reference/build-cache.html">build cache</a> documentation for more details.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-doc--r"><a class="option-anchor" href="#option-cargo-doc--r"></a><code>-r</code></dt>
|
||||
|
||||
@ -29,16 +29,18 @@ you plan to use Cargo without a network with the `--offline` flag.
|
||||
|
||||
<dl>
|
||||
<dt class="option-term" id="option-cargo-fetch---target"><a class="option-anchor" href="#option-cargo-fetch---target"></a><code>--target</code> <em>triple</em></dt>
|
||||
<dd class="option-desc">Fetch for the specified target (may be specified multiple times) The default is all architectures. The general format of the triple is
|
||||
<dd class="option-desc">Fetch for the specified target architecture. Flag may be specified multiple times. The default is all architectures. The general format of the triple is
|
||||
<code><arch><sub>-<vendor>-<sys>-<abi></code>.</p>
|
||||
<p>You may specify the following kinds of targets:</p>
|
||||
<p>Possible values:</p>
|
||||
<ul>
|
||||
<li>Any supported target in <code>rustc --print target-list</code> (note: you have to install/add the target to use it).</li>
|
||||
<li><code>host</code>, 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 <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
|
||||
<li>A path to a custom target specification (further reading <a href="https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path">here</a>).</li>
|
||||
<li>Any supported target in <code>rustc --print target-list</code>.</li>
|
||||
<li><code>"host"</code>, 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 <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
|
||||
<li>A path to a custom target specification. See <a href="../../rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
|
||||
</ul>
|
||||
<p>This may also be specified with the <code>build.target</code> <a href="../reference/config.html">config value</a>.</p>
|
||||
<p><strong>Note</strong>: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the <a href="../reference/build-cache.html">build cache</a> documentation for more details.</dd>
|
||||
<p>Note that specifying this flag makes Cargo run in a different mode where the
|
||||
target artifacts are placed in a separate directory. See the
|
||||
<a href="../reference/build-cache.html">build cache</a> documentation for more details.</dd>
|
||||
|
||||
</dl>
|
||||
|
||||
|
||||
@ -247,16 +247,18 @@ be specified multiple times, which enables all specified features.</dd>
|
||||
<dl>
|
||||
|
||||
<dt class="option-term" id="option-cargo-fix---target"><a class="option-anchor" href="#option-cargo-fix---target"></a><code>--target</code> <em>triple</em></dt>
|
||||
<dd class="option-desc">Fix for the specified target (may be specified multiple times) The default is the host architecture. The general format of the triple is
|
||||
<dd class="option-desc">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
|
||||
<code><arch><sub>-<vendor>-<sys>-<abi></code>.</p>
|
||||
<p>You may specify the following kinds of targets:</p>
|
||||
<p>Possible values:</p>
|
||||
<ul>
|
||||
<li>Any supported target in <code>rustc --print target-list</code> (note: you have to install/add the target to use it).</li>
|
||||
<li><code>host</code>, 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 <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
|
||||
<li>A path to a custom target specification (further reading <a href="https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path">here</a>).</li>
|
||||
<li>Any supported target in <code>rustc --print target-list</code>.</li>
|
||||
<li><code>"host"</code>, 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 <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
|
||||
<li>A path to a custom target specification. See <a href="../../rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
|
||||
</ul>
|
||||
<p>This may also be specified with the <code>build.target</code> <a href="../reference/config.html">config value</a>.</p>
|
||||
<p><strong>Note</strong>: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the <a href="../reference/build-cache.html">build cache</a> documentation for more details.</dd>
|
||||
<p>Note that specifying this flag makes Cargo run in a different mode where the
|
||||
target artifacts are placed in a separate directory. See the
|
||||
<a href="../reference/build-cache.html">build cache</a> documentation for more details.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-fix--r"><a class="option-anchor" href="#option-cargo-fix--r"></a><code>-r</code></dt>
|
||||
|
||||
@ -212,16 +212,18 @@ be specified multiple times, which enables all specified features.</dd>
|
||||
<dl>
|
||||
|
||||
<dt class="option-term" id="option-cargo-install---target"><a class="option-anchor" href="#option-cargo-install---target"></a><code>--target</code> <em>triple</em></dt>
|
||||
<dd class="option-desc">Install for the specified target The default is the host architecture. The general format of the triple is
|
||||
<dd class="option-desc">Install for the specified target architecture. The default is the host architecture. The general format of the triple is
|
||||
<code><arch><sub>-<vendor>-<sys>-<abi></code>.</p>
|
||||
<p>You may specify the following kinds of targets:</p>
|
||||
<p>Possible values:</p>
|
||||
<ul>
|
||||
<li>Any supported target in <code>rustc --print target-list</code> (note: you have to install/add the target to use it).</li>
|
||||
<li><code>host</code>, 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 <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
|
||||
<li>A path to a custom target specification (further reading <a href="https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path">here</a>).</li>
|
||||
<li>Any supported target in <code>rustc --print target-list</code>.</li>
|
||||
<li><code>"host"</code>, 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 <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
|
||||
<li>A path to a custom target specification. See <a href="../../rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
|
||||
</ul>
|
||||
<p>This may also be specified with the <code>build.target</code> <a href="../reference/config.html">config value</a>.</p>
|
||||
<p><strong>Note</strong>: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the <a href="../reference/build-cache.html">build cache</a> documentation for more details.</dd>
|
||||
<p>Note that specifying this flag makes Cargo run in a different mode where the
|
||||
target artifacts are placed in a separate directory. See the
|
||||
<a href="../reference/build-cache.html">build cache</a> documentation for more details.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-install---target-dir"><a class="option-anchor" href="#option-cargo-install---target-dir"></a><code>--target-dir</code> <em>directory</em></dt>
|
||||
|
||||
@ -202,16 +202,18 @@ single quotes or double quotes around each pattern.</dd>
|
||||
<dl>
|
||||
|
||||
<dt class="option-term" id="option-cargo-package---target"><a class="option-anchor" href="#option-cargo-package---target"></a><code>--target</code> <em>triple</em></dt>
|
||||
<dd class="option-desc">Package for the specified target (may be specified multiple times) The default is the host architecture. The general format of the triple is
|
||||
<dd class="option-desc">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
|
||||
<code><arch><sub>-<vendor>-<sys>-<abi></code>.</p>
|
||||
<p>You may specify the following kinds of targets:</p>
|
||||
<p>Possible values:</p>
|
||||
<ul>
|
||||
<li>Any supported target in <code>rustc --print target-list</code> (note: you have to install/add the target to use it).</li>
|
||||
<li><code>host</code>, 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 <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
|
||||
<li>A path to a custom target specification (further reading <a href="https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path">here</a>).</li>
|
||||
<li>Any supported target in <code>rustc --print target-list</code>.</li>
|
||||
<li><code>"host"</code>, 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 <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
|
||||
<li>A path to a custom target specification. See <a href="../../rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
|
||||
</ul>
|
||||
<p>This may also be specified with the <code>build.target</code> <a href="../reference/config.html">config value</a>.</p>
|
||||
<p><strong>Note</strong>: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the <a href="../reference/build-cache.html">build cache</a> documentation for more details.</dd>
|
||||
<p>Note that specifying this flag makes Cargo run in a different mode where the
|
||||
target artifacts are placed in a separate directory. See the
|
||||
<a href="../reference/build-cache.html">build cache</a> documentation for more details.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-package---target-dir"><a class="option-anchor" href="#option-cargo-package---target-dir"></a><code>--target-dir</code> <em>directory</em></dt>
|
||||
|
||||
@ -122,16 +122,18 @@ single quotes or double quotes around each pattern.</dd>
|
||||
<dl>
|
||||
|
||||
<dt class="option-term" id="option-cargo-publish---target"><a class="option-anchor" href="#option-cargo-publish---target"></a><code>--target</code> <em>triple</em></dt>
|
||||
<dd class="option-desc">Publish for the specified target (may be specified multiple times) The default is the host architecture. The general format of the triple is
|
||||
<dd class="option-desc">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
|
||||
<code><arch><sub>-<vendor>-<sys>-<abi></code>.</p>
|
||||
<p>You may specify the following kinds of targets:</p>
|
||||
<p>Possible values:</p>
|
||||
<ul>
|
||||
<li>Any supported target in <code>rustc --print target-list</code> (note: you have to install/add the target to use it).</li>
|
||||
<li><code>host</code>, 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 <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
|
||||
<li>A path to a custom target specification (further reading <a href="https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path">here</a>).</li>
|
||||
<li>Any supported target in <code>rustc --print target-list</code>.</li>
|
||||
<li><code>"host"</code>, 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 <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
|
||||
<li>A path to a custom target specification. See <a href="../../rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
|
||||
</ul>
|
||||
<p>This may also be specified with the <code>build.target</code> <a href="../reference/config.html">config value</a>.</p>
|
||||
<p><strong>Note</strong>: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the <a href="../reference/build-cache.html">build cache</a> documentation for more details.</dd>
|
||||
<p>Note that specifying this flag makes Cargo run in a different mode where the
|
||||
target artifacts are placed in a separate directory. See the
|
||||
<a href="../reference/build-cache.html">build cache</a> documentation for more details.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-publish---target-dir"><a class="option-anchor" href="#option-cargo-publish---target-dir"></a><code>--target-dir</code> <em>directory</em></dt>
|
||||
|
||||
@ -88,16 +88,18 @@ be specified multiple times, which enables all specified features.</dd>
|
||||
<dl>
|
||||
|
||||
<dt class="option-term" id="option-cargo-run---target"><a class="option-anchor" href="#option-cargo-run---target"></a><code>--target</code> <em>triple</em></dt>
|
||||
<dd class="option-desc">Run for the specified target The default is the host architecture. The general format of the triple is
|
||||
<dd class="option-desc">Run for the specified target architecture. The default is the host architecture. The general format of the triple is
|
||||
<code><arch><sub>-<vendor>-<sys>-<abi></code>.</p>
|
||||
<p>You may specify the following kinds of targets:</p>
|
||||
<p>Possible values:</p>
|
||||
<ul>
|
||||
<li>Any supported target in <code>rustc --print target-list</code> (note: you have to install/add the target to use it).</li>
|
||||
<li><code>host</code>, 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 <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
|
||||
<li>A path to a custom target specification (further reading <a href="https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path">here</a>).</li>
|
||||
<li>Any supported target in <code>rustc --print target-list</code>.</li>
|
||||
<li><code>"host"</code>, 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 <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
|
||||
<li>A path to a custom target specification. See <a href="../../rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
|
||||
</ul>
|
||||
<p>This may also be specified with the <code>build.target</code> <a href="../reference/config.html">config value</a>.</p>
|
||||
<p><strong>Note</strong>: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the <a href="../reference/build-cache.html">build cache</a> documentation for more details.</dd>
|
||||
<p>Note that specifying this flag makes Cargo run in a different mode where the
|
||||
target artifacts are placed in a separate directory. See the
|
||||
<a href="../reference/build-cache.html">build cache</a> documentation for more details.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-run--r"><a class="option-anchor" href="#option-cargo-run--r"></a><code>-r</code></dt>
|
||||
|
||||
@ -160,16 +160,18 @@ be specified multiple times, which enables all specified features.</dd>
|
||||
<dl>
|
||||
|
||||
<dt class="option-term" id="option-cargo-rustc---target"><a class="option-anchor" href="#option-cargo-rustc---target"></a><code>--target</code> <em>triple</em></dt>
|
||||
<dd class="option-desc">Build for the specified target (may be specified multiple times) The default is the host architecture. The general format of the triple is
|
||||
<dd class="option-desc">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
|
||||
<code><arch><sub>-<vendor>-<sys>-<abi></code>.</p>
|
||||
<p>You may specify the following kinds of targets:</p>
|
||||
<p>Possible values:</p>
|
||||
<ul>
|
||||
<li>Any supported target in <code>rustc --print target-list</code> (note: you have to install/add the target to use it).</li>
|
||||
<li><code>host</code>, 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 <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
|
||||
<li>A path to a custom target specification (further reading <a href="https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path">here</a>).</li>
|
||||
<li>Any supported target in <code>rustc --print target-list</code>.</li>
|
||||
<li><code>"host"</code>, 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 <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
|
||||
<li>A path to a custom target specification. See <a href="../../rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
|
||||
</ul>
|
||||
<p>This may also be specified with the <code>build.target</code> <a href="../reference/config.html">config value</a>.</p>
|
||||
<p><strong>Note</strong>: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the <a href="../reference/build-cache.html">build cache</a> documentation for more details.</dd>
|
||||
<p>Note that specifying this flag makes Cargo run in a different mode where the
|
||||
target artifacts are placed in a separate directory. See the
|
||||
<a href="../reference/build-cache.html">build cache</a> documentation for more details.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-rustc--r"><a class="option-anchor" href="#option-cargo-rustc--r"></a><code>-r</code></dt>
|
||||
|
||||
@ -166,16 +166,18 @@ be specified multiple times, which enables all specified features.</dd>
|
||||
<dl>
|
||||
|
||||
<dt class="option-term" id="option-cargo-rustdoc---target"><a class="option-anchor" href="#option-cargo-rustdoc---target"></a><code>--target</code> <em>triple</em></dt>
|
||||
<dd class="option-desc">Document for the specified target (may be specified multiple times) The default is the host architecture. The general format of the triple is
|
||||
<dd class="option-desc">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
|
||||
<code><arch><sub>-<vendor>-<sys>-<abi></code>.</p>
|
||||
<p>You may specify the following kinds of targets:</p>
|
||||
<p>Possible values:</p>
|
||||
<ul>
|
||||
<li>Any supported target in <code>rustc --print target-list</code> (note: you have to install/add the target to use it).</li>
|
||||
<li><code>host</code>, 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 <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
|
||||
<li>A path to a custom target specification (further reading <a href="https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path">here</a>).</li>
|
||||
<li>Any supported target in <code>rustc --print target-list</code>.</li>
|
||||
<li><code>"host"</code>, 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 <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
|
||||
<li>A path to a custom target specification. See <a href="../../rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
|
||||
</ul>
|
||||
<p>This may also be specified with the <code>build.target</code> <a href="../reference/config.html">config value</a>.</p>
|
||||
<p><strong>Note</strong>: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the <a href="../reference/build-cache.html">build cache</a> documentation for more details.</dd>
|
||||
<p>Note that specifying this flag makes Cargo run in a different mode where the
|
||||
target artifacts are placed in a separate directory. See the
|
||||
<a href="../reference/build-cache.html">build cache</a> documentation for more details.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-rustdoc--r"><a class="option-anchor" href="#option-cargo-rustdoc--r"></a><code>-r</code></dt>
|
||||
|
||||
@ -278,16 +278,18 @@ be specified multiple times, which enables all specified features.</dd>
|
||||
<dl>
|
||||
|
||||
<dt class="option-term" id="option-cargo-test---target"><a class="option-anchor" href="#option-cargo-test---target"></a><code>--target</code> <em>triple</em></dt>
|
||||
<dd class="option-desc">Test for the specified target (may be specified multiple times) The default is the host architecture. The general format of the triple is
|
||||
<dd class="option-desc">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
|
||||
<code><arch><sub>-<vendor>-<sys>-<abi></code>.</p>
|
||||
<p>You may specify the following kinds of targets:</p>
|
||||
<p>Possible values:</p>
|
||||
<ul>
|
||||
<li>Any supported target in <code>rustc --print target-list</code> (note: you have to install/add the target to use it).</li>
|
||||
<li><code>host</code>, 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 <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
|
||||
<li>A path to a custom target specification (further reading <a href="https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path">here</a>).</li>
|
||||
<li>Any supported target in <code>rustc --print target-list</code>.</li>
|
||||
<li><code>"host"</code>, 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 <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
|
||||
<li>A path to a custom target specification. See <a href="../../rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
|
||||
</ul>
|
||||
<p>This may also be specified with the <code>build.target</code> <a href="../reference/config.html">config value</a>.</p>
|
||||
<p><strong>Note</strong>: Specifying this flag makes Cargo run in a different mode where the target artifacts are placed in a separate directory. See the <a href="../reference/build-cache.html">build cache</a> documentation for more details.</dd>
|
||||
<p>Note that specifying this flag makes Cargo run in a different mode where the
|
||||
target artifacts are placed in a separate directory. See the
|
||||
<a href="../reference/build-cache.html">build cache</a> documentation for more details.</dd>
|
||||
|
||||
|
||||
<dt class="option-term" id="option-cargo-test--r"><a class="option-anchor" href="#option-cargo-test--r"></a><code>-r</code></dt>
|
||||
|
||||
@ -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`
|
||||
|
||||
@ -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<arch><sub>\-<vendor>\-<sys>\-<abi>\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 <https://doc.rust\-lang.org/rustc/targets/custom.html#custom\-target\-lookup\-path>).
|
||||
\h'-04'\(bu\h'+03'A path to a custom target specification. See \fICustom Target Lookup Path\fR <https://doc.rust\-lang.org/rustc/targets/custom.html#custom\-target\-lookup\-path> for more information.
|
||||
.RE
|
||||
.sp
|
||||
This may also be specified with the \fBbuild.target\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.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 <https://doc.rust\-lang.org/cargo/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
|
||||
\fIbuild cache\fR <https://doc.rust\-lang.org/cargo/reference/build\-cache.html> documentation for more details.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-profile\fR \fIname\fR
|
||||
|
||||
@ -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<arch><sub>\-<vendor>\-<sys>\-<abi>\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 <https://doc.rust\-lang.org/rustc/targets/custom.html#custom\-target\-lookup\-path>).
|
||||
\h'-04'\(bu\h'+03'A path to a custom target specification. See \fICustom Target Lookup Path\fR <https://doc.rust\-lang.org/rustc/targets/custom.html#custom\-target\-lookup\-path> for more information.
|
||||
.RE
|
||||
.sp
|
||||
This may also be specified with the \fBbuild.target\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.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 <https://doc.rust\-lang.org/cargo/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
|
||||
\fIbuild cache\fR <https://doc.rust\-lang.org/cargo/reference/build\-cache.html> documentation for more details.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-r\fR,
|
||||
|
||||
@ -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<arch><sub>\-<vendor>\-<sys>\-<abi>\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 <https://doc.rust\-lang.org/rustc/targets/custom.html#custom\-target\-lookup\-path>).
|
||||
\h'-04'\(bu\h'+03'A path to a custom target specification. See \fICustom Target Lookup Path\fR <https://doc.rust\-lang.org/rustc/targets/custom.html#custom\-target\-lookup\-path> for more information.
|
||||
.RE
|
||||
.sp
|
||||
This may also be specified with the \fBbuild.target\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.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 <https://doc.rust\-lang.org/cargo/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
|
||||
\fIbuild cache\fR <https://doc.rust\-lang.org/cargo/reference/build\-cache.html> documentation for more details.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-r\fR,
|
||||
|
||||
@ -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<arch><sub>\-<vendor>\-<sys>\-<abi>\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 <https://doc.rust\-lang.org/rustc/targets/custom.html#custom\-target\-lookup\-path>).
|
||||
\h'-04'\(bu\h'+03'A path to a custom target specification. See \fICustom Target Lookup Path\fR <https://doc.rust\-lang.org/rustc/targets/custom.html#custom\-target\-lookup\-path> for more information.
|
||||
.RE
|
||||
.sp
|
||||
This may also be specified with the \fBbuild.target\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.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 <https://doc.rust\-lang.org/cargo/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
|
||||
\fIbuild cache\fR <https://doc.rust\-lang.org/cargo/reference/build\-cache.html> documentation for more details.
|
||||
.RE
|
||||
.SS "Display Options"
|
||||
.sp
|
||||
|
||||
@ -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<arch><sub>\-<vendor>\-<sys>\-<abi>\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 <https://doc.rust\-lang.org/rustc/targets/custom.html#custom\-target\-lookup\-path>).
|
||||
\h'-04'\(bu\h'+03'A path to a custom target specification. See \fICustom Target Lookup Path\fR <https://doc.rust\-lang.org/rustc/targets/custom.html#custom\-target\-lookup\-path> for more information.
|
||||
.RE
|
||||
.sp
|
||||
This may also be specified with the \fBbuild.target\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.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 <https://doc.rust\-lang.org/cargo/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
|
||||
\fIbuild cache\fR <https://doc.rust\-lang.org/cargo/reference/build\-cache.html> documentation for more details.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-r\fR,
|
||||
|
||||
@ -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<arch><sub>\-<vendor>\-<sys>\-<abi>\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 <https://doc.rust\-lang.org/rustc/targets/custom.html#custom\-target\-lookup\-path>).
|
||||
\h'-04'\(bu\h'+03'A path to a custom target specification. See \fICustom Target Lookup Path\fR <https://doc.rust\-lang.org/rustc/targets/custom.html#custom\-target\-lookup\-path> for more information.
|
||||
.RE
|
||||
.sp
|
||||
This may also be specified with the \fBbuild.target\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.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 <https://doc.rust\-lang.org/cargo/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
|
||||
\fIbuild cache\fR <https://doc.rust\-lang.org/cargo/reference/build\-cache.html> documentation for more details.
|
||||
.RE
|
||||
.SS "Display Options"
|
||||
.sp
|
||||
|
||||
@ -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<arch><sub>\-<vendor>\-<sys>\-<abi>\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 <https://doc.rust\-lang.org/rustc/targets/custom.html#custom\-target\-lookup\-path>).
|
||||
\h'-04'\(bu\h'+03'A path to a custom target specification. See \fICustom Target Lookup Path\fR <https://doc.rust\-lang.org/rustc/targets/custom.html#custom\-target\-lookup\-path> for more information.
|
||||
.RE
|
||||
.sp
|
||||
This may also be specified with the \fBbuild.target\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.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 <https://doc.rust\-lang.org/cargo/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
|
||||
\fIbuild cache\fR <https://doc.rust\-lang.org/cargo/reference/build\-cache.html> documentation for more details.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-r\fR,
|
||||
|
||||
@ -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<arch><sub>\-<vendor>\-<sys>\-<abi>\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 <https://doc.rust\-lang.org/rustc/targets/custom.html#custom\-target\-lookup\-path>).
|
||||
\h'-04'\(bu\h'+03'A path to a custom target specification. See \fICustom Target Lookup Path\fR <https://doc.rust\-lang.org/rustc/targets/custom.html#custom\-target\-lookup\-path> for more information.
|
||||
.RE
|
||||
.sp
|
||||
This may also be specified with the \fBbuild.target\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.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 <https://doc.rust\-lang.org/cargo/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
|
||||
\fIbuild cache\fR <https://doc.rust\-lang.org/cargo/reference/build\-cache.html> documentation for more details.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-target\-dir\fR \fIdirectory\fR
|
||||
|
||||
@ -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<arch><sub>\-<vendor>\-<sys>\-<abi>\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 <https://doc.rust\-lang.org/rustc/targets/custom.html#custom\-target\-lookup\-path>).
|
||||
\h'-04'\(bu\h'+03'A path to a custom target specification. See \fICustom Target Lookup Path\fR <https://doc.rust\-lang.org/rustc/targets/custom.html#custom\-target\-lookup\-path> for more information.
|
||||
.RE
|
||||
.sp
|
||||
This may also be specified with the \fBbuild.target\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.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 <https://doc.rust\-lang.org/cargo/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
|
||||
\fIbuild cache\fR <https://doc.rust\-lang.org/cargo/reference/build\-cache.html> documentation for more details.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-target\-dir\fR \fIdirectory\fR
|
||||
|
||||
@ -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<arch><sub>\-<vendor>\-<sys>\-<abi>\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 <https://doc.rust\-lang.org/rustc/targets/custom.html#custom\-target\-lookup\-path>).
|
||||
\h'-04'\(bu\h'+03'A path to a custom target specification. See \fICustom Target Lookup Path\fR <https://doc.rust\-lang.org/rustc/targets/custom.html#custom\-target\-lookup\-path> for more information.
|
||||
.RE
|
||||
.sp
|
||||
This may also be specified with the \fBbuild.target\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.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 <https://doc.rust\-lang.org/cargo/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
|
||||
\fIbuild cache\fR <https://doc.rust\-lang.org/cargo/reference/build\-cache.html> documentation for more details.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-\-target\-dir\fR \fIdirectory\fR
|
||||
|
||||
@ -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<arch><sub>\-<vendor>\-<sys>\-<abi>\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 <https://doc.rust\-lang.org/rustc/targets/custom.html#custom\-target\-lookup\-path>).
|
||||
\h'-04'\(bu\h'+03'A path to a custom target specification. See \fICustom Target Lookup Path\fR <https://doc.rust\-lang.org/rustc/targets/custom.html#custom\-target\-lookup\-path> for more information.
|
||||
.RE
|
||||
.sp
|
||||
This may also be specified with the \fBbuild.target\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.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 <https://doc.rust\-lang.org/cargo/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
|
||||
\fIbuild cache\fR <https://doc.rust\-lang.org/cargo/reference/build\-cache.html> documentation for more details.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-r\fR,
|
||||
|
||||
@ -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<arch><sub>\-<vendor>\-<sys>\-<abi>\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 <https://doc.rust\-lang.org/rustc/targets/custom.html#custom\-target\-lookup\-path>).
|
||||
\h'-04'\(bu\h'+03'A path to a custom target specification. See \fICustom Target Lookup Path\fR <https://doc.rust\-lang.org/rustc/targets/custom.html#custom\-target\-lookup\-path> for more information.
|
||||
.RE
|
||||
.sp
|
||||
This may also be specified with the \fBbuild.target\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.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 <https://doc.rust\-lang.org/cargo/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
|
||||
\fIbuild cache\fR <https://doc.rust\-lang.org/cargo/reference/build\-cache.html> documentation for more details.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-r\fR,
|
||||
|
||||
@ -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<arch><sub>\-<vendor>\-<sys>\-<abi>\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 <https://doc.rust\-lang.org/rustc/targets/custom.html#custom\-target\-lookup\-path>).
|
||||
\h'-04'\(bu\h'+03'A path to a custom target specification. See \fICustom Target Lookup Path\fR <https://doc.rust\-lang.org/rustc/targets/custom.html#custom\-target\-lookup\-path> for more information.
|
||||
.RE
|
||||
.sp
|
||||
This may also be specified with the \fBbuild.target\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.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 <https://doc.rust\-lang.org/cargo/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
|
||||
\fIbuild cache\fR <https://doc.rust\-lang.org/cargo/reference/build\-cache.html> documentation for more details.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-r\fR,
|
||||
|
||||
@ -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<arch><sub>\-<vendor>\-<sys>\-<abi>\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 <https://doc.rust\-lang.org/rustc/targets/custom.html#custom\-target\-lookup\-path>).
|
||||
\h'-04'\(bu\h'+03'A path to a custom target specification. See \fICustom Target Lookup Path\fR <https://doc.rust\-lang.org/rustc/targets/custom.html#custom\-target\-lookup\-path> for more information.
|
||||
.RE
|
||||
.sp
|
||||
This may also be specified with the \fBbuild.target\fR \fIconfig value\fR <https://doc.rust\-lang.org/cargo/reference/config.html>\&.
|
||||
.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 <https://doc.rust\-lang.org/cargo/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
|
||||
\fIbuild cache\fR <https://doc.rust\-lang.org/cargo/reference/build\-cache.html> documentation for more details.
|
||||
.RE
|
||||
.sp
|
||||
\fB\-r\fR,
|
||||
|
||||
@ -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(),
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user