IzPack offers the possibility to You can set a list of default installation directories depending on the target installation platform.
When the compiled installer is executed, IzPack chooses the one matching default that matches the assigned platform.
This can be achieved by explicitely setting variables with the The prefix: TargetPanel.dir
is used to specify variables related to setting the default installation directory.
IzPack recognizes this as a built-in variable which can be user-modified.
...
Code Block | ||||
---|---|---|---|---|
| ||||
<resources> <res id="TargetPanel.dir.windows" src="@{izpack.dir.app}/installpath.windows.txt"/> <res id="TargetPanel.dir.unix" src="@{izpack.dir.app}/installpath.unix.txt"/> </resources> |
to
Code Block | ||||
---|---|---|---|---|
| ||||
<variables> <variable name="TargetPanel.dir.windows" value="C:/MyApp"/> <variable name="TargetPanel.dir.unix" value="/usr/local/myapp"/> </variables> |
This uses the following variable search order to determine the default directory to display:
...
- aix
- debian_linux
- fedora_linux
- freebsd
- hp_ux
- linux
- mac
- mac_osx
- mandrake_linux
- mandriva_linux
- os_2
- red_hat_linux
- sunos
- sunos_x86
- sunos_sparc
- suse_linux
- unix
- ubuntu_linux
- windows
- windows_7
- windows_8
- windows_xp
- windows_2003
- windows_vista
Differences The DEFAULT_INSTALL_PATH variable is initialised to <PARENT_DIRECTORY>/$APP_NAME where <PARENT_DIRECTORY> is determined by:
OS | Parent Directory |
---|---|
Windows | ProgramFiles environment variable |
Mac OSX | /Applications |
Others | /usr/local/ if writeable, or System.getProperty("user.home") if not |
Changes from 4.3.6
...
Changes from earlier versions
Prior to 4.3.6In 4.3.5, resources were used rather than variables. Resources were searched for with the following names
...