Binary file core/com.nokia.carbide.cpp.doc.user/html/images/step1.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/images/step2.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/images/step4.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/images/step5.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/images/step6.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/images/step7.png has changed
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/CreatingNewProjects.html Wed Feb 10 14:32:22 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/CreatingNewProjects.html Wed Feb 10 14:38:27 2010 -0600
@@ -1,112 +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 in Tasks</title>
-<link rel="StyleSheet" href="../../book.css" type="text/css"/>
-</head>
-<body>
-<h2>Creating New Projects</h2>
- <div class="Bodytext">
- <p> A new Symbian OS C++ project can be created using the <b>New Project
- Wizard</b>. A number of templates are available that support different SDKs and executable types. </p>
- <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 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>
- <h3>Creating New Symbian OS C++ Projects</h3>
- <div class="step">
- <ol>
- <li style="font-weight: normal;"> Select <b>File
-> New > Symbian OS C++ Project</b> to invoke the <b>New Project</b> wizard.</li>
- <div align="center">
- <p><img src="../images/step1.png" width="506" height="318" alt="" ></p>
- <p> </p>
- </div>
- <li style="font-weight: normal;">The <b>New Symbian OS C++ Project</b> wizard appears. Select a template related to an installed SDK. Select the "Filter templates based on enabled SDKs" option to list only SDKs enabled in the <a href="../reference/SDKPreferences.html">SDK Preferences panel</a>. Unselect this option to list SDKs that can be used with Carbide. Click Next.</li>
- <p>A project template provides an initial set of source files and project settings appropriate for the project type that you have chosen. The text at the bottom of the window provides a brief description of each template. The project type determines the type of program that you are writing.</p>
- <p class="note"><b>NOTE</b><b> </b>If the selected template requires user input, additional wizard pages will collect data from the user before creating the project. </p>
- <p align="center"><img src="../images/step2.png" width="500" height="567" alt="" > </p>
- <p align="center"> </p>
- <li style="font-weight: normal;">Enter a name for your project. Enable the <b>Use default location</b> option to save the project in the current workspace. Unselect this option to save your project to another location. Enter the path in the <b>Location</b> field or click Browse button to locate the directory. Click <b>Next</b>.</li>
- <p align="center"><span class="Image"><img src="images/new_proj_name_location.png" alt="new project" width="500" height="400"></span></p>
- <p class="note"><strong>NOTE</strong> There will be two builders available in Carbide, one for SBSv1 (current version of Symbian Build System) and one for SBSv2 (newer version). The Builder option will only be displayed when a SBSv2 installation is detected.</p>
- <p class="Image">SBSv2 only works with recent versions of Symbian OS9.5. Both SBSv1 and SBSv2 are GNU make based build systems. SBSv1 uses Perl to generate make files, while SBSv2 uses Python. Select the appropriate builder for your project.</p>
- When building for SBSv2, the builder will set EPOCROOT to the absolute path (including drive letter) to the kit for the active build configuration. It will also add the path to the sbs bin directory to the start of the PATH variable. This is derived from the SBS_HOME environment variable.
- <p class="Image">For SBSv2, all build configurations (platform/target), including the built-in platforms (WISNCW, ARMV5), are declared in xml files in the \sbs\lib\config directory. The Build Configurations selection page will display only those kits known to support SBSv2.<span class="Image"><br>
- </span></p>
- <li style="font-weight: normal;">Select the <b>SDKs and Build Configurations</b>. Enable the <b>Filter SDKs based on selected template</b> option to show only the build configurations based on the SDK template you previously selected. Uncheck this option to show all enabled SDKs and their related build configurations.</li>
-
- <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 that are available to be used, and for each
- SDK, the type of builds that can be done. You can select a single SDK
- if you are developing the program for just one version of a platform,
- or multiple SDKs if you intend to build your program for multiple build platforms or SDK versions.</p>
- <p> The build configuration allows you to choose 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>
- <li span style="font-weight: normal;">Click <b>Next</b> to set 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. </blockquote>
- <blockquote>
- <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 template
- selected. That is, the directories required to store project data may
- change based on the template selected. </p>
- </div>
- <li style="font-weight: normal;">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. </li>
- <li style="font-weight: normal;"> Click <b>Finish</b> to create the project, which will generate the necessary files for the project based
- on the template selected and show them in the <a href="../reference/view_cpp_projects.htm">C/C++ Projects view</a>.</li>
- </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 © 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>
-
-</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="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>
Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/images/new_proj_name_location.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/build_console.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/run_config_new.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_build_config_select_tgt.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/images/wnd_launch_configuration_blank.png has changed
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_build.htm Wed Feb 10 14:32:22 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_build.htm Wed Feb 10 14:38:27 2010 -0600
@@ -1,83 +1,83 @@
-<!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>Building Projects</title>
-<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
-<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
-</head>
-<body bgcolor="#FFFFFF">
-<h2>Building Projects and Symbian Components </h2>
-<p>Building projects consists of a new 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">bldmake bldfiles</span> and <span class="code">abld 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="../CreatingNewProjects.html">Creating New Projects</a>. You can later <a href="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>—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>—(CTRL+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>
-<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>
- <ul>
- <li>Right-click the project name in the C/C++ Projects view and select Build Project (Figure 1) </li>
- </ul>
- <ol>
- <p></p>
- or
- </ol>
- <ul>
- <li>Select the Project > Build Project menu item </li>
- </ul>
- <ul>
- <p></p>
- or
- </ul>
- <ul>
- <li>Click the Build icon in the tool bar (Figure 2) to build the current build configuration </li>
- <p align="center"><img src="images/wnd_build_config_select_tgt.png" width="321" height="69" /></p>
- <p class="figure">Figure 2 - Build icon </p>
- <p>or
- </p>
- </ul>
- <ul>
- <li>Select a build configuration using the Build icon’s dropdown list in the tool bar (Figure 2)</li>
- </ul>
- <ol>
- <p>Carbide.c++ builds the project. During the build a build dialog will appear on screen and a task bar is shown at the bottom right of the perspective when the build is run in the background. All output as the build progresses is shown in the Console view and all build errors and warnings appear in the Problems view.</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. So Carbide will always check that makefiles are up-to-date and
- check dependencies.</p>
- <p>A project is also built if you make a change to a project 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>
- </ol>
- <p>When performing a build, output is displayed in the Console window. If you do not want to clear the console before each build you need to uncheck the option <span class="code">Always clear console before building</span> in the Build Console panel. This option is enabled by default. You can access this panel by selecting <b>Window > Preferences > C/C++ ><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)")'> Build Console</a></b> preference panel (figure 2).</p>
- <p>Not clearing the console can be 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>
-<p align="center"><img src="images/build_console.png" width="532" height="451" /></p>
-<p align="left" class="figure">Figure 4 - Build Console Preference Panel</p>
-<p> </p>
-</div>
- <h5>Concepts</h5>
- <ul>
- <li><a href="../../concepts/Projects.html">Projects</a></li>
-</ul>
- <h5>Tasks</h5>
- <ul>
- <li><a href="prj_clean.htm">Cleaning Projects</a> </li>
- <li><a href="../../reference/menus/compile_source.htm">Compile Source</a></li>
- <li><a href="../CreatingNewProjects.html">Creating Projects</a></li>
- <li><a href="prj_debug_config.htm">Creating a Launch Configuration</a></li>
- <li><a href="../start/carbide_debugging.htm">Debugging a Symbian OS Program</a></li>
- <li><a href="../../reference/menus/build_symbian_comp.htm">Build Symbian Component</a></li>
- <li><a href="../../reference/menus/clean_symbian_comp.htm">Clean Symbian Component</a></li>
- <li><a href="../../reference/menus/build_pkg_file.htm">Build Package (.pkg) File</a></li>
- <li><a href="../ImportingProjects.html">Importing BLD.INF Files</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>
-
-</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>Building Projects</title>
+<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
+<script language="JavaScript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
+</head>
+<body bgcolor="#FFFFFF">
+<h2>Building Projects and Symbian Components </h2>
+<p>Building projects consists of a new 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">bldmake bldfiles</span> and <span class="code">abld 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="../CreatingNewProjects.html">Creating New Projects</a>. You can later <a href="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>—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>—(CTRL+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>
+<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>
+ <ul>
+ <li>Right-click the project name in the Project Explorer view and select Build Project (Figure 1) </li>
+ </ul>
+ <ol>
+ <p></p>
+ or
+ </ol>
+ <ul>
+ <li>Select the Project > Build Project menu item </li>
+ </ul>
+ <ul>
+ <p></p>
+ or
+ </ul>
+ <ul>
+ <li>Click the Build icon in the tool bar (Figure 2) to build the current build configuration </li>
+ <p align="center"><img src="images/wnd_build_config_select_tgt.png" width="341" height="128" /></p>
+ <p class="figure">Figure 2 - Build icon </p>
+ <p>or
+ </p>
+ </ul>
+ <ul>
+ <li>Select a build configuration using the Build icon’s dropdown list in the tool bar (Figure 2)</li>
+ </ul>
+ <ol>
+ <p>Carbide.c++ builds the project. A build dialog and a task bar appear during a build process. All build output is shown in the Console view while build errors and warnings appear in the Problems view.</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>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>
+ </ol>
+ <p>When performing a build, output is displayed in the Console window. 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>Build Console</b> panel. This option is enabled by default. You can access this panel by selecting <b>Window > Preferences > C/C++ ><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)")'> Build Console</a></b> preference panel (figure 2).</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>
+<p align="center"><img src="images/build_console.png" width="562" height="446" /></p>
+<p align="left" class="figure">Figure 4 - Build Console Preference Panel</p>
+<p> </p>
+</div>
+ <h5>Concepts</h5>
+ <ul>
+ <li><a href="../../concepts/Projects.html">Projects</a></li>
+</ul>
+ <h5>Tasks</h5>
+ <ul>
+ <li><a href="prj_clean.htm">Cleaning Projects</a> </li>
+ <li><a href="../../reference/menus/compile_source.htm">Compile Source</a></li>
+ <li><a href="../CreatingNewProjects.html">Creating Projects</a></li>
+ <li><a href="prj_debug_config.htm">Creating a Launch Configuration</a></li>
+ <li><a href="../start/carbide_debugging.htm">Debugging a Symbian OS Program</a></li>
+ <li><a href="../../reference/menus/build_symbian_comp.htm">Build Symbian Component</a></li>
+ <li><a href="../../reference/menus/clean_symbian_comp.htm">Clean Symbian Component</a></li>
+ <li><a href="../../reference/menus/build_pkg_file.htm">Build Package (.pkg) File</a></li>
+ <li><a href="../ImportingProjects.html">Importing BLD.INF Files</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/projects/prj_debug_config.htm Wed Feb 10 14:32:22 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_config.htm Wed Feb 10 14:38:27 2010 -0600
@@ -18,23 +18,21 @@
</ul>
<div class="step">
<h4>Creating a Default Launch Configuration</h4>
-<p class="note"><b>NOTE</b> Carbide.c++ only creates a new default launch configuration when it cannot find one in the project. If the project already contains a launch configuration, Carbide.c++ launches that instead. </p>
+<p class="note"><b>NOTE</b> Carbide only creates a new default launch configuration when it cannot find one in the project. If the project already contains a launch configuration, Carbide launches that instead. </p>
<ul>
<li>Click the <b>Run</b> (<img src="../../images/icons/btn_run.png" alt="Run icon" width="16" height="16" align="middle" />) or <b>Debug</b> (<img src="../../images/icons/btn_debug.png" width="17" height="16" align="middle" alt="Debug icon"/>) icon in the tool bar
<p>or</p>
</li>
<li>Choose Select <b>Run > Run</b> menu option to launch the project or <b>Run > Debug</b> menu option to debug the project</li>
- <p>Carbide.c++ creates a default launch configuration for the project and begins running or debugging the project. If the project already has a defined launch configuration, clicking Run or Debug uses it instead of creating a new one. There are two possible scenarios when creating a default launch configuration: </p>
+ <p>Carbide creates a default launch configuration for the project that is used to run or debug the project. If the project already has a defined launch configuration, clicking <b>Run</b> or <b>Debug</b> uses it instead of creating a new one. There are two possible scenarios when creating a default launch configuration: </p>
<ul>
- <li><b>for emulator targets </b> - an emulator launch configuration is created based on the project settings </li>
+ <li><b>for emulator targets</b> <b> - an emulator launch configuration is created based on the project settings </b></li>
<li><b>for target devices</b> - the <a href="../../projects/launch/wiz_new_launch_config.htm">New Launch Configuration Wizard</a> appears asking for additional information</li>
</ul>
</ul>
</div>
- <p class="note"><b>NOTE</b> To see if a project already has a launch configuration, open a Run or Debug window using the <b>Run > Open Run Dialog...</b> or <b>Run > Open Debug Dialog...</b> menu items.
-
- </p>
- <p>In the event that the default launch configuration settings need to be changed, it is possible to edit them in the <a href="../../reference/wnd_debug_configuration.htm">Debug</a> window, or create a new launch configuration for the project that deviates from the default settings.</p>
+ <p class="note"><b>NOTE</b> To see if a project already has a launch configuration, open a Run or Debug window using the <b>Run > Run As</b> or <b>Run > Debug As</b> menu items. </p>
+<p>In the event that the default launch configuration settings must be changed, edit them in the <a href="../../reference/wnd_debug_configuration.htm">Debug</a> window, or simply create a new launch configuration for the project that deviates from the default settings.</p>
<div class="step">
<h4>Creating a Custom Launch Configuration </h4>
<ol>
@@ -44,16 +42,16 @@
<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="709" height="455" alt="Undefined launch configuration"/> </p>
+ <p align="center"><img src="images/wnd_launch_configuration_blank.png" width="736" height="505" 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
configuration of that type.
- <p>A new configuration appears in the Configuration list under the
+ <p>A new configuration appears in the configuration list under the
appropriate section using the project name and target to create the configuration name.</p>
- <p class="note"><b>NOTE</b> By default, when you click New, the project information is used to fill in the Project and Process to launch text boxes. You normally should not have to edit these for a run/debug a project. If a bld.inf has multiple MMPS then the first executable named in the list of MMP files is used to fill in the executable field. Therefore, for projects with multiple MMPs you may need to change the executable field. </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="787" height="489" alt="New launch configuration" /> </p>
+ <p align="center"><img src="images/run_config_new.png" width="819" height="539" 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
@@ -94,7 +92,7 @@
<li><a href="prj_build.htm">Building Projects</a></li>
<li><a href="prj_debug_dlls.htm">Debugging DLLs</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>
+<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/start/carbide_debugging.htm Wed Feb 10 14:32:22 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_debugging.htm Wed Feb 10 14:38:27 2010 -0600
@@ -10,38 +10,28 @@
<body bgcolor="#FFFFFF">
<h2>Debugging a Symbian OS Program</h2>
<p>Use the Carbide.c++ debugger to debug a compiled Symbian OS program in an emulator or on-device. The same process works for other emulators and target devices as well.</p>
-<p class="note"><b>NOTE</b> This example uses an emulator. The steps are identical for on-device debugging, although a .sym file is not needed for emulator builds.</p>
+<p class="note"><b>NOTE</b> This example uses the emulator included with the S60 5th Edition SDK. The steps are identical for on-device debugging, although a <span class="code">.sym</span> file is not needed for emulator builds.</p>
<div class="step">
<h4>Debugging a Symbian OS program</h4>
-<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. You will also need a symbolics ( .sym) file for debugging on a target device. Ensure that a .sym file has been created. If you are importing an existing application, you may have to rebuild the application and create a related .sym file. Make sure a .sym file has been created in the output directory.</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>
<ol>
- <li>Set a breakpoint in the HelloCarbide program</li>
- <p>Open the <span class="code">\src\CHelloCarbideAppUI.cpp</span> file and <a href="../breakpoints/pgm_bp_setting.htm">set a breakpoint</a> in the <span class="code">HandleCommandL</span> routine.</p>
- <p align="center"><img src="images/debug_set_breakpoint.png" width="602" height="238" /></p>
- <p class="figure">Figure 1 - Breakpoint set in <span class="code">CHelloCarbideAppUI</span>::HandleCommandL routine. </p>
- <li>Launch the Carbide.c++ debugger and S60 EPOC Emulator</li>
- <p><a href="../../debugger/debug/cmds_starting.htm">Start</a> the Carbide debugger which launches the S60 EPOC Emulator and installs the HelloCarbide application. For on-device debugging, the application is installed on the target device.</p>
- <p align="center"><img src="images/debug_s60_emulator_launch.png" width="293" height="391" /></p>
- <p class="figure"><span class="figure">Figure 2 - S60 Emulator launches</span></p>
- <li>Open the Installed directory within the S60 Emulator or your target device </li>
- Use the S60 Emulator controls to locate and open the Installation directory. Select Open from the Options menu (Figure 3).
- <p align="center"><img src="images/debug_s60_emulator_02.png" width="352" height="168" /></p>
- <p class="figure">Figure 3 - Open the Installed directory </p>
- <li>Launch the HelloCarbide application</li>
- <p>Use the S60 Emulator or target device controls to launch the HelloCarbide application (Figure 4).
- </p>
- <p align="center"><img src="images/debug_s60_emulator_03.png" width="122" height="106" /></p>
- <p class="figure">Figure 4 - Launch the HelloCarbide application </p>
- <p>The HelloCarbide application launches (Figure 5). </p>
- <p align="center"><img src="images/debug_s60_emulator_04.png" width="293" height="391" /></p>
- <p class="figure">Figure 5 - HelloCarbide application running on S60 Emulator </p>
- <li>Click the Options soft-key on the S60 Emulator to display the Select menu.</li>
- <li>Choose the Message menu item and press the Select soft-key to send a message (Figure 6).</li>
- <p></p><p align="center"><img src="images/debug_s60_emulator_05.png" width="384" height="254" /></p>
- <p class="figure">Figure 6 - Send Message to HelloCarbide application </p>
- <p>The <span class="code">HandleCommandL</span> breakpoint is hit in the program and control returns to the Carbide.c++ debugger (Figure 7). You can now set additional breakpoints, examine variables, or use the<a href="../../debugger/debug/viewing_debug.htm"> Debug view</a> buttons to control the program. </p>
- <p align="center"><img src="images/debug_s60_emulator_06.png" width="602" height="238" /></p>
- <p class="figure">Figure 7 - Back in the CHelloCarbideAppUI::HandleCommandL routine</p>
+ <li>Set a breakpoint in the MyProject program</li>
+ <p>Open the <span class="code">\src\MyProjectAppUI.cpp</span> file and <a href="../breakpoints/pgm_bp_setting.htm">set a breakpoint</a> in the <span class="code">HandleCommandL</span> routine.</p>
+ <p align="center"><img src="images/debug_set_breakpoint.png" width="707" height="253" /></p>
+ <p class="figure">Figure 1 - Breakpoint set in MyProjectAppUI::HandleCommandL routine. </p>
+ <li>Launch the Carbide debugger and S60 SDK Emulator</li>
+ <p><a href="../../debugger/debug/cmds_starting.htm">Start</a> the Carbide debugger which launches the S60 SDK Emulator, installs and launches the executable. For on-device debugging, the application is installed on the target device.</p>
+ <p>The HelloCarbide application launches (Figure 2). </p>
+ <p align="center"><img src="images/debug_s60_emulator_04.png" width="465" height="811" /></p>
+ <p class="figure">Figure 2 - MyProject application running on S60 Emulator </p>
+ <p class="note"><b>NOTE</b> For SDKs prior to the S60 5th Edition it may be necessary to locate the installed application and manually launch it in the emulator or on the target device.</p>
+ <li>Click the Options soft-key on the S60 Emulator to display the Options menu.</li>
+ <li>Choose the Message menu item and press the Select soft-key to send a message (Figure 3).</li>
+ <p></p><p align="center"><img src="images/debug_s60_emulator_05.png" width="465" height="458" /></p>
+ <p class="figure">Figure 3 - Send Message to MyProject application </p>
+ <p>The <span class="code">HandleCommandL</span> breakpoint is hit in the program and control returns to the Carbide debugger (Figure 4). You can now set additional breakpoints, examine variables, or use the <a href="../../debugger/debug/viewing_debug.htm">Debug</a> view buttons to control the program. </p>
+ <p align="center"><img src="images/debug_s60_emulator_06.png" width="686" height="276" /></p>
+ <p class="figure">Figure 4 - Back in the CMyProjectAppUI::HandleCommandL routine</p>
</ol>
<p>That's it for this basic introduction to debugging with Carbide.c++.</p>
</div>
@@ -55,7 +45,7 @@
<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>
</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>
+ <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
Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/start/images/debug_s60_emulator_04.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/start/images/debug_s60_emulator_05.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/start/images/debug_s60_emulator_06.png has changed
Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/start/images/debug_set_breakpoint.png has changed
--- a/core/com.nokia.carbide.cpp/html/help_home.html Wed Feb 10 14:32:22 2010 -0600
+++ b/core/com.nokia.carbide.cpp/html/help_home.html Wed Feb 10 14:38:27 2010 -0600
@@ -22,6 +22,7 @@
<ul>
<li>New technologies support:
<ul>
+ <li>PnP On-device Debugging</li>
<li><a href="PLUGINS_ROOT/com.nokia.carbide.cpp.sysdoc.hover/resources/help context/dl_hover/html/index.html">Hover Help</a></li>
<li><a href="PLUGINS_ROOT/com.nokia.carbide.cpp.doc.user/html/qt_help/qt_overview.htm">Qt SDK for S60</a></li>
</ul>
--- a/core/com.nokia.carbide.cpp/html/intro/migrateExtensionContent.xml Wed Feb 10 14:32:22 2010 -0600
+++ b/core/com.nokia.carbide.cpp/html/intro/migrateExtensionContent.xml Wed Feb 10 14:38:27 2010 -0600
@@ -9,7 +9,6 @@
style="carbide.css"
path="migrate/@">
- <!-- Removed 20091201 since links are no longer valid
<group label="Carbide.c++ Development" id="carbide-cpp" style-id="content-group">
<link
@@ -21,7 +20,6 @@
</link>
</group>
- -->
</extensionContent>
--- a/core/com.nokia.carbide.cpp/plugin.xml Wed Feb 10 14:32:22 2010 -0600
+++ b/core/com.nokia.carbide.cpp/plugin.xml Wed Feb 10 14:38:27 2010 -0600
@@ -139,11 +139,9 @@
configId="org.eclipse.ui.intro.universalConfig"
content="html/intro/webresourcesExtensionContent2.xml" />
- <!-- Removed 20091201 as links were outdated
<configExtension
configId="org.eclipse.ui.intro.universalConfig"
content="html/intro/migrateExtensionContent.xml" />
- -->
</extension>