On Sat, Feb 05, 2022 at 01:27:48PM +0400, Marc-André Lureau wrote:
Hi
On Sat, Feb 5, 2022 at 2:44 AM Richard W.M. Jones <rjones(a)redhat.com> wrote:
On Fri, Feb 04, 2022 at 05:20:31PM +0400, Marc-André Lureau wrote:
> Projects releasing for Windows should probably natively build and test
their
> releases with Msys2, and they can do so for msvcrt targets.
This isn't a very useful suggestion. We build using mingw precisely
to avoid touching Windows at all.
Even freedesktop offers Windows CI instances where you can build natively.
I have honest doubts about projects doing releases for Windows without ever
running it.
This isn't what I said - we don't want to use Windows to build the
package (rhsrvany is the package in this case). We do test it in a
Windows VM before release. If it were to fail -- I don't recall it
ever failing actually, so this is theoretical -- then we'd go back to
the Fedora mingw environment to fix it. What I don't want is to have
to use a Windows environment to build the package.
I'm a little confused about the thread though. If we use
mingw32-*
after this change, does it still use msvcrt?
There is no change on the existing mingw32 and mingw64 targets. Did you read
the proposal? :)
I did read it yes, but later messages in the thread confused things.
If we're not touching the mingw32 target, at least for now, then
that's fine. Eventually I guess when absolutely no one is using
Windows 7 and doesn't want to use V2V to convert those guests we can
drop the 32 bit / msvcrt stuff.
Rich.
--
Richard Jones, Virtualization Group, Red Hat
http://people.redhat.com/~rjones
Read my programming and virtualization blog:
http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html