On Tue, Nov 17, 2009 at 02:10:42PM -0600, Jason L Tibbitts III wrote:
I just wanted to let you folks know about a current discussion going
between various Wine developers. Wine uses Gecko, the Mozilla rendering
engine, as a replacement for whatever is in Windows. Currently at issue
is how a user of Wine actually gets gecko on their system. It can be
downloaded at wine startup, which is problematic for various reasons, or the
distro can package it. But what's needed are the actual win32 gecko
libraries, not a native Linux version, which sort of involves
using mingw and cross-compiling.
As Erik said, Fedora MinGW should be able to cross-compile Gecko just
fine. We are already able to compile large C++ graphical apps
(eg. Inkscape, FlightGear etc.)
The only note of caution I would add is that Mozilla stuff uses its
own crazy-stupid build system which doesn't really understand
cross-compilation properly (or much else for that matter). For
example, I had a lot of problems cross-compiling NSS and NSPR. You
can see the sorts of troubles we had by looking at the spec files:
and patches named things like "nspr-configure-remove-crack.patch"
which should give you a flavour of what was involved.
On the subject of: http://wiki.winehq.org/BuildingWineGecko
Note that Fedora MinGW already supplies binutils, runtime, w32api, gcc
packages. So any instructions about installing those can be
disregarded. They claim to need gcc 3 (which we don't supply), but
looking at the supposed bug it seems that this is issue should be
fixed in the gcc 4.4.3 (we don't yet have this, but gcc version bumps
are usually simple).
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-p2v converts physical machines to virtual machines. Boot with a
live CD or over the network (PXE) and turn machines into Xen guests.