-
Compiler variables
Compiler variables that are defined on the
Compiler Variables tab can be overridden
on a per-media file basis. For example, this would be useful to adjust the
native library directories in
a launcher definition.
The variable table shows 4 columns:
-
Override marker
If you have overriden a variable by editing the value column, the first column will
display a
marker
to indicate that that variable has been overridden. In that case, the
reset button column will display a button to restore the original value.
-
Variable name
Shows the name of the variable.
-
Variable value
Shows the value of the variable. This column is editable. To override the variable,
double-click on the desired cell in this column and edit the value. The override marker
column and the reset button column will then show that the variable has been overridden.
-
Reset button
If a variable has been overriden, this column shows a [Reset] button that
allows you to restore the original value as defined on the
Compiler Variables tab.
Overriding compiler variables on a per-media file basis is also possible from the
command line and from the
ant task.
-
Media file name
The file name pattern defined in the
Media File Options tab
determines the actual name of the media file. If you want to override that pattern,
you can enter an individual name here. To enter an individual name, select the
custom name radio button and enter a file name in the text field below it.
-
Principal language
By default, the language used by an installer is governed by the setting on the
Languages tab. If you would like to
generate installers with fixed languages, you leave those settings at their default values
and override the principal language and custom localization file here.
You can change the principal language for all media files or on a per-media file basis from the
command line or from the
ant task by defining the variable
LANGUAGE_ID
with the 2-letter ISO code of the desired language (see
http://www.w3.org/WAI/ER/IG/ert/iso639.htm).
-
Exclude components
Here, you can select components that should not be distributed by
selecting their attached check boxes. This is useful if you have installation components that do not work with
specific media files, such as a Windows-only extension, for example.
-
Exclude files
This step is useful to tailor your distribution to platform-specific needs. The distribution
tree is shown in expanded form and shows all files. This is unlike the distribution
tree in the Files step which shows the
definition of the distribution tree.
Each file and subdirectory has a check box attached. If you select that check box, the entry will
not be distributed. Selections of subdirectories are recursive. If you select a
subdirectory, its contents are hidden from the tree since they will be excluded anyway.
-
Exlude launchers
This step is complementary to the "Exclude files" screen where launchers are not shown.
Each launcher has a check box attached. If you select that check box, the launcher will
not be generated.
-
Exclude screens
If you some screens of the installer or uninstaller should not be shown for this media file,
you can exclude those screens by selecting their attached check boxes. Note that for
more complex cases
you can also skip screens by entering a condition property in the
screens configuration.
This customization category is not shown for archives.