Rewinding the discussion on MinGW+Wine

Erik van Pienbroek erik at vanpienbroek.nl
Tue Jul 28 10:17:39 UTC 2009


Op dinsdag 28-07-2009 om 11:19 uur [tijdzone +0200], schreef Paolo
Bonzini:
> >> AM_PATH_GLIB_2_0 will detect mismatched header files vs.
> >> installed libraries, while PKG_CHECK_MODULES, so your solution is not
> >> 100% equivalent.
> >
> > So far, in us packaging about 100 packages (many dependent on glib),
> > this has not proved a problem.
> 
> Because you do not have Wine installed, so that check is not run.  A 
> user (not a fedora packager) will have it 99% of the time.

That's strange. I do have wine installed here (with the binfmt stuff
enabled) and I've never seen that behaviour when using ./configure
--host=i686-pc-mingw32

> > There's no issue with mismatching headers and libraries because
> > everything is installed via RPM.
> 
> If you do not fix bug 513825, the configure script will get the Linux 
> pkg-config, not the cross pkg-config.  Then it will definitely report 
> (if you have Wine installed, and with today's Fedora 11) mismatched 
> headers and libraries.

The rename of mingw32-pkg-config to i686-pc-mingw32-pkg-config is
something I think we all agree of. However, we don't have any influence
on the contents of the .pc files produced by packages. To get the
sysroot part operational we need a lot of manual fiddling in all
generated .pc files and a fully coordinated mass-rebuild. Both of which
I'm sure the Fedora-MinGW32 packages aren't really interested in. And
even if we have prepared all the packages and done a mass-rebuild, it'll
still be a pain in the ass to maintain as it's easy to break or to
forget to patch new .pc files.

Regards,

Erik van Pienbroek





More information about the mingw mailing list