core/com.nokia.carbide.cpp.doc.user/html/projects/launch/wiz_new_launch_config.htm
BUG 10651 - added debugging dll with any process info, revised launch config pages and others
<!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>New Launch Configuration Wizard</title>
<link rel="StyleSheet" href="../../../book.css" type="text/css" />
</head>
<body >
<h2>New Launch Configuration Wizard </h2>
<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 TRK requires different information than one targeted for System TRK. </p>
<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>
<p align="center"><img src="images/menu_build_target.png" width="428" height="224"></p>
<p class="figure">Figure 1. Build configurations for the chosen project appear under the Build icon</p>
<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>
<h2>Launch Configuration Wizard Pages</h2>
<p>The following are the possible pages you will see depending upon your choice of build configuration and type of debugging required. Different launch configurations need different information to work properly. The following table lists all the pages seen when choosing common types of debugging.</p>
<table width="700" border="0" cellpadding="2" cellspacing="0">
<tr>
<th width="41%" scope="col">Launch Configuration</th>
<th width="59%" scope="col">Wizard Pages</th>
</tr>
<tr>
<td><b>Common pages</b></td>
<td><ul>
<li><a href="#DEBUGAS">Debug As</a></li>
<li>Launch Types</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>
</tr>
<tr>
<td><b>Simulator</b></td>
<td><ul>
<li><a href="#EXE_SEL">Executable Selection</a></li>
<li><a href="#BLD_OPT">Build Option Selection</a></li>
<li><a href="#FINISH">New Launch Configuration</a></li>
</ul></td>
</tr>
<tr>
<td><b>Application TRK and System TRK</b></td>
<td><ul>
<li><a href="#TRK_CONN">TRK Connection Settings</a></li>
<li><a href="#TRK_SIS">TRK SIS Selection</a> (<i>Application TRK only</i>) </li>
</ul></td>
</tr>
<tr>
<td><b>Attach to Process</b></td>
<td><ul>
<li><a href="#TRK_CONN">TRK Connection Settings</a></li>
</ul></td>
</tr>
</table>
<h3><a name="DEBUGAS" id="LAUNCH2"></a>Debug As</h3>
<p>Use the<b> Debug As </b>dialog to select the method of debugging for the chosen build configuration. The choices include: </p>
<ul>
<li><b>Symbian OS Phone of Simulator Launch</b> – choose to work with attached phones or devices</li>
</ul>
<ul>
<li><b>Symbian OS Platform Simulator Launch</b> – choose to work with platform boards</li>
</ul>
<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>
<p align="center"><img src="images/wiz_launch_config_debug_as.png" alt="Debug As dialog" width="346" height="435"></p>
<p class="figure">Figure 1 - Debug As dialog </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/wiz_launch_config_launch_types.png" width="438" height="533"></p>
<p class="figure">Figure 2 - 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 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>
<p align="center"><img src="images/wiz_launch_config_build_options.png" width="631" height="433"></p>
<p class="figure">Figure 3 - 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/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>
<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/wiz_launch_config_trk_conn.png" width="487" height="533"> </p>
<p class="figure">Figure 5 - 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/wiz_launch_config_trk_sis.png" width="463" height="533"></p>
<p class="figure">Figure 6 - 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/wiz_launch_new_launch_config.png" alt="New Launch Configuration dialog" width="631" height="433"></p>
<p class="figure">Figure 7 - New Launch Configuration page </p>
<h5>Other references</h5>
<ul>
<li><a href="../../projects/launch/launch_configs_overview.htm">Launch Configuration</a> </li>
<li><a href="launch_emulator.htm">Symbian OS Emulator Launch</a></li>
<li><a href="launch_phone.htm">Symbian OS Phone Launch</a></li>
<li><a href="launch_board.htm">Symbian OS Reference Board Launch</a></li>
</ul>
<div id="footer">Copyright © 2010 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>
</body>
</html>