On 2021-06-20 13:00, Brian Inglis wrote:
On 2021-06-20 12:50, Brian Inglis wrote:
On 2021-06-20 09:54, Brian Inglis wrote:
On 2020-12-28 11:23, Achim Gratz wrote:
Yaakov Selkowitz writes:
To ease the maintenance of MinGW cross-compiling packages, I have
written a new mingw.cygclass (actually,
On 2021-06-20 12:50, Brian Inglis wrote:
On 2021-06-20 09:54, Brian Inglis wrote:
On 2020-12-28 11:23, Achim Gratz wrote:
Yaakov Selkowitz writes:
To ease the maintenance of MinGW cross-compiling packages, I have
written a new mingw.cygclass (actually, a series of cygclasses, but
that's the to
On 2021-06-20 09:54, Brian Inglis wrote:
On 2020-12-28 11:23, Achim Gratz wrote:
Yaakov Selkowitz writes:
To ease the maintenance of MinGW cross-compiling packages, I have
written a new mingw.cygclass (actually, a series of cygclasses, but
that's the top-level one that you should use) which is
On 2020-12-28 11:23, Achim Gratz wrote:
Yaakov Selkowitz writes:
To ease the maintenance of MinGW cross-compiling packages, I have
written a new mingw.cygclass (actually, a series of cygclasses, but
that's the top-level one that you should use) which is designed to
allow building both 32- and 64
Yaakov Selkowitz writes:
> To ease the maintenance of MinGW cross-compiling packages, I have
> written a new mingw.cygclass (actually, a series of cygclasses, but
> that's the top-level one that you should use) which is designed to
> allow building both 32- and 64-bit MinGW binaries in the same bui
To ease the maintenance of MinGW cross-compiling packages, I have
written a new mingw.cygclass (actually, a series of cygclasses, but
that's the top-level one that you should use) which is designed to
allow building both 32- and 64-bit MinGW binaries in the same build.
It also allows for the intro
