curl / Mailing Lists / curl-library / Single Mail
Buy commercial curl support from WolfSSL. We help you work out your issues, debug your libcurl applications, use the API, port to new platforms, add new features and more. With a team lead by the curl founder himself.

Re: Windows Aarch64 build

From: Michał Janiszewski via curl-library <curl-library_at_cool.haxx.se>
Date: Mon, 21 Oct 2019 23:14:09 +0200

You can browse GitHub tags:
 * via the webui:
https://github.com/janisozaur/curl-win-aarch64/blob/curl-7_66_0/curl.exe
 * for raw files for download:
https://github.com/janisozaur/curl-win-aarch64/raw/curl-7_66_0/curl.exe
 * for automated release packages:
https://github.com/janisozaur/curl-win-aarch64/archive/curl-7_66_0.zip

Does that suffice? Note the currently uploaded binaries are linked in
shared mode, I can probably rebuild them as static ones if needed.

> Releases are built from release tarballs and not straight from git so they
> won't appear completely the same...

Don't the tags then end up on master branch anyway? Who/what builds
the binaries then? The PR to enable AArch64 was trivial, can't this be
added to the release builds the same way?

On Mon, 21 Oct 2019 at 23:04, Daniel Stenberg <daniel_at_haxx.se> wrote:
>
> On Sat, 19 Oct 2019, Michał Janiszewski wrote:
>
> > I think I have addressed most of your suggestions.
>
> Almost!
>
> Do you have any suggestion on how my bot can find the curl version number of
> the package on page? "7.66.0" being the version number of the latest release.
>
> The file you provide isn't named with the version number anywhere either so my
> bot can't check for the presence of a file like "curl-$version.zip" either,
> right?
>
> > I have also submitted a set of pull requests so that the builds are
> > done by your appveyor setup instead:
>
> Releases are built from release tarballs and not straight from git so they
> won't appear completely the same...
>
> > I'm *not* particularly interested in maintaining those builds by myself in
> > the long run
>
> I don't think we need a long term commitment up front for this package to
> offer value to users. I'm fine with it being a package that serves a purpose
> for now and then we decide in the future if we ever think it stops serving a
> good purpose and you can maintain it as good as you like and have the energy
> to!
>
> --
>
> / daniel.haxx.se | Get the best commercial curl support there is - from me
> | Private help, bug fixes, support, ports, new features
> | https://www.wolfssl.com/contact/

-- 
Michal Janiszewski
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette:   https://curl.haxx.se/mail/etiquette.html
Received on 2019-10-22