Hi Thomas, On Wed, Apr 27, 2011 at 08:44:04PM +0200, Thomas Gaugler wrote: > I combined the best of your patch and the input from > http://sourceforge.net/support/tracker.php?aid=2949102. > > The result is now visible in the collab-maint subversion repository. > http://svn.debian.org/wsvn/collab-maint/ext-maint/nsis/trunk/?op=log > > The preference is given to mingw-w64. However in case mingw-w64 is not > available then the build process would fall back to mingw32.
That's great! I've taken a look at the result, and noticed a few things: * README.Debian still refers to the old i586-mingw32msvc paths only; * nsis-pluginapi recommends mingw-w64 but nsis suggests gcc-mingw32; * headers and libraries are only installed in /usr/i686-w64-mingw32 (when built with mingw-w64, since I take it it's /usr/i586-mingw32msvc when building with mingw32). As a result even though nsis itself can still be built with either mingw-w64 or mingw32 (which is very nice indeed), the resulting package only allows building with whichever compiler was used to build nsis... mingw32 and mingw-w64 produce ABI-compatible binaries, so building using the output of either works with both compilers; shipping the same library in /usr/i586-mingw32msvc/lib/nsis and /usr/i686-w64-mingw32/lib/nsis works fine. I'm wondering about this since you asked about it previously, in order to avoid making win32-loader FTBFS once nsis switches to mingw-w64! > So building nsis with mingw-w64 should be officially possible once > nsis-2.46-4 is released. Excellent. > Your work for mingw-w64 is very much appreciated. Thanks a lot for that. You're very welcome, yours on nsis is too! Regards, Stephen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
