SPITOOL
SPITOOL is a utility for creating static plug-in information (SPI) files,
which contain registration data for ROM-based plug-ins.
The tool is normally invoked by BUILDROM, though it can be used independently (for
example, for test purposes).
Syntax conventions
All commands and options should be entered as explicitly stated. For
more information on the usual syntax conventions, see the BNF grammar section
in Symbian OS Library >> About the Symbian Developer Library
>> Documentation conventions.
SPITOOL command syntax
spitool [options] files directories
The tool creates an SPI file by concatenating the specified input
files, using the options specified.
You can specify the input files by specifying the full path to each
file, or by specifying a directory name, in which case all files from that
directory are included.
options
can be one or more of the following:
-t<SPIFileName>
|
<SPIFileName> is the name for the produced SPI
file (e.g. ecom.spi )
|
-d<TargetDir>
|
<TargetDir> is the directory where the SPI
file should be created. The directory name should end with a \ .
|
-i<Existing>
|
<Existing> is the path of an existing SPI file
to which to concatenate the specified input files.
If this option is used, then the specified file is used as a base
for the new output file. The output file will contain the contents of the
existing file with new input files appended. The location of the output file is
still specified using the -d and -t options.
|
-uid[1 | 2 | 3]=<UIDValue>
|
Specifies that input files should be filtered by their UID
values.
This option can be used multiple times, so a list of valid UID1
values can be specified, and similarly for UID2 and UID3 values. The UIDs of
each input file are compared with this list, and if a UID value matches a
relevant value in the UID lists, then that file is included in the SPI file. If
the file does not match any values, it is excluded.
Use 1, 2, or 3 in the option keyword to specify to which of the
three UIDs the filter should apply. <UIDValue> should be a
UID value in decimal or hexadecimal (0x....).
|
-existinguid[1 | 2 | 3]=<UIDValue>
|
Test that files concatenated in an existing SPI file use the
specified UID value. This allows the possibility of checking that the correct
type of files are being concatenated together.
Use 1, 2, or 3 in the option to specify to which of the three
UIDs the test should apply. <UIDValue> should be a UID value
in decimal or hexadecimal (0x....).
|
-existinguidcrc=<CRCValue>
|
Test that files concatenated in an existing SPI file use the
specified CRC checksum value. A file's CRC is generated from all three of its
UIDs.
<CRCValue> should be a value in decimal or
hexadecimal (0x....).
|
-hide <ResourceFileNames>
|
Marks a resource file as hidden in the SPI file.
<ResourceFileNames> is a list of resource file names
separated by a space or comma, which need to be marked as hidden in the SPI
file.
|