The MakeSIS tool generates unsigned Software Installation (SIS) files based on the information provided in package (PKG) files.
makesis [OPTIONS] <ARGS>
The following table lists the options supported by the MakeSIS tool.
Options | Description | Usage |
---|---|---|
-h |
Displays the help for PKG file format. |
makesis [-h] |
-i |
Displays the Open SSL licence. |
makesis [-i] |
-v |
Displays verbose output. |
makesis [-v] |
-s |
Generates a ROM stub file. See Notes for more information. |
makesis [-s] [-d directory] pkgfile |
-c |
Reports an error if the generated SIS file is not compatible with the InterpretSIS tool for preinstall. |
makesis [-c] [-d directory] pkgfile |
The following table lists the arguments to be specified with the MakeSIS tool.
Arguments | Description |
---|---|
-d directory |
Specifies absolute paths in PKG files or paths relative to the current directory. |
pkgfile |
Specifies the PKG file, for which a SIS file is generated. |
sisfile |
Specifies the name of the generated SIS file. If not specified, the output SIS filename is derived from the name of the PKG file, but with a SIS file extension. |
A stub SIS file is created by the software installer on the Symbian device after a package has been installed. It details which files were installed and where, and is used when uninstalling and upgrading the package. For pre-installed applications in ROM, makesis -s can be used to create a stub SIS file.
Stub files that are created, contain a fixed date/time stamp of 2004/01/01 00:00.
You can use the –d argument with the EPOCROOT environment variable to avoid using absolute paths in PKG files or relative paths to the current directory.
By default, binaries are built to the epoc32 tree. So, if files are described in the PKG file as, for example:
"epoc32\release\armv5\urel\HelloWorld.exe"-"!:\sys\bin\HelloWorld.exe" "epoc32\release\armv5\urel\z\resource\apps\HelloWorld.rsc"-"!:\resource\apps\HelloWorld.rsc"
then MakeSIS can be invoked from any location using:
makesis -d%EPOCROOT% HelloWorld.pkg