Building RPM Installer Projects

InstallShield 11 Universal

When you click Build to build your RPM Installer project, the build is created using the build configuration that is currently selected in the Releases view.

This project type can only be built on a development machine with RPM installed.

The type of build configuration you select or add and the value of its properties determine the following:

• Whether the project will be built as a product that can be installed. This is determined by selecting and configuring an RPM Build Configuration.
• Whether the project will be built as an RPM assembly. This is determined by selecting and configuring an RPM Assembly Build Configuration, resulting in an RPM assembly that can be installed by the following types of projects:
  
  • A Universal Installer that is built as a product
  • A Condenser Installer that is built as a product
  • An RPM Installer that is built as a product
  • A Universal Dynamic Suite that was built with a Dynamic Suite Build Configuration
  • A Condenser Dynamic Suite that was built with a Dynamic Suite Build Configuration
• Which platform will be targeted. This is determined by setting the build configuration's Platform property.
• Whether this build can target machines both with and without RPM installed. This is determined by setting the Platform Support/Linux/Include Support for Non-RPM Platforms property to "True."

You specify which platforms your RPM Installer project should be able to target in the Files and Folders view Platforms property. Then you set each build configuration's Platform property to the platform it should target.

You need to add and configure one build configuration for each targeted platform.

An RPM Build Configuration builds the project into a fully installable product, and its output files are named <projectName>.uip and assembly.dat. An RPM Assembly Build Configuration builds the project into an RPM assembly, and its output is assembly.dat.

An RPM assembly can also reference other RPM and non-RPM assemblies. For non-RPM assemblies to be registered by RPM on the target machine, however, the RPM Installer project's Platform Support/Linux/RPM Integration Enabled property (in the Releases view) must have been set to "True."

If a java.lang.OutOfMemoryError is received, the size of your project is too large for the default heap size (16MB). This can be increased in the following properties:

• the Java Arguments property of the Distribution
• a .ja file located in the same directory as the build output

The syntax for increasing the heap size is as follows:

%IF_EXISTS%("INIT_HEAP_SIZE", "@INIT_HEAP_SIZE@20m")
%IF_EXISTS%("MAX_HEAP_SIZE", "@MAX_HEAP_SIZE@40m")

See Also

Creating an RPM Installer Project