In rust-num/num-complex#83, they reported problems detecting features under cargo no-std-check, which I found to be using RUSTC_WRAPPER to rewrite arguments for a fake target. This seems like something that autocfg could reasonably support. When present and non-empty, we would just wrap commands as $RUSTC_WRAPPER $RUSTC <args...>.
An alternate environment name is CARGO_BUILD_RUSTC_WRAPPER, or it can be set in .cargo/config -- but we don't have any support to find or parse config files yet.
In rust-num/num-complex#83, they reported problems detecting features under
cargo no-std-check, which I found to be usingRUSTC_WRAPPERto rewrite arguments for a fake target. This seems like something thatautocfgcould reasonably support. When present and non-empty, we would just wrap commands as$RUSTC_WRAPPER $RUSTC <args...>.An alternate environment name is
CARGO_BUILD_RUSTC_WRAPPER, or it can be set in.cargo/config-- but we don't have any support to find or parse config files yet.