Skip to content

Conversation

@MarijnS95
Copy link
Member

Environment variables can be set and optionally override the process environment through .cargo/config.toml's [env] section: https://doc.rust-lang.org/cargo/reference/config.html#env

These config variables have specific precedence rules with regards to overriding the environment set in the process, and can optionally represent paths relative to the parent of the containing .cargo/ folder.

Besides exposing variables to all other processes called by xbuild, this also allows xbuild itself to be driven by variables set in .cargo/config.toml, such as $ANDROID_HOME needed for #116.

rust-mobile/cargo-subcommand#12
rust-mobile/cargo-subcommand#16

…nment

Environment variables can be set and optionally override the process
environment through `.cargo/config.toml`'s `[env]` section:
https://doc.rust-lang.org/cargo/reference/config.html#env

These config variables have specific precedence rules with regards to
overriding the environment set in the process, and can optionally
represent paths relative to the parent of the containing `.cargo/`
folder.

Besides exposing variables to all other processes called by `xbuild`,
this also allows `xbuild` itself to be driven by variables set in
`.cargo/config.toml`, such as `$ANDROID_HOME` needed for #116.

rust-mobile/cargo-subcommand#12
rust-mobile/cargo-subcommand#16
Cargo doesn't do this either, and canonicalization requires the path to
exist which it does not have to.
@MarijnS95 MarijnS95 merged commit 203d111 into master Aug 22, 2023
@MarijnS95 MarijnS95 deleted the env branch August 22, 2023 22:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants