-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Multiple Packages With Binaries Found #3049
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Ah yeah if a git repository has multiple crates inside of it all with binaries Cargo has to know which one is actually being installed. The package on crates.io, however, is specific, so that's why that works instead. Does this work for you?
|
That does work perfectly. |
The RFC is still indicating to use |
I added the `-p` (paralell) parameter as mentioned in rust-lang/cargo#3049
https://doc.rust-lang.org/cargo/commands/cargo-install.html says
neither of these worked for me, still giving the error about wanting to know which of multiple packages to install, but passing the binary name as an argument like suggested in this issue did work. |
I have a git repo where I have adjacent directories that specify dependencies among them using eg I also had to pass CARGO_NET_GIT_FETCH_WITH_CLI=true to even authenticate to the git server on macOS. |
@spease this is a fairly old issue and it is unclear if its related to this issue. If this appears to be a bug, it might be good to create a new issue and include full reproduction steps. If this is a question on how to use Cargo, you might want to post on https://users.rust-lang.org/ |
Sorry, maybe it's not clear how I arrived at this ticket. If I run
I get If I run
which is what the If I use the suggested solution in this ticket
then I get
I don't know if this is the best ticket, but it seems like this is broadly the same usability issue. EDIT: Seems CARGO_NET_GIT_FETCH_WITH_CLI=true is no longer necessary since I added the |
As you highlighted, something is going on with |
Figured it out. The issue was that an underlying dependency was outside the project tree as I had to modify a third-party library and the PR never got accepted or rejected, so I never updated the dependency to a permanent value. Opened #14924 to discuss making the error clearer. |
Having an odd issue which I can't figure out. If I install my Rust application with:
I get this error:
Yet if I install the application with this command:
It compiles perfectly.
The text was updated successfully, but these errors were encountered: