Ken Takata wrote:
> @brammool I'm now thinking adding support for 64-bit installer, because there > are some requests for that. (E.g. vim/vim-win32-installer#73) > But I have a question about the current NSIS script. It requires some > executables have the `w32` suffixes. (E.g. `installw32.exe`, > `uninstalw32.exe`, ...) > Why they are needed? If we remove them, we can use the same script for both > 32- and 64-bit installer. > Otherwise, we should add many !ifdefs (or we should also use the `w32` > suffixes for the 64-bit installer.) The "w32" addition is to make sure it doesn't get confused with the other install.exe that can be build. It's possible to use "win" instead of "w32" if that is clearer. But if there actually are two versions of the executable, it's probably best to give them different names, otherwise it's very easy to end up with the wrong one. -- Living in Hollywood is like living in a bowl of granola. What ain't fruits and nuts is flakes. /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
