Output Files at the End of the Build Process
The following types of files are generated at the end of the image build
process:
-
OBY file: This is the final ROMBUILD or ROFSBUILD OBY file containing
configuration details of the ROM/ROFS image.
-
Log file: This file contains a log of the binaries that the ROMBUILD
tool loads and processes in order to build a ROM image. This file is primarily
used for debugging purposes.
The following is an extract from a .log file.
Creating Rom image h4hrp_001.techview.IMG
MemModel: 2
ChunkSize: 00100000
PageSize: 00001000
Loading E32Image file \epoc32\release\ARMV5\urel\_h4hrp_ekern.exe
compression format:0x101f7afc
Loading E32Image file \epoc32\release\ARMV5\urel\_h4hrp_kaomap.dll
compression format:0x101f7afc
Loading E32Image file \epoc32\release\ARMV5\urel\_h4hrp_dma.dll
compression format:0x101f7afc
Loading E32Image file \epoc32\release\ARMV5\urel\_h4hrp_ecust_tv.dll
compression format:0x101f7afc
Loading E32Image file \epoc32\release\ARMV5\urel\_h4hrp_exmoncommon.dll
compression format:0x101f7afc
.
.
.
-
Dir file: This file contains a list of the source directories from
which the binaries are accessed, and the corresponding directories in the
device where they are placed. The following is an extract from a .dir file.
private\101F7988\esock_tr.cmi \epoc32\data\z\private\101F7988\esock_tr.cmi
private\101F7988\etel.cmi \epoc32\data\z\private\101F7988\etel.cmi
private\101F7989\backup_registration.xml \epoc32\data\z\private\101F7989\backup_registration.xml
Private\101F7989\Bluetooth\bluetooth_stack.ini \epoc32\data\Z\Private\101F7989\Bluetooth\bluetooth_stack.ini
Private\101F7989\Bluetooth\cmdq.ini \epoc32\data\Z\Private\101F7989\Bluetooth\cmdq.ini
Private\101F7989\Bluetooth\corehci_symbian.ini \epoc32\data\Z\Private\101F7989\Bluetooth\corehci_symbian.ini
Private\101F7989\Bluetooth\hctl_bcsp.ini \epoc32\data\Z\Private\101F7989\Bluetooth\hctl_bcsp_port3.ini
.
.
.
-
Symbol file: This file lists the various binaries used in the build
processes. For each binary, the symbol file also lists the executed functions,
their corresponding start and virtual addresses, and . The following is an
extract from a .symbol file.
From \epoc32\release\ARMV5\urel\_h4hrp_ekern.exe
8001c000 00c8 __this_must_go_at_the_beginning_of_the_kernel_image k_entry_.o(.emb_text)
8001c044 0000 btrace_fiq k_entry_.o(.emb_text)
8001c064 0000 HandleIrq k_entry_.o(.emb_text)
8001c090 0000 btrace_irq k_entry_.o(.emb_text)
8001c0c8 0014 _E32Startup k_entry_.o(.emb_text)
8001c0c8 0000 __dso_handle k_entry_.o(.emb_text)
.
.
.
-
The ROM/ROFS image file
Note:In case you build multiple images, a separate file of
each of the listed types is generated for every image.