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

better explain what compiler flags mean and how flow control instructions should be used around them

Browse source 
git-svn-id: https://svn.code.sf.net/p/nsis/code/NSIS/trunk@5186 212acab6-be3b-0410-9dea-997c60f758d6
This commit is contained in:
kichik 2007-07-04 17:52:47 +00:00
parent d2c161f2da
commit ef34c07654
1 changed files with 20 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

21
Docs/src/compilerflags.but
View file

@ -1,6 +1,25 @@
\S1{flags} Compiler Flags
The following commands change how the compiler generates code and compresses data. Unless otherwise noted, these commands are valid anywhere in the script, and effect every line below where each one is placed (until overridden by another command).
The following commands affect how the compiler generates code and compresses data. Unless otherwise noted, these commands are valid anywhere in the script, and effect every line below where each one is placed (until overridden by another command). They cannot be jumped over using \R{flowcontrol}{flow control insutrctions}.
For example, in the following script, blah.dat will never be overwritten.
\c ${If} $0 == 0
\c SetOverwrite on
\c ${Else}
\c SetOverwrite off
\c ${EndIf}
\c File blah.dat # overwrite is always off here!
Instead, the following should be used.
\c ${If} $0 == 0
\c SetOverwrite on
\c File blah.dat
\c ${Else}
\c SetOverwrite off
\c File blah.dat
\c ${EndIf}
\S2{asetallowskipfiles} AllowSkipFiles