summaryrefslogtreecommitdiff
path: root/nasm.nsi
AgeCommit message (Collapse)AuthorFilesLines
2011-07-15nsis: Remove desktop bat link as wellCyrill Gorcunov1-3/+17
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-15nsis: Inform a user about files being deletedCyrill Gorcunov1-5/+10
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-07nsis: Make sure the registry keys existCyrill Gorcunov1-2/+14
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>
2009-09-27nasm.nsi: use "delete recursively" specificatorCyrill Gorcunov1-7/+1
Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2009-09-26nsis.nsi: add VS8 rules file to installCyrill Gorcunov1-0/+10
Add "VS8 intergartion" section with appropriate files to be installed on user request. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2009-09-23nasm.nsi: fixup shortcut target on nasm manualCyrill Gorcunov1-1/+1
There is no "manual.pdf" but "nasmdoc.pdf" instead. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2009-09-23nasm.nsi: fixup output nameCyrill Gorcunov1-1/+1
Sigh... It should be PACKAGE_SHORT_NAME rather then PRODUCT_SHORT_NAME. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2009-09-23nasm.nsi: set compressor before MUI macrosCyrill Gorcunov1-1/+2
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-23nasm.nsi: restore old output name and compressorCyrill Gorcunov1-1/+2
Othrewise build robot fails Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2009-09-23nasm.nsi: do not define VERSION twiceCyrill Gorcunov1-1/+0
VERSION is already defined in version.nsh no need to define it araing otherwise nsis compiler fails. Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
2009-09-21substitute nasm.nsi with new nasm2.nsiCyrill Gorcunov1-71/+158
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-07-06nasm.nsi: remove COPYING; add LICENSEH. Peter Anvin1-2/+2
The licensing information has been moved into file LICENSE. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2009-07-05nasm.nsi: in the "NASM shell", put NASM first in PATHH. Peter Anvin1-1/+1
In the "NASM shell", it makes sense for NASM to be first in the PATH, not last. That way if the user has more than one version of NASM installed, and one of them is global, the "NASM shell" for any one version will still pick up the proper version. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2009-07-05nasm.nsi: use LZMA compressionH. Peter Anvin1-1/+1
Using LZMA compression produces a significantly smaller installer binary. Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2009-07-05nasm.nsi: add additional rdf2bin aliasesH. Peter Anvin1-0/+4
Add additiona rdf2bin aliases to nasm.nsi Signed-off-by: H. Peter Anvin <hpa@zytor.com>
2009-04-06nasm.nsi: add COPYING to the list of files to packageH. Peter Anvin1-0/+2
2009-04-06nasm.nsi: add NASM Manual; automate version generationH. Peter Anvin1-0/+106
Add the NASM Manual (as a PDF) to the Windows installer, and abstract out the version number.