dragonleo/NSIS
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Documentation fixes and clarifications

Browse source 
git-svn-id: https://svn.code.sf.net/p/nsis/code/NSIS/trunk@6728 212acab6-be3b-0410-9dea-997c60f758d6
This commit is contained in:
anders_k 2016-03-27 23:24:43 +00:00
parent 2b5baa3639
commit e7ac6581e4
39 changed files with 315 additions and 429 deletions
Download patch file Download diff file Expand all files Collapse all files

12
Docs/src/usage.but
View file

@ -3,15 +3,15 @@
\H{usage} MakeNSIS Usage
NSIS installers are generated by using the 'MakeNSIS' program to compile a NSIS script (.NSI) into an installer executable.
The NSIS development kit installer sets up your computer so that you can compile a .nsi file by simply right-clicking on it in explorer, and selecting 'compile'.
The NSIS development kit installer sets up your computer so that you can compile a .nsi file by simply right-clicking on it in Explorer and selecting 'compile'.
If you want to use MakeNSIS on the command line, the syntax of the makensis command is:
If you want to use MakeNSIS on the command line, the syntax of makensis is:
\c makensis [ option | script.nsi | - ] [...]
\S1{usagereference} Options
\b /LICENSE displays a keen license page.
\b /LICENSE displays license information.
\b The /V switch followed by a number between 0 and 4 will set the verbosity of output accordingly. 0=no output, 1=errors only, 2=warnings and errors, 3=info, warnings, and errors, 4=all output.
@ -25,7 +25,7 @@ If you want to use MakeNSIS on the command line, the syntax of the makensis comm
\b /CMDHELP prints basic usage information for command (if specified), or all commands (if command is not specified).
\b /HDRINFO prints out information on what options were used to compile makensis was compiled with.
\b /HDRINFO prints information about which options were used to compile makensis.
\b /NOCD disables the current directory change to that of the .nsi file
@ -45,12 +45,10 @@ If you want to use MakeNSIS on the command line, the syntax of the makensis comm
\S1{usagenotes} Notes
\b Parameters are processed by order. \c{makensis /Ddef script.nsi} is not the same as \c{makensis script.nsi /Ddef}.
\b Parameters are processed in order. \c{makensis /Ddef script.nsi} is not the same as \c{makensis script.nsi /Ddef}.
\b If multiple scripts are specified, they are treated as one concatenated script.
\b On Windows 95, 98 and NT, below normal and above normal process priorities are not available. On those systems, below normal will actually set priority to idle and above normal will set to high.
\S1{usageenvironment} Environment variables
makensis checks a number of environment variables that tell it where to locate the things it needs in order to create installers. These variables include: