|
|
||
MakeSIS - the Installation File Generator
Installation files are created using the Installation File Generator,
MakeSIS.exe, based on a specification defined in a package control
file. This documentation provides an overview of the information specified in
the package file, and of the installation file creation process.
A package control file (extension .pkg) defines the files
to be packaged into an installation file (extension .sis). The
information defined in the package file includes:
the names and locations on the developer's PC of all the files to be included in the installation file. In addition to files installed in every installation, these may include a number of language specific resource files, only one of which is installed on the target phone.
the location on the target phone to which the files are to be installed.
details of the dependencies upon other components required by the
application, e.g. common libraries supplied as separate sis
files — optional. This information is used to ensure that libraries are
deleted only if they are not needed by other applications.
licence agreements which can be displayed during installation — optional.
A link to the canonical definition of the package file format is given below.
The diagram below provides a brief overview of how the Installation
File Generator is used, and shows some of the file types which might be bundled
in a sis installation file. The types of files included are
dependent on the programming language and on the nature of the application.
Installation files may also include other installation files.
The Installation File Generator package file (pkg) defines
the location of source component files on the PC, the target path and filename,
and other installation information. The process of preparing components for
installation is therefore:
Develop an application
Debug/test application on the Emulator.
Ensure that all components of the application are in native Symbian OS format; see the sections on font, image and sound file utilities.
Create a package file.
Run the Installation File Generator on the package file.
Sign the the installation file using the Installation File Signer.