InstallAnywhere 2020
In some scenarios, you may need to generate multiple installers for the same application, each with a slightly different configuration. For example:
| • | You may want to provide different locale support for different platforms. |
| • | You may want to create two different editions of an application—with both editions containing most of the same content but diverging in a few select files. |
One way you could do this would be to create multiple InstallAnywhere projects, each with different settings. However, a much more efficient way of accomplishing this is to define different build configurations in the same project in InstallAnywhere. Each build configuration defines how InstallAnywhere builds an installer for a particular set of platforms, build distributions, JVMs, locales, and other settings. You can store as many build configurations with a project as necessary.
When you are building your InstallAnywhere project, you have the option of building a selected build configuration, all build configurations that exist in the project, or just a specified set of build configurations. For each build configuration that you build, InstallAnywhere generates a separate installer, each in its own directory.
To create and modify build configurations, use the Build Installers view on the Build page of the Advanced Designer. In this view, you can add, rename, copy, or delete a build configuration. This section of the documentation explains how.
From the Default Locale for Targets with Unsupported Languages list, select the language to use if the target machine’s operating system uses a language that is not supported by the installer. If the installer is started on a platform that uses an unsupported language, then the selected language will be used.
Note • For more information on the Default Locale for Targets with Unsupported Languages option, see Locales Subtab.
InstallAnywhere 2020 Help LibraryOctober 2019 |
Copyright Information | Flexera |