Using --target-dir makes Cross look for libraries on host

[ClementNerma]

Checklist

• [X] I've looked through the issues and pull requests for similar reports

Describe your issue

If I run cross build, it pulls the missing Rust toolchain and runs the build step in Docker. If I run cross build --target-dir /some/path, it doesn't and complains about a library missing on my host (which is a dependency of my project).

I don't know why this happens, but it seems like providing --target-dir makes Cargo perform some tasks on the host instead of going directly in the container.

What target(s) are you cross-compiling for?

aarch64-unknown-linux-musl

Which operating system is the host (e.g computer cross is on) running?

• [ ] macOS
• [ ] Windows
• [X] Linux / BSD
• [ ] other OS (specify in description)

What architecture is the host?

• [X] x86_64 / AMD64
• [ ] arm32
• [ ] arm64 (including Mac M1)

What container engine is cross using?

• [X] docker
• [ ] podman
• [ ] other container engine (specify in description)

cross version

0.2.5

Example

No response

Additional information / notes

No response

[Emilgardis]

can you please post the logs when cross is also provided with -v

[Emilgardis]

we might be resolving the paths wrong when using --target-dir, but we shouldn't as all that data comes from cargo metadata