cargo-binstall icon indicating copy to clipboard operation
cargo-binstall copied to clipboard

Help with usage for crates with multiple binaries

Open andrewdavidmackenzie opened this issue 2 years ago • 6 comments

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

andrewdavidmackenzie avatar Sep 22 '23 14:09 andrewdavidmackenzie

There are two solutions to this problem.

The first solution is to put all the binaries into a single achieve flowr-{ version }-{ target }.tar.gz, then cargo-binstall should work out-of-the-box.

The other solution is to wait for #854 to be implemented in cargo-binstall, since your release contains a disr-manifest.json

NobodyXu avatar Sep 23 '23 00:09 NobodyXu

I will prioritize this issue since I think supporting this use case is important.

NobodyXu avatar Sep 23 '23 12:09 NobodyXu

P.S. @andrewdavidmackenzie Your flowr is also using very old cargo-dist, we will probably only support newer version (>0.0.2) of cargo-dist.

@andrewdavidmackenzie I've opened https://github.com/andrewdavidmackenzie/flow/pull/2053 to use latest cargo-dist in flow

NobodyXu avatar Sep 23 '23 12:09 NobodyXu

Thanks for the advice, work and PR. I will look at this tomorrow night.

andrewdavidmackenzie avatar Sep 24 '23 08:09 andrewdavidmackenzie

Do you recommend I wait for you to implement #854 then?

andrewdavidmackenzie avatar Sep 26 '23 13:09 andrewdavidmackenzie

Do you recommend I wait for you to implement #854 then?

Yes, I am working on it.

NobodyXu avatar Sep 26 '23 21:09 NobodyXu