Op dinsdag 17-11-2009 om 21:35 uur [tijdzone +0100], schreef Erik van Pienbroek: > With our MinGW toolchain it should be perfectly possible to build the > wine-gecko library from source. The instructions at > http://wiki.winehq.org/BuildingWineGecko are all that we need to create > a .spec file for it.
> If you're interested I can try to create a .spec file for it. However, > if you want to have it in Fedora I don't want to be it's primary > maintainer (but co-maintaining is fine with me). Hi, Creating a .spec file for wine-mozilla turned out to be easier than expected. I just managed to get everything packaged with the exception of the final step: creating a .cab file. We can't do that because there's no open source tool to create .cab files. So now I created a package which puts all the gecko files in the folder /usr/share/wine/gecko. We might want to patch Wine so that it uses the gecko files directly instead of unpacking the .cab file on first use. Some small patches were required to get everything compiled (due to the use of a more recent GCC and some missing w32api declarations) but in the end I managed to get a working environment (by symlinking ~/.wine/drive_c/windows/system32/gecko/1.0.0/wine_gecko to /usr/share/wine/gecko). I tested this with Wine's iexplore.exe and didn't encounter anything unusual. Regarding my comment on not wanting to be primary maintainer of this package: I'd prefer it if somebody else who has a closer connection to upstream (the current wine maintainer?) maintains this as I don't really have the time to monitor for new releases. Whenever MinGW specific issues arise I'm willing to help with resolving those (hence the co-maintainer offer). The Koji build can be found at http://koji.fedoraproject.org/koji/taskinfo?taskID=1815495 As scratch builds tend to get removed quite quickly I also uploaded the SRPM to my personal server: http://www.ftd4linux.nl/contrib/mingw32-wine-gecko-1.0.0-1.fc12.src.rpm and the .spec file to http://www.ftd4linux.nl/contrib/mingw32-wine-gecko.spec Feel free to put them up for review Op woensdag 18-11-2009 om 11:18 uur [tijdzone +0000], schreef Richard W.M. Jones: > 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. It's strange that you had these issues. NSS and NSPR just compiled here fine without any manual fiddling. Perhaps it's caused by the fact that wine-gecko is a forked copy of the gecko engine and is aimed for cross-compilation in the first place. > 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[1] 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). To build this package all I needed was the basic tools: binutils, runtime, w32api and gcc At that wiki page there was some talk about a GCC bug, but I didn't run into it as everything compiled just fine and also runs fine in Wine. Regards, Erik van Pienbroek _______________________________________________ fedora-mingw mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/fedora-mingw
