Unnamed repository; edit this file 'description' to name the repository.
Small fixups
- use `path` instead of `paths` - don't mark rust-analyzer as an optional tool - print the cargo command that's run in the proc-macro-test build script this originally was part of a change to fix `test --stage 0 rust-analyzer`, but I'm going to leave that for a separate PR so it's easier to review.
Joshua Nelson 2022-07-24
parent b351e11 · commit 20eb2dd
-rw-r--r--crates/proc-macro-test/build.rs10
1 files changed, 6 insertions, 4 deletions
diff --git a/crates/proc-macro-test/build.rs b/crates/proc-macro-test/build.rs
index cd99eea5ae..c90144509d 100644
--- a/crates/proc-macro-test/build.rs
+++ b/crates/proc-macro-test/build.rs
@@ -62,7 +62,7 @@ fn main() {
Command::new(toolchain::cargo())
};
- let output = cmd
+ cmd
.current_dir(&staging_dir)
.args(&["build", "-p", "proc-macro-test-impl", "--message-format", "json"])
// Explicit override the target directory to avoid using the same one which the parent
@@ -70,9 +70,11 @@ fn main() {
// This can happen when `CARGO_TARGET_DIR` is set or global config forces all cargo
// instance to use the same target directory.
.arg("--target-dir")
- .arg(&target_dir)
- .output()
- .unwrap();
+ .arg(&target_dir);
+
+ println!("Running {:?}", cmd);
+
+ let output = cmd.output().unwrap();
if !output.status.success() {
println!("proc-macro-test-impl failed to build");
println!("============ stdout ============");