Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Consider binary releases? #138

Open
thejpster opened this issue Oct 8, 2023 · 2 comments
Open

Consider binary releases? #138

thejpster opened this issue Oct 8, 2023 · 2 comments

Comments

@thejpster
Copy link

cargo-dist now does the hard work of setting up binary releases, meaning people can cargo binstall <package> and save themselves a bunch of CI build time.

Would that work here? Or do we need to compile against the specific version of cargo someone has?

@therealprof
Copy link
Contributor

cargo-binutils only provides a nice frontend to find and call the llvm-tools binutils which are installed as a separate component to the rust compiler. It's (pretty much, unless the some critical CLI parameters of those tools change again) independent of the actually installed llvm-tools and the rust compiler version. The same is true for cargo, all the cargo "plugins" are independent of the actual cargo version.

So it should be fine to use/provide binaries.

@thejpster
Copy link
Author

thejpster commented Oct 8, 2023

How do you find llvm-objcopy? It's not in $PATH, nor .cargo/bin?

Actually you can cargo binstall cargo-binutils because this project has been built by quickinstall. But it would be better if it was built (and signed) here instead of by someone else.

Edit: reading comprehension fail

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants