Brendan Cully c4664609ed Use package root as cargo check working directory ... Cargo commands are affected by the `.cargo/config` files above their working directory. If cargo is invoked from above the directory holding `Cargo.toml`, it may not pick up important settings like registry replacements, causing it to behave differently or even fail. Most cargo invocations are currently setting their working directories to the directory containing `Cargo.toml`, but a couple of paths remain in which cargo is invoked from the default workspace root instead. This change fixes that, resolving some cargo check failures that I experienced in a multi-root workspace in which packages used different registries.		2021-05-12 19:50:52 -07:00
..
build_data.rs	Use package root as cargo check working directory	2021-05-12 19:50:52 -07:00
cargo_workspace.rs	Fix build script dependencies	2021-05-12 14:48:26 +02:00
cfg_flag.rs	internal: use API stabilized in 1.52	2021-05-06 20:12:15 +03:00
lib.rs	Allow automatically detect the rustc-src directory (fixes #3517).	2021-02-13 18:20:46 +01:00
project_json.rs	More maintainable config	2021-01-06 15:39:28 +03:00
rustc_cfg.rs	Use RUSTC_BOOTSTRAP=1 instead of +nightly when discovering rust_cfgs throughs cargo	2021-05-09 00:07:04 +02:00
sysroot.rs	Allow automatically detect the rustc-src directory (fixes #3517).	2021-02-13 18:20:46 +01:00
workspace.rs	Fix build script dependencies	2021-05-12 14:48:26 +02:00