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
I have a rather large project and I need to sometimes change RUSTC_BOOTSTRAP for some reasons. This causes proc_macro2 to recompile, which in turn recompile a large portion of our dependency tree. I personally find it quite surprising that this happens as this behavior is not documented anywhere.
I think the only way to solve this would be for Cargo to expose a way that crates can ask for a particular environment variable to be hashed into the crate's metadata. Similar to what was done in rust-lang/cargo#14830 for RUSTFLAGS. Either dynamically from a build script (cargo:rerun-if-env-changed-hashed=…) or statically from a manifest entry.
For rustc 1.85+ (current beta), one workaround is to use different RUSTFLAGS between your RUSTC_BOOTSTRAP builds and non-RUSTC_BOOTSTRAP builds.
I have a rather large project and I need to sometimes change
RUSTC_BOOTSTRAP
for some reasons. This causesproc_macro2
to recompile, which in turn recompile a large portion of our dependency tree. I personally find it quite surprising that this happens as this behavior is not documented anywhere.Cargo verbose log:
Offending source code:
proc-macro2/build.rs
Line 131 in aa9476b
The text was updated successfully, but these errors were encountered: