cargo-binstall VS cargo-xtask

Unfortunately not really usable in production (for me) until https://github.com/cargo-bins/cargo-binstall/issues/1 is fixed :( Really much looking forward to it though, as I think it's a great addition to the Rust ecosystem!

Oh looks like cargo-binstall is currently broken (https://github.com/cargo-bins/cargo-binstall/issues/1094)

Unfortunately, I ended up running into an issue with the zip support, but I'll come back to it once this is fixed: https://github.com/cargo-bins/cargo-binstall/issues/1080

I've encountered a strange lifetime error when developing new features in cargo-binstall:

Once you feel like releasing it, could you please add binstall support?

I think in a similar vein there is cargo-binstall that is a cargo install alternative that attempts to use pre-built binary artifacts when possible

I hope ld64 and lld add supports for plugin-opt I'm trying to enable cross-lang-lto on MacOS but failed due to -plugin-opt not supported.

You can use cargo-binstall --install-path to install binaries to custom locations.

If you happen to install a lot of things with cargo, check out cargo-binstall: https://github.com/cargo-bins/cargo-binstall

It'll fetch the binary release from the repo so you don't have to compile it yourself.

I'd recommend to use cargo-binstall, which can download pre-built artifacts from github release.

💡 Inspired by matklad/cargo-xtask and based on 🏃‍♂️ Write your Rust project scripts in task.rs from the Rust ecosystem.

Using a cargo-xtask task to generate them as a manual step (inlyne currently does this)

As someone else said just is good for that job, or you could implement an xtask helper for these things and setup a suitable development environment with that: https://github.com/matklad/cargo-xtask/

Well tools like cornucopia, prisma-rust-client, protoc-gen-tonic, they don't generate in build.rs, but instead provide either a cli to be called ahead of time, or provide a library that can be called by your own binary (which should generally follow the xtask pattern)

If I understand, this is a tool for when working on the project itself? Akin to a helper script? You could go the cargo install route as already pointed out but there is also the xtask convention.

For simple cli apps for internal use, such as cargo-xtasks, I prefer pico_args due to its fast compile times.

For developer-oriented stuff, there's tools like xshell and cargo-xtask. For operator tasks that need to run in a deployed environment, it's not usually a big lift to add CLI subcommands to your binary. It's certainly more boilerplate and inertia than doing stuff in a live REPL, though, and sometimes difficult to recommend for truly one-off situations.