This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallAnywhere
- :
- InstallAnywhere Knowledge Base
- :
- Using a BuildProperties.xml File
Subscribe
- Mark as New
- Mark as Read
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Using a BuildProperties.xml File
Using a BuildProperties.xml File
Summary
Information on how to use a BuildProperties.xml file for building installers.Synopsis
You can use a build properties XML file, such as BuildProperties.xml, to pass build properties to the command-line builder in a single file. To use this properties file, pass the -p argument with the path and name of the build properties file to build.exe:build.exe C:\MySetups\MyProduct.iap_xml -p C:\Path\BuildPropeties.xmlIf you do not provide an absolute path to your build properties file, the builder looks for it in the same directory as your project. The settings that are specified in the .xml file override the build settings in the project.
InstallAnywhere also supports the use of Ant properties in buildproperties.xml. An Ant property can be defined in the buildproperties.xml using:
<property name="ia.home" value="D:\\IA_Codebase\\main" />
Discussion
Many of the settings that you can configure in the Advanced Designer can also be set in a BuildProperties.xml file. The following tables correlate the options in the Advanced Designer with settings in the BuildProperties.xml file.Option | File Setting |
---|---|
General Settings > Send stderr to | InstallerStdErrRedirect="<path_to_file>" |
General Settings > Send stdout to | InstallerStdOutRedirect="<path_to_file>" |
Platforms > Default UNIX Installer UI Mode > Installer UI Mode | UnixDefaultUI="<Silent/GUI/Console>" |
Platforms > Default Windows UI Mode > Installer UI Mode | WindowsDefaultUI="<Silent/GUI/Console>" |
Platforms > Default Windows UI Mode > Installer UI Mode (Pure 64-bit) | Windows64DefaultUI="<Silent/GUI/Console>" |
JVM Settings > Valid VM list | InstallerValidVMList="<1.5+, 1.8*>" |
JVM Settings > Minimum Heap Size | InstallerInitialHeapSize="<16777216>" |
JVM Settings > Maximum Heap Size | InstallerMaxHeapSize="<50331648>" |
Look & Feel Settings > Auto populate labels when saving | AutoPopulateLabels="<true/false>" |
Components > Auto-clean when building | AutoCleanComponents="<true/false>" |
Build Installers > Select Build Configuration | Create a <configuration> element for each build configuration that you want to build, using the following syntax: <configuration name="name_of_build_configuration"> <webInstaller enable="true/false" optimize="true/false"> <language>en/ja</language> </webInstaller> <cdRomInstaller enable="true/false" optimize="true/false" /> <mergeModule enable="true/false" optimize="true/false" readOnly="true/false" /> <locales> <localeSuffix>en</localeSuffix> <localeSuffix>de</localeSuffix> </locales> <target platform="aix/hpux/solaris/hpux/unixwithvm/macosx/java/unix/windows" buildWithVM="true/false" buildWithNoVM="true/false" outputDir="myOutputDir" bundledVM="path_to_file" /> </configuration> Regarding each <target> element, note the following: ? Each <target> element appends one new target to those already in the build configuration. ? There can be multiple <target> elements. ? The outputDir and bundledVM attributes are optional. ? Each <target> element must include a buildWithVM attribute, a buildWithNoVM attribute, or both. Important: The following subelements of the <configuration> element can also be specified outside of a <configuration> element. However, those elements defined within a <configuration> element override those defined elsewhere. |
Build Installers > Build Output Location | BuildOutputLocation="<path_to_directory>" |
[Working Directory] | BuildWorkdirLocation="<path_to_directory>" Note: The working directory, which is used to store all temporary files (such as the build log and the locales directory) is set by default to the InstallAnywhere project directory. It is not specifically set in the Advanced Designer user interface. |
Build Targets > OS X | BuildMacOSXWithVM="<true/false>" BuildMacOSXWithoutVM="<true/false>" WindowsVMpackLocation="<path_to_file>" WantAuthenticationMacOSX="<true/false>" WantAuthenticationMacOSXShowGUI="<true/false>" |
Build Targets > Windows | BuildWindowsWithVM="<true/false>" BuildWindowsWithoutVM="<true/false>" WindowsVMpackLocation="<path_to_file>" WindowsConsoleLauncher="<true/false>" |
Build Targets > Windows_Pure_64_Bit | BuildWindows64WithVM="<true/false>" BuildWindows64WithoutVM="<true/false>" Windows64VMpackLocation="<path_to_file>" |
Build Targets > AIX | BuildAIXWithVM="<true/false>" BuildAIXWithoutVM="<true/false>" AIXVMpackLocation="<path_to_file>" |
Build Targets > HP-UX | BuildHPUXWithVM="<true/false>" BuildHPUXWithoutVM="<true/false>" HPUXVMpackLocation="<path_to_file>" |
Build Targets > Linux | BuildLinuxWithVM="<true/false>" BuildLinuxWithoutVM="<true/false>" LinuxVMpackLocation="<path_to_file>" |
Build Targets > Solaris | BuildSolarisWithVM="<true/false>" BuildSolarisWithoutVM="<true/false>" SolarisVMpackLocation="<path_to_file>" |
Build Targets > Unix (All) | BuildUnixAll="<true/false>" |
Build Targets > UNIX_with_VM | BuildNamedUnixWithVM="<true/false>" BuildNamedUnixWithoutVM="<true/false>" NamedUnixVMpackLocation="<path_to_file>" NamedUnixTitle="<name_of_unix>" |
Build Targets > Other Java-Enabled Platforms | BuildPureJava="<true/false>" |
[Not available in the Advanced Designer] | OverrideAllPlatformSettings="<true/false>" |
Distribution > Build Web Installers | BuildWebInstaller="<true/false>" |
Distribution > Optimize [Web] Installer Size by Platform and Tags | OptimizeWebInstaller="<true/false>" |
Distribution > Web page displays in | This option is set within a <webInstaller> element inside of a build configuration element, <configuration>: <configuration name="<name_of_build_configuration>"> <webInstaller> <language><en/ja></language> </webInstaller> ? </configuration> |
Distribution > Build CD-ROM installers | BuildCDROMInstaller="<true/false>" |
Distribution > Optimize [CD-ROM] Installer Size by Platform and Tags | OptimizeCDROMInstaller="<true/false>" |
Distribution > Build Merge Module Template | BuildMergeModule="<true/false>" |
Distribution > Optimize Merge Module/Template Size by Platform and Tags | OptimizeMergeModule="<true/false>" |
Distribution > Read Only | BuildReadOnlyMergeModule="<true/false>" |
Additional Information
InstallAnywhere includes a build properties file template named BuildProperties.xml:IA_HOME/resource/build/BuildProperties.xml
This template file provides a sample of all possible build settings; you can use it as a template to meet your build requirements.
Add Supported Locales At Build Time Through Ant Or A Build Properties File
Setting the Product Version at Build Time
No ratings