-
-
Notifications
You must be signed in to change notification settings - Fork 62
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
Help with usage for crates with multiple binaries #1380
Comments
There are two solutions to this problem. The first solution is to put all the binaries into a single achieve The other solution is to wait for #854 to be implemented in cargo-binstall, since your release contains a disr-manifest.json |
I will prioritize this issue since I think supporting this use case is important. |
P.S. @andrewdavidmackenzie Your flowr is also using very old @andrewdavidmackenzie I've opened andrewdavidmackenzie/flow#2053 to use latest |
Thanks for the advice, work and PR. I will look at this tomorrow night. |
Do you recommend I wait for you to implement #854 then? |
Yes, I am working on it. |
I have looked for this in Support.md and elsewheer but have not found it yet, appologies if it is already documented.
I have a crate (flowr) that is part of a workspace project (flow) that builds multiple binaries (flowrcli, flowrgui, flowrex).
In the same workspace project I have a crate flowc that builds a binary flowc.
I have been able to use cargo binstall to install flowc without problems, as it can find the flowc binary asset in releases.
How can I use (i.e. command line options required) cargo binstall to install all the binaries of the flowr crate?
thanks
The text was updated successfully, but these errors were encountered: