Closed jasonsewall closed 1 year ago
This might just be a symptom of cargo
itself exhibiting this behavior, upon further experimentation.
Yes, this is how cargo works, you'll get the same behaviour when using cargo build --target target --target-dir target-dir
Checklist
Describe your issue
cargo build --target-dir=<dir>
will use<dir>
instead of any target-specific prefix. So:cross
appears to do something quite different that I don't understand.So it still creates the target dir of its choosing, just inside whatever target-dir I specify. Furthermore, it appears to copy some of the build artifacts (but not the final products) among/.
I'd expect this instead to work the way cargo does. This makes target-dir pretty unusable.
What target(s) are you cross-compiling for?
aarch64-unknown-linux-gnu
Which operating system is the host (e.g computer cross is on) running?
What architecture is the host?
What container engine is cross using?
cross version
cross 0.2.5 (a599f20 2023-08-23)
Example
See the description.
Additional information / notes
No response