# HG changeset patch # User fturovic # Date 1271449774 18000 # Node ID 9654af560a30e633edfd44aad05d8e05146dba9d # Parent 6004c3763d66fb478d93eb2e192175aba49a5944 adding missing .ini file to product plugin diff -r 6004c3763d66 -r 9654af560a30 core/com.nokia.carbide.cpp.doc.user/html/debugger/watchpoints/setting_watchpoints.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/debugger/watchpoints/setting_watchpoints.htm Fri Apr 16 14:48:20 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/watchpoints/setting_watchpoints.htm Fri Apr 16 15:29:34 2010 -0500 @@ -51,6 +51,6 @@

Watchpoints overview

- + diff -r 6004c3763d66 -r 9654af560a30 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 Apr 16 14:48:20 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/ROM_build_settings.html Fri Apr 16 15:29:34 2010 -0500 @@ -5,7 +5,7 @@

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.

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.2\S60_5th_Ed\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:

Symbian OS components making up a set of releasables

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

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 +Note that your SDK and working directory should be on the same drive, otherwise some of the rombuild scripts will fail.