View Single Post
Old 9th February 2019, 10:52   #7
Junior Member
Join Date: Jun 2014
Posts: 3
Originally Posted by Anders View Post
The official NSIS source code can be compiled as 64-bit as well (but the System plug-in is not fully functional). 32-bit MakeNSIS can produce 64-bit installers but you have to compile or get the 64-bit stubs and plug-ins first, and then add "Target AMD64-Unicode" to your .NSI.
Just looking in the Stubs folder, I can see the installer stubs, as well as uninst, which is obviously the uninstaller stub.

Which reminds me, what's the best way to handle registry access if I have a 64 bit installer stub and a 32 bit uninstaller stub. Should I be OK if I just specify HKCU64 / HKLM64 for both?

I'm a little curious what the effect of "SetRegView 64" will be on a program that's already 64 bit.

Or just build a 64 bit uninstaller stub and be done with it?
dgnuff is offline   Reply With Quote