# HG changeset patch # User fturovic # Date 1285351927 18000 # Node ID 4036e1c78a68f53d327ae4e517cf10d631226bda # Parent f54753dc7b54c79fd83fafb44ed4a4918b7fdd81 additional TOC changes and page editing diff -r f54753dc7b54 -r 4036e1c78a68 core/com.nokia.carbide.cpp.doc.user/html/reference/ROM_build_settings.html --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/ROM_build_settings.html Fri Sep 24 12:50:36 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/ROM_build_settings.html Fri Sep 24 13:12:07 2010 -0500 @@ -1,42 +1,42 @@ - -ROM Builder pane - - - - -

ROM Builder pane

-

Use the ROM Builder pane to specify commands and a working directory for building a GUI ROM Image. The tool used to build GUI ROM images is called buildrom and can typically be found in your SDK path, for example in the \Symbian\9.1\S60_3rd\Epoc32\tools directory. The tool used to build text shell images is called ROM. The ROM image generated from the ROM building process specifies a base address for the image to run at. This might be an address in RAM or ROM. The image must be downloaded to the device at this address.

-

Building a ROM requires that the following are available, or have been successfully created:

- -

Rom build assembles executable and data files into a ROM image.

-

Executables are pre-processed, relocated, and have their imports and exports bound for a ROM image based at some given virtual address. The files, base address of the ROM, and various other parameters are specified by means of the obey file. This is a file of type .oby and is a text file containing statements that specify how the ROM image is to be built. A .oby file can include other files in the same way that files containing C++ source can #include other C++ files. By convention, the included files have the .iby file type. This structure allows flexibility in the way that ROM images are defined.

-

NOTE The ROM image will be rebuilt for any target whenever a change to the project occurs; except for WINSCW targets.

-

-

Figure 1. ROM Builder pane

-
Table 1. ROM Build Settings —items
- - - - - - - - - - -
NameFunction
ROM Build Command Line

Enter commands to build the GUI ROM Image. For example, the following sample command is used for building a techview - rom image for a H4 reference board.

-

buildrom -D_FULL_DEBUG -DRVCT -DSTOP_MODE_DEBUGGING -D_EABI=ARMV5 h4hrp techview -oh4.img

Working Directory

Specify the working directory for building the ROM Image. Typically, the working directory is the folder where you need to have your rom image built. -Note that your sdk and working directory should be on -the same drive, otherwise some of the rombuild scripts will fail.

-
- - - - + +ROM Builder pane + + + + +

ROM Builder pane

+

Use the ROM Builder pane to specify commands and a working directory for building a GUI ROM Image. The tool used to build GUI ROM images is called buildrom and can typically be found in your SDK path, for example in the \Symbian\9.4\S60_5rd\Epoc32\tools directory. The tool used to build text shell images is called ROM. The ROM image generated from the ROM build process specifies a base address for the image to run at. This might be an address in RAM or ROM. The image must be downloaded to the device at this address.

+

Building a ROM requires that the following are available, or have been successfully created:

+ +

Rom build assembles executable and data files into a ROM image.

+

Executables are pre-processed, relocated, and have their imports and exports bound for a ROM image based at some given virtual address. The files, base address of the ROM, and various other parameters are specified by means of the obey file. This is a file of type .oby and is a text file containing statements that specify how the ROM image is to be built. A .oby file can include other files in the same way that files containing C++ source can #include other C++ files. By convention, the included files have the .iby file type. This structure allows flexibility in the way that ROM images are defined.

+

NOTE The ROM image will be rebuilt for any target whenever a change to the project occurs; except for WINSCW targets.

+

+

Figure 1. ROM Builder pane

+
Table 1. ROM Build Settings —items
+ + + + + + + + + + +
NameFunction
ROM Build Command Line

Enter commands to build the GUI ROM Image. For example, the following sample command is used for building a techview + rom image for a H4 reference board.

+

buildrom -D_FULL_DEBUG -DRVCT -DSTOP_MODE_DEBUGGING -D_EABI=ARMV5 h4hrp techview -oh4.img

Working Directory

Specify the working directory for building the ROM Image. Typically, the working directory is the folder where you need to have your rom image built. +Note that your sdk and working directory should be on +the same drive, otherwise some of the rombuild scripts will fail.

+
+ + + + \ No newline at end of file diff -r f54753dc7b54 -r 4036e1c78a68 core/com.nokia.carbide.cpp.doc.user/html/reference/reference.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/reference.htm Fri Sep 24 12:50:36 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/reference.htm Fri Sep 24 13:12:07 2010 -0500 @@ -11,9 +11,39 @@

Reference

This section provides reference information on the Carbide IDE including:

diff -r f54753dc7b54 -r 4036e1c78a68 core/com.nokia.carbide.cpp.doc.user/tocCarbide.xml --- a/core/com.nokia.carbide.cpp.doc.user/tocCarbide.xml Fri Sep 24 12:50:36 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/tocCarbide.xml Fri Sep 24 13:12:07 2010 -0500 @@ -105,15 +105,16 @@ - - - - + + + + + @@ -239,13 +240,13 @@ - - - - + + + + - - + +