Adding binary to the releases?

[GitMensch]

Hi Bill,

as I wanted to create a complete build with the last release in any case I can put some extra effort in and make them available for download.
Therefore: what do you think about adding binary packages to the latest release?

If you are fine with this I'd add binaries for win32 and win32a (sdl2 would be nice, too; will do so if everything works out of the box with the official SDL2 binaries).

For VS2015 (maybe later VS2017+WinSDK and if MinGW works unpatched later MinGW versions, too).

• all variants (WIDE/NON-WIDE, UTF yes/no, dynamic/static [no static for SDL2 version as you need an external lib in any case])
• maybe with demos for the dynamic versions in a sub-directory [if I understand this correctly we only need wide/non-wide for both x86/x64, UTF no libraries would work with UTF yes demos, correct?]
• release only, if someone really wants to debug this it would be better to have the complete environment on that machine in any case

You may provide binaries for use with other compilers.
Opinions?

Additional question: Is there a standard procedure of packing PDCurses? Otherwise I tend to add this to the Makefiles I can test...
Maybe as prepare-dist-bin target in the subfolders and a dist-bin in the main folder that uses whatever is placed in the dist folder before? [depending on your answer I'll move this to a new issue]

[GitMensch]

... this seems only to be reasonable if the release process is automated by tagging (and we have the normal CI build as part of this adding the binaries from this build to the release).