4 ms·
Side note: Back when I did Win32 packaging of cross-platform applications, I never liked InnoSetup much, mostly because of the many levels of unpacking into te
by vog 10y ago
Side note:
Back when I did Win32 packaging of cross-platform applications, I never liked InnoSetup much, mostly because of the many levels of unpacking into temporary directories, but also because it was relatively slow and not as compact as it could be. Instead, I always preferred NSIS using the makensis command.
Among others, NSIS can be compiled on *nix systems, but still produces a Windows executable file (like a cross compiler), so you can put it in your cross compiling toolchain. That way, you can create your full Windows port including installer without ever having to touch a Windows.
- tonyedgecombe 10y agoInteresting, I've always been a huge fan of InnoSetup, I've used it for many projects a couple of which had very complex installation requirements.
- dom0 10y agoInnoSetup was very easy to get started with and get the expected results, while NSIS looked more complex. I'm not particularly opinionated about installers as long as they install and uninstall things :)