On Thu, 8 May 2025 at 22:37, Collin Funk <collin.fu...@gmail.com> wrote:
> Since the whole MSYS2 thing has caused repeated confusion, including to > me [1], maybe we should add a section to the Gnulib manual. > Also it would be nice to have some advice on what to use instead. Bruno outlined to me that there are at least 3 options for developing for MinGW: 1. Cross-compile from GNU/Linux, use WINE to run compiled programs. 2. Use MSYS2 (but we don't like this) 3. Use Cygwin with mingw packages My problem is that I'm trying to build and test portable packages on native Windows. Therefore, option 1 is rather weak (it's not really testing on Windows), option 2 is out because of MSYS2 problems, and it's not clear to me that option 3 is going to work either. (Another problem for me is that GitHub's continuous integration service uses MSYS2. GitHub is a convenient and powerful free-as-in-beer way to test my packages on the systems that almost all my users use—GNU/Linux, macOS, and Windows. It would be nice not to need a proprietary service for this, but then I am testing on proprietary OSes.) -- https://rrt.sc3d.org
