Closed nipunn1313 closed 5 years ago
To repro the above example
https://github.com/alexcrichton/cargo-vendor
cd cargo-vendor
cargo vendor -x
# Update .cargo/config as requested
then compare these two
cargo build --verbose
cargo install --path . --verbose
I think this may have recently been fixed in https://github.com/rust-lang/cargo/pull/6804, can you try the latest nightly Cargo and see if it fixes the issue? (I think that change should have made its way to nightly by now)
This crate is now included natively in Cargo as of https://github.com/rust-lang/cargo/pull/6869 and today's nightly Rust. I'm closing all issues in this repository before I archive the repository, but if you're still interested in seeing this issue fixed then please feel free to file an issue with Cargo itself!
Seems slightly related to #62 - was looking into vendoring binaries recently After running cargo vendor and updating the
.cargo/config
, I found thatcargo build
respects the config butcargo install --path .
does not.vs
as a result, if we want to use a cargo installed binary, we have to do
cargo build --release
followed by copying the binary target over fromtarget/release/{name}
to abin/
directoryAccording to comments on #62 - this is not how it used to work - though I don't remember exactly.