Plan for tomorrows (20080910) FESCO meeting

[Kevin Kofler]

Richard W.M. Jones <rjones <at> redhat.com> writes:
> I'm not sure I understand the question, but: The native Fedora NSIS
> doesn't have any plugins enabled.  If you need functionality contained
> in NSIS plugins then you have to run the Windows version under Wine
> (or actually in Windows).  This isn't as much of a problem as it
> sounds since if Wine is installed then Windows executables "just work"
> without you needing to do anything special.

FYI, as the plugins are just Window$ DLLs and noarch data, it is technically 
possible to simply use the plugins from the Window$ binary ZIP. I have NSIS 
packages at http://repo.calcforge.org/fedora/ which do this (nsis is the stuff 
built from source, nsis-data is a noarch package with the copied binaries). I 
realize that doing this is against Fedora guidelines though. I just wanted to 
point out it is possible.

Debian, on the other hand, has had success with building much of NSIS with a 
MinGW cross-compiler. You can take a look at their package. The README.Debian 
in the current Debian experimental package says only the System plugin still 
doesn't build (due to inline assembly, and there are attempts to fix that). You 
may need a fairly old MinGW GCC to get it to build without heavy patching 
though, at least last I checked NSIS used stuff like lvalue casts in their 
code, as M$VC doesn't complain about those. Debian also had a patch to support 
64-bit builds (real ones, not -m32 as upstream NSIS used), which I used in my 
package too, but this appears to be finally fixed upstream in 2.39.

        Kevin Kofler