As a developer/release engineer I want the tarball created by make dist to be added automatically to the GitHub release.
I've already played around with this in a test repository and it works.
I'll just have to copy my pipeline and configure it for gbsplay.
If this works, we could also attach the binaries from the Windows builds to a release, but I don't know if that is really useful because as I understand it we don't create portable .EXE files (as in "static compile"), but we still depend on MSYS or CygWin DLLs.
That way a generated binary will be of no use for Windows users that don't want to install MSYS or CygWin (see this comment in #102).
Or am I mistaken?
As a developer/release engineer I want the tarball created by
make dist
to be added automatically to the GitHub release.I've already played around with this in a test repository and it works. I'll just have to copy my pipeline and configure it for gbsplay.
If this works, we could also attach the binaries from the Windows builds to a release, but I don't know if that is really useful because as I understand it we don't create portable .EXE files (as in "static compile"), but we still depend on MSYS or CygWin DLLs. That way a generated binary will be of no use for Windows users that don't want to install MSYS or CygWin (see this comment in #102). Or am I mistaken?