Skip to content

CARGO_TARGET_DIR doesn't have to be relative #16735

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
epage merged 1 commit into from
Mar 11, 2026
+5 −5
Merged

CARGO_TARGET_DIR doesn't have to be relative #16735

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/doc/man/cargo-install.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ force Cargo to always reinstall the package.

If the source is crates.io or `--git` then by default the crate will be built
in a temporary target directory. To avoid this, the target directory can be
specified by setting the `CARGO_TARGET_DIR` environment variable to a relative
specified by setting the `CARGO_TARGET_DIR` environment variable to a
path. In particular, this can be useful for caching build artifacts on
continuous integration systems.

Expand Down
4 changes: 2 additions & 2 deletions src/doc/man/generated_txt/cargo-install.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,8 +64,8 @@ DESCRIPTION
If the source is crates.io or --git then by default the crate will be
built in a temporary target directory. To avoid this, the target
directory can be specified by setting the CARGO_TARGET_DIR environment
variable to a relative path. In particular, this can be useful for
caching build artifacts on continuous integration systems.
variable to a path. In particular, this can be useful for caching build
artifacts on continuous integration systems.

Dealing with the Lockfile
By default, the Cargo.lock file that is included with the package will
Expand Down
2 changes: 1 addition & 1 deletion src/doc/src/commands/cargo-install.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ force Cargo to always reinstall the package.

If the source is crates.io or `--git` then by default the crate will be built
in a temporary target directory. To avoid this, the target directory can be
specified by setting the `CARGO_TARGET_DIR` environment variable to a relative
specified by setting the `CARGO_TARGET_DIR` environment variable to a
path. In particular, this can be useful for caching build artifacts on
continuous integration systems.

Expand Down
2 changes: 1 addition & 1 deletion src/etc/man/cargo-install.1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -84,7 +84,7 @@ force Cargo to always reinstall the package.
.sp
If the source is crates.io or \fB\-\-git\fR then by default the crate will be built
in a temporary target directory. To avoid this, the target directory can be
specified by setting the \fBCARGO_TARGET_DIR\fR environment variable to a relative
specified by setting the \fBCARGO_TARGET_DIR\fR environment variable to a
Comment thread
nabijaczleweli marked this conversation as resolved.
path. In particular, this can be useful for caching build artifacts on
continuous integration systems.
.SS "Dealing with the Lockfile"
Expand Down