--- a/core/com.nokia.carbide.cpp.doc.user/book.css Tue Jul 13 15:27:30 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/book.css Tue Jul 13 15:35:51 2010 -0500
@@ -101,7 +101,7 @@
}
th {
- background-color: #E6E6E6;
+ background-color: #66CC66;
}
div.ol.p {
@@ -120,7 +120,7 @@
div h5, div h4 {
padding:5px 0px 5px 12px;
- background-color: #E6E6E6;
+ background-color: #D3DAD4;
font-weight:bold;
color: #000000;
}
Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/images/debugging_project_02.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/images/debugging_project_04.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/images/debugging_project_05.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/images/dlg_build_project_progress.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/images/icon_build_project.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/images/icon_debug.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/images/icon_project_built.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/images/icon_project_error_badge.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/images/icon_project_warning_badge.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/images/icon_run.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/images/menu_new_proj_build_project.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/images/new_build_project_console_view.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/images/new_build_project_executables_view.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/images/new_build_project_problems_view.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/images/new_launch_config_03.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/images/new_launch_config_04.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/images/new_launch_config_05.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/images/new_launch_config_08.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/images/new_project_template_01.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/images/new_project_template_02.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/images/new_project_template_07.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/images/pref_cdt_build_console.png has changed
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/tutorials/new_proj_from_template_00.htm Tue Jul 13 15:35:51 2010 -0500
@@ -0,0 +1,23 @@
+<!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>Creating New Projects Tutorial</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Creating New Projects Tutorial</h2>
+<p>In this example we show how to create a new project using one of the built-in Carbide templates, how to build it into an executable, and how to launch the debugger to verify program accuracy. The steps to do this include:</p>
+<ol>
+ <li><a href="new_proj_from_template_01.htm">Creating</a> a project from a project template</li>
+ <li><a href="new_proj_from_template_02.htm">Building</a> an executable based on the project sources</li>
+ <li><a href="new_proj_from_template_03.htm">Defining</a> a launch configuration for running or debugging the application</li>
+ <li><a href="new_proj_from_template_04.htm">Controlling and debugging</a> the running program using the Carbide debugger</li>
+</ol>
+<p class="note"><b>NOTE</b> There must be at least one recognized SDK installed before you can create a project. See the <a href="../../../reference/SDKPreferences.html">SDK Preferences panel</a> to determine if the installed SDKs are recognized by Carbide.c++ IDE. If the SDK you have installed is not recognized, you may still be able to <a href="../../AddinganSDK.html">add</a> it to the Discovered Symbian OS SDK list.</p>
+<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>
\ No newline at end of file
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/tutorials/new_proj_from_template_01.htm Tue Jul 13 15:35:51 2010 -0500
@@ -0,0 +1,64 @@
+<!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>Creating New Projects from Templates</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Creating New Projects from Templates</h2>
+<p>In this example we show how to create a new project using one of the built-in Carbide templates, how to build it into an executable, and how to launch the debugger to verify program accuracy. The steps to do this include:</p>
+<ol>
+ <li><strong>Creating a project from a project template</strong></li>
+ <li><a href="new_proj_from_template_02.htm">Building</a> an executable based on the project sources</li>
+ <li><a href="new_proj_from_template_03.htm">Defining</a> a launch configuration for running or debugging the application</li>
+ <li><a href="new_proj_from_template_04.htm">Controlling and debugging</a> the running program using the Carbide debugger</li>
+</ol>
+<hr>
+<p>Everything starts with a project. So the first step is to use the <strong>New Project</strong> wizard to create a project based on a known template. Program templates are designed to make creating common project types fast and simple. They include the basic sources, resources, includes, and build files that Carbide uses to manage your project. </p>
+<div class="step">
+ <h4><strong></strong>Creating projects from a template</h4>
+ <ol>
+ <li>Click the <strong>File > New > Symbian OS C++ Project</strong> menu option.<br />
+ <p>The <strong>New Symbian OS C++ Project</strong> window appears to guide you through project creation process.</p>
+ <p><img src="../images/new_project_template_01.png" alt="New Symbian OS C++ Project window" width="525" height="503"></p>
+ </li>
+ <li>Select a template from the available, then click <strong>Next</strong>.<br />
+ <p>Select the template for the type of project you want to create. For this example we chose the <strong>S60 > GUI Application</strong> template. Note that as you select a template a brief description appears below the list explaining it attributes.</p>
+ </li>
+ <li>Use the <strong>New Symbian OS C++ Project</strong> page to define the project name and build system.<br />
+ <p><img src="../images/new_project_template_02.png" width="525" height="503"></p>
+ <ol type="a">
+ <li>Type a name into the <strong>Project name</strong> text box.<br />
+ <p>The project name is used to define several of the pre-build source files in the prject.</p>
+ </li>
+ <li>(Optional) Change the project location.<br />
+ <p>Uncheck the <strong>Use default location</strong> option to specify a different location for the project.</p>
+ </li>
+ <li>Select the <strong>Builder</strong> type.<br />
+ <p>Based on the installed SDKs you can choose between SBSv2 (recommended) and the older SBSv1 build systems.</p>
+ </li>
+ <li>Click <strong>Next</strong>.</li>
+ </ol>
+ </li>
+ <li>In the Symbian OS SDKs page, select the SDK and build configurations for the project.<br />
+ <p>Here you can select from any SDK that is both installed and recognized by Carbide. If the SDK supports several build configurations (GCCE, RVCT, etc.) then you can pick and choose among them for your project.</p>
+ </li>
+ <li>(Optional) Click Next to provide Basic Settings like author, copyright and other info for your project.</li>
+ <li>(Optional) Click Next to rename the Project Directories used to organize the project.</li>
+ <li>Click Finish.<br>
+ <p>Carbide uses the selected project template and your settings to create a new project in the <a href="../../reference/view_cpp_projects.htm">Project Explorer</a> view.</p>
+ </li>
+ </ol>
+</div>
+<strong>NEXT STEP</strong> > <a href="new_proj_from_template_02.htm">Building</a> an executable based on the project sources
+<h4>Other references</h4>
+<ul>
+ <li><a href="./">Creating New Projects Tutorial</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>
\ No newline at end of file
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/tutorials/new_proj_from_template_02.htm Tue Jul 13 15:35:51 2010 -0500
@@ -0,0 +1,97 @@
+<!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" />
+<title>Building Projects and Components</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
+</head>
+<body >
+<h2>Building Projects and Components</h2>
+<p>In this example we show how to create a new project using one of the built-in Carbide templates, how to build it into an executable, and how to launch the debugger to verify program accuracy. The steps to do this include:</p>
+<ol>
+ <li><a href="new_proj_from_template_01.htm">Creating</a> a project from a project template</li>
+ <li><strong>Building an executable based on the project sources</strong></li>
+ <li><a href="new_proj_from_template_03.htm">Defining</a> a launch configuration for running or debugging the application</li>
+ <li><a href="new_proj_from_template_04.htm">Controlling and debugging</a> the running program using the Carbide debugger</li>
+</ol>
+<hr>
+<p><strong></strong>Once you have a project in hand, the next thing to do is compile or build it into object code.</p>
+<p>Building projects consists of a sbs or abld-based build system that wraps build functionality around existing SDK build tools that invoke <span class="code">makmake</span> commands (e.g. <span class="code">makmake bldfiles</span> and <span class="code">sbs build</span>).</p>
+<p> The plug-ins provide extra functionality to set up suitable build configurations for Symbian OS C++ projects. The initial selection of a build configuration is done when you create a project, as described in <a href="new_proj_from_template_01.htm">Creating New Projects from Templates</a>. You can later <a href="../../tasks/projects/prj_set_build_tgt.htm">change</a> the Active Build Configuration. The Build Configurations also provides a command (<b>Project > <a href="../../reference/menus/build_all_targets.htm">Build All Configurations</a></b>) to build all the selected build configurations in a batch.</p>
+<p> Building Symbian OS C++ projects can involve the use of Symbian OS specific tools, such as the Symbian OS resource compiler. For detailed information on such tools, see the documentation for the SDK that you are using.</p>
+<p>You build projects to process the source files that comprise a program and
+ generate object code. The compiler flags syntax errors in the source files. Use the <a href="../../reference/ProjectPreferences.html">Properties for <project_name> </a> window to control how the project is built. The following methods build a project:</p>
+<ul>
+ <li><b>Build All Configurations</b> (<span class="code">CTRL-ALT-A</span>) — builds all build configurations for a project</li>
+ <li><b>Build Working Set</b> — specify which projects to build in a working set </li>
+ <li><b>Build Project</b> — builds the entire project if it has never been built before or on subsequent builds only those files that have changed since the last build operation</li>
+</ul>
+<blockquote>
+ <p align="left"><img src="../images/menu_new_proj_build_project.png" alt="Build Project menu" width="355" height="357"></p>
+</blockquote>
+<div class="step">
+ <h4>Building a project</h4>
+ <ol>
+ <li>Build the project using one of these actions:
+ <div align="left">
+ <ul>
+ <li>Right-click the project in the Project Explorer view and choose Build Project (see above).</li>
+ <li>Click the Run > Build Project menu option.</li>
+ <li>Click the Build (<img src="../images/icon_build_project.png" alt="Build Project icon" width="17" height="17" align="absmiddle">) icon in the toolbar to build the project.</li>
+ </ul>
+ </li>
+ </ol>
+ <blockquote>
+ <p>Choosing any of the above actions causes Carbide to build the selected project. A <strong>Build Project</strong> dialog (below) and a progress bar appear during a lengthy build operation. All build output is shown in a <a href="../../reference/view_log.htm">Console</a> view while build errors and warnings appear in the Problems view.</p>
+ <p align="left"><img src="../images/dlg_build_project_progress.png" alt="Build Project progress dialog" width="532" height="233"></p>
+ <p>Whether a full build or incremental build is requested, Carbide forwards the request to the SDK make system. The SDK make system determines if anything needs to be
+ built. Carbide always checks that makefiles are up-to-date and
+ dependencies present.</p>
+ <p>The project is also built if you make a change to it and then click <b>Debug</b>. It may be useful to automatically save modified resources before a manual build process by enabling the <b>Save automatically before build</b> option in the <b>Window > Preferences > General ></b> <img src="../../images/command_link.png" width="16" height="12"> <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.ui.preferencePages.Workbench)")'> Workspace</a> preference panel. </p>
+ <p class="note"><b>NOTE</b> If you want to turn off building before launching, uncheck the <b>Build (if required) before launching</b> option in the <b>Window > Preferences > Run/Debug ><img src="../../images/command_link.png" width="16" height="12"> <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.debug.ui.LaunchingPreferencePage)")'> Launching</a></b> preference panel.</p>
+ <p>When performing a build, output is displayed in the <a href="../../reference/view_log.htm">Console</a> view. If you do not want to clear the console before each build you need to uncheck the option <b>Always clear console before building</b> in the <b> Console</b> panel. This option is enabled by default. You can access this panel by selecting <b>Window > Preferences > C/C++ > Build ><img src="../../images/command_link.png" width="16" height="12"> <a class="command-link" href='javascript:executeCommand("org.eclipse.ui.window.preferences(preferencePageId=org.eclipse.cdt.ui.preferneces.CBuildConsolePreferernces)")'> Console</a></b> preference panel (below).</p>
+ <p align="left"><img src="../images/pref_cdt_build_console.png" alt="Console preference panel" width="635" height="554"></p>
+ <p>Not clearing the console is useful when you are performing multiple builds, such as a regular project build, building a project package (.pkg) file, and building a ROM image. For example, if you do not clear the console before each build, then a subsequent build will not overwrite information from a previous build.</p>
+ </blockquote>
+ <ol start="2">
+ <li>Verifying a successful project build <br />
+ <p>Once compiling is complete use the <strong>Project Explorer</strong>, <strong>Problems</strong>, <strong>Console</strong>, and <strong>Executables</strong> views to locate and resolve any problems generated during the build.</p>
+ <ol type="a">
+ <li>Examine the project icon in the Project Explorer view<br>
+ <ul>
+ <li><img src="../images/icon_project_built.png" alt="Project built icon" width="19" height="17"> — a successfully built project icon.</li>
+ <li> <img src="../images/icon_project_warning_badge.png" alt="Warning badge" width="19" height="18"> — projects with warning messages show a yield badge.</li>
+ <li><img src="../images/icon_project_error_badge.png" alt="Error badge" width="20" height="19"> — projects with error messages show a red badge.</li>
+ </ul>
+ </li>
+
+ <li>Check the Problems view for error or warning messages<br />
+ <p>Examine the <a href="PLUGINS_ROOT//org.eclipse.cdt.doc.user/reference/cdt_u_problems_view.htm">Problems</a> view to see what errors and warning messages were generated during the build. The Description column contains additional information about the problem that can help you resolve it.</p>
+ <p><img src="../images/new_build_project_problems_view.png" alt="Executables view" width="797" height="210"></p>
+ </li>
+ <li>Examine the Console view for more specific details on an error or warning message<br />
+ <p>Use the <a href="../../reference/view_log.htm">Console</a> view to see where a specific problem occured during the build.</p>
+ <p><img src="../images/new_build_project_console_view.png" alt="Executables view" width="797" height="210"></p>
+ </li>
+ <li>Examine the Executables view for missing source files<br />
+ <p>Use the <a href="../../reference/view_executables.htm">Executables</a> view to see what source files were used during the build. Sources shown in gray are those Carbide cannot find. Missing sources in an SDK not built on your machine are common, but missing sources that you created can be resolved.</p>
+ <p><img src="../images/new_build_project_executables_view.png" alt="Executables view" width="713" height="210"></p>
+ </li>
+ </ol>
+ <p>Once you're resolved all the build errors in a project, its time to link the program to a specific target. This is done with a launch configuration.</p>
+ </li>
+ </ol>
+</div>
+<h4><strong>NEXT STEP</strong> > <a href="new_proj_from_template_03.htm">Defining</a> a launch configuration for running or debugging the application</h4>
+<h4></h4>
+<h4>Other references</h4>
+<ul>
+
+ <li><a href="./">Creating New Projects Tutorial</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>
\ No newline at end of file
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/tutorials/new_proj_from_template_03.htm Tue Jul 13 15:35:51 2010 -0500
@@ -0,0 +1,65 @@
+<!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>Defining a launch configuration</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Defining a launch configuration</h2>
+<p>In this example we show how to create a new project using one of the built-in Carbide templates, how to build it into an executable, and how to launch the debugger to verify program accuracy. The steps to do this include:</p>
+<ol>
+ <li><a href="new_proj_from_template_01.htm">Creating</a> a project from a project template</li>
+ <li><a href="new_proj_from_template_02.htm">Building</a> an executable based on the project sources</li>
+ <li><strong>Defining a launch configuration for running or debugging the application</strong></li>
+ <li><a href="new_proj_from_template_04.htm">Controlling and debugging</a> the running program using the Carbide debugger</li>
+</ol>
+<hr>
+<p><strong></strong>To run or debug a project you need a <a href="../../projects/launch/launch_configs_overview.htm">launch configuration</a>. A project must have at least one launch configuration, and can have as many as necessary. It is not unusual to have two or more launch configurations per target device, usually a debug version and a run version. You can use the <a href="../../projects/launch/wiz_new_launch_config.htm">New Launch Configuration Wizard</a> to create them all.</p>
+<ul>
+ <li>On emulator targets, the <strong>New Launch Configuration</strong> <strong>Wizard</strong> usually has all the information it requires to create a launch configuration and launch the program on the emulator. If at any time it needs additional information, dialogs will ask for it, then launch the program.</li>
+ <li>On device targets, the <strong>New Launch Configuration</strong> <strong>Wizard</strong> requests all the additional information it needs like the target device, the remote connection, and more, before it creates the launch configuration. Once it has all the required data, it creates the launch configuration, then downloads the executable to the device and launches it.</li>
+</ul>
+<p>Once the emulator or device is loaded with the executable, a debug session can begin. </p>
+<p>If at any time the <strong>New Launch Configuration</strong> <strong>Wizard</strong> encounters a problem during a later launch sequence it will request settings clarification before continuing. For example, maybe the target device has changed, or a new ROM has been installed. Either of these will trigger a request for clarification.</p>
+<div class="step">
+ <h4>Defining a launch configuration (emulator example)</h4>
+ <ol>
+ <li>Select the project to run in the Project Explorer view.</li>
+ <li>To run the project without the debugger choose:<br />
+ <p>To simply run the project on the chosen target use one of the following actions. Use this option to verify a release program's execution without debugging symbols.</p>
+ <ol type="a">
+ <li>Right-click the project and click Run As > Run Symbian OS Application on Emulator.</li>
+ <li>Click the Run > Run (<span class="code">CTRL-F11</span>) menu item.</li>
+ <li>Click the Run (<img src="../images/icon_run.png" alt="Run icon" width="16" height="16" align="absmiddle">) icon in the toolbar.</li>
+ </ol>
+ </li>
+ <li>Select the Process to launch in the Executable Selection page, then click Next.<br />
+ <p><img src="../images/new_launch_config_03.png" width="671" height="433"></p>
+ </li>
+ <li>Set the Build (if required) before launching option in the Build Options Selection page, then click Next.<br />
+ <p><img src="../images/new_launch_config_04.png" width="671" height="433"></p>
+ </li>
+ <li>Verify the new launch configuration settings in the New Launch Configuration page.<br />
+ <p><img src="../images/new_launch_config_05.png" width="671" height="433"></p>
+ </li>
+ <li>(Optional) Checkmark the Advanced settings option to further customize the launch configuration.</li>
+ <li>Click Finish. <br />
+ <p>Carbide launches the emulator, transfers the HelloWorld executable to it, then launches the program (see below). You can then use the soft-keys to choose actions from the <strong>Options</strong> soft-menu. Click the <strong>Exit</strong> soft-key to close the emulator and return to Carbide.c++.</p>
+ <p align="left"><img src="../images/new_launch_config_08.png" alt="Emulator" width="235" height="450"></p>
+ </li>
+ </ol>
+ <p>With a launch configuration in place, its now possible to edit, build, and run a project in the emulator. However, since none of us can write perfect code the first time the use of a debugger is essential for further development of our project.</p>
+</div>
+<h4><strong>NEXT STEP</strong> > <a href="new_proj_from_template_04.htm">Controlling and debugging</a> the running program using the Carbide debugger</h4>
+<h4>Other references</h4>
+<ul>
+
+ <li><a href="./">Creating New Projects Tutorial</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>
\ No newline at end of file
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/tutorials/new_proj_from_template_04.htm Tue Jul 13 15:35:51 2010 -0500
@@ -0,0 +1,67 @@
+<!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" />
+<title>Launching and debugging an executable </title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+</head>
+<body bgcolor="#FFFFFF">
+<h2><strong>Launching and debugging an executable </strong></h2>
+<p>In this example we show how to create a new project using one of the built-in Carbide templates, how to build it into an executable, and how to launch the debugger to verify program accuracy. The steps to do this include:</p>
+<ol>
+ <li><a href="new_proj_from_template_01.htm">Creating</a> a project from a project template</li>
+ <li><a href="new_proj_from_template_02.htm">Building</a> an executable based on the project sources</li>
+ <li><a href="new_proj_from_template_03.htm">Defining</a> a launch configuration for running or debugging the application</li>
+ <li><strong>Launching and debugging an executable using the Carbide debugger</strong></li>
+</ol>
+<hr>
+<p> </p>
+<p class="note"><b>NOTE</b> You can only debug compiled programs. Use the <a href="../projects/prj_build.htm">Build Project</a> command to compile project sources into a binary file if you do not already have an executable in the project. A symbolics (<span class="code">.sym</span>) file is also required for debugging on a target device. Ensure that a <span class="code">.sym</span> file has been created. If you are importing an existing application, you may have to rebuild the application and create a related <span class="code">.sym</span> file. Make sure a <span class="code">.sym</span> file has been created in the output directory.</p>
+<div class="step">
+ <h4><strong></strong>Launching and debugging an executable</h4>
+ <ol>
+ <li>Select the project to debug in the Project Explorer view.<br />
+ <p>For this example you should choose the HelloWorld project created in <a href="new_proj_from_template_01.htm">Step 1</a> of this tutorial.</p>
+ </li>
+ <li>Set a breakpoint in the project.<br>
+ <p>Open the <span class="code">\src\HelloWorldAppUi.cpp</span> file and <a href="../../debugger/breakpoints/toggling_breakpoints.htm">set</a> a breakpoint in the <span class="code">HandleCommandL</span> routine on Line 103.</p>
+ <p><img src="../images/debugging_project_02.png" alt="Setting a breakpoint" width="577" height="192"></p>
+ </li>
+ <li>Launch the debug session.<br />
+ <p>To run the project on the chosen target and start a debug session use one of the following actions. Clicking Debug is the most common choice as it enables you to assume control of the executable should you encounter a problem.</p>
+ <ul>
+ <li>Right-click the project and choose Debug As > Debug Symbian OS Application on Emulator.</li>
+ <li>Click the Run > Debug (<span class="code">F11</span>) menu item.</li>
+ <li>Click the Debug (<img src="../images/icon_debug.png" alt="Debug icon" width="17" height="17" align="absmiddle">) icon in the toolbar.</li>
+ </ul>
+ <p>The emulator is launched and the <a href="../../reference/perspective_debug.htm">Debug</a> perspective appears to manage the debug session.</p>
+ </li>
+ <li>Click the Options soft-menu and select any menu option to hit the breakpoint set in Step 2. <br />
+ <p><img src="../images/debugging_project_04.png" alt="Select menu option" width="360" height="397"></p>
+ <p>Which returns control to the <strong>Debug</strong> perspective in Carbide. Use the various views to examine the program as it runs. Examine variables, set more breakpoints, etc.</p>
+ <p><img src="../images/debugging_project_05.png" alt="Select menu option" width="749" height="626"></p>
+ </li>
+ <li>Use any of the step commands in the Debug view to step through the program source code.<br />
+ <ul>
+ <li>Click Step Into (<span class="code">F5</span>) to execute the current line and enter a function or method.</li>
+ <li>Click Step Over (<span class="code">F6</span>) to execute the current line.</li>
+ <li>Click Step Return (<span class="code">F7</span>) to execute lines until exiting the function or method.</li>
+ </ul>
+ </li>
+ <li>Click the Resume icon in the Debug view to return control to the program.</li>
+ <li>Click the Exit soft-key in the emulator to exit the debug session.<br />
+ <p>The HelloWorld program stops, the emulator exits, and control returns to Carbide.</p>
+ </li>
+ </ol>
+</div>
+<p>That's it. Congratulations on creating, building, and debugging a Carbide project.</p>
+<h4>Other references</h4>
+<ul>
+
+ <li><a href="./">Creating New Projects Tutorial</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>
\ No newline at end of file
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/CreatingNewProjects.html Tue Jul 13 15:27:30 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/CreatingNewProjects.html Tue Jul 13 15:35:51 2010 -0500
@@ -1,101 +1,101 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
-<html>
-<head>
- <title>Creating New Projects</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-</head>
-<body>
-<h2>Creating New Projects</h2>
- <div class="Bodytext">
- <p>New projects are created using the <b>New Project Wizard</b>. Carbide includes a number of templates that make creating projects for different SDKs and executables quick and easy.</p>
- <p class="note"><b>NOTE</b> You must have at least one recognized SDK installed before you can create a project. See the <a href="../reference/SDKPreferences.html">SDK Preferences panel</a> to determine if the installed SDKs are recognized by Carbide.c++ IDE. If the SDK you have is not recognized, you may still be able to <a href="sdks/sdk_add.htm">add</a> it to the Discovered Symbian OS SDK list.</p>
- <p class="note"><b>NOTE</b> When creating or importing projects the sources and SDK must be on the same drive. This is due to many of the internal SDK tools using an implicit working drive to calculate paths (e.g. \epoc32\tools). Avoid spaces in SDK paths since this will also cause problems.</p>
- <div class="step">
- <h3>Creating New Symbian OS C++ Projects</h3>
- <ol>
- <li class="step">Select <b>File > New > Symbian OS C++ Project</b> to invoke the <b>New Project</b> wizard.</span></li>
- <p><img src="../images/step1.png" width="546" height="142" alt="" ></p>
- <li>The <b class="step">New Symbian OS C++ Project</b> wizard appears. Select a template related to an installed SDK.</li>
- <p>A project template provides the initial source files and project settings appropriate for the chosen project type. A brief description of each template appears below the list. The project type determines the type of program that you are writing.</p>
- <p class="note"><b>NOTE</b> If the selected template requires user input, additional wizard pages will collect data from the user before creating the project.</p>
- <p>Checkmark the <b>Filter templates based on enabled SDKs</b> option to only list SDKs enabled in the <a href="../reference/SDKPreferences.html">SDK Preferences</a> panel. Uncheck this option to list SDKs that can be used with Carbide. Click <b>Next</b>.</p>
- <p align="center"><img src="../images/step2.png" width="500" height="567" alt="" ></p>
- <li>Enter a name for your project. </li>
- <p>Checkmark the <b>Use default location</b> option to save the project in the current workspace by default or uncheck it to save to another location. Enter the path in the <b>Location</b> field or click <b>Browse</b> button to locate the directory. Click <b>Next</b>.</p>
- <p align="center"><span class="Image"><img src="images/new_proj_name_location.png" alt="new project" width="500" height="567"></span><span class="Image"><br>
- </span></p>
- <li>Select the <b>SDKs and Build Configurations</b>. </li>
- <p>Checkmark the <b>Filter SDKs based on selected template</b> option to only show build configurations based on the selected SDK template, or uncheck to show all enabled SDKs and their related build configurations.</p>
- <p align="center"><img src="../images/step4.png" width="500" height="567" alt="" ></p>
- <p class="Image">The Symbian OS SDKs wizard page shows a tree of the SDKs and the type of builds available within that SDK. Select a single SDK
- if the program you are developing is for just one version of a platform,
- or select multiple SDKs to build the program for multiple build platforms or SDK versions.</p>
- <p> The build configuration allows you to specify the compiler(s) to
- do the build, and whether debug and/or release builds are required. For this example we recommend using the Emulator Debug version as the <a href="../concepts/build_configurations.htm">build configuration</a>. Later, you can <a href="projects/prj_set_build_tgt.htm">switch</a> to another build configuration to create the project for a specific device.</p>
- <p> Click <b>Next</b>.</p>
- <li>Set the project properties in the <b>Basic Settings</b> page. </li>
- <div align="center"><img src="../images/step5.png" width="500" height="567" alt="" > </div>
- <blockquote>
- <p align="left" class="note"><b>NOTE</b> The basic properties for a project may change based on the template selected for a particular project type. </p>
- <p align="left" style="font-weight: normal;">Fill in the applicable fields, which
- may include UID2, UID3, Vendor ID, Author, Support Email, Copyright
- notice and Target Type for console EXEs.</p>
-
- <p>Application UID (or UID3) is used to uniquely identify the binary (EXE or DLL) within the system. The purpose of UID 3 is to prevent one executable from interfering the operation of another executable.</p>
- <p> A Vendor ID (VID) is a unique identifier for the organization that is supplying the program. In versions of Symbian OS with platform security, a program can read a VID at runtime to check that a binary comes from a particular source. In most cases, the VID should be zero, meaning that source of the executable is not required for any security checks.</p>
- <p style="font-weight: normal;">UID 2 is a unique identifier number that identifies the type of interface that the
- project implements. The values are defined by Symbian</p>
-
- <ul>
- <li>For GUI applications, it is always 0x100039CE</li>
- <li>For static interface DLLs, the UID 2 is always 0x1000008d</li>
- <li>For polymorphic DLLs, the UID2 is defined by the framework which is being implemented</li>
- </ul>
- Author, Copyright notice, and Text to be shown are used in comments created by the wizard in the source code.
- <p><span style="font-weight: normal;"> For more information on UIDs
- and Vendor IDs, see </span><a
- href="https://www.symbiansigned.com/app/page/uidfaq"
- style="font-weight: normal;">Symbian Signed</a>,
- <span style="font-weight: normal;">which allocates these values.</span> </p>
- </blockquote>
- <li span style="font-weight: normal;">
- Click <b>Next</b> to move to the <b>Project Directories</b> page.</li>
- <div class="Figure">
- <p align="center" class="Image"><img src="../images/step6.png" width="500" height="567" alt="" ><br>
- </p>
- <p class="note" style="font-weight: normal;"> <b>NOTE</b> The project directories depends on the selected template. That is, the directories required to store project data may
- change based on the template used. </p>
- </div>
- <p>Accept the defaults or enter the names for Include and Source folders to be created under the project root directory. Generated files will be copied to these directories.</p>
- <li> Click <b>Finish</b> to create the project.</li>
- <p>This generates the necessary files for the project based on the template selected and show them in the <a href="../reference/view_cpp_projects.htm">Project Explorer</a> view.</p>
- </ol>
- <blockquote>
- <p align="center"><img src="../images/step7.png" width="277" height="339" alt="" > </p>
- </blockquote>
- </div>
- <blockquote>
- <p class="note"><b>NOTE</b> If the Carbide.c++ perspective is not visible, select the <b>Window
-> Open Perspective > Other</b>... command to list all available
- perspectives, then select the Carbide.c++ perspective and click OK.</p>
- </blockquote>
-</div>
-<h5>Concepts</h5>
-<ul>
- <li><a href="../concepts/Projects.html">Projects</a> </li>
- <li><a href="../concepts/Modify.html">Project Resources</a></li>
- <li><a href="../reference/ProjectPreferences.html">Project Preferences</a></li>
- <li><a href="../reference/ProjectTypeandSDK.html">Project Types</a></li>
- <li><a href="../concepts/templates.htm">Project Templates</a> </li>
-</ul>
- <h5>Tasks</h5>
- <ul>
- <li><a href="projects/prj_build.htm">Building Projects</a></li>
- <li><a href="projects/prj_debug_config.htm">Creating a Launch Configuration</a></li>
- <li><a href="start/carbide_debugging.htm">Debugging a Symbian OS Program</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>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+ <title>Creating New Projects</title>
+<link rel="StyleSheet" href="../../book.css" type="text/css"/>
+</head>
+<body>
+<h2>Creating New Projects</h2>
+ <div class="Bodytext">
+ <p>New projects are created using the <b>New Project Wizard</b>. Carbide includes a number of templates that make creating projects for different SDKs and executables quick and easy.</p>
+ <p class="note"><b>NOTE</b> You must have at least one recognized SDK installed before you can create a project. See the <a href="../reference/SDKPreferences.html">SDK Preferences panel</a> to determine if the installed SDKs are recognized by Carbide.c++ IDE. If the SDK you have is not recognized, you may still be able to <a href="sdks/sdk_add.htm">add</a> it to the Discovered Symbian OS SDK list.</p>
+ <p class="note"><b>NOTE</b> When creating or importing projects the sources and SDK must be on the same drive. This is due to many of the internal SDK tools using an implicit working drive to calculate paths (e.g. \epoc32\tools). Avoid spaces in SDK paths since this will also cause problems.</p>
+ <div class="step">
+ <h3>Creating New Symbian OS C++ Projects</h3>
+ <ol>
+ <li class="step">Select <b>File > New > Symbian OS C++ Project</b> to invoke the <b>New Project</b> wizard.</span></li>
+ <p><img src="../images/step1.png" width="506" height="318" alt="" ></p>
+ <li>The <b class="step">New Symbian OS C++ Project</b> wizard appears. Select a template related to an installed SDK.</li>
+ <p>A project template provides the initial source files and project settings appropriate for the chosen project type. A brief description of each template appears below the list. The project type determines the type of program that you are writing.</p>
+ <p class="note"><b>NOTE</b> If the selected template requires user input, additional wizard pages will collect data from the user before creating the project.</p>
+ <p>Checkmark the <b>Filter templates based on enabled SDKs</b> option to only list SDKs enabled in the <a href="../reference/SDKPreferences.html">SDK Preferences</a> panel. Uncheck this option to list SDKs that can be used with Carbide. Click <b>Next</b>.</p>
+ <p align="center"><img src="../images/step2.png" width="500" height="567" alt="" ></p>
+ <li>Enter a name for your project. </li>
+ <p>Checkmark the <b>Use default location</b> option to save the project in the current workspace by default or uncheck it to save to another location. Enter the path in the <b>Location</b> field or click <b>Browse</b> button to locate the directory. Click <b>Next</b>.</p>
+ <p align="center"><span class="Image"><img src="images/new_proj_name_location.png" alt="new project" width="500" height="400"></span><span class="Image"><br>
+ </span></p>
+ <li>Select the <b>SDKs and Build Configurations</b>. </li>
+ <p>Checkmark the <b>Filter SDKs based on selected template</b> option to only show build configurations based on the selected SDK template, or uncheck to show all enabled SDKs and their related build configurations.</p>
+ <p align="center"><img src="../images/step4.png" width="500" height="500" alt="" ></p>
+ <p class="Image">The Symbian OS SDKs wizard page shows a tree of the SDKs and the type of builds available within that SDK. Select a single SDK
+ if the program you are developing is for just one version of a platform,
+ or select multiple SDKs to build the program for multiple build platforms or SDK versions.</p>
+ <p> The build configuration allows you to specify the compiler(s) to
+ do the build, and whether debug and/or release builds are required. For this example we recommend using the Emulator Debug version as the <a href="../concepts/build_configurations.htm">build configuration</a>. Later, you can <a href="projects/prj_set_build_tgt.htm">switch</a> to another build configuration to create the project for a specific device.</p>
+ <p> Click <b>Next</b>.</p>
+ <li>Set the project properties in the <b>Basic Settings</b> page. </li>
+ <div align="center"><img src="../images/step5.png" width="500" height="500" alt="" > </div>
+ <blockquote>
+ <p align="left" class="note"><b>NOTE</b> The basic properties for a project may change based on the template selected for a particular project type. </p>
+ <p align="left" style="font-weight: normal;">Fill in the applicable fields, which
+ may include UID2, UID3, Vendor ID, Author, Support Email, Copyright
+ notice and Target Type for console EXEs.</p>
+
+ <p>Application UID (or UID3) is used to uniquely identify the binary (EXE or DLL) within the system. The purpose of UID 3 is to prevent one executable from interfering the operation of another executable.</p>
+ <p> A Vendor ID (VID) is a unique identifier for the organization that is supplying the program. In versions of Symbian OS with platform security, a program can read a VID at runtime to check that a binary comes from a particular source. In most cases, the VID should be zero, meaning that source of the executable is not required for any security checks.</p>
+ <p style="font-weight: normal;">UID 2 is a unique identifier number that identifies the type of interface that the
+ project implements. The values are defined by Symbian</p>
+
+ <ul>
+ <li>For GUI applications, it is always 0x100039CE</li>
+ <li>For static interface DLLs, the UID 2 is always 0x1000008d</li>
+ <li>For polymorphic DLLs, the UID2 is defined by the framework which is being implemented</li>
+ </ul>
+ Author, Copyright notice, and Text to be shown are used in comments created by the wizard in the source code.
+ <p><span style="font-weight: normal;"> For more information on UIDs
+ and Vendor IDs, see </span><a
+ href="https://www.symbiansigned.com/app/page/uidfaq"
+ style="font-weight: normal;">Symbian Signed</a>,
+ <span style="font-weight: normal;">which allocates these values.</span> </p>
+ </blockquote>
+ <li span style="font-weight: normal;">
+ Click <b>Next</b> to move to the <b>Project Directories</b> page.</li>
+ <div class="Figure">
+ <p align="center" class="Image"><img src="../images/step6.png" width="500" height="500" alt="" ><br>
+ </p>
+ <p class="note" style="font-weight: normal;"> <b>NOTE</b> The project directories depends on the selected template. That is, the directories required to store project data may
+ change based on the template used. </p>
+ </div>
+ <p>Accept the defaults or enter the names for Include and Source folders to be created under the project root directory. Generated files will be copied to these directories.</p>
+ <li> Click <b>Finish</b> to create the project.</li>
+ <p>This generates the necessary files for the project based on the template selected and show them in the <a href="../reference/view_cpp_projects.htm">Project Explorer</a> view.</p>
+ </ol>
+ <blockquote>
+ <p align="center"><img src="../images/step7.png" width="273" height="301" alt="" > </p>
+ </blockquote>
+ </div>
+ <blockquote>
+ <p class="note"><b>NOTE</b> If the Carbide.c++ perspective is not visible, select the <b>Window
+> Open Perspective > Other</b>... command to list all available
+ perspectives, then select the Carbide.c++ perspective and click OK.</p>
+ </blockquote>
+</div>
+<h5>Concepts</h5>
+<ul>
+ <li><a href="../concepts/Projects.html">Projects</a> </li>
+ <li><a href="../concepts/Modify.html">Project Resources</a></li>
+ <li><a href="../reference/ProjectPreferences.html">Project Preferences</a></li>
+ <li><a href="../reference/ProjectTypeandSDK.html">Project Types</a></li>
+ <li><a href="../concepts/templates.htm">Project Templates</a> </li>
+</ul>
+ <h5>Tasks</h5>
+ <ul>
+ <li><a href="projects/prj_build.htm">Building Projects</a></li>
+ <li><a href="projects/prj_debug_config.htm">Creating a Launch Configuration</a></li>
+ <li><a href="start/carbide_debugging.htm">Debugging a Symbian OS Program</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>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_build.htm Tue Jul 13 15:27:30 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_build.htm Tue Jul 13 15:35:51 2010 -0500
@@ -22,7 +22,7 @@
<p align="center"><img src="images/menu_build_project.png" width="359" height="341" /></p>
<p class="figure">Figure 1 - Right-click project name to build a project </p>
<div class="step">
- <h4>Building a Project</h4>
+ <h4>Building a project</h4>
<ul>
<li>Right-click the project name in the Project Explorer view and select Build Project (Figure 1) </li>
</ul>
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_config.htm Tue Jul 13 15:27:30 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_config.htm Tue Jul 13 15:35:51 2010 -0500
@@ -42,7 +42,7 @@
<p>The appropriate Run or <a href="../../reference/wnd_debug_configuration.htm">Debug</a> launch configuration window appears (Figure 1).</p>
</li>
</ul>
- <p align="center"><img src="images/wnd_launch_configuration_blank.png" width="736" height="505" alt="Undefined launch configuration"/> </p>
+ <p align="center"><img src="images/wnd_launch_configuration_blank.png" width="709" height="455" alt="Undefined launch configuration"/> </p>
<p class="figure">Figure 1 - Initial blank Debug launch configuration window</p>
</li>
<li>Select a type of launch configuration (for example, Symbian OS Emulation), then click the New launch configuration icon to create a new
@@ -51,7 +51,7 @@
appropriate section using the project name and target to create the configuration name.</p>
<p class="note"><b>NOTE</b> Project information is used to fill in the <b>Project</b> and <b>Process to launch</b> text boxes by default when you click <b>New</b>. You should not have to edit these for a normal run/debug project. If a <span class="code">bld.inf</span> has multiple MMP files listed, then the first executable in the list is used to fill in the executable field. Therefore, for projects with multiple MMPs you may need to change the executable field. </p>
</li>
- <p align="center"><img src="images/run_config_new.png" width="819" height="539" alt="New launch configuration" /> </p>
+ <p align="center"><img src="images/run_config_new.png" width="787" height="489" alt="New launch configuration" /> </p>
<p class="figure">Figure 2 - New launch configuration with name and settings filled in (emulator)</p>
<li>View the information to define the project and executable
--- a/core/com.nokia.carbide.cpp.doc.user/intro/tutorialsCarbideExtContent.xml Tue Jul 13 15:27:30 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/intro/tutorialsCarbideExtContent.xml Tue Jul 13 15:35:51 2010 -0500
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="UTF-8" ?>
+DLL<?xml version="1.0" encoding="UTF-8" ?>
<introContent>
@@ -12,11 +12,11 @@
<group label="Carbide.c++ Development" id="carbide-cpp" style-id="content-group">
<link
- label="Create an application emulator debug example"
- url="http://org.eclipse.ui.intro/showHelpTopic?id=/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_example.htm"
+ label="Creating New Symbian OS Projects"
+ url="http://org.eclipse.ui.intro/showHelpTopic?id=/com.nokia.carbide.cpp.doc.user/html/projects/tutorials/new_proj_from_template_00.htm"
id="carbide-sample"
style-id="content-link">
- <text>Learn how to create, build, and debug a program for the emulator called HelloCarbide using Carbide project templates.</text>
+ <text>Learn how to create, build, and debug programs on the emulator using Carbide project templates.</text>
</link>
<link
--- a/core/com.nokia.carbide.cpp.doc.user/tocCarbide.xml Tue Jul 13 15:27:30 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/tocCarbide.xml Tue Jul 13 15:35:51 2010 -0500
@@ -18,11 +18,11 @@
<topic label="Updating Carbide" href="html/tasks/start/carbide_updating.htm" />
<topic label="Tour of the UI" href="html/concepts/tour.html" />
<topic label="Concepts" href="html/concepts/concepts.htm" />
- <topic label="Application Emulator Example" href="html/tasks/start/carbide_example.htm" >
- <topic label="1. Creating New Projects" href="html/tasks/CreatingNewProjects.html" />
- <topic label="2. Building Projects and Symbian Components" href="html/tasks/projects/prj_build.htm" />
- <topic label="3. Creating a Launch Configuration" href="html/tasks/projects/prj_debug_config.htm" />
- <topic label="4. Debugging a Symbian OS Program" href="html/tasks/start/carbide_debugging.htm" />
+ <topic label="Creating New Projects tutorial" href="html/projects/tutorials/new_proj_from_template_00.htm" >
+ <topic label="Creating new projects from templates" href="html/projects/tutorials/new_proj_from_template_01.htm" />
+ <topic label="Building projects and components" href="html/projects/tutorials/new_proj_from_template_02.htm" />
+ <topic label="Defining a launch configuration" href="html/projects/tutorials/new_proj_from_template_03.htm" />
+ <topic label="Launching and debugging an executable" href="html/projects/tutorials/new_proj_from_template_04.htm" />
</topic>
</topic>
<topic label="Carbide Menus " href="html/reference/menus/menus.htm" >