MAKSYM/MAKSYMROFS
MAKSYM/MAKSYMROFS tool is used to create a symbol file, which lists the
addresses of every global and exported function in the ROM. It reads a log file
to generate the symbol file. The log file contains information about the
contents of the ROM or ROFS image.
MAKSYM reads the log file which is created by ROMBUILD when building a
ROM image. MAKSYMROFS reads the log file which is created by ROFSBUILD when
building a ROFS image. The command syntax for MAKSYM and MAKSYMROFS is the
same.
Syntax conventions used here
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.
MAKSYM command syntax
MAKSYM <logfile> [<outfile>]
<logfile>
|
This is the name of the log file generated by the
ROMBUILD tool.
|
<outfile>
|
This is the name for the MAKSYM output file. If not specified, it
defaults to <ROMimagename>.symbol .
|
By default, ROMBUILD produces a log file called
ROMBUILD.LOG
, which is passed to MAKSYM tool in the following way:
> MAKSYM rombuild.log
This will generate an output text file (Symbolic information file)
called <romimagename>.symbol
.
The file contains all the global variables along with their address and
length. For example, the start of EKERN.EXE
looks like this:
From \Epoc32\Release\Misa\UREL\ekern.exe
50003040 0094 _E32Startup
500030d4 002c ImpDma::Init1(void)
50003100 0004 ImpDma::Init3(void)
50003104 0008 ImpDma::MaxBlockSize(void)
In this example, the function ImpDma::Init1()
starts at
address 0x500030d4
and is 0x2c
bytes long.
Notes:
-
If you are distributing ROM images for testing, it is also useful
to supply the symbolic information file for that image.
-
If you re-build the ROM image you must also rebuild the symbolic
information file using MAKSYM.