-
Notifications
You must be signed in to change notification settings - Fork 103
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
How to get trurl binaries #375
Comments
In the linked comment I'm just offering ideas. We hadn't made the decision to provide trurl binaries within the official curl binaries. It seems unpractical and out-of-place. The curl-for-win build scripts are capable to create a tailor-made static trurl binary, but it needs its own build configuration (different from what's ideal for curl itself). So it's best done within the trurl project. This tailor-made curl-for-win build is already running in trurl's CI. What's missing is the process to do that for stable trurl releases and publish them somehow, somewhere. In the meantime you may run it locally to produce |
Moved this thread to the trurl repo. |
I started a wiki page to collect information about how to get trurl for different OSes and distros: |
As originally discussed in #130 (comment) the curl/curl-for-win project stated to offer Windows builds of trurl.
However, it appears that the
trurl.exe
binaries are only available as pipeline artifacts of the daily build pipelines. Specifically, the binaries are deeply nested in thecurl-windows-daily
artifact which contains arch specific zip files, e.g.curl-8.11.0-DEV_20241020-win64-mingw-test.zip
within which in thebin/
folder I can finally find the desiredtrurl.exe
.I am now wondering whether there's an option to make this process easier? Is there a way you can provide the
trurl.exe
in a way that is easier to consume and use? Are you already doing so somewhere and I missed it?The official trurl page is rather bare, especially compared to the curl download page which offers everything even links to WinGet or Homebrew.
The text was updated successfully, but these errors were encountered: