-
Notifications
You must be signed in to change notification settings - Fork 102
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
wanted: binary Windows releases #130
Comments
If someone wants to work on that I'll help out, but it's not a priority for me personally. |
lots of distros already ship trurl. |
having a official windows binary would still be a thing |
Agreed. It would be great if someone provided such. |
@bagder i started working on this a few days ago, but had no time to go on... if you want to take a look... it builds, but both gh actions files should be merged in a single one using matrix, so there will be a single final release, with all the artifacts generated and attached to it... or maybe 2 files, 1 for build and 1 for release... right now, the fastest build will push the binary and create release, the slowest follows and halts overwriting the other built one (different arch), and cannot create a new release because it already exists... once merged these 2 files in a single build one, i think the windows part should be trivial to add... edit: |
I would presume that for Linux and macOS this is less interesting than for Windows. |
why? Having binaries instead of just sources published on releases page would allow to release an asdf plugin, too, to have this versioned |
i also think that having official binaries for all platforms is good thing. being able to simply wget the binary with the latest version from the official source is so nice. not having to wait for third parties until they update their packages or fiddle around with docker. one of the main reasons i meanwhile narrow my search to golang for small cli tools (sometimes rust too) - they offical sources ship binaries. |
If someone wants to provide builds for any platform, feel free to work on it. |
@bagder done! :D |
I've added trurl to curl-for-win. For now I did not enable it in the live releases, They are already present in the daily curl-for-win builds: FWIW it's not only Windows (3 CPUs), but also LInux MUSL (amd64, aarch64, |
Windows builds are running now in CI. For release purposes it may use a slightly different configuration, for a bit smaller binaries with longer build times. Otherwise the existing CI logic can be re-used for this Issue almost as-is. The question is where to upload the result, how to trigger it and adding the necessary logic for these. It would be a better way to distribute trurl than adding them to the official curl package. The latter features shared UPDATE: After further optimizing thin libcurl, |
After another round of optimizations with trurl builds, the size of the reference Windows ARM64 |
Either the thing suggested in the last comment could be used to pull this off, though it'd be a new process and someone needs to do it. It could probably be done in GHA with results uploaded to the Release page. (I have no recipes ready for this.) Or, to avoid the extra work, it's possible to enable trurl in official curl-for-win builds. In such case, it'd be using the existing curl/libcurl build process, which builds a "universal" libcurl lib (= not specifically optimized for trurl, meaning much larger in size). This would make a static
|
it would be nice to have binary releases on github (including windows). for golang tools it is quite common that they provide multiplatform builds on github.
The text was updated successfully, but these errors were encountered: