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

Some more bold defaults

Browse source 
git-svn-id: https://svn.code.sf.net/p/nsis/code/NSIS/trunk@1615 212acab6-be3b-0410-9dea-997c60f758d6
This commit is contained in:
kichik 2002-11-07 23:40:57 +00:00
parent 21bd819e3e
commit 839eb3fe36
1 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

10
Docs/src/compilerflags.but
View file

@ -4,30 +4,30 @@ The following commands change how the compiler generates code and compresses dat
\S{asetcompress} SetCompress
\c auto|force|off
\c \\<b\\>auto\\</b\\>|force|off
This command sets the compress flag which is used by the installer to determine whether or not data should be compressed. Typically the SetCompress flag will effect the commands after it, and the last SetCompress command in the file also determines whether or not the install info section and uninstall data of the installer is compressed. If compressflag is 'auto', then files are compressed if the compressed size is smaller than the uncompressed size. If compressflag is set to 'force', then the compressed version is always used. If compressflag is 'off' then compression is not used (which can be faster). Note that this option has no effect on bzip2 installers (compression is always used on bzip2 installers).
\S{asetcompressor} SetCompressor
\c zlib|bzip2
\c \\<b\\>zlib\\</b\\>|bzip2
This command sets the compression algorithm used to compress files/data in the installer. Options are ZLib or BZip2. ZLib (the default) uses deflate compression. This mode uses less memory at runtime and is faster. BZip2 compression is usually better for large installers, but it is slower and uses a lot more memory at runtime.
\S{asetdatablockoptimize} SetDatablockOptimize
\c on|off
\c \\<b\\>on\\</b\\>|off
This command tells the compiler whether or not to do datablock optimizations. Datablock optimizations have the compiler check to see if any data being added to the data block is already in the data block, and if so, it is simply referenced as opposed to added (can save a little bit of size). It is highly recommended to leave this option on.
\S{asetdatesave} SetDateSave
\c on|off
\c \\<b\\>on\\</b\\>|off
This command sets the file date/time saving flag which is used by the File command to determine whether or not to save the last write date and time of the file, so that it can be restored on installation. Valid flags are 'on' and 'off'. 'on' is the default.
\S{asetoverwrite} SetOverwrite
\c on|off|try|ifnewer
\c \\<b\\>on\\</b\\>|off|try|ifnewer
This command sets the overwrite flag which is used by the File command to determine whether or not the file should overwrite any existing files that are present. If overwriteflag is 'on', files are overwritten (this is the default). If overwriteflag is 'off', files that are already present are not overwritten. If overwriteflag is 'try', files are overwritten if possible (meaning that if the file is not able to be written to, it is skipped without any user interaction). If overwriteflag is 'ifnewer', then files are only overwritten if the existing file is older than the new file (note that when in 'ifnewer' mode, the destination file's date is set, regardless of what SetDateSave is set to).