To check whether your definition actually produces the desired results, please go to the View Results tab of the Files steps.
Within a single file set, it causes an error if the installation paths for two files collide. For example, if you have added the contents of two different directories into the same folder in the distribution tree and both directories contain a file file.txt, building the project will fail with a corresponding error message. In this case, you have to exclude the file in one of the directory entries. This is only valid for files, sub-directory hierarchies on the other hand are merged and can overlap between multiple directory entries and explicitly added folders.
You can create new file sets with the
[New File Set]
action in the
add menu on the right side.
Each file set has its own "Installation directory" root. If you define custom roots that should be present
in multiple file sets, you have to duplicate them.
The default root of the distribution tree is labeled as "Installation directory" and
has a special icon. This
is the directory where your application will be installed on the target system. The directory
is dependent on user actions at the time of installation. In regular installers
a user can select an arbitrary directory where the application should be installed. For RPM
media files, a user can override the default directory with command line parameters. For
archives, the files are simply extracted into a commmon top-level directory.
The installation directory will only be created if you execute an "Install files" action in the installer configuration. By default, the "Install files" action is placed on the "Installation" screen. If your installer should not create an installation directory, you can ignore this root and remove the "Install files" action.
To learn more on the various installer modes, please see the corresponding help topic.
If you build installers for different platforms, that root is likely to be different for each platform. In that case, you can use a compiler variable for the name of the custom root and override its value for each media file.
The most common case would be to add a "Directory selection" screen to the screen sequence and set its variable name property to the variable that you've used as the name of the custom root. For the above example, that would be "rootDir" (without the ${installer:...} variable syntax).
Alternatively, you could use a "Set a variable" action to determine the location programmatically.
If a custom installation root is not bound at runtime or if it points to an invalid directory, the contained files will not be installed. There will be no error messages, if you require error handling, you can use a "Run a script" action before the "Install files" action with the appropriate error message and failure strategy.
Note: For archive media file types, custom installation roots are not installed. If you require these custom roots for your installation, you cannot use archives.
An alternative way to redirect installed files to different directories is to use the "Directory resolver" property of the "Install files" actions. Also, the "File filter" property of that action can be used to conditionally install files. The use of these properties is only recommended if you require their full flexibility. Otherwise, using custom installation roots and installation components is a better approach.
Enter
. To configure further properties of the folder, you can
edit the folder node (see below) to show the
folder property dialog.
DEL
key or using the corresponding
tool bar button or menu entry.
Some types of entries can be renamed by using the
[Rename] action on the right
side of the tree or from the context menu. The name of the entry can then be edited in-place.
Renaming entries is possible for:
ENTER
key while the entry is selected.
Editing entries is possible for:
For conditions that are evaluated at runtime or for adding platform dependent files, you should use files sets instead.