Building and packaging Wine Gecko

Ben Klein shacklein at
Fri Dec 11 16:49:35 CST 2009

2009/12/12 Ove Kaaven <ovek at>:
> Anssi Hannula wrote:
>> However, the instructions on that page ask for copying binaries directly
>> provided in wine-mozilla tarball, and for modifying mingw32 headers.
> It's probably also possible to generate these at package build time by
> invoking the appropriate commands. If it's the lib*.a files, you can
> probably just build-depend on wine-dev and run i586-mingw32msvc-dlltool or
> something on the appropriate Wine .def file to get a mingw32 import library
> in .a format.
> I'm not sure about the wintools libs, but if they're actually needed, there
> must be a way to build them... even if it might take making official
> mingw-built packages of glib and libidl to include in the distro...
> Well, I've been planning to try to make a Debian package of gecko, but won't
> have time to finish it before the holidays.

Have you looked at my wine-gecko-1.0.0 package at the
repository? It's just the pre-packaged cab file stored in

More information about the wine-devel mailing list