On Thu, 8 May 2025 at 23:06, Collin Funk wrote:
>
> Bruno's GitHub CI projects use cygwin/cygwin-install-action@v4, which
> seems pretty straight forward [1] [2].
>
> Collin
>
> [1] https://github.com/gnu-gnulib/ci-testdir-check/tree/master
> [2] https://github.com/cygwin/cygwin-install-action
>
On Thu, 8 May 2025 at 23:11, Bruno Haible wrote:
>
> Of course, option 3 works! I use this way of building things for
> native Windows, for a dozen of GNU packages, and
> - have documented it as the recommended way in the INSTALL.windows file
> of many of these packages,
> - am using this
Reuben Thomas wrote:
> 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 Cygwi
Reuben Thomas writes:
> 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
Collin Funk wrote:
> Since the whole MSYS2 thing has caused repeated confusion, including to
> me [1], maybe we should add a section to the Gnulib manual.
I agree with you that the best way to fix this confusion is through
documentation. But not in the Gnulib manual, since the confusion is
unrelat
Hi Bruno,
Bruno Haible via Gnulib discussion list writes:
> That is the MSYS2 environment, and in particular with an augmented PATH
> that contains tools for producing mingw binaries that are linked to
> the Microsoft 'MSVCRT' runtime library.
>
> Whereas the other one, that MSYS2 calls "UCRT64"
On Thu, 8 May 2025 at 22:37, Collin Funk 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
Reuben Thomas wrote:
> I am not using MSYS2 per se, I am using the Mingw64 environment
There is no such thing as "the Mingw64 environment". Better be
careful about the terms.
We need to distinguish
* mingw - which is a toolchain (set of runtime libraries, together
with a customized
