Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/launch/images/page_debug_main.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/launch/images/page_main_run_mode.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/launch/images/page_main_stop_mode.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/launch/images/wiz_launch_config_build_options.png has changed
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/page_main.htm Mon Jun 22 09:41:33 2009 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/page_main.htm Mon Jun 22 09:50:30 2009 -0500
@@ -1,99 +1,117 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
-<meta http-equiv="Content-Style-Type" content="text/css" />
-<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
-<title>Carbide Main page </title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Main page </h2>
-<p>The options shown in the <b>Main</b> page differ based upon the type of launch configuration. Generally, the options fall into these choices: </p>
-<ul>
- <li><a href="#emulator_mode">Emulation Main page</a> (Emulation) </li>
- <li><a href="#run_mode">Run-mode Main page</a> (Application TRK) </li>
- <li><a href="#stop_mode">Stop-Mode Main page</a> (System TRK, Sophia, Trace32) </li>
-</ul>
-<h3><a name="emulator_mode" id="emulator_mode"></a>Emulation Main page </h3>
-<p>The <b>Symbian OS <a href="emulation.htm">Emulation</a></b> launch configuration uses the <b>Main</b> page to define the process to be launched by the emulator. </p>
-<p>The behavior that occurs when launching a debug session varies based upon the <a href="page_main.htm">SDK</a>. Normally, <a href="../../tasks/debugger/work_debug_act_start.htm">starting</a> a debug session launches the emulator (<span class="code">epoc.exe</span>) and you must then navigate to your application and open it. However, starting a debug session for an .exe file will, in most cases, launch the .exe directly. This starts the emulator and then opens your application automatically. Note that some SDKs do not support this behavior. In those cases you must still open your application in the emulator manually.</p>
-<p align="center"><img src="images/page_debug_main.png" width="639" height="278"></p>
-<p class="figure">Figure 1. Main page (Emulation shown) </p>
-<h5>Table 1. Emulator Main page —items </h5>
-<table width="94%" border="0" cellpadding="2" cellspacing="0">
- <tr>
- <th width="38%" scope="col">Item</th>
- <th width="62%" scope="col">Explanation</th>
- </tr>
- <tr>
- <td><b>Project</b></td>
- <td><p>The project to associate with this debug launch configuration. Click <b>Browse</b> to select a different project. </p> </td>
- </tr>
- <tr>
- <td><b>Process to launch </b></td>
- <td>The path to the emulator or executable to launch. For Symbian OS 9.1 the emulator path is required. For Symbian OS 9.2 and later the path to the executable should be used. Click <b>Browse</b> to select a different emulator. </td>
- </tr>
-</table>
-
-<h3><a name="run_mode" id="run_mode"></a>Run-mode Main page </h3>
-<p>The <b>Symbian OS <a href="run_mode.htm">Application TRK </a></b> launch configuration uses the <b>Main</b> page to defines the project and the process to launch on the target device. </p>
-<p align="center"><img src="images/page_main_run_mode.png" width="615" height="264"></p>
-<p class="figure">Figure 2 - Main page (Application TRK shown) </p>
-<h5>Table 2. Run-mode Main page —items </h5>
-<table width="94%" border="0" cellpadding="2" cellspacing="0">
- <tr>
- <th width="38%" scope="col">Item</th>
- <th width="62%" scope="col">Explanation</th>
- </tr>
- <tr>
- <td><b>Project</b></td>
- <td><p>The project to associate with this launch configuration. Click Browse to select a different project. </p></td>
- </tr>
- <tr>
- <td><b>Remote process to launch </b></td>
- <td><p>The absolute path of the remote executable to launch on the target device. The binary to debug may be stored on one of several memory locations, the most common are:</p>
- <ul>
- <li><b>RAM</b> (default) — programs running in RAM are launched from <span class="code">c:\sys\bin\</span> </li>
- <li><b>ROM</b> — programs running in ROM are launched from <span class="code">z:\sys\bin\</span></li>
- <li><b>Memory cards</b> — programs running on a memory card are launched from <span class="code">e:\sys\bin\</span> </li>
- </ul>
- <p>In the event a program is not launching, verify that the<b> </b>path is correct for the memory location where the binary resides.</p></td>
- </tr>
- <tr>
- <td><b>Use connection</b></td>
- <td>Choose the remote connection type to associate with this launch configuration. Click <a href="../../reference/trk/wnd_new_conn_wiz_add.htm">New</a> to add a new connection, or <a href="../../reference/trk/wnd_new_conn_wiz_edit.htm">Edit</a> to modify the current one.</td>
- </tr>
-</table>
-<h3><a name="stop_mode" id="stop_mode"></a>Stop-mode Main page </h3>
-<p>The <b>Symbian OS <a href="stop_mode.htm">System TRK</a>, <a href="sophia.htm">Sophia</a></b>, and <b><a href="trace32.htm">Trace32</a> </b> launch configurations uses the <b>Main</b> page to defines the project and the executable to launch on the target device. </p>
-<p align="center"><img src="images/page_main_stop_mode.png" width="642" height="264" /></p>
-<p class="figure">Figure 3. Main page </p>
-<h5>Table 3. Stop-mode Main page — items</h5>
-<table width="94%" border="0" cellpadding="2" cellspacing="0">
- <tr>
- <th width="32%" scope="col">Item</th>
- <th width="68%" scope="col">Explanation</th>
- </tr>
- <tr>
- <td><b>Project</b></td>
- <td>The project to associate with this debug launch configuration. Click Browse to select a different project. </td>
- </tr>
- <tr>
- <td><b>Executable</b></td>
- <td><span
- style="font-weight: normal;">This is the name of the executable that is linked to the project. </span>Click <b>Browse</b> to select a different executable. </td>
- </tr>
- <tr>
- <td><b>Use connection</b></td>
- <td>Choose the remote connection type to associate with this launch configuration. Click <a href="../../reference/trk/wnd_new_conn_wiz_add.htm">New</a> to add a new connection, or <a href="../../reference/trk/wnd_new_conn_wiz_edit.htm">Edit</a> to modify the current one.</td>
- </tr>
-</table>
-<h4>Other references</h4>
-<ul>
- <li><a href="launch_configs_overview.htm">Launch Configuration Overview</a></li>
-</ul>
-<div id="footer">Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
-<h5> </h5>
-</body>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+<meta http-equiv="Content-Style-Type" content="text/css" />
+<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
+<title>Carbide Main page </title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Main page </h2>
+<p>The options shown in the <b>Main</b> page differ based upon the type of launch configuration. Generally, the options fall into these choices: </p>
+<ul>
+ <li><a href="#emulator_mode">Emulation Main page</a> (Emulation) </li>
+ <li><a href="#run_mode">Run-mode Main page</a> (Application TRK) </li>
+ <li><a href="#stop_mode">Stop-Mode Main page</a> (System TRK, Sophia, Trace32) </li>
+</ul>
+<h3><a name="emulator_mode" id="emulator_mode"></a>Emulation Main page </h3>
+<p>The <b>Symbian OS <a href="emulation.htm">Emulation</a></b> launch configuration uses the <b>Main</b> page to define the process to be launched by the emulator. </p>
+<p>The behavior that occurs when launching a debug session varies based upon the <a href="page_main.htm">SDK</a>. Normally, <a href="../../tasks/debugger/work_debug_act_start.htm">starting</a> a debug session launches the emulator (<span class="code">epoc.exe</span>) and you must then navigate to your application and open it. However, starting a debug session for an .exe file will, in most cases, launch the .exe directly. This starts the emulator and then opens your application automatically. Note that some SDKs do not support this behavior. In those cases you must still open your application in the emulator manually.</p>
+<p align="center"><img src="images/page_debug_main.png" width="627" height="243"></p>
+<p class="figure">Figure 1. Main page (Emulation shown) </p>
+<h5>Table 1. Emulator Main page —items </h5>
+<table width="94%" border="0" cellpadding="2" cellspacing="0">
+ <tr>
+ <th width="38%" scope="col">Item</th>
+ <th width="62%" scope="col">Explanation</th>
+ </tr>
+ <tr>
+ <td><b>Project</b></td>
+ <td><p>The project to associate with this debug launch configuration. Click <b>Browse</b> to select a different project. </p> </td>
+ </tr>
+ <tr>
+ <td><b>Process to launch </b></td>
+ <td>The path to the emulator or executable to launch. For Symbian OS 9.1 the emulator path is required. For Symbian OS 9.2 and later the path to the executable should be used. Click <b>Browse</b> to select a different emulator. </td>
+ </tr>
+ <tr>
+ <td><b>Build (if required) before launching</b></td>
+ <td><p>Controls how auto build is configured for the launch configuration. Changing this setting overrides the global workspace setting and can provide some speed improvements. The options include:</p>
+ <ul>
+ <li><b>Disable auto build</b> – Disables auto build for the launch configuration which may improve launch performance.</li>
+ <li><b>Enable auto build</b> – Enables auto build for the launch configuration which can slow down launch performance.</li>
+ <li><b>Use workspace settings</b> (default) – Uses the global auto build settings.</li>
+ <li><b>Configure Workspace Settings...</b> – Opens the Launching preference panel where you can change the workspace settings.</li>
+ </ul> </td>
+ </tr>
+</table>
+
+<h3><a name="run_mode" id="run_mode"></a>Run-mode Main page </h3>
+<p>The <b>Symbian OS <a href="run_mode.htm">Application TRK </a></b> launch configuration uses the <b>Main</b> page to defines the project and the process to launch on the target device. </p>
+<p align="center"><img src="images/page_main_run_mode.png" width="545" height="337"></p>
+<p class="figure">Figure 2 - Main page (Application TRK shown) </p>
+<h5>Table 2. Run-mode Main page —items </h5>
+<table width="94%" border="0" cellpadding="2" cellspacing="0">
+ <tr>
+ <th width="38%" scope="col">Item</th>
+ <th width="62%" scope="col">Explanation</th>
+ </tr>
+ <tr>
+ <td><b>Project</b></td>
+ <td><p>The project to associate with this launch configuration. Click Browse to select a different project. </p></td>
+ </tr>
+ <tr>
+ <td><b>Remote process to launch </b></td>
+ <td><p>The absolute path of the remote executable to launch on the target device. The binary to debug may be stored on one of several memory locations, the most common are:</p>
+ <ul>
+ <li><b>RAM</b> (default) — programs running in RAM are launched from <span class="code">c:\sys\bin\</span> </li>
+ <li><b>ROM</b> — programs running in ROM are launched from <span class="code">z:\sys\bin\</span></li>
+ <li><b>Memory cards</b> — programs running on a memory card are launched from <span class="code">e:\sys\bin\</span> </li>
+ </ul>
+ <p>In the event a program is not launching, verify that the<b> </b>path is correct for the memory location where the binary resides.</p></td>
+ </tr>
+ <tr>
+ <td><b>Use connection</b></td>
+ <td>Choose the remote connection type to associate with this launch configuration. Click <a href="../../reference/trk/wnd_new_conn_wiz_add.htm">New</a> to add a new connection, or <a href="../../reference/trk/wnd_new_conn_wiz_edit.htm">Edit</a> to modify the current one.</td>
+ </tr>
+ <tr>
+ <td><b>Build (if required) before launching</b></td>
+ <td>See <a href="#emulator_mode">Emulation Main page</a> above.</td>
+ </tr>
+</table>
+<h3><a name="stop_mode" id="stop_mode"></a>Stop-mode Main page </h3>
+<p>The <b>Symbian OS <a href="stop_mode.htm">System TRK</a>, <a href="sophia.htm">Sophia</a></b>, and <b><a href="trace32.htm">Trace32</a> </b> launch configurations uses the <b>Main</b> page to defines the project and the executable to launch on the target device. </p>
+<p align="center"><img src="images/page_main_stop_mode.png" width="603" height="337"></p>
+<p class="figure">Figure 3. Main page </p>
+<h5>Table 3. Stop-mode Main page — items</h5>
+<table width="94%" border="0" cellpadding="2" cellspacing="0">
+ <tr>
+ <th width="32%" scope="col">Item</th>
+ <th width="68%" scope="col">Explanation</th>
+ </tr>
+ <tr>
+ <td><b>Project</b></td>
+ <td>The project to associate with this debug launch configuration. Click Browse to select a different project. </td>
+ </tr>
+ <tr>
+ <td><b>Executable</b></td>
+ <td><span
+ style="font-weight: normal;">This is the name of the executable that is linked to the project. </span>Click <b>Browse</b> to select a different executable. </td>
+ </tr>
+ <tr>
+ <td><b>Use connection</b></td>
+ <td>See <a href="#run_mode">Run-mode Main page</a> above.</td>
+ </tr>
+ <tr>
+ <td><b>Build (if required) before launching</b></td>
+ <td>See <a href="#emulator_mode">Emulation Main page</a> above.</td>
+ </tr>
+</table>
+<h4>Other references</h4>
+<ul>
+ <li><a href="launch_configs_overview.htm">Launch Configuration Overview</a></li>
+</ul>
+<div id="footer">Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+<h5> </h5>
+</body>
</html>
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/wiz_new_launch_config.htm Mon Jun 22 09:41:33 2009 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/wiz_new_launch_config.htm Mon Jun 22 09:50:30 2009 -0500
@@ -21,6 +21,7 @@
<td><ul>
<li><a href="#CATEGORY">Category Type</a></li>
<li><a href="#LAUNCH">Launch Type</a></li>
+ <li><a href="#BLD_OPT">Build Option Selection</a></li>
<li><a href="#EXE_SEL">Executable Selection</a></li>
<li><a href="#FINISH">New Launch Configuration</a></li>
</ul> </td>
@@ -59,49 +60,53 @@
<p align="center"><img src="../../images/icons/menu_build_target.png" width="270" height="120"></p>
<p class="figure">Figure 1 - Build Target selection list </p>
<h3><a name="CATEGORY" id="LAUNCH2"></a>Category Types</h3>
-<p>Use the<b> Category Types</b> page to select the the launch category. The choices include Phone, Board, and possibly others. The choice made here filters the <b>Launch Types</b> page to show valid launch configurations. Once a category is selected, click <b>Next</b>. </p>
+<p>Use the<b> Category Types</b> page to select the the launch category. The choices include Phone, Board, and possibly others. The choice made here filters the <b>Launch Types</b> page to only show valid launch configurations. Once a category is selected, click <b>Next</b>. </p>
<p align="center"><img src="images/wiz_launch_config_categories.png" width="438" height="533"></p>
<p class="figure">Figure 2 - Category Types page </p>
<h3><a name="LAUNCH" id="LAUNCH"></a>Launch Types</h3>
<p>Use the<b> Launch Types</b> page to select the type of launch configuration for the build target. This page does not appear when using an Emulator target. Available types are listed from the most frequently chosen (Application TRK) to the least likely type (Attach to Process). Select a type and click <b>Next</b>. </p>
<p align="center"><img src="../../images/icons/wiz_launch_config_launch_types.png" width="438" height="533"></p>
<p class="figure">Figure 3 - Launch Type page </p>
+<h3><a name="BLD_OPT" id="EXE_SEL2"></a>Build Options Selection </h3>
+<p>Use the <b>Build Options Selection </b> page to define if the launch configuration uses auto build or not. Choices include using the global auto built setting (default), enable or disable auto build for the launch configuration. You can also set the global option using the Configure Workspace Settings... to open the Launching preference panel.</p>
+<p align="center"><img src="images/wiz_launch_config_build_options.png" width="484" height="533"></p>
+<p class="figure">Figure 4 - Build Options Selection page </p>
<h3><a name="EXE_SEL" id="EXE_SEL"></a>Executable Selection </h3>
<p>Use the <b>Application Selection </b> page to choose a binary created by the project to launch and debug and verify its location. If only a single binary is available the <b>Process to launch</b> option is disabled. </p>
<p><b>EMULATOR ONLY</b> Use the <b>Location</b> field for emulator targets to verify that the correct executable on the host is selected. This field is not used with on-device launch configurations. </p>
<p>Use the <b>Specify device path of remote process to launch</b> option to specify alternate paths for launching the executable from RAM (c:\sys\bin\), ROM (z:\sys\bin\) or memory cards (e:\sys\bin\) . </p>
<p>Select the Executable to launch, verify it is the correct binary, then click <b>Next</b>. </p>
<p align="center"><img src="../../images/icons/wiz_launch_config_app_selection.png" width="438" height="533"> </p>
-<p class="figure">Figure 4 - Executable Selection page (when project has multiple EXEs)</p>
+<p class="figure">Figure 5 - Executable Selection page (when project has multiple EXEs)</p>
<h3><a name="TRK_CONN" id="TRK_CONN"></a>TRK Connection Settings </h3>
<p>Use the <b>TRK Connection Settings</b> page to specify the connection used to communicate with the target device. If the device is already connected, the drop down list will include both the COM port and the name of the device using that port. Use the <a href="../../reference/trk/wnd_on_device_setup.htm">On-Device Conection</a> dialog to verify and update all Carbide software services on the device. Choose the serial port used to communicate with the target device and click <b>Next</b>. </p>
-<p align="center"><img src="../../images/icons/wiz_launch_config_trk_conn.png" width="463" height="533"> </p>
-<p class="figure">Figure 5 - TRK Connection Settings page </p>
+<p align="center"><img src="../../images/icons/wiz_launch_config_trk_conn.png" width="487" height="533"> </p>
+<p class="figure">Figure 6 - TRK Connection Settings page </p>
<p> </p>
<h3><a name="TRK_SIS" id="TRK_SIS"></a>TRK SIS Selection</h3>
<p>Use the <b>TRK SIS Selection</b> page to select the SIS file to install on the target device. Click the <b>Modify SIS builder settings for build configuration</b> link to open the <a href="../../reference/build_properties/pane_build_config_sis.htm">SIS Builder</a> properties pane to add, edit, or review the SIS files to build. Once the correct SIS File to Install is selected, click <b>Next</b>. </p>
<p align="center"><img src="../../images/icons/wiz_launch_config_trk_sis.png" width="463" height="533"></p>
-<p class="figure">Figure 6 - TRK SIS Selection page </p>
+<p class="figure">Figure 7 - TRK SIS Selection page </p>
<h3><a name="FINISH" id="FINISH"></a>New Launch Configuration</h3>
<p>Use the <b>New Launch Configuration</b> page to note the name of the configuration, confirm the launch configuration settings, and then launch the debug session. If something doesn't look right, click <b>Back</b> to return to a page and change its setting. If all the settings are correct, click <b>Finish</b> to start the debug session using this launch configuration. </p>
<p>If you checkmark <b> Advanced settings</b>, the <a href="../../reference/wnd_debug_configuration.htm">Debug</a> dialog appears instead of launching the project. This enables you to make additional changes to the new launch configuration before starting the debug session. By design and intent, this should seldom be required for the initial launch. </p>
<p align="center"><img src="../../images/icons/wiz_launch_config_finish.png" width="438" height="533"></p>
-<p class="figure">Figure 7 - New Launch Configuration page </p>
+<p class="figure">Figure 8 - New Launch Configuration page </p>
<h3><a name="TRACE32" id="TRACE32"></a>Trace32 Initialization Settings</h3>
<p>Use the <b>Trace32 Initialization Settings</b> page to specify the <a href="../../reference/wnd_Trace32_config.htm">initialization</a> script and target processor of the target device.Enter the Trace32 Initialization Script and choose the Target Processor, then click <b>Next</b>. </p>
<p> This page only appears when creating a Trace32 launch configuration. </p>
<p align="center"><img src="../../images/icons/wiz_launch_config_trace32.png" width="438" height="533"></p>
-<p class="figure">Figure 8 - <b>Trace32 Initialization Settings</b> page </p>
+<p class="figure">Figure 9 - <b>Trace32 Initialization Settings</b> page </p>
<h3><a name="SOPHIA" id="SOPHIA"></a>Sophia STI Initialization Settings</h3>
<p>Use the <b>Sophia STI Initialization Settings</b> page to specify the target interface, <a href="../../reference/wnd_sophia_config.htm">initialization</a> file, and target processor of the target device. Enter the Sophia Target Interface and Target Initialization File paths, choose a Target Processor, then click <b>Next</b>. </p>
<p>This page only appears when creating a Sophia STI launch configuration. </p>
<p align="center"><img src="../../images/icons/wiz_launch_config_sophia.png" width="438" height="533"></p>
-<p class="figure">Figure 9 - Sophia STI Initialization Settings page </p>
+<p class="figure">Figure 10 - Sophia STI Initialization Settings page </p>
<h3><a name="ROM_IMG" id="ROM_IMG"></a>Symbian ROM Image Settings</h3>
<p>Use the <b>Symbian ROM Image Settings</b> page to specify the method of <a href="../../reference/launch_configs/page_trk_debugger.htm">debugging</a>, the start address, and the <a href="../../reference/launch_configs/stop_mode_rom_image.htm">ROM Image</a> and Log File locations. </p>
<p>This page appears when creating a Trace32 or Sophia STI launch configuration. </p>
<p align="center"><img src="../../images/icons/wiz_launch_config_rom_image.png" width="438" height="533"></p>
-<p class="figure">Figure 10 - Symbian ROM Image Settings page</p>
+<p class="figure">Figure 11 - Symbian ROM Image Settings page</p>
<h5>Other references</h5>
<ul>
<li><a href="../../projects/launch/launch_configs_overview.htm">Launch Configuration</a> </li>
