8 <title>New Launch Configuration Wizard</title> |
8 <title>New Launch Configuration Wizard</title> |
9 <link rel="StyleSheet" href="../../../book.css" type="text/css" /> |
9 <link rel="StyleSheet" href="../../../book.css" type="text/css" /> |
10 </head> |
10 </head> |
11 <body > |
11 <body > |
12 <h2>New Launch Configuration Wizard </h2> |
12 <h2>New Launch Configuration Wizard </h2> |
13 <p>The <b>New Launch Configuration Wizard</b> launches when no launch configuration exists for a build configuration in a project. Wherever possible the <b>New Launch Configuration </b> wizard gathers the information from the project and asks additional questions based on the type of launch configuration chosen. For example, a launch configuration using Application CODA requires different information than one targeted for System CODA. </p> |
13 <p>The <b>New Launch Configuration Wizard</b> launches when no launch configuration exists for a build configuration in a project. Wherever possible the <b>New Launch Configuration </b> wizard gathers the information from the project and asks additional questions based on the type of launch configuration chosen. For example, a launch configuration using Symbian OS Device (Install SIS) requires different information than one targeted for Symbian OS Device. </p> |
14 <p>Every project consists of one or more build configurations as listed under the <b>Build project</b> icon (<img src="../images/icon_build_project.png" alt="Build project icon" width="17" height="17" align="absmiddle">) of the toolbar or in the <a href="../../tasks/projects/prj_new_build_config.htm">Add/Remove Carbide Build Configuration</a> dialog. Every build configuration needs a launch configuration to enable debugging. Launch configurations can be shared between build configurations. The <b>New Launch Configuration Wizard</b> detects when a build configuration doesn't have an associated launch configuration and guides you through the setup process.</p> |
14 <p>Every project consists of one or more build configurations as listed under the <b>Build project</b> icon (<img src="../images/icon_build_project.png" alt="Build project icon" width="17" height="17" align="absmiddle">) of the toolbar or in the <a href="../../tasks/projects/prj_new_build_config.htm">Add/Remove Carbide Build Configuration</a> dialog. Every build configuration needs a launch configuration to enable debugging. Launch configurations can be shared between build configurations. The <b>New Launch Configuration Wizard</b> detects when a build configuration doesn't have an associated launch configuration and guides you through the setup process.</p> |
15 <p align="center"><img src="images/menu_build_target.png" width="428" height="224"></p> |
15 <p align="center"><img src="images/menu_build_target.png" width="428" height="224"></p> |
16 <p class="figure">Figure 1. Build configurations for the chosen project appear under the Build icon</p> |
16 <p class="figure">Figure 1. Build configurations for the chosen project appear under the Build icon</p> |
17 <p>To access the <b>New Launch Configuration Wizard</b> click the <b>Debug</b> icon (<img src="../../projects/images/icon_debug.png" alt="" width="17" height="16" align="absmiddle">) on the toolbar. If no launch configuration exists for the selected build target the wizard is launched. If a launch configuration already exists, then that launch configuration is launched and not the wizard.</p> |
17 <p>To access the <b>New Launch Configuration Wizard</b> click the <b>Debug</b> icon (<img src="../../projects/images/icon_debug.png" alt="" width="17" height="16" align="absmiddle">) on the toolbar. If no launch configuration exists for the selected build target the wizard is launched. If a launch configuration already exists, then that launch configuration is launched and not the wizard.</p> |
18 <h2>Launch Configuration Wizard Pages</h2> |
18 <h2>Launch Configuration Wizard Pages</h2> |
39 <li><a href="#BLD_OPT">Build Option Selection</a></li> |
39 <li><a href="#BLD_OPT">Build Option Selection</a></li> |
40 <li><a href="#FINISH">New Launch Configuration</a></li> |
40 <li><a href="#FINISH">New Launch Configuration</a></li> |
41 </ul></td> |
41 </ul></td> |
42 </tr> |
42 </tr> |
43 <tr> |
43 <tr> |
44 <td><b>Application CODA and System CODA</b></td> |
44 <td><b>Symbian OS Device (Install SIS)</b></td> |
45 <td><ul> |
45 <td><ul> |
46 <li><a href="#TRK_CONN">CODA Connection Settings</a></li> |
46 <li><a href="#TRK_CONN">CODA Connection Settings</a></li> |
47 <li><a href="#TRK_SIS">CODA SIS Selection</a> (<i>Application CODA only</i>) </li> |
47 <li><a href="#TRK_SIS">CODA SIS Selection</a> (<i>Symbian OS Device (Install SIS) only</i>) </li> |
48 </ul></td> |
48 </ul></td> |
49 </tr> |
49 </tr> |
50 <tr> |
50 <tr> |
51 <td><b>Attach to Process</b></td> |
51 <td><b>Symbian OS Device (Attach to Process)</b></td> |
52 <td><ul> |
52 <td><ul> |
53 <li><a href="#TRK_CONN">CODA Connection Settings</a></li> |
53 <li><a href="#TRK_CONN">CODA Connection Settings</a></li> |
54 </ul></td> |
54 </ul></td> |
55 </tr> |
55 </tr> |
56 </table> |
56 </table> |
64 </ul> |
64 </ul> |
65 <p>The choice made here filters the <b>Launch Types</b> page to only show valid launch configurations. Once a debug as choice is made, click <b>OK</b>. </p> |
65 <p>The choice made here filters the <b>Launch Types</b> page to only show valid launch configurations. Once a debug as choice is made, click <b>OK</b>. </p> |
66 <p align="center"><img src="images/wiz_launch_config_debug_as.png" alt="Debug As dialog" width="346" height="435"></p> |
66 <p align="center"><img src="images/wiz_launch_config_debug_as.png" alt="Debug As dialog" width="346" height="435"></p> |
67 <p class="figure">Figure 1 - Debug As dialog </p> |
67 <p class="figure">Figure 1 - Debug As dialog </p> |
68 <h3><a name="LAUNCH" id="LAUNCH"></a>Launch Types</h3> |
68 <h3><a name="LAUNCH" id="LAUNCH"></a>Launch Types</h3> |
69 <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 CODA) to the least likely type (Attach to Process). Select a type and click <b>Next</b>. </p> |
69 <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 to the least likely type. Select a type and click <b>Next</b>. </p> |
70 <p align="center"><img src="images/wiz_launch_config_launch_types.png" width="438" height="533"></p> |
70 <p align="center"><img src="images/wiz_launch_config_launch_types.png" width="438" height="533"></p> |
71 <p class="figure">Figure 2 - Launch Type page </p> |
71 <p class="figure">Figure 2 - Launch Type page </p> |
72 <h3><a name="BLD_OPT" id="EXE_SEL2"></a>Build Options Selection </h3> |
72 <h3><a name="BLD_OPT" id="EXE_SEL2"></a>Build Options Selection </h3> |
73 <p>Use the <b>Build Options Selection </b> page to define if the launch configuration uses automatic build or not. Choices include using the global automatic built setting (default), enable or disable automatic build for the launch configuration. You can also set the global option using the Configure Workspace Settings... to open the Launching preference panel.</p> |
73 <p>Use the <b>Build Options Selection </b> page to define if the launch configuration uses automatic build or not. Choices include using the global automatic built setting (default), enable or disable automatic build for the launch configuration. You can also set the global option using the Configure Workspace Settings... to open the Launching preference panel.</p> |
74 <p align="center"><img src="images/wiz_launch_config_build_options.png" width="631" height="433"></p> |
74 <p align="center"><img src="images/wiz_launch_config_build_options.png" width="631" height="433"></p> |
75 <p class="figure">Figure 3 - Build Options Selection page </p> |
75 <p class="figure">Figure 3 - Build Options Selection page </p> |
76 <h3><a name="EXE_SEL" id="EXE_SEL"></a>Executable Selection </h3> |
76 <h3><a name="EXE_SEL" id="EXE_SEL"></a>Executable Selection </h3> |
77 <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> |
77 <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> |
78 <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> |
78 <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> |
79 <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> |
79 <p>Select the <b>Process to launch</b>, verify it is the correct binary. </p> |
80 <p>Select the Executable to launch, verify it is the correct binary, then click <b>Next</b>. </p> |
80 <p>Use the <b>Specify device path of remote process to launch</b> option to specify alternate paths for launching the executable from RAM (<span class="code">c:\sys\bin\</span>), ROM (<span class="code">z:\sys\bin\</span>) or memory cards (<span class="code">e:\sys\bin\</span>), then click <b>Next</b>. </p> |
81 <p align="center"><img src="images/wiz_launch_config_app_selection.png" width="438" height="533"> </p> |
81 <p align="center"><img src="images/wiz_launch_config_app_selection.png" width="438" height="533"> </p> |
82 <p class="figure">Figure 4 - Executable Selection page (when project has multiple EXEs)</p> |
82 <p class="figure">Figure 4 - Executable Selection page (when project has multiple EXEs)</p> |
83 <h3><a name="TRK_CONN" id="TRK_CONN"></a>CODA Connection Settings </h3> |
83 <h3><a name="TRK_CONN" id="TRK_CONN"></a>CODA Connection Settings </h3> |
84 <p>Use the <b>CODA 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> |
84 <p>Use the <b>CODA 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> |
85 <p align="center"><img src="images/wiz_launch_config_trk_conn.png" width="487" height="533"> </p> |
85 <p align="center"><img src="images/wiz_launch_config_trk_conn.png" width="487" height="533"> </p> |