mirror/nasm
2
0
Fork 0
mirror of https://github.com/netwide-assembler/nasm.git synced 2024-11-27 08:10:07 +08:00
Code Issues Packages Projects Releases Wiki Activity
d9bc244f8a
nasm/nsis/nasm.nsi

245 lines
8.1 KiB
Plaintext
Raw Normal View History

Add NSIS script to make a Windows installer Here is an NSIS script for making a simple NASM package. It creates a NASM folder with some of the important binaries in it, as well as a simple batch file to get a CLI with the NASM folder included in the PATH. Expects to be built from inside the bin/ directory. Fairly primitive. Feedback welcome. - Shao
2009-04-07 10:07:37 +08:00
#!Nsis Installer Command Script
substitute nasm.nsi with new nasm2.nsi We always have "restore point" but such an action will allow us to test new installer in more wide audience. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2009-09-22 03:15:55 +08:00
#
Add NSIS script to make a Windows installer Here is an NSIS script for making a simple NASM package. It creates a NASM folder with some of the important binaries in it, as well as a simple batch file to get a CLI with the NASM folder included in the PATH. Expects to be built from inside the bin/ directory. Fairly primitive. Feedback welcome. - Shao
2009-04-07 10:07:37 +08:00
# Copyright (c) 2009, Shao Miller (shao.miller@yrdsb.edu.on.ca)
substitute nasm.nsi with new nasm2.nsi We always have "restore point" but such an action will allow us to test new installer in more wide audience. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2009-09-22 03:15:55 +08:00
# Copyright (c) 2009, Cyrill Gorcunov (gorcunov@gmail.com)
Add NSIS script to make a Windows installer Here is an NSIS script for making a simple NASM package. It creates a NASM folder with some of the important binaries in it, as well as a simple batch file to get a CLI with the NASM folder included in the PATH. Expects to be built from inside the bin/ directory. Fairly primitive. Feedback welcome. - Shao
2009-04-07 10:07:37 +08:00
# All rights reserved.
#
substitute nasm.nsi with new nasm2.nsi We always have "restore point" but such an action will allow us to test new installer in more wide audience. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2009-09-22 03:15:55 +08:00
# The script requires NSIS v2.45 (or any later)
#
Add NSIS script to make a Windows installer Here is an NSIS script for making a simple NASM package. It creates a NASM folder with some of the important binaries in it, as well as a simple batch file to get a CLI with the NASM folder included in the PATH. Expects to be built from inside the bin/ directory. Fairly primitive. Feedback welcome. - Shao
2009-04-07 10:07:37 +08:00
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions are met:
# * Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
# * Redistributions in binary form must reproduce the above copyright
# notice, this list of conditions and the following disclaimer in the
# documentation and/or other materials provided with the distribution.
#
# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
# ''AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
# TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
# PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL <copyright holder> BE LIABLE FOR
# ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
# DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
# SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
# CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
# OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
# OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Fix building in a separate directory from the source code The code to handle building in a separate directory had seriously bitrotted. This contains a number of fixes to make it possible, including bits like the documentation which never worked in the past. Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-05-17 11:30:09 +08:00
!addincludedir "${objdir}/nsis"
!addincludedir "${srcdir}/nsis"
nasm.nsi: add NASM Manual; automate version generation Add the NASM Manual (as a PDF) to the Windows installer, and abstract out the version number.
2009-04-07 10:12:34 +08:00
!include "version.nsh"
nsis: make nsis output automatically select architecture Make the NSIS output automatically select the output architecture to generate the proper filename and, much more importantly, set up the proper default install directory. This requires Perl as well as makensis to be present in order to make an installer, but that doesn't really seem like a too onerous of a requirement (NSIS being the big external dependency here.) Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2016-03-04 13:37:37 +08:00
!include /nonfatal "arch.nsh"
nsis: Use Program Files (x86) directory for nasm installation on x86-64 https://bugzilla.nasm.us/show_bug.cgi?id=3392365 Reported-by: Mat <mberchtold@gmail.com> Based-on-patch-by: Mat <mberchtold@gmail.com> Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2016-10-23 18:16:31 +08:00
!include /nonfatal "x64.nsh"
nsis: make nsis output automatically select architecture Make the NSIS output automatically select the output architecture to generate the proper filename and, much more importantly, set up the proper default install directory. This requires Perl as well as makensis to be present in order to make an installer, but that doesn't really seem like a too onerous of a requirement (NSIS being the big external dependency here.) Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2016-03-04 13:37:37 +08:00
Add NSIS script to make a Windows installer Here is an NSIS script for making a simple NASM package. It creates a NASM folder with some of the important binaries in it, as well as a simple batch file to get a CLI with the NASM folder included in the PATH. Expects to be built from inside the bin/ directory. Fairly primitive. Feedback welcome. - Shao
2009-04-07 10:07:37 +08:00
!define PRODUCT_NAME "Netwide Assembler"
!define PRODUCT_SHORT_NAME "nasm"
!define PACKAGE_NAME "${PRODUCT_NAME} ${VERSION}"
!define PACKAGE_SHORT_NAME "${PRODUCT_SHORT_NAME}-${VERSION}"
nasm.nsi: set compressor before MUI macros MULTIUSER_MUI may set own compressor so we need to set it earlies to success. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2009-09-24 01:14:32 +08:00
SetCompressor lzma
substitute nasm.nsi with new nasm2.nsi We always have "restore point" but such an action will allow us to test new installer in more wide audience. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2009-09-22 03:15:55 +08:00
!define MULTIUSER_EXECUTIONLEVEL Highest
!define MULTIUSER_MUI
!define MULTIUSER_INSTALLMODE_COMMANDLINE
nsis: make nsis output automatically select architecture Make the NSIS output automatically select the output architecture to generate the proper filename and, much more importantly, set up the proper default install directory. This requires Perl as well as makensis to be present in order to make an installer, but that doesn't really seem like a too onerous of a requirement (NSIS being the big external dependency here.) Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2016-03-04 13:37:37 +08:00
!define MULTIUSER_INSTALLMODE_INSTDIR "NASM"
!include "MultiUser.nsh"
substitute nasm.nsi with new nasm2.nsi We always have "restore point" but such an action will allow us to test new installer in more wide audience. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2009-09-22 03:15:55 +08:00
!insertmacro MULTIUSER_PAGE_INSTALLMODE
!insertmacro MULTIUSER_INSTALLMODEPAGE_INTERFACE
;--------------------------------
;General
;Name and file
Add NSIS script to make a Windows installer Here is an NSIS script for making a simple NASM package. It creates a NASM folder with some of the important binaries in it, as well as a simple batch file to get a CLI with the NASM folder included in the PATH. Expects to be built from inside the bin/ directory. Fairly primitive. Feedback welcome. - Shao
2009-04-07 10:07:37 +08:00
Name "${PACKAGE_NAME}"
Fix building in a separate directory from the source code The code to handle building in a separate directory had seriously bitrotted. This contains a number of fixes to make it possible, including bits like the documentation which never worked in the past. Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-05-17 11:30:09 +08:00
OutFile "${objdir}/${PACKAGE_SHORT_NAME}-installer-${ARCH}.exe"
substitute nasm.nsi with new nasm2.nsi We always have "restore point" but such an action will allow us to test new installer in more wide audience. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2009-09-22 03:15:55 +08:00
;Get installation folder from registry if available
InstallDirRegKey HKCU "Software\${PRODUCT_SHORT_NAME}" ""
;Request application privileges for Windows Vista
RequestExecutionLevel user
;--------------------------------
;Variables
Var StartMenuFolder
Var CmdFailed
;--------------------------------
;Interface Settings
Caption "${PACKAGE_SHORT_NAME} installation"
Fix building in a separate directory from the source code The code to handle building in a separate directory had seriously bitrotted. This contains a number of fixes to make it possible, including bits like the documentation which never worked in the past. Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-05-17 11:30:09 +08:00
Icon "${srcdir}/nsis/nasm.ico"
UninstallIcon "${srcdir}/nsis/nasm-un.ico"
substitute nasm.nsi with new nasm2.nsi We always have "restore point" but such an action will allow us to test new installer in more wide audience. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2009-09-22 03:15:55 +08:00
!define MUI_ABORTWARNING
;--------------------------------
;Pages
!insertmacro MUI_PAGE_COMPONENTS
!insertmacro MUI_PAGE_DIRECTORY
;Start Menu Folder Page Configuration
!define MUI_STARTMENUPAGE_REGISTRY_ROOT "HKCU"
!define MUI_STARTMENUPAGE_REGISTRY_KEY "Software\${PRODUCT_SHORT_NAME}"
!define MUI_STARTMENUPAGE_REGISTRY_VALUENAME "${PRODUCT_SHORT_NAME}"
!insertmacro MUI_PAGE_STARTMENU Application $StartMenuFolder
!insertmacro MUI_PAGE_INSTFILES
!insertmacro MUI_UNPAGE_CONFIRM
!insertmacro MUI_UNPAGE_INSTFILES
;--------------------------------
;Installer Sections
!insertmacro MUI_LANGUAGE English
Section "NASM" SecNasm
Sectionin RO
SetOutPath "$INSTDIR"
Fix building in a separate directory from the source code The code to handle building in a separate directory had seriously bitrotted. This contains a number of fixes to make it possible, including bits like the documentation which never worked in the past. Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-05-17 11:30:09 +08:00
File "${srcdir}/LICENSE"
File "${objdir}/nasm.exe"
File "${objdir}/ndisasm.exe"
File "${srcdir}/nsis/nasm.ico"
substitute nasm.nsi with new nasm2.nsi We always have "restore point" but such an action will allow us to test new installer in more wide audience. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2009-09-22 03:15:55 +08:00
;Store installation folder
WriteRegStr HKCU "Software\${PRODUCT_SHORT_NAME}" "" $INSTDIR
;Store shortcuts folder
WriteRegStr HKCU "Software\${PRODUCT_SHORT_NAME}\" "lnk" $SMPROGRAMS\$StartMenuFolder
nsis: Remove desktop bat link as well In case of installation procedure being used in a per-user fasion the display link to a bat file remain untouched at uninstallation time. Fix it. I hope this time all things go smooth. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2011-07-16 03:10:46 +08:00
WriteRegStr HKCU "Software\${PRODUCT_SHORT_NAME}\" "bat-lnk" $DESKTOP\${PRODUCT_SHORT_NAME}.lnk
substitute nasm.nsi with new nasm2.nsi We always have "restore point" but such an action will allow us to test new installer in more wide audience. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2009-09-22 03:15:55 +08:00
;
; the bat we need
StrCpy $CmdFailed "true"
FileOpen $0 "nasmpath.bat" w
IfErrors skip
StrCpy $CmdFailed "false"
FileWrite $0 "@set path=$INSTDIR;%path%$\r$\n"
FileWrite $0 "@%comspec%"
FileClose $0
CreateShortCut "$DESKTOP\${PRODUCT_SHORT_NAME}.lnk" "$INSTDIR\nasmpath.bat" "" "$INSTDIR\nasm.ico" 0
skip:
;Create uninstaller
WriteUninstaller "$INSTDIR\Uninstall.exe"
!insertmacro MUI_STARTMENU_WRITE_BEGIN Application
;Create shortcuts
CreateDirectory "$SMPROGRAMS\$StartMenuFolder"
StrCmp $CmdFailed "true" +2
CreateShortCut "$SMPROGRAMS\$StartMenuFolder\${PRODUCT_SHORT_NAME}-shell.lnk" "$INSTDIR\nasmpath.bat"
CreateShortCut "$SMPROGRAMS\$StartMenuFolder\${PRODUCT_SHORT_NAME}.lnk" "$INSTDIR\nasm.exe" "" "$INSTDIR\nasm.ico" 0
CreateShortCut "$SMPROGRAMS\$StartMenuFolder\Uninstall.lnk" "$INSTDIR\Uninstall.exe"
!insertmacro MUI_STARTMENU_WRITE_END
Add NSIS script to make a Windows installer Here is an NSIS script for making a simple NASM package. It creates a NASM folder with some of the important binaries in it, as well as a simple batch file to get a CLI with the NASM folder included in the PATH. Expects to be built from inside the bin/ directory. Fairly primitive. Feedback welcome. - Shao
2009-04-07 10:07:37 +08:00
SectionEnd
substitute nasm.nsi with new nasm2.nsi We always have "restore point" but such an action will allow us to test new installer in more wide audience. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2009-09-22 03:15:55 +08:00
Section "RDOFF" SecRdoff
Fix building in a separate directory from the source code The code to handle building in a separate directory had seriously bitrotted. This contains a number of fixes to make it possible, including bits like the documentation which never worked in the past. Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-05-17 11:30:09 +08:00
File "${objdir}/rdoff/ldrdf.exe"
File "${objdir}/rdoff/rdf2bin.exe"
File "${objdir}/rdoff/rdf2com.exe"
File "${objdir}/rdoff/rdf2ith.exe"
File "${objdir}/rdoff/rdf2ihx.exe"
File "${objdir}/rdoff/rdf2srec.exe"
File "${objdir}/rdoff/rdfdump.exe"
File "${objdir}/rdoff/rdflib.exe"
Add NSIS script to make a Windows installer Here is an NSIS script for making a simple NASM package. It creates a NASM folder with some of the important binaries in it, as well as a simple batch file to get a CLI with the NASM folder included in the PATH. Expects to be built from inside the bin/ directory. Fairly primitive. Feedback welcome. - Shao
2009-04-07 10:07:37 +08:00
SectionEnd
substitute nasm.nsi with new nasm2.nsi We always have "restore point" but such an action will allow us to test new installer in more wide audience. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2009-09-22 03:15:55 +08:00
Section "Manual" SecManual
SetOutPath "$INSTDIR"
Fix building in a separate directory from the source code The code to handle building in a separate directory had seriously bitrotted. This contains a number of fixes to make it possible, including bits like the documentation which never worked in the past. Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-05-17 11:30:09 +08:00
File "${objdir}/doc/nasmdoc.pdf"
nasm.nsi: fixup shortcut target on nasm manual There is no "manual.pdf" but "nasmdoc.pdf" instead. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2009-09-24 03:33:11 +08:00
CreateShortCut "$SMPROGRAMS\$StartMenuFolder\Manual.lnk" "$INSTDIR\nasmdoc.pdf"
Add NSIS script to make a Windows installer Here is an NSIS script for making a simple NASM package. It creates a NASM folder with some of the important binaries in it, as well as a simple batch file to get a CLI with the NASM folder included in the PATH. Expects to be built from inside the bin/ directory. Fairly primitive. Feedback welcome. - Shao
2009-04-07 10:07:37 +08:00
SectionEnd
nsis.nsi: add VS8 rules file to install Add "VS8 intergartion" section with appropriate files to be installed on user request. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2009-09-26 15:21:20 +08:00
Section "VS8 integration" SecVS8
nsis: make nsis output automatically select architecture Make the NSIS output automatically select the output architecture to generate the proper filename and, much more importantly, set up the proper default install directory. This requires Perl as well as makensis to be present in order to make an installer, but that doesn't really seem like a too onerous of a requirement (NSIS being the big external dependency here.) Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2016-03-04 13:37:37 +08:00
CreateDirectory "$INSTDIR\VSrules"
SetOutPath "$INSTDIR\VSrules"
Fix building in a separate directory from the source code The code to handle building in a separate directory had seriously bitrotted. This contains a number of fixes to make it possible, including bits like the documentation which never worked in the past. Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
2016-05-17 11:30:09 +08:00
File "${srcdir}/contrib/VSrules/nasm.README"
File "${srcdir}/contrib/VSrules/nasm.rules"
nsis.nsi: add VS8 rules file to install Add "VS8 intergartion" section with appropriate files to be installed on user request. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2009-09-26 15:21:20 +08:00
SectionEnd
substitute nasm.nsi with new nasm2.nsi We always have "restore point" but such an action will allow us to test new installer in more wide audience. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2009-09-22 03:15:55 +08:00
;--------------------------------
;Descriptions
;Language strings
LangString DESC_SecNasm ${LANG_ENGLISH} "NASM assembler and disassember modules"
LangString DESC_SecManual ${LANG_ENGLISH} "Complete NASM manual (pdf file)"
LangString DESC_SecRdoff ${LANG_ENGLISH} "RDOFF utilities (you may not need it if you don't know what is it)"
nsis.nsi: add VS8 rules file to install Add "VS8 intergartion" section with appropriate files to be installed on user request. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2009-09-26 15:21:20 +08:00
LangString DESC_SecVS8 ${LANG_ENGLISH} "Visual Studio 2008 NASM integration (rules file)"
substitute nasm.nsi with new nasm2.nsi We always have "restore point" but such an action will allow us to test new installer in more wide audience. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2009-09-22 03:15:55 +08:00
;Assign language strings to sections
!insertmacro MUI_FUNCTION_DESCRIPTION_BEGIN
!insertmacro MUI_DESCRIPTION_TEXT ${SecNasm} $(DESC_SecNasm)
!insertmacro MUI_DESCRIPTION_TEXT ${SecRdoff} $(DESC_SecRdoff)
!insertmacro MUI_DESCRIPTION_TEXT ${SecManual} $(DESC_SecManual)
nsis.nsi: add VS8 rules file to install Add "VS8 intergartion" section with appropriate files to be installed on user request. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2009-09-26 15:21:20 +08:00
!insertmacro MUI_DESCRIPTION_TEXT ${SecVS8} $(DESC_SecVS8)
substitute nasm.nsi with new nasm2.nsi We always have "restore point" but such an action will allow us to test new installer in more wide audience. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2009-09-22 03:15:55 +08:00
!insertmacro MUI_FUNCTION_DESCRIPTION_END
;--------------------------------
;Uninstaller Section
Add NSIS script to make a Windows installer Here is an NSIS script for making a simple NASM package. It creates a NASM folder with some of the important binaries in it, as well as a simple batch file to get a CLI with the NASM folder included in the PATH. Expects to be built from inside the bin/ directory. Fairly primitive. Feedback welcome. - Shao
2009-04-07 10:07:37 +08:00
Section "Uninstall"
substitute nasm.nsi with new nasm2.nsi We always have "restore point" but such an action will allow us to test new installer in more wide audience. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2009-09-22 03:15:55 +08:00
;
; files on HDD
nsis: Make sure the registry keys exist It was reported on nasm forum (http://forum.nasm.us/index.php?topic=1013.0) that if uninstallation procedure get stopped (for any reason) in a middle leading to read empty registry values an attempt to remove arbitrary files might happen. So make sure there are some sane values in registry. N.B: People, if you find some bug in nasm, don't write to forum, file bug directly in bugzilla, if it's not a bug we simply close it, otherwise we might miss serious problems like this one! Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2011-07-07 04:56:35 +08:00
IfFileExists "$INSTDIR" +3 +1
MessageBox MB_OK "No files found, aborting."
Abort
nsis: Inform a user about files being deleted Since a user might have some weird access rules on NTFS such as allow to write files but not to delete them it might happen that uninstallation procedure fails at deleting files but deleting registry keys still success, and in result a user might try to uninstall nasm for second time with registry keys corrupted. So prompt a user with files being deleted so he can double check what is going on. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2011-07-16 02:38:47 +08:00
MessageBox MB_YESNO "The following directory will be deleted$\n$INSTDIR" IDYES rm_instdir_true IDNO rm_instdir_false
rm_instdir_true:
RMDir /r /rebootok "$INSTDIR"
rm_instdir_false:
nsis: Remove desktop bat link as well In case of installation procedure being used in a per-user fasion the display link to a bat file remain untouched at uninstallation time. Fix it. I hope this time all things go smooth. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2011-07-16 03:10:46 +08:00
nsis: Make sure the registry keys exist It was reported on nasm forum (http://forum.nasm.us/index.php?topic=1013.0) that if uninstallation procedure get stopped (for any reason) in a middle leading to read empty registry values an attempt to remove arbitrary files might happen. So make sure there are some sane values in registry. N.B: People, if you find some bug in nasm, don't write to forum, file bug directly in bugzilla, if it's not a bug we simply close it, otherwise we might miss serious problems like this one! Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2011-07-07 04:56:35 +08:00
;
nsis: Remove desktop bat link as well In case of installation procedure being used in a per-user fasion the display link to a bat file remain untouched at uninstallation time. Fix it. I hope this time all things go smooth. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2011-07-16 03:10:46 +08:00
; Desktop link
ReadRegStr $0 HKCU Software\${PRODUCT_SHORT_NAME} "bat-lnk"
StrCmp $0 0 +1 +3
MessageBox MB_OK "Invalid path to a bat-lnk file, aborting"
Abort
IfFileExists $0 +3 +1
MessageBox MB_OK "No bat-lnk files found, aborting."
Abort
MessageBox MB_YESNO "The following file will be deleted$\n$0" IDYES rm_batlinks_true IDNO rm_batlinks_false
rm_batlinks_true:
Delete /rebootok "$0"
RMDir "$0"
rm_batlinks_false:
substitute nasm.nsi with new nasm2.nsi We always have "restore point" but such an action will allow us to test new installer in more wide audience. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2009-09-22 03:15:55 +08:00
;
nsis: Make sure the registry keys exist It was reported on nasm forum (http://forum.nasm.us/index.php?topic=1013.0) that if uninstallation procedure get stopped (for any reason) in a middle leading to read empty registry values an attempt to remove arbitrary files might happen. So make sure there are some sane values in registry. N.B: People, if you find some bug in nasm, don't write to forum, file bug directly in bugzilla, if it's not a bug we simply close it, otherwise we might miss serious problems like this one! Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2011-07-07 04:56:35 +08:00
; Start menu folder
substitute nasm.nsi with new nasm2.nsi We always have "restore point" but such an action will allow us to test new installer in more wide audience. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2009-09-22 03:15:55 +08:00
ReadRegStr $0 HKCU Software\${PRODUCT_SHORT_NAME} "lnk"
nsis: Make sure the registry keys exist It was reported on nasm forum (http://forum.nasm.us/index.php?topic=1013.0) that if uninstallation procedure get stopped (for any reason) in a middle leading to read empty registry values an attempt to remove arbitrary files might happen. So make sure there are some sane values in registry. N.B: People, if you find some bug in nasm, don't write to forum, file bug directly in bugzilla, if it's not a bug we simply close it, otherwise we might miss serious problems like this one! Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2011-07-07 04:56:35 +08:00
StrCmp $0 0 +1 +3
MessageBox MB_OK "Invalid path to a lnk file, aborting"
Abort
IfFileExists $0 +3 +1
MessageBox MB_OK "No lnk files found, aborting."
Abort
nsis: Inform a user about files being deleted Since a user might have some weird access rules on NTFS such as allow to write files but not to delete them it might happen that uninstallation procedure fails at deleting files but deleting registry keys still success, and in result a user might try to uninstall nasm for second time with registry keys corrupted. So prompt a user with files being deleted so he can double check what is going on. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2011-07-16 02:38:47 +08:00
MessageBox MB_YESNO "The following directory will be deleted$\n$0" IDYES rm_links_true IDNO rm_links_false
rm_links_true:
Delete /rebootok "$0\*"
RMDir "$0"
rm_links_false:
nsis: Remove desktop bat link as well In case of installation procedure being used in a per-user fasion the display link to a bat file remain untouched at uninstallation time. Fix it. I hope this time all things go smooth. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2011-07-16 03:10:46 +08:00
DeleteRegKey /ifempty HKCU "Software\${PRODUCT_SHORT_NAME}"
Add NSIS script to make a Windows installer Here is an NSIS script for making a simple NASM package. It creates a NASM folder with some of the important binaries in it, as well as a simple batch file to get a CLI with the NASM folder included in the PATH. Expects to be built from inside the bin/ directory. Fairly primitive. Feedback welcome. - Shao
2009-04-07 10:07:37 +08:00
SectionEnd
substitute nasm.nsi with new nasm2.nsi We always have "restore point" but such an action will allow us to test new installer in more wide audience. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2009-09-22 03:15:55 +08:00
;
; MUI requires this hooks
Function .onInit
!insertmacro MULTIUSER_INIT
nsis: Use Program Files (x86) directory for nasm installation on x86-64 https://bugzilla.nasm.us/show_bug.cgi?id=3392365 Reported-by: Mat <mberchtold@gmail.com> Based-on-patch-by: Mat <mberchtold@gmail.com> Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2016-10-23 18:16:31 +08:00
${If} ${RunningX64}
SetRegView 64
${EnableX64FSRedirection}
StrCpy $INSTDIR "$PROGRAMFILES64\${PRODUCT_SHORT_NAME}"
${Else}
StrCpy $INSTDIR "$PROGRAMFILES\${PRODUCT_SHORT_NAME}"
${EndIf}
substitute nasm.nsi with new nasm2.nsi We always have "restore point" but such an action will allow us to test new installer in more wide audience. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2009-09-22 03:15:55 +08:00
FunctionEnd
Add NSIS script to make a Windows installer Here is an NSIS script for making a simple NASM package. It creates a NASM folder with some of the important binaries in it, as well as a simple batch file to get a CLI with the NASM folder included in the PATH. Expects to be built from inside the bin/ directory. Fairly primitive. Feedback welcome. - Shao
2009-04-07 10:07:37 +08:00
substitute nasm.nsi with new nasm2.nsi We always have "restore point" but such an action will allow us to test new installer in more wide audience. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2009-09-22 03:15:55 +08:00
Function un.onInit
!insertmacro MULTIUSER_UNINIT
FunctionEnd
Reference in New Issue Copy Permalink