You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For Linux, there is currently an overcomplicated mechanism involving moving container-specific cache directories to and from the global cache dir into static paths that have previously been set in PATH and CARGO_HOME/RUSTUP_HOME. I did it this way because I thought I'd only have access to the name of the current architecture inside the before_all, before_build and test/repair commands.
But actually, CIBW_ENVIRONMENT is evaluated inside each container, so I already have access to the name of the architecture there, e.g. via $(uname -m). Hence, this can be simplified to not move anything around and just set architecture-containing paths from the get go.
The text was updated successfully, but these errors were encountered:
smheidrich
changed the title
Rust toolchain caching in CI could be simplified
Rust toolchain caching in CI could use dynamic CIBW_ENVIRONMENT to set paths
Oct 31, 2022
smheidrich
changed the title
Rust toolchain caching in CI could use dynamic CIBW_ENVIRONMENT to set paths
Rust toolchain caching in CI could use dynamic CIBW_ENVIRONMENT definitions to set paths
Oct 31, 2022
For Linux, there is currently an overcomplicated mechanism involving moving container-specific cache directories to and from the global cache dir into static paths that have previously been set in
PATH
andCARGO_HOME
/RUSTUP_HOME
. I did it this way because I thought I'd only have access to the name of the current architecture inside thebefore_all
,before_build
and test/repair commands.But actually,
CIBW_ENVIRONMENT
is evaluated inside each container, so I already have access to the name of the architecture there, e.g. via$(uname -m)
. Hence, this can be simplified to not move anything around and just set architecture-containing paths from the get go.Cf. pypa/cibuildwheel#1329 (comment)
The text was updated successfully, but these errors were encountered: