Viktor Szakats

Oh, okay, no worries, I do understand the feeling! :) [ as a shot in the abyss why this PR is not going anywhere, I was about to reinstate the...

Updated the patch to keep support for these legacy bits: 1. Windows 16-bit Resource flags. 2. MinGW releases that do not support those Windows 16-bit Resource flags. Please let me...

Added a build error log to the top post.

With MinGW (and MSYS/Cygwin) the expected names are: `libz.a` for static and `libz.dll.a` for the implib. These are recognized by the toolchain as static/shared libs when linking.

I agree that self-signed signatures aren't really useful for most cases. A signature accepted by default Windows installations will almost certainly cost money though. At least I couldn't find a...

Cygwin is definitely not Windows builds indeed (it doesn't build against the Win32 API for example). I'm in favour of renaming it to **Cygwin**, possibly even merging the separate **32...

Agreed that 32/64 bit would best be merged for the Windows platform as well. 'win' as in Cygwin already says it's related to Windows, so sticking Windows before it seems...

ARM64 builds will probably stay with us. So re-opening this in the hope somone is kind to put this up on the downloads page.

Referring to https://github.com/curl/curl-www/issues/74, it might be an opportunity to merge the separate 32-bit and 64-bit Windows/Cygwin sections respectively. Something along these lines (this draft includes the Cygwin merge as well,...

Ref: https://github.com/curl/curl/pull/9727#issuecomment-1279257592