On Thu, Sep 02, 2021 at 04:58:01PM -0500, Zebediah Figura (she/her) wrote: > It's worth pointing out that we will almost certainly need a > fallback solution, if we do end up using shared libraries and > *-w64-mingw32-pkg-config. This is mainly because Fedora, as far as I > can tell, is unusual in providing mingw libraries (Debian ships a > scant few; Arch ships none and in fact only recently even started > shipping the cross-compiler.) And even Fedora doesn't provide all of > the libraries we need. > > I'm happy to work with Fedora and with other distributions to help > get support across the board for mingw libraries and pkg-config, but > it's going to be a hard sell to the Wine maintainers to rely on a > feature that isn't widely supported. Still, we might be able to use > it where it's present... I'm surprised - I thought Debian had a fairly complete set but I checked just now and they don't have many. OpenSUSE's package set is a bit thin which is also a surprise because we collaborated with them on packaging in the early days. (I might be looking in the wrong place for OpenSUSE). Does Wine need 32- or 64-bit packages (or both)? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests. http://libguestfs.org/virt-v2v _______________________________________________ packaging mailing list -- packaging@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to packaging-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/packaging@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
