cargo-rustc --- Compile the current package, and pass extra options to the compiler
cargo rustc
[options] [--
args]
The specified target for the current package (or package specified by -p
if provided) will be compiled along with all of its dependencies. The specified args will all be passed to the final compiler invocation, not any of the dependencies. Note that the compiler will still unconditionally receive arguments such as -L
, --extern
, and --crate-type
, and the specified args will simply be added to the compiler invocation.
See https://doc.rust-lang.org/rustc/index.html for documentation on rustc flags.
This command requires that only one target is being compiled when additional arguments are provided. If more than one target is available for the current package the filters of --lib
, --bin
, etc, must be used to select which target is compiled.
To pass flags to all compiler processes spawned by Cargo, use the RUSTFLAGS
environment variable or the build.rustflags
config value.
By default, the package in the current working directory is selected. The -p
flag can be used to choose a different package in a workspace.
When no target selection options are given, cargo rustc
will build all binary and library targets of the selected package.
Binary targets are automatically built if there is an integration test or benchmark being selected to build. This allows an integration test to execute the binary to exercise and test its behavior. The CARGO_BIN_EXE_<name>
environment variable is set when the integration test is built so that it can use the env
macro to locate the executable.
Passing target selection flags will build only the specified targets.
Note that --bin
, --example
, --test
and --bench
flags also support common Unix glob patterns like *
, ?
and []
. However, to avoid your shell accidentally expanding glob patterns before Cargo handles them, you must use single quotes or double quotes around each glob pattern.
The feature flags allow you to control which features are enabled. When no feature options are given, the default
feature is activated for every selected package.
See the features documentation for more details.
See the reference for details on environment variables that Cargo reads.
0
: Cargo succeeded.101
: Cargo failed to complete.Check if your package (not including dependencies) uses unsafe code:
cargo rustc --lib -- -D unsafe-code
Try an experimental flag on the nightly compiler, such as this which prints the size of every type:
cargo rustc --lib -- -Z print-type-sizes
Override crate-type
field in Cargo.toml with command-line option:
cargo rustc --lib --crate-type lib,cdylib