cargo build --show-out

[stepancheg]

Problem

I'm building a test to debug it with debugger, or copy it to another machine if it is build for another architecture.

Where is the binary?

cargo build --tests --verbose

does not print the path. There is a lot of paths with hashes in targets directory, finding the binary with the latest built test is not easy.

Proposed Solution

Either:

• print binary paths by default (to stderr, so paths are not machine readable, so this is not API change), or
• add an option cargo build --show-out

Notes

Related to #12140

cargo 1.68.0-nightly (d992ab4e9 2023-01-10)

[bjorn3]

--message-format json prints out artifact messages, which I believe would be enough to get the info you need.

[weihanglo]

With --no-run, Cargo also emits the executable paths for human. For instance,

$ cargo test --no-run
    Finished test [unoptimized + debuginfo] target(s) in 0.46s
  Executable unittests src/cargo/lib.rs (target/debug/deps/cargo-f8c8ae4254239e92)
  Executable tests/build-std/main.rs (target/debug/deps/build_std-de679ea102561ead)
  Executable tests/internal.rs (target/debug/deps/internal-5b3c0fb3a9e0c0d1)
  Executable tests/testsuite/main.rs (target/debug/deps/testsuite-afcbe389bffe84ae)

Does it meet your needs?

[stepancheg]

It does. TIL, thanks!