On Mon, Sep 26, 2011 at 12:10:13AM +0200, Stephen Kitt wrote: > mingw-w64, which is intended to eventually replace mingw32 and the
Why is it then cllaed w*64*? And why didn't it replace them yet? Sound like either a broken package name or wishful thinking to me - or even both, > I've rebuilt libreoffice successfully using mingw-w64, but I'm not > sure what the Windows build environment is actually used for so I > haven't been able to check that the resulting build is actually > correct. (LibreOffice itself starts up and functions correctly, but I > don't know how to determine whether the Windows-targeted build > artifacts are being used.) Of course I don't expect you to do the > checking for me; if you have the time to point me in the right > direction I'd be happy to complete the investigation. It's only used for unowinreg.dll, which in turn is only used in the SDK. (It should be bundled to stuff wanting to use the registry, and for that the Java stuff is supposed to use that .dll) Grüße/Regards, René -- .''`. René Engelhard -- Debian GNU/Linux Developer : :' : http://www.debian.org | http://people.debian.org/~rene/ `. `' r...@debian.org | GnuPG-Key ID: D03E3E70 `- Fingerprint: E12D EA46 7506 70CF A960 801D 0AA0 4571 D03E 3E70 -- To UNSUBSCRIBE, email to debian-openoffice-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110925231029.gf22...@rene-engelhard.de
