I think I have addressed most of your suggestions. I moved the files to their own repo: https://github.com/janisozaur/curl-win-aarch64 where I have added some basic readme and the license file copied from upstream. The files are properly tagged (using the same format as upstream), so you can get GitHub's automated archive via https://github.com/janisozaur/curl-win-aarch64/tags
I have also submitted a set of pull requests so that the builds are done by your appveyor setup instead: * https://github.com/curl/curl/pull/4509 appveyor: publish artifacts on appveyor * https://github.com/curl/curl/pull/4507 appveyor: Add MSVC ARM64 build Other than the PR building a static version (which I simply forgot to do) it is pretty much exactly how I came up with the builds in the first place, albeit on a local machine. I'm *not* particularly interested in maintaining those builds by myself in the long run, but I sometimes do check up how well projects support MSVC+ARM (cf. https://github.com/curl/curl/pull/2363), I was simply in need of Aarch64 curl binary. I will likely occasionally update this new repository with new builds, provided the PRs I've sent get merged. If that's a blocker for linking to my builds, I'm fine with that. Best regards, Michał. On Fri, 18 Oct 2019 at 13:09, Daniel Stenberg <dan...@haxx.se> wrote: > > On Fri, 18 Oct 2019, Michał Janiszewski via curl-library wrote: > > > I've prepared Windows Aarch64 build that you can find here: > > https://gist.github.com/janisozaur/584f5e04485b7d3a7b29b6fb4db3584b#file-curl-exe > > It is 7.66 release, built with WinSSL, using MSVC2019 and the CMake project. > > Is there any interest in linking to it from > > https://curl.haxx.se/download.html? Should I do anything else > > regarding how the package is compiled or distributed? > > Thanks for your consideration! > > I think you could do a few things to improve what you're offering: > > 1 - package the binary in a zip or similar and bundle some basic information > about it - like what SSL (version) it is built to use, other > dependencies, perhaps some basic docs and the license etc. > > 2 - make sure that the version number is clearly visible on the web page and > in the download file itself. Our download page works best when our > automated bot can poll the download pages itself and figure out what > version you're offering - as I assume you want to keep the download > package up to date going forward. > > 3 - that page is a github gist, which has a rather user hostile URL. Are you > going to keep that as the fixed URL for your curl packages also going > forward? > > 4 - make sure you can produce your packages with a script so that it gets > easier to do subsequent packages. We release a new curl every eight > weeks > after all! > > -- > > / 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
