Carbide.c++ User Guide

- The Symbian OS plug-ins for the Eclipse environment help provide support - for developers to create and build C++ programs that run on Symbian OS. + The Symbian plug-ins for the Eclipse environment help provide support + for developers to create and build C++ programs that run on Symbian.

- The plug-ins provide the following support to Symbian OS developers: + The plug-ins provide the following support to Symbian developers:

- Documentation is available in the C/C++ Development Toolkit User Guide (CDT) for the Symbian OS plug-ins that work with the C/C++ Development Toolkit (CDT). Programming for Symbian OS based platforms is described in the + Documentation is available in the C/C++ Development Toolkit User Guide (CDT) for the Symbian plug-ins that work with the C/C++ Development Toolkit (CDT). Programming for Symbian based platforms is described in the documentation supplied with the development kit that you use. Please consult - that documentation for further information on Symbian OS concepts and + that documentation for further information on Symbian concepts and development processes.

MBM File

- MBM, or multi-bitmap, is a Symbian OS-specific bitmap file format. This + MBM, or multi-bitmap, is a Symbian-specific bitmap file format. This file contains multiple bitmaps and can contain bitmaps with masks and bitmaps without masks. It optimizes the bitmap handling capability of Symbian - OS. The MMP Editor (in Sources tab > Resources > Bitmaps) and Symbian Project Navigator view provide support for creating and editing MBM - files. In the Symbian Project Navigator view you can right-click on a scalable icon makefile (for example, Icons_scalable_dc.mk) and select Add MBM/MIF Entry... to open the Edit MBM/MIF Contents window.

The tools that are available to support modification of existing project diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/concepts/SampleExampleProjectCreate.html --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/SampleExampleProjectCreate.html Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/SampleExampleProjectCreate.html Wed Oct 06 10:31:32 2010 -0500 @@ -15,14 +15,14 @@

Creating a DLL Project

Click File > New > Symbian OS C++ Project to invoke the New Symbian OS C++ Project wizard.
Click File > New > Symbian C++ Project to invoke the New Symbian C++ Project wizard.
Select Basic dynamically linked library (DLL) project template and click Next.

Figure 1. Select Basic DLL template

Enter a project name and specify a workspace location to store the project.

Figure 2. Project name and location information

Select the Symbian OS SDK and Build Configurations to use for this project, then click Next.
Select the Symbian SDK and Build Configurations to use for this project, then click Next.

Figure 3. SDK selection for project

Enter Specify UID2 as “0x0000008d”, your name as the Author and your Copyright notice. diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/concepts/autotargeting.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/autotargeting.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/autotargeting.htm Wed Oct 06 10:31:32 2010 -0500 @@ -15,7 +15,7 @@
The debugger will target any executable not already started whenever a "process load" event occurs, resolving its breakpoints as well.

Debugging DLLs

One common debugging DLL use case is when the developer doesn't know which process calls the DLL. This makes it difficult to debug the DLL because you doesn't know which process to attach to nor start. Carbide enables DLL debugging by simply attaching the DLL to any running process as long as the DLL is included in the Executables view. See Attaching to a Process for more details.

Other References

Executables

Breakpoints Overview

A breakpoint is a marker set on a specific line of source code and is designed to halt program execution when encountered by the debugger. After you set a breakpoint at a key point in the program, you can halt its execution, examine its current state, and check register and variable values. You can also change values and alter the flow of normal program execution. Setting breakpoints helps you debug your program and verify its efficiency.

A project can have multiple breakpoints set in the source code files. All breakpoints in a project are shown in the Breakpoints view. Breakpoints are enabled or disabled on the currently selected line within a source code editor by selecting the Run > Toggle Breakpoint menu option, right-clicking the marker bar in the editor and selecting Toggle Breakpoint, or by pressing CTRL-SHIFT-B.

You can set a breakpoint on any executable line of code that the debugger can resolve. Lines containing comments and other non executable code cannot be assigned a breakpoint as they are normally stripped from the compiled binary. The debugger must load the symbols for a module before it can attempt to resolve breakpoints within the module. This is most easily done using the Executables view to import a binary file, especially if the binary is not in the workspace.

When the debugger attempts to resolve a breakpoint it will result in:

resolved — the symbols for the module are loaded and the breakpoint located in the executable that’s currently being debugged, circle icon changes to flagged icon

Other references

Executables view
Executables view
Setting Breakpoints
Enabling Breakpoints
Disabling Breakpoints
a project
a build configuration - a project level configuration that includes an SDK and any related files required to compile and build the project

Build configurations are defined when the project is created. A project can have any number of build configurations and more can be added as necessary. Each build configuration can have its own combination of tool settings to precisely control how it is defined and built. Build configurations are maintained in the project Properties window in the Carbide Build Configurations panel. To open the panel, select a project in the Project Explorer or Symbian Project Navigator view and select Project > Properties or right-click and select Properties.

You can select a build configuration in the Active Configuration group or use the Project > Active Configuration menu option to set which build configuration to launch when running or debugging a program. The currently selected project can be launched by clicking the Run () or Debug () control on the tool bar to launch the project with the currently active build configuration. When no project is selected the last project debugged will be launched.

If no launch configuration is present in the project, one is created on initial launch. Subsequent launches of the project will use either the last launch configuration or if more than one launch configuration exists, it uses the most correct one.

Build System Overview

The Carbide.c++ build system provides a wrapper around the standard Symbian OS build process utilizing component description files (bld.inf) and project definition files (.mmp files). Because the Carbide.++ build system provides a visual view into this system, it will be useful for new developers to the Symbian OS to become familiar with the basic Symbian OS build process. Further information on the Symbian OS build system can be found in the Symbian Developer Library under the Build Tools Guide and Build Tools Reference sections. If you are already familiar with the Symbian OS build system then you should feel right at home with the Carbide.c++ builder user interface.

In Carbide.c++, as in the Symbian OS, a project is described by a bld.inf file. Hence, all projects must start with a bld.inf file. Carbide.c++ supports either building all components of a project (including extension makefiles) or only building selected sub-components. This gives the developer the granularity to either build all of a project’s dependencies or, if you are working on very large projects, only building a small sub-component of a larger project.

The Carbide.c++ build system provides a wrapper around the standard Symbian build process utilizing component description files (bld.inf) and project definition files (.mmp files). Because the Carbide.++ build system provides a visual view into this system, it will be useful for new developers to the Symbian to become familiar with the basic Symbian build process. Further information on the Symbian build system can be found in the Symbian Developer Library under the Build Tools Guide and Build Tools Reference sections. If you are already familiar with the Symbian build system then you should feel right at home with the Carbide.c++ builder user interface.

In Carbide.c++, as in the Symbian, a project is described by a bld.inf file. Hence, all projects must start with a bld.inf file. Carbide.c++ supports either building all components of a project (including extension makefiles) or only building selected sub-components. This gives the developer the granularity to either build all of a project’s dependencies or, if you are working on very large projects, only building a small sub-component of a larger project.

Basic Build Commands

There are several methods of invoking the Symbian OS build tools on a project or source file.

There are several methods of invoking the Symbian build tools on a project or source file.

Build Project - The is the default build process which invokes the call: calls 'abld build <platform> <target>'. The basic build process insures that the project definition makefiles are up to date and calls 'bldmake bldfiles' for the current platform where necessary.
Compile - This command simply compiles a single file for a project by calling its makefile target directly.

NOTE The debugger has a setting under the Run/Debug > Launching preference page which performs a full build before the start of each debug session. If you prefer to do your own target build only you will want to turn the “Build (if required) before launching” setting off.

Command Line Arguments

The Carbide build system supports the use of command-line arguments for all stages of the build system. You can add these arguments in the Arguments pane of the +

The Carbide build system supports the use of command-line arguments for all stages of the build system. You can add these arguments in the Arguments pane of the Carbide Build Configurations panel in the Properties for <project> window.

For example, to generate a SYM file for UREL build you need to add the -debug argument to the abld makefile stage of the build process.

Always refer to the Symbian Developer Library to learn which arguments are supported by the SDK used by the project.

Concepts

This section of the User Guide provides an overview of the main concepts in -Carbide to create and build programs for Symbian OS.

The Symbian OS plug-ins are a set of Eclipse plug-ins that provide project, - SDK and build support for Symbian OS developers. The plug-ins extend the +Carbide to create and build programs for Symbian.

The Symbian plug-ins are a set of Eclipse plug-ins that provide project, + SDK and build support for Symbian developers. The plug-ins extend the functionality provided by Eclipse and the C/C++ Development Toolkit (CDT).

The plug-ins simplify Symbian OS development by removing the need to use - command line build tools, and provide a graphical interface to Symbian OS +

The plug-ins simplify Symbian development by removing the need to use + command line build tools, and provide a graphical interface to Symbian specific file formats, such as MBM.

The plug-ins provide a new perspective, called the Carbide.c++ Perspective, on +

The plug-ins provide a new perspective, called the Carbide.c++ Perspective, on the Eclipse workbench. This perspective enhances the standard CDT C/C++ perspective by allowing you to select easily the SDKs and build target types that you want to use for each project.

Breakpoints view - enable, disable, remove, or select all breakpoints
Debug view - restart, step into, over, or out of routines, terminate or suspend program execution
Memory view - add or remove memory monitors
Project Explorer view - manage projects, build, delete, freeze, run, debug, and other common project commands
Project Explorer view - manage projects, build, delete, freeze, run, debug, and other common project commands
Variables view - enable, disable, find, and change the format or value of variables displayed

TIP Experiment using the context menu in various views to discover additional capabilities.

Other revision systems are also supported but require the downloading of an Eclipse plug-in to add that capability to Carbide. Visit the eclipse-plugins.2y.net sites to locate the plug-ins you need.

Using SCM in Carbide

The SCM you install normally adds its commands to the Team sub-menu in the Project Explorer view's context menu (Figure 1). Some SCM's install their own menu to Carbide. If this is the case, refer to the documentation included with the plug-in for details.

Team commands

Figure 1. Team sub-menu

diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/concepts/emulators.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/emulators.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/emulators.htm Wed Oct 06 10:31:32 2010 -0500 @@ -9,8 +9,8 @@

Emulation Debugging

Symbian SDKs include an emulator that runs Symbian OS on a - Microsoft Windows host computer. The emulator provides the full range of Symbian OS +

Symbian SDKs include an emulator that runs Symbian on a + Microsoft Windows host computer. The emulator provides the full range of Symbian functionality, letting you do most development tasks on a single desktop computer. The emulator and the software you build for it with the Carbide.c++ software run natively on the Intel x86 family of processors.

In many cases, you can build and debug a complete application using the emulator, then test the application on the actual device. There are cases however, where you cannot use @@ -21,7 +21,7 @@

C:\Symbian\<version>\<sdk>\Epoc32\release\winscw\udeb

where Symbian is the path containing the subdirectories and version number of the Symbian OS SDK.

where Symbian is the path containing the subdirectories and version number of the Symbian SDK.

NOTE The first time you launch an emulator it may take some time to appear. Remember that it is implementing the operating system on the target device and that some setup time is required.

Related tasks

Symbian projects are defined by an .mmp file which specifies the essential elements of the project. All details of the project lifecycle are handled by the IDE. There is no editable makefile the user can edit to modify the build behavior of the project.

Related reference

MMP Editor
MMP Editor

diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/concepts/ngage_projects.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/ngage_projects.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/ngage_projects.htm Wed Oct 06 10:31:32 2010 -0500 @@ -17,7 +17,7 @@

Install the N-Gage SDK on your PC

Place your game project inside the N-Gage SDK

In Carbide.c++, click File > Import

Select Symbian OS Bld.inf File importer and navigate to your bld.inf file to import it

Select Symbian Bld.inf File importer and navigate to your bld.inf file to import it

Building the N-Gage project

Once the game project has been imported, use these steps to create an N-GAGE game file:

@@ -54,14 +54,14 @@

Figure 4 - Builder dialog with new N-Gage Builder defined

Click OK to close the Properties for project_name window

Build the project and its SISX file by selecting the Project > Build Project menu item

The Console view shows information as the project and it's SISX file are built and then the build of the installation file (N-GAGE).

For On-device Debugging

Deploying the N-Gage project to a device

Once you have an .N-GAGE game file, you need to deploy it on the target device:

Verify that you have a valid developer certificate on the target device given to you by the Nokia R&D Certificate Service. If not, get and install one.
Verify that you have CODA installed on the target device. If not, install it now using On-Device Connections > New Connection Wizard > Install remote agents pane.
Verify that you have CODA installed on the target device. If not, install it now using On-Device Connections > New Connection Wizard > Install remote agents pane.
Manually install the .N-GAGE file on the device

Debugging the Game project

@@ -69,7 +69,7 @@

Open Window > Preferences > Run/Debug > Launching preference panel and disable the Build (if required) before launching option under the General Options group
Right-click the project and choose Debug As > Debug Configuration to open the Debug Cinfigurations window
Create an Symbian OS Device (Install SIS) launch configuration +

Create an Symbian Device (Install SIS) launch configuration

In the Connection tab select the COM port used to connect to the device.
In the Installation tab, verify that the game SISX file is correct

Open Window > Preferences > Run/Debug > Launching and disable the Build (if required) before launching option under the General Options group
Right-click the project and choose Debug As > Debug Configurations to open the Debug Configurations window
Create an Symbian OS Emulation launch configuration
Create an Symbian Emulation launch configuration
Click Debug to launch the emulator
In the emulator, select File > Open, locate and select the .N-GAGE installation file and click Open to install the project
Open the Installation folder, launch the N-Gage runtime application

Precompiled Headers

Precompiled header support is available for Symbian OS projects that use the Nokia x86 +

Precompiled header support is available for Symbian projects that use the Nokia x86 compiler. Precompiled header files use the .pch++ extension and are only supported by emulator targets.

By default, the x86 compiler compiles the .pch++ file before compiling any .cpp files in a project.

A precompiled header file (.pch++) outputs to a new identically named file with the .mch extension. For example, HelloWorld.pch++ outputs as HelloWorld.mch. C++ source files must use the .pch++ extension.

General registers

Registers are the register contents of the central processing unit (CPU) of the host computer or the targeted device. When debugging projects using the emulator, only the host computer x86 registers are visible in the Registers view. When debugging projects on a device, only the target device registers are visible.

In most cases, the contents of all the registers can be modified. However, when debugging applications on a target device with Symbian OS Device (Install SIS), you cannot change the LR and SP registers.

In most cases, the contents of all the registers can be modified. However, when debugging applications on a target device with Symbian Device (Install SIS), you cannot change the LR and SP registers.

Figure 1. Registers view with possible register types

The types of registers can include:

diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/concepts/templates.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/templates.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/templates.htm Wed Oct 06 10:31:32 2010 -0500 @@ -17,7 +17,7 @@ Available Templates - Generic Symbian OS + Generic Symbian

Basic console application (EXE) - used for any SDK
Basic dynamically linked library (DLL) - used for any SDK

Eclipse and the C/C++ Development Toolkit (CDT) provides a rich collection of views, editors, wizards and preference windows for performing C++ - development. The Symbian OS plug-ins for Eclipse extend this user interface so - that you can perform the tasks involved in Symbian OS development from the - Eclipse workbench, instead of needing to use the Symbian OS command-line + development. The Symbian plug-ins for Eclipse extend this user interface so + that you can perform the tasks involved in Symbian development from the + Eclipse workbench, instead of needing to use the Symbian command-line toolchain.

- When you work with a Symbian OS C++ project, the workbench uses the Carbide C/C++ perspective, which will look + When you work with a Symbian C++ project, the workbench uses the Carbide C/C++ perspective, which will look something like this:

@@ -29,22 +29,22 @@ Development Toolkit documentation.

- The Symbian OS plug-ins also add new wizards and editors. You can use + The Symbian plug-ins also add new wizards and editors. You can use these to:

- Create new Symbian OS projects using the New command, which is available on the File menu, and on the - pop-up menus of the Project Explorer and Symbian Project Navigator views.
+ Create new Symbian projects using the New command, which is available on the File menu, and on the + pop-up menus of the Project Explorer and Symbian Project Navigator views.

For more information, see Creating New Projects.
- Import existing projects from Symbian OS bld.inf files using the Import command, which is + Import existing projects from Symbian bld.inf files using the Import command, which is available on the File menu, and on the pop-up menus of the Project Explorer and Symbian Project Navigator views.

For more information, see Importing Projects from a Bld.Inf File. @@ -52,7 +52,7 @@

- Add scalable graphics (MIF) and Symbian OS bitmaps (MBM) to projects, and edit these resources. You can add these using the New command, which is available on the File menu, and on the pop-up menus of the Project Explorer and Symbian Project Navigator views. MBM and MIF editors are provided to modify + Add scalable graphics (MIF) and Symbian bitmaps (MBM) to projects, and edit these resources. You can add these using the New command, which is available on the File menu, and on the pop-up menus of the Project Explorer and Symbian Project Navigator views. MBM and MIF editors are provided to modify the resources.

For more information, see Creating an MBM File.

diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/concepts/trk.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/trk.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/trk.htm Wed Oct 06 10:31:32 2010 -0500 @@ -11,13 +11,13 @@

Carbide On-device Debug Agent

The Carbide On-device Debug Agent (CODA) is a program that enables on-device debugging of phone prototypes, reference boards, and retail phones. An on-device debug agent is a program that is installed on a phone or reference board. It communicates with the debugger using a serial-over-Bluetooth or serial-over-USB connection. Through this serial communication, the on-device debug agent acts as the interface between the Carbide.c++ debugger and the target device. The CODA provides:

Debug agent running on Symbian OS
Provides a stable & integrated interface to Symbian OS
Debug agent running on Symbian
Provides a stable & integrated interface to Symbian
Used to debug applications on actual devices
Can be built-in to the OS image or installed as a .sis file

Using the on-device remote agent, one can use the Carbide.c++ IDE to debug programs running on phone hardware, making the debugging process much easier. The on-device debug agent works on all Nokia Qt SDK, Symbian^3, and Symbian TechView devkits.

The Symbian OS Device (Install SIS) is stored online and available for download and installation using the On-Device Connections > New Connection Wizard > Install remote agents pane.

The Symbian Device (Install SIS) is stored online and available for download and installation using the On-Device Connections > New Connection Wizard > Install remote agents pane.

Some of the key benefits to using an on-device debug agent include:

Easy debugging via serial interface (Bluetooth, USB, IrDA, etc)

There are two variations of the on-device debug agent, they are:

Symbian OS Device (Install SIS)—supports application debugging only and available to developers creating applications for devices. Developers do not have access to system level routines, system ROM, other user application code, cannot modify the LR and SR registers, and must use a SIS file to debug an application.
Symbian OS Device— - supports both application and limited ROM debugging (includes application executables and limited ROM based components (i.e. no device drivers) and available to original equipment manufacturers (OEM) for device creation and customization
Symbian Device (Install SIS)—supports application debugging only and available to developers creating applications for devices. Developers do not have access to system level routines, system ROM, other user application code, cannot modify the LR and SR registers, and must use a SIS file to debug an application.
Symbian Device— supports both application and limited ROM debugging (includes application executables and limited ROM based components (i.e. no device drivers) and available to original equipment manufacturers (OEM) for device creation and customization

Related tasks

Working with Debugger Data

This section explains how to work with data that the Carbide.c++ debugger generates. The following windows show various types of debugger data.

Console view —shows messages generated during the debugging session

Console view —shows messages generated during the debugging session

Workspace Information

A workspace is the default place to store and create resources like projects, folders, and files. These are then presented to the user in a perspective which enables the presentation and manipulation of the stored resources.

When Carbide is launched it asks for a workspace to open (Figure 1). As you can have multiple workspaces, all independent from each other, choosing the workspace containing the projects to work on is important. Projects within a workspace are shown in the Carbide workbench within the Project Explorer and C/C++ Project views. When you create a new project it is automatically added to the currently open workspace. You can import existing projects into a workspace from INF files.

Workspace Launcher dialog

Figure 1. Workspace Launcher dialog

WARNING Bld.inf imported projects are not copied, so do not delete the contents when deleting the project.

Carbide generates project support files, such as .project and .cproject and a .metadata folder, which stores preferences. Metadata files like ".project" are placed in the source tree. If adding these files to CVS causes a problem, these files may be excluded from CVS using Team > Ignored Resources preference panel to specify name patterns to exclude from version control.

Other references

- Select the type of Symbian OS device to debug. + Select the type of Symbian device to debug. @@ -287,7 +287,7 @@ - Symbian OS + Symbian Select the project, class, or file to create. diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/debugger.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/debugger.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger.htm Wed Oct 06 10:31:32 2010 -0500 @@ -1,12 +1,11 @@ - - - Carbide.c++ User Guide - - + + - - -

- - - - - - - - -

Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
- License: http://www.eclipse.org/legal/epl-v10.html

Carbide.c++ User Guide -

Version 3.0.0, Sept, 2010

+ +

+ + + + + + + + +

Copyright � 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
+ License: http://www.eclipse.org/legal/epl-v10.html

+ Carbide.c++ User Guide +

Version 3.0.0, Sept, 2010

- \ No newline at end of file + diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/resolving_breakpoints.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/resolving_breakpoints.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/resolving_breakpoints.htm Wed Oct 06 10:31:32 2010 -0500 @@ -10,7 +10,7 @@

Breakpoint Status Indicators

Breakpoints must be located and resolved by the debugger before they can be hit. When a breakpoint is hit in the module, the debugger halts program execution and displays the state of the program in the Debug perspective.

To hit a breakpoint during a debug session, the debugger must first load the symbols for an executable module and then attempt to resolve the breakpoints within the loaded module. Any module listed into the Executables view is available for loading by a debug session. If a module is not present in the Executable view you'll need to import it before the debugger to load and resolve any breakpoints within that module.

You set a breakpoint on any executable line of code that the debugger can resolve. Lines containing comments and other non executable code cannot be assigned a breakpoint as they are normally stripped from the compiled binary. Carbide helps by preventing you from setting a breakpoint on a non-compilable line of code.

When the debugger attempts to resolve a breakpoint the possible results are shown in Table 1.

Table 1 Breakpoint—type, icons, and states

diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/toggling_breakpoints.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/toggling_breakpoints.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/toggling_breakpoints.htm Wed Oct 06 10:31:32 2010 -0500 @@ -27,8 +27,8 @@

NOTE Once a breakpoint is removed from the Breakpoints view it cannot be recovered using the Breakpoints view, it must be set in an editor or disassembly view.

Breakpoints must first be loaded and resolved before they can be hit during a debug session. See Resolving Breakpoint States for more information on the various states a breakpoint can exhibit.

See Saving and importing breakpoints for information on storing breakpoint data sets for sharing or re-use.

TIP If you find that a breakpoint is not being hit during a debug session, verify that the EXE or DLL is listed in the Executables view.

TIP If debugging a server launched by a client, you must attach to the server process using the Symbian OS Data view in order to hit the breakpoints in the server. Alternately, you can launch the server and client as two independent EXEs using the same COM port and debug them that way.

TIP If you find that a breakpoint is not being hit during a debug session, verify that the EXE or DLL is listed in the Executables view.

TIP If debugging a server launched by a client, you must attach to the server process using the Symbian Data view in order to hit the breakpoints in the server. Alternately, you can launch the server and client as two independent EXEs using the same COM port and debug them that way.

Other references

Breakpoints overview

Use the Terminate command () to stop or halt a program based on the type of debugging session underway. Terminate behavior includes:

Emulator - terminates program execution and ends the debug session
Symbian OS Device - kills the process on the device and ends the debug session. To terminate without killing the process, use Disconnect instead.
Symbian Device - kills the process on the device and ends the debug session. To terminate without killing the process, use Disconnect instead.
Stop-mode soft attach - suspends the attached process while other processes continue to run on the device. If only a single process is running on the device, the device CPU is suspended. Once the CPU is suspended you must launch a new debug session to resume the device CPU.

This behavior differs from suspending a program, as this temporarily suspends execution.

Other references

Stepping into a routine

Use the Step Into command () to execute one source-code statement at a time and follow execution into a routine call.

When stepping through a program in a debug session the IDE attempts to match the program counter (PC) location in the executable with a known project source file. If there is no source file associated with the PC the debugger displays in the Debug view the current PC address of the thread (e.g. 0x6002CC11(EUSER.DLL)()) instead of the function name. At this point you can open the Disassembly view to step through the assembler code. This most commonly happens when trying to step into Symbian OS code. We recommend that you Step Return out of the OS code and back into your project to continue debugging.

When stepping through a program in a debug session the IDE attempts to match the program counter (PC) location in the executable with a known project source file. If there is no source file associated with the PC the debugger displays in the Debug view the current PC address of the thread (e.g. 0x6002CC11(EUSER.DLL)()) instead of the function name. At this point you can open the Disassembly view to step through the assembler code. This most commonly happens when trying to step into Symbian code. We recommend that you Step Return out of the OS code and back into your project to continue debugging.

Click the Step Into button () in the Debug view
Right-click the thread in the Debug view and select Step Into from the context menu
One of the SDKs is set as the "default" SDK
The SDK must have a valid EPOCROOT setting

In any of the above are missing or incorrect, Carbide.c++ can not build a Symbian OS program.

In any of the above are missing or incorrect, Carbide.c++ can not build a Symbian program.

Adding Program Resources

diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/index.xml --- a/core/com.nokia.carbide.cpp.doc.user/html/index.xml Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/index.xml Wed Oct 06 10:31:32 2010 -0500 @@ -25,7 +25,7 @@ - + @@ -47,7 +47,7 @@ --> - + @@ -174,13 +174,13 @@ - + - + @@ -192,7 +192,7 @@ - + @@ -238,14 +238,14 @@ - + - + @@ -385,7 +385,7 @@ - + @@ -393,14 +393,14 @@ - + - - + + - + @@ -420,7 +420,7 @@ - + @@ -640,7 +640,7 @@ - + diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/legal.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/legal.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/legal.htm Wed Oct 06 10:31:32 2010 -0500 @@ -1,36 +1,34 @@ - - - Legal - + + Legal + - -
License Information
-
COPYRIGHTS
-
Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. This component and the accompanying materials are made available under the terms of the License "Symbian Foundation License v1.0" which accompanies this distribution, and is available at the URL "http://www.symbianfoundation.org/legal/sfl-v10.html".
-
Initial Contributors:
-
Nokia Corporation - initial contribution
-
NOTICES
-
Portions of this product are covered by the following licenses:
-
-
Eclipse 3.6 (available at http://www.eclipse.org/legal/epl/notice.php)
-
Eclipse CDT 7.0 (available at http://www.eclipse.org/legal/epl/notice.php)
-
Eclipse EMF 2.5 (available at http://www.eclipse.org/legal/epl/notice.php)
-
Eclipse GEF 3.5 (available at http://www.eclipse.org/legal/epl/notice.php)
-
Eclipse Remote System Explorer-1.0 (available at http://www.eclipse.org/legal/epl-v10.html)
-
Eclipse System Search (available at http://www.eclipse.org/legal/epl/notice.php)
-
Apache Xerces-2.2.0 (available at http://www.apache.org/licenses/LICENSE-2.0)
-
Apache Batick-1.6 (available at http://www.apache.org/licenses/LICENSE-2.0)
-
Apache HttpClient-3.1.0 (available at http://www.apache.org/licenses/LICENSE-2.0)
-
Mozilla Rhino 1.5r2 (available at http://www.mozilla.org/NPL/)
-
OmniORB-4.0.4 (available at http://www.gnu.org/licenses/)
-
GNU Binutils (available at http://sources.redhat.com/binutils/)
-
Python 2.5.1 (available from http://www.python.org/download/releases/2.5/license/)
-
Psyco 1.5.2 (available from http://www.opensource.org/licenses/mit-license.php)
-
-

+
License Information
+
COPYRIGHTS
+
Copyright � 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. This component and the accompanying materials are made available under the terms of the License "Symbian Foundation License v1.0" which accompanies this distribution, and is available at the URL "http://www.symbianfoundation.org/legal/sfl-v10.html".
+
Initial Contributors:
+
Nokia Corporation - initial contribution
+
NOTICES
+
Portions of this product are covered by the following licenses:
+
+
Eclipse 3.6 (available at http://www.eclipse.org/legal/epl/notice.php)
+
Eclipse CDT 7.0 (available at http://www.eclipse.org/legal/epl/notice.php)
+
Eclipse EMF 2.5 (available at http://www.eclipse.org/legal/epl/notice.php)
+
Eclipse GEF 3.5 (available at http://www.eclipse.org/legal/epl/notice.php)
+
Eclipse Remote System Explorer-1.0 (available at http://www.eclipse.org/legal/epl-v10.html)
+
Eclipse System Search (available at http://www.eclipse.org/legal/epl/notice.php)
+
Apache Xerces-2.2.0 (available at http://www.apache.org/licenses/LICENSE-2.0)
+
Apache Batick-1.6 (available at http://www.apache.org/licenses/LICENSE-2.0)
+
Apache HttpClient-3.1.0 (available at http://www.apache.org/licenses/LICENSE-2.0)
+
Mozilla Rhino 1.5r2 (available at http://www.mozilla.org/NPL/)
+
OmniORB-4.0.4 (available at http://www.gnu.org/licenses/)
+
GNU Binutils (available at http://sources.redhat.com/binutils/)
+
Python 2.5.1 (available from http://www.python.org/download/releases/2.5/license/)
+
Psyco 1.5.2 (available from http://www.opensource.org/licenses/mit-license.php)
+
+

- \ No newline at end of file + diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/projects/images/perspective_carbide.png Binary file core/com.nokia.carbide.cpp.doc.user/html/projects/images/perspective_carbide.png has changed diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/projects/inf/INF_Editor.html --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/inf/INF_Editor.html Wed Oct 06 10:31:32 2010 -0500 @@ -0,0 +1,53 @@ + + +INF Editor + + + +
INF Editor - Overview Tab
+ +
+ The INF Editor allows you to view and modify Symbian project files and export files to be included in building your application. The settings displayed are those active for the active build configuration. However, changes made in the INF editor can be applied globally to all build configurations. Changes made in the INF editor are automatically written to the project's .INF file. You can view the .INF file by selecting the bld.inf tab located along the bottom of the INF editor.
+
+ The INF Editor is shown when an INF file is + opened from the Project Explorer view or Symbian Project Navigator view by double-clicking on the file. The INF Editor is shown in Figure 1.
+
+
Figure 1 - INF Editor
+
+ + +
Name Function
+
+ Components
+
+ Add components such as MMP and make files to be part of the normal build process.
+
+
Create New MMP File - creates a new MMP file at the bottom of the Component list.
+
Add Existing MMP File - imports a MMP file at the bottom of the Component list.
+
Add Existing Makefile - adds a smake file to the bottom of the Component list.
+
Edit - Select a component and click Edit to apply the Tidy attribute or specify the Build as ARM option.
+
Open - Select a component and click Open to open the component in an editor window.
+
Up - Select a component and click Up to move the component up in the list.
+
Down - Select a component and click Down to move the component down in the list.
+
Remove - Select a component and click Remove to remove the component from the build process.
+
+
+ Test Components +
+
+ Create, import, edit, open, move, or remove MMP and make files that are part of a test build process.
+
Other references
+
+
INF Editor - Add/Edit MMP File
+
INF Editor - Add/Edit Make File
+
INF Editor - Exports
+
+ + +
Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
+ License: http://www.eclipse.org/legal/epl-v10.html
+ + + + \ No newline at end of file diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/projects/inf/INF_Editor_addedit_make.html --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/inf/INF_Editor_addedit_make.html Wed Oct 06 10:31:32 2010 -0500 @@ -0,0 +1,47 @@ + + +INF Editor - Create/Edit Make + + + +
INF Editor - Create / Edit Makefile Entry
+ +
The Add Makefile entry dialog (figure 1) is used to add a makefile to the build process. Enter or browse to the make file in the File path field and, if desired, apply the Tidy attribute or specify the Build as ARM option to the make file.
+
+
Figure 1 - Add/Edit makefile entry
+
Table 1. Add/Edit Makefile entry — items
+ + + + + + + + + + + + + + + + + + + + + +
Name Function
File path
Type the path and filename for the makefile to create or click Browse to set a path.

Tidy
Specify the tidy attribute if the release that an .mmp file defines is internal to your component and not required by other components or for your component to execute.
Build as ARM Specifies the build_as_arm statement, which instructs an ARMV5 or later build to build the project for the ARM instruction set and not the THUMB instruction set.
Makefile format Set the format of the makefile to be created.
+
Other references
+
+
INF Editor
+
INF Editor - Exports
+
+ + +
Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
License: http://www.eclipse.org/legal/epl-v10.html
+ + + + \ No newline at end of file diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/projects/inf/INF_Editor_addedit_mmp.html --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/inf/INF_Editor_addedit_mmp.html Wed Oct 06 10:31:32 2010 -0500 @@ -0,0 +1,47 @@ + + +INF Editor - Add/Edit MMP + + + +
INF Editor - Add / Edit MMP File Entry
+ + The Add MMP File Entry dialog (figure 1) is used to add a mmp file and apply the Tidy, Manual, and Support attributes. +
+
Figure 1 - Add MMP File Entry
+
Table 1. Add MMP file entry — items
+ + + + + + + + + + + + + + + + + + + + + +
Name Function
File path
Type the path and filename for the MMP file to create or click Browse to set a path.
Tidy
Specify the tidy attribute if the release that an .mmp file defines is internal to your component and not required by other components or for your component to execute.
Manual Checkmark to indicate a test that requires manual interaction to complete.
Support Checkmark to not include the test in a batch file.
+
Other references
+
+
INF Editor
+
INF Editor - Exports
+
+ + +
Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
License: http://www.eclipse.org/legal/epl-v10.html
+ + + + \ No newline at end of file diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/projects/inf/INF_Editor_exports.html --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/inf/INF_Editor_exports.html Wed Oct 06 10:31:32 2010 -0500 @@ -0,0 +1,97 @@ + + +INF Editor Exports + + + +
INF Editor - Exports Tab
+ +
+ The INF Editor Exports pane lists files to be copied to the indicated destination path that are part of the normal build process. You can add files, edit paths, move files up or down in the list, or remove files from the list.
+
+
Figure 1 - INF Editor - Exports Pane
+
Table 1. Export tab — items
+ + + + + + + + + + + + + +
Name Function
Exports
Add, edit, arrange order, or remove files that will be part of the build process.
+
+
Add - Click to add a file to the list of files to be exported as part of the build process.
+
Edit - Select a file and click Edit to change the source and destination paths for the file.
+
Up - Select a file and click Up to move the file up in the list.
+
Down - Select a file and click Down to move the file down in the list.
+
Remove - Select a file and click Remove to remove the file from the build process.
+
Test Exports
Add, edit paths, arrange order, or remove files that will be part of the test build process.
+
+
Add Export dialog
+
Click the Add control to open the Add Export dialog (figure 2) to add a file to be exported to the destination path when the project is built.
+
+
Figure 2 - Add Export dialog
+
+
Table 2. Add Export — items
+ + + + + + + + + + + + + + + + + +
Name Function
Source path
Path and name of file to be exported.
Destination path
Path location where file is to be exported.
Export is a zip file Check this option if the export is a zip file and you want to extract it on the destination path.
+
Edit Export dialog
+
Click the Edit control to open the Edit Export dialog (figure 3) to edit the source and destination path of the selected file.
+
+
Figure 3 - Edit Export dialog
+
Table 3. Edit Export — items
+ + + + + + + + + + + + + + + + + +
Name Function
Source path
Path and name of file to be exported.
Destination path
Path location where file is to be exported.
Export is a zip file Check this option if the export is a zip file and you want to extract it on the destination path.
+
Other references
+
+
INF Editor
+
INF Editor - bld.inf
+
+ + +
Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
License: http://www.eclipse.org/legal/epl-v10.html
+ + + + \ No newline at end of file diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/projects/inf/INF_Editor_file.html --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/inf/INF_Editor_file.html Wed Oct 06 10:31:32 2010 -0500 @@ -0,0 +1,25 @@ + + +BLD.INF File + + + +
INF Editor - BLD.INF Tab
+ +
+ The bld.inf pane shows the source text of the bld.inf file. This file is automatically updated with changes made in the INF editor Overview and Exports panes or changes can be made manually in this pane. Validation is provided in this window. For example, an error mark is displayed next to the line where an error occurs, as shown in Figure 1. Hover your mouse pointer over the error mark or red error markers in upper right column to display helpful error information.
+
+
Figure 1 - INF Editor - bld.inf Pane
+
+
Related references
+
+
INF Editor
+
INF Editor - Exports
+
+ + +
Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
License: http://www.eclipse.org/legal/epl-v10.html
+ + + + \ No newline at end of file diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/projects/launch/applications.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/applications.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/applications.htm Wed Oct 06 10:31:32 2010 -0500 @@ -9,7 +9,7 @@
Applications Launch Configuration
-
Use the Symbian OS Device launch configuration to launch projects using the best launch configuration match. When chosen, Carbide examines the project and determines which specific launch configuration works best for the project, then launches it with the selected launch configuration. It is essentially identical to clicking the Debug icon () in the toolbar.
+
Use the Symbian Device launch configuration to launch projects using the best launch configuration match. When chosen, Carbide examines the project and determines which specific launch configuration works best for the project, then launches it with the selected launch configuration. It is essentially identical to clicking the Debug icon () in the toolbar.

Other references

Launch Configuration Overview
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/projects/launch/attach_process.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/attach_process.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/attach_process.htm Wed Oct 06 10:31:32 2010 -0500 @@ -9,19 +9,19 @@
Attach to Process Launch Configuration
-
Use the Symbian OS Device (Attach to Process) launch configuration to attach the debugger to an already running Symbian OS process or thread on a target device from within any project. This is useful for debugging servers running in RAM in a client-server relationship where the client relies on the presence of the server process to operate as one example.
-
Attaching to a process requires a both target device running the Symbian OS and the presence of CODA on the device. You can also use the Symbian OS Data view to attach to a process while debugging. However, you can not attach to a process running on an emulator.
-
If the New Launch Configuration Wizard created the Attach to Process launch configuration no changes are usually needed. The Attach to Process options match those of Symbian OS Device with one additional step, selection of the process to debug in the Attach to Process dialog.
+
Use the Symbian Device (Attach to Process) launch configuration to attach the debugger to an already running Symbian process or thread on a target device from within any project. This is useful for debugging servers running in RAM in a client-server relationship where the client relies on the presence of the server process to operate as one example.
+
Attaching to a process requires a both target device running the Symbian and the presence of CODA on the device. You can also use the Symbian Data view to attach to a process while debugging. However, you can not attach to a process running on an emulator.
+
If the New Launch Configuration Wizard created the Attach to Process launch configuration no changes are usually needed. The Attach to Process options match those of Symbian Device with one additional step, selection of the process to debug in the Attach to Process dialog.

To modify the launch configuration settings, select the Run > Debug As menu option to open the Debug dialog. Select the Attach to Process configuration and click a tab to set specific options. Click Apply to save any option modifications. Click Debug to launch a debugging session using the new settings.

Figure 1. Attach to Process launch configuration in the Debug dialog
-
The Symbian OS Device (Attach to Process) launch configuration panes include:
+
The Symbian Device (Attach to Process) launch configuration panes include:

The Main tab defines the project to be launched. Enter the name of the project in the Project field, and the executable name in the Executable field.

The Debugger tab defines debug configurations, such as entry point to begin debugging, target options, and instruction set.

The ROM Log tab allows you to specify where the ROM log file is stored and the Epoc32 directory.

The Executables tab allows you to specify which executables that you want to debug that are part of the project.
-
The Source tab (standard CDT page) defines the location of source files used to display source when debugging an application. By default, these settings are derived from the associated project's build path. You may override these settings here.
+
The Source tab (standard CDT page) defines the location of source files used to display source when debugging an application. By default, these settings are derived from the associated project's build path. You may override these settings here.

The Common tab (standard CDT page) defines general information about the launch configuration. You may choose to store the launch configuration in a specific file.

Other references
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/projects/launch/customizing_launch_configs.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/customizing_launch_configs.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/customizing_launch_configs.htm Wed Oct 06 10:31:32 2010 -0500 @@ -32,7 +32,7 @@

Figure 1 - Initial blank Debug launch configuration window
-
Select a type of launch configuration (for example, Symbian OS Emulation), then click the New launch configuration icon to create a new +
Select a type of launch configuration (for example, Symbian Emulation), then click the New launch configuration icon to create a new configuration of that type.
A new configuration appears in the Configuration list under the appropriate section using the project name and target to create the configuration name.
@@ -63,7 +63,7 @@
Source (Eclipse)

Common (Eclipse)

-
To debug something outside of the workspace, be sure to import the binary into the Executables view.
+
To debug something outside of the workspace, be sure to import the binary into the Executables view.

Click Debug
The IDE launches the executable. If the launch configuration is set to change perspective, it switches to the specified perspective.
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/projects/launch/emulation.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/emulation.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/emulation.htm Wed Oct 06 10:31:32 2010 -0500 @@ -9,11 +9,11 @@
Emulator Launch Configuration
-
Select the Symbian OS Emulator launch configuration to run or debug executables using an emulator.
-
If the New Launch Configuration Wizard was used to create a emulator launch configuration no changes are usually needed. To modify the launch configuration settings, select the Run > Debug As menu option to open the Debug dialog. Select the Symbian OS Emulation launch configuration and click a tab to set specific options. Click Apply to save any option modifications. Click Debug to launch a debugging session using the new settings.
+
Select the Symbian Emulator launch configuration to run or debug executables using an emulator.
+
If the New Launch Configuration Wizard was used to create a emulator launch configuration no changes are usually needed. To modify the launch configuration settings, select the Run > Debug As menu option to open the Debug dialog. Select the Symbian Emulation launch configuration and click a tab to set specific options. Click Apply to save any option modifications. Click Debug to launch a debugging session using the new settings.

Figure 1 - Emulator launch configuration in Debug dialog
-
The Debug window provides C/C++ emulator debug options when a Symbian OS Emulation launch configuration is created. The settings included in the Symbian OS Emulation launch configuration are a combination of Carbide, CDT, and Eclipse options. The tabs in the window include:
+
The Debug window provides C/C++ emulator debug options when a Symbian Emulation launch configuration is created. The settings included in the Symbian Emulation launch configuration are a combination of Carbide, CDT, and Eclipse options. The tabs in the window include:

The Main tab defines the project to be launched. Enter the name of the project containing the class to launch in the project field, and the executable name in the the Executable field and the emulator or host application in the Emulator or host application field.

The Arguments tab (standard CDT page) defines the arguments to be passed to the application and to the virtual machine (if any). You can also specify the working directory to be used by the launched application.
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_board.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_board.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_board.htm Wed Oct 06 10:31:32 2010 -0500 @@ -8,11 +8,11 @@ -
Symbian OS Reference Board Launch
+
Symbian Reference Board Launch

Use the Debug As dialog to select the New Launch Configuration Wizard to create a launch configuration for a development board or reference hardware using a JTAG connection. Currently there are two choices of debugger:

-
Symbian OS Phone Launch — uses the Eclipse Debugger for C/C++ as the debugger engine which includes snapshots, improved variables view, and other features not available in the Classic debugger.
-
Classic Symbian OS Reference Board Launch — uses the classic debugger engine.
+
Symbian Phone Launch — uses the Eclipse Debugger for C/C++ as the debugger engine which includes snapshots, improved variables view, and other features not available in the Classic debugger.
+
Classic Symbian Reference Board Launch — uses the classic debugger engine.

Figure 1. Debug As dialog
@@ -21,7 +21,7 @@

Select the Run > Debug menu item, or click the Debug () icon, or press F11

-
Select the Symbian OS Device item, then click OK
+
Select the Symbian Device item, then click OK

Select a Launch Type, then click Next

Complete each page in the New Launch Configuration Wizard for the chosen Launch Type.

Review the settings in the New Launch Configuration page
@@ -31,8 +31,8 @@
Other references

-
Symbian OS Emulator Launch
-
Symbian OS Phone Launch
+
Symbian Emulator Launch
+
Symbian Phone Launch

Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
License: http://www.eclipse.org/legal/epl-v10.html
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_configs_overview.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_configs_overview.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_configs_overview.htm Wed Oct 06 10:31:32 2010 -0500 @@ -16,11 +16,11 @@
Available Launch Configurations

Launch configurations come in several varieties, each designed for a specific purpose. You must choose one at the very start of the New Launch Configuration Wizard, so knowing the differences between them is important. Currently, the types to choose from include:

-
Symbian OS Device — used to run or debug applications or ROM code on a target device using CODA (Carbide On-device Debug Agent). CODA is an application that runs on reference boards and prototype phones and allows you to debug executables. The debugger will download files to the phone prior to launching.
-
Symbian OS Device (Attach to Process) — used to debug processes running on a target device for which a symbol file is available. This is available only for CODA and stop mode debugging. This launch configuration is not available for emulator debugging. Stop mode and CODA can both attach to a process from the Symbian OS Data view.
-
Symbian OS Device (Install SIS) — used to run or debug applications on a target device using CODA. CODA is an application that runs on released phones and allows you to debug your executables. The debugger will download a Symbian OS installation file to the phone and install it prior to launching.
-
Symbian OS Emulator — used to run or debug executables on an emulator.
-
Symbian OS Simulator — used to run or debug executables on a simulator.
+
Symbian Device — used to run or debug applications or ROM code on a target device using CODA (Carbide On-device Debug Agent). CODA is an application that runs on reference boards and prototype phones and allows you to debug executables. The debugger will download files to the phone prior to launching.
+
Symbian Device (Attach to Process) — used to debug processes running on a target device for which a symbol file is available. This is available only for CODA and stop mode debugging. This launch configuration is not available for emulator debugging. Stop mode and CODA can both attach to a process from the Symbian Data view.
+
Symbian Device (Install SIS) — used to run or debug applications on a target device using CODA. CODA is an application that runs on released phones and allows you to debug your executables. The debugger will download a Symbian installation file to the phone and install it prior to launching.
+
Symbian Emulator — used to run or debug executables on an emulator.
+
Symbian Simulator — used to run or debug executables on a simulator.

Other references

diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_emulator.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_emulator.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/launch_emulator.htm Wed Oct 06 10:31:32 2010 -0500 @@ -8,11 +8,11 @@ -
Symbian OS Emulator Launch
+
Symbian Emulator Launch

Use the Debug As dialog to select the New Launch Configuration Wizard that will create a launch configuration for the project. Currently there are two choices of debugger:

-
Symbian OS Phone Launch — uses the Eclipse Debugger for C/C++ as the debugger engine which includes snapshots, improved variables view, and other features not available in the Classic debugger.
-
Classic Symbian OS Reference Board Launch — uses the classic debugger engine.
+
Symbian Phone Launch — uses the Eclipse Debugger for C/C++ as the debugger engine which includes snapshots, improved variables view, and other features not available in the Classic debugger.
+
Classic Symbian Reference Board Launch — uses the classic debugger engine.

Figure 1. Debug As dialog
@@ -21,7 +21,7 @@

Select the Run > Debug menu item, or click the Debug () icon, or press F11

-
Select the Symbian OS Emulator item, then click OK
+
Select the Symbian Emulator item, then click OK

Complete each page in the New Launch Configuration Wizard , then click Next

Review the settings in the New Launch Configuration page

Click Debug to download and debug the project on the emulator
@@ -29,8 +29,8 @@

Name	Function
+ + Components	+ + Add components such as MMP and make files to be part of the normal build process. + + Create New MMP File - creates a new MMP file at the bottom of the Component list. + Add Existing MMP File - imports a MMP file at the bottom of the Component list. + Add Existing Makefile - adds a smake file to the bottom of the Component list. + Edit - Select a component and click Edit to apply the Tidy attribute or specify the Build as ARM option. + Open - Select a component and click Open to open the component in an editor window. + Up - Select a component and click Up to move the component up in the list. + Down - Select a component and click Down to move the component down in the list. + Remove - Select a component and click Remove to remove the component from the build process. +
+ + Test Components +	+ + Create, import, edit, open, move, or remove MMP and make files that are part of a test build process.

Name	Function
File path	Type the path and filename for the makefile to create or click Browse to set a path.
Tidy	Specify the tidy attribute if the release that an .mmp file defines is internal to your component and not required by other components or for your component to execute.
Build as ARM	Specifies the build_as_arm statement, which instructs an ARMV5 or later build to build the project for the ARM instruction set and not the THUMB instruction set.
Makefile format	Set the format of the makefile to be created.

Name	Function
File path	Type the path and filename for the MMP file to create or click Browse to set a path.
Tidy	Specify the tidy attribute if the release that an .mmp file defines is internal to your component and not required by other components or for your component to execute.
Manual	Checkmark to indicate a test that requires manual interaction to complete.
Support	Checkmark to not include the test in a batch file.

Name	Function
Exports	Add, edit, arrange order, or remove files that will be part of the build process. + + Add - Click to add a file to the list of files to be exported as part of the build process. + Edit - Select a file and click Edit to change the source and destination paths for the file. + Up - Select a file and click Up to move the file up in the list. + Down - Select a file and click Down to move the file down in the list. + Remove - Select a file and click Remove to remove the file from the build process. +
Test Exports	Add, edit paths, arrange order, or remove files that will be part of the test build process.

Name	Function
Source path	Path and name of file to be exported.
Destination path	Path location where file is to be exported.
Export is a zip file	Check this option if the export is a zip file and you want to extract it on the destination path.

Name	Function
Source path	Path and name of file to be exported.
Destination path	Path location where file is to be exported.
Export is a zip file	Check this option if the export is a zip file and you want to extract it on the destination path.

Other references

Symbian OS Device Launch

Symbian Device Launch

Use the Debug As dialog to select the New Launch Configuration Wizard that will create a launch configuration for the project. Currently there are two choices of debugger:

Device — uses the Eclipse Debugger for C/C++ as the debugger engine which includes snapshots, improved variables view, and other features not available in the Classic debugger.
Classic Symbian OS Reference Board Launch — uses the classic debugger engine.
Classic Symbian Reference Board Launch — uses the classic debugger engine.

Figure 1. Debug As dialog

Other references

Launch Types

The following launch configuration types are available:

Symbian OS Device
Symbian OS Device (Attach to Process)
Symbian OS Device (Install SIS)
Symbian OS Emulator
Symbian OS Simulator

Other references

Stop-mode Debugger page (Device, Device (Attach to Process))

Emulation Debugger page

The Symbian OS Emulator launch configurations the Debugger page to specify entry point breaks and which logs to output to the Console view.

The Symbian Emulator launch configurations the Debugger page to specify entry point breaks and which logs to output to the Console view.

Figure 1 - Debugger page showing emulation options

Table 1. Debugger page — emulation options

View program output

Enable to direct standard output messages to the Emulation Program Output Console in the Console view.

NOTE In the epoc.ini file the option LogToFile must also be set to 1.

Run-mode Debugger page

In a run-mode launch configuration like Symbian OS Device (Install SIS), you can specify an entry break point and how messages are handled as well as define the default instruction set.

In a run-mode launch configuration like Symbian Device (Install SIS), you can specify an entry break point and how messages are handled as well as define the default instruction set.

Figure 2 - Debugger page showing run-mode options

Table 2. Debugger page — run-mode options

View program output

Enable to direct standard output messages to the CODA Program Output Console in the Console view.

NOTE In the epoc.ini file the option LogToFile must also be set to 1.

Stop-mode Debugger page

In stop-mode launch configurations like Symbian OS Device, and Symbian OS Device (Attach to Process), use the Startup Options to attach to a target and debug or run from the specified start address. Then use Target Options to specify the target's processor type, and set which initialization and memory configuration files to use in the debug session.

In stop-mode launch configurations like Symbian Device, and Symbian Device (Attach to Process), use the Startup Options to attach to a target and debug or run from the specified start address. Then use Target Options to specify the target's processor type, and set which initialization and memory configuration files to use in the debug session.

Figure 3 - Debugger page showing stop-mode options

Table 3. Debugger page — stop-mode options

Other references

Executables page

The Executables page specifies the executables available to debug with your project based on the chosen rule. The Executables page gives you project level control over the executables associated with it. The page shows all the executables in the workspace or those imported into the Executables view from outside the workspace that can be debugged by this project. See the Executables view for information on controlling executables from the workspace.

Figure 1 - Executables page (Device example)

Table 1. Executable page —items

File Transfer page

The File Transfer page displays an auto-populated list of files for Symbian OS Device that the IDE transfers to the target device at the start of each launch. For RnD device images, the target location for files is normally c:\sys\bin or another protected area. For production device images Symbian OS Device (Install SIS) does not support the transfer of files to c:\sys\bin or other protected areas.

The File Transfer page displays an auto-populated list of files for Symbian Device that the IDE transfers to the target device at the start of each launch. For RnD device images, the target location for files is normally c:\sys\bin or another protected area. For production device images Symbian Device (Install SIS) does not support the transfer of files to c:\sys\bin or other protected areas.

Users can add, edit, or delete files in the list and sort by clicking on a column header. By default, any file added is automatically checked for downloading to the device. Users can uncheck a file to remove it from the download list without removing the file itself. CODA (Carbide On-device Debug Agent) users can use this panel to download any type of file, like bitmaps, HTML, sounds, and more, to the phone and applicable to CODA for transfering any files outside of the installation file.

Figure 1. File Transfer page

The target directories where files can be installed depends upon the type of device image you have on the device and which version of CODA you are using.

-
Symbian OS Device (Install SIS) - public folders only on production device images
-
Symbian OS Device - public and protected folders, like c:\sys\bin, on RnD device images
+
Symbian Device (Install SIS) - public folders only on production device images
+
Symbian Device - public and protected folders, like c:\sys\bin, on RnD device images

Installation page

The Installation page specifies the .sis file to install on the target device when using Symbian OS Device (Install SIS). This is required when using CODA with 9.x based SDK’s.

The Installation page specifies the .sis file to install on the target device when using Symbian Device (Install SIS). This is required when using CODA with 9.x based SDK’s.

Figure 1. Installation page

Table 1. Installation page —items

Stop-Mode Main page (CODA)

Emulation Main page

The Symbian OS Emulator launch configuration uses the Main page to define the process to be launched by the emulator.

The Symbian Emulator launch configuration uses the Main page to define the process to be launched by the emulator.

The behavior that occurs when launching a debug session varies based upon the SDK. Normally, starting a debug session launches the emulator (epoc.exe) and you must then navigate to your application and open it. However, starting a debug session for an .exe file will, in most cases, launch the .exe directly. This starts the emulator and then opens your application automatically. Note that some SDKs do not support this behavior. In those cases you must still open your application in the emulator manually.

Figure 1. Main page (Emulation shown)

Process to launch

Browse

Build Configuration

Run-mode Main page

The Symbian OS Device (Install SIS) launch configuration uses the Main page to defines the project and the process to launch on the target device.

The Symbian Device (Install SIS) launch configuration uses the Main page to defines the project and the process to launch on the target device.

Figure 2 - Main page (Device (Install SIS) shown)

Table 2. Run-mode Main page —items

Use connection

Build Configuration

Stop-mode Main page

The Symbian OS Device launch configurations uses the Main page to defines the project and the executable to launch on the target device.

The Symbian Device launch configurations uses the Main page to defines the project and the executable to launch on the target device.

Figure 3. Main page

Table 3. Stop-mode Main page — items

ROM Image page

Use the ROM Image page in a Symbian OS Device launch configuration to define startup options and ROM image download information.

Use the ROM Image page in a Symbian Device launch configuration to define startup options and ROM image download information.

Figure 1 - ROM Image page in launch configuration

Table 4. Launch configuration window—ROM Image tab items

Symbian Rom Log File

Symbian Epoc32 Directory

Enter or browse to the epoc32 directory for the Symbian OS kit that is being targeted for debugging. This is necessary for the debugger to resolve the full paths for each module in the log file since the log file does not contain the full paths.

Enter or browse to the epoc32 directory for the Symbian kit that is being targeted for debugging. This is necessary for the debugger to resolve the full paths for each module in the log file since the log file does not contain the full paths.

Log unresolved modules

Symbian Rom Image

Download Address (hex)

ROM Log page

Use the ROM Log page in a Symbian OS Device launch configuration to specify where the ROM log file is stored and the Epoc32 directory.

Use the ROM Log page in a Symbian Device launch configuration to specify where the ROM log file is stored and the Epoc32 directory.

Figure 1. ROM Log page

Table 1. ROM Log page—items

x86 Exceptions page

Use the x86 Exceptions page in the Symbian OS Emulator launch configuration to set the x86 exceptions the debugger should catch. If you want the debugger to catch all the exceptions, enable all of the options in this page. However, if you prefer to handle only certain exceptions, enable only those options that reflect the exceptions you want to handle.

Use the x86 Exceptions page in the Symbian Emulator launch configuration to set the x86 exceptions the debugger should catch. If you want the debugger to catch all the exceptions, enable all of the options in this page. However, if you prefer to handle only certain exceptions, enable only those options that reflect the exceptions you want to handle.

Figure 1 - x86 Exceptions page

Table 1. x86 Exceptions page —items

ROM Image
ROM Log
x86 Exceptions
Source (standard CDT page)
Source (standard CDT page)
Common (standard CDT page)

diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/projects/launch/run_mode.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/run_mode.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/launch/run_mode.htm Wed Oct 06 10:31:32 2010 -0500 @@ -8,12 +8,12 @@ -

Symbian OS Device (Install SIS) Launch Configuration (Run-mode)

Select the Symbian OS Device (Install SIS) launch configuration to debug or run applications on a target device using the CODA (Carbide On-Device Debug Agent). CODA is an application that runs on released phones and allows you to debug your executables. The debugger will download a Symbian OS installation file to the phone and install it prior to launching.

If the New Launch Configuration Wizard was used to create the CODA launch configuration no changes are usually needed. To modify the launch configuration settings, select the Run > Debug As menu option to open the Debug dialog. Select the Symbian OS Device (Install SIS) configuration and click a tab to set specific options. Click Apply to save any option modifications. Click Debug to launch a debugging session using the new settings.

Symbian Device (Install SIS) Launch Configuration (Run-mode)

Select the Symbian Device (Install SIS) launch configuration to debug or run applications on a target device using the CODA (Carbide On-Device Debug Agent). CODA is an application that runs on released phones and allows you to debug your executables. The debugger will download a Symbian installation file to the phone and install it prior to launching.

If the New Launch Configuration Wizard was used to create the CODA launch configuration no changes are usually needed. To modify the launch configuration settings, select the Run > Debug As menu option to open the Debug dialog. Select the Symbian Device (Install SIS) configuration and click a tab to set specific options. Click Apply to save any option modifications. Click Debug to launch a debugging session using the new settings.

Figure 1. Device launch configuration in the Debug dialog

The Symbian OS Device (Install SIS) launch configuration panes include:

The Symbian Device (Install SIS) launch configuration panes include:

The Main tab defines the project to be launched. Enter the name of the project in the Project field, and the executable name in the Executable field.
The Arguments tab (standard CDT page) lets you specify the program arguments that an application uses.

Symbian OS Device Launch Configuration (Stop-mode)

Select the Symbian OS Device launch configuration provides C/C++ stop-mode debug options. The settings included in these launch configuration are a combination of Carbide, CDT, and Eclipse options.

If the New Launch Configuration Wizard was used to create the Symbian OS Device launch configuration no changes are usually needed. To modify the launch configuration settings, select the Run > Debug As menu option to open the Debug dialog. Select the Symbian OS Device or Symbian OS Device (Attach to Process) configuration and click a tab to set specific options. Click Apply to save any option modifications. Click Debug to launch a debugging session using the new settings.

Symbian Device Launch Configuration (Stop-mode)

Select the Symbian Device launch configuration provides C/C++ stop-mode debug options. The settings included in these launch configuration are a combination of Carbide, CDT, and Eclipse options.

If the New Launch Configuration Wizard was used to create the Symbian Device launch configuration no changes are usually needed. To modify the launch configuration settings, select the Run > Debug As menu option to open the Debug dialog. Select the Symbian Device or Symbian Device (Attach to Process) configuration and click a tab to set specific options. Click Apply to save any option modifications. Click Debug to launch a debugging session using the new settings.

Figure 1. Symbian OS Device launch configuration in the Debug dialog

The Symbian OS Device launch configuration panes include:

Figure 1. Symbian Device launch configuration in the Debug dialog

The Symbian Device launch configuration panes include:

The Main tab defines the project to be launched. Enter the name of the project in the Project field, and the executable name in the Executable field.
The Debugger tab defines debug configurations, such as entry point to begin debugging and target options.

New Launch Configuration Wizard

The New Launch Configuration Wizard launches when no launch configuration exists for a build configuration in a project. Wherever possible the New Launch Configuration wizard gathers the information from the project and asks additional questions based on the type of launch configuration chosen. For example, a launch configuration using Symbian OS Device (Install SIS) requires different information than one targeted for Symbian OS Device.

The New Launch Configuration Wizard launches when no launch configuration exists for a build configuration in a project. Wherever possible the New Launch Configuration wizard gathers the information from the project and asks additional questions based on the type of launch configuration chosen. For example, a launch configuration using Symbian Device (Install SIS) requires different information than one targeted for Symbian Device.

Every project consists of one or more build configurations as listed under the Build project icon () of the toolbar or in the Add/Remove Carbide Build Configuration dialog. Every build configuration needs a launch configuration to enable debugging. Launch configurations can be shared between build configurations. The New Launch Configuration Wizard detects when a build configuration doesn't have an associated launch configuration and guides you through the setup process.

Figure 1. Build configurations for the chosen project appear under the Build icon

Other references

Connect to device

Shows the current remote connection setting used to communicate with the Symbian OS phone or device. Click Change... to open the Change Connection page of the New Launch Configuration Wizard to modify the connection settings.

Shows the current remote connection setting used to communicate with the Symbian phone or device. Click Change... to open the Change Connection page of the New Launch Configuration Wizard to modify the connection settings.

Debug process

By default, Carbide creates a debug launch configuration the first time you launch the debugger based on current project settings. If additional information is required, like a port ID, the New Launch Configuration Wizard appears asking for the additional information.

The tabs in the window vary depending upon the currently selected launch configuration.

Figure 1 - Debug or launch configuration window (Symbian OS Emulator view)

Figure 1 - Debug or launch configuration window (Symbian Emulator view)

Table 1. Debug Configuration window — common items

MMP Editor

+ The MMP Editor Overview tab allows you to view and modify your project definitions. Changes made in the MMP editor are automatically written to the project's .MMP file. You can view the .mmp file by selecting the project_name.mmp tab located along the bottom of the MMP editor.

+ The MMP Editor is shown when an MMP file is + opened from the Project Explorer or Symbian Project Navigator views. The MMP Editor is shown in Figure 1. MMP editor fields are validated for existing or correct entries. For example, if the UID 2 field is blank the label is highlighted in red. If an error exists in the mmp file, the line where the error occurs is marked and also displayed in the Problems view.

Figure 1 - MMP Editor Overview tab

Name	Function
+ + Target name	+ + Enter the name of the target file.
+ + Target type	+ + Select the type of target file from the dropdown list. The list of supported target types are provided by SBSv2 build system. The number and type of targets may change depending upon the chosen SDK.
+ + UID 2	+ UID 2 is a unique identifier number that identifies the type of interface that the project implements. The values are defined by Symbian: + + For GUI applications, it is always 0x100039CE + For static interface DLLs, the UID 2 is always 0x1000008d + For polymorphic DLLs, the UID2 is defined by the framework which is being implemented + +
+ + UID 3	+ + 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.
Common tasks	This group provides links to the User and System include path options located in the Options window.
+ + Project definition	+ + The Project definition group provides links to the Sources, Libraries, and Options windows. You can also select the Sources, Libraries, and Options tabs to open the related window.

Any changes made to the MMP file either in Carbide or using an external editor are detected. If the build is for emulation, these changes are detected and used automatically.

For other build types like GCCE you are presented with the Modified MMP Files Detected dialog (Figure 2) and asked which build action to take for each MMP file that has changed. Set the build option for each listed MMP file and click OK.

Figure 2 - Modified MMP Files Detected dialog

The options are identical to the workspace setting Default action to take when MMP files are modified option in the Build preference panel. Click the Configure Workspace Settings... to open the Build preference panel to set the default build options for the workspace. The options can also be modified at the project level in the Properties for <project> > Carbide Project Settings panel.

Related references

MMP Editor Libraries

MMP Editor > Libraries

+ The MMP editor libraries window lists the libraries used by the currently selected build configuration in the selected project. The MMP editor libraries window is shown in Figure 1. Click on a library group to expand the list of libraries and show the related control buttons. You can add, remove or edit the list of libraries for each group. You can also move libraries up or down in the list.

Figure 1 - MMP Editor Libraries window

Name	Function
+ + Libraries	+ + Specify import libraries to be included in all builds.
+ + Static libraries	+ + Specify additional static libraries to be used in all builds.
Debug libraries	Specify additional libraries to be used for debug builds only.
Win32 libraries	Specify additional libraries for Win32 builds only.
ASSP libraries	Specify libraries for ASSP builds. If you are not linking to the Symbian kernel you can ignore this section.

Related references

MMP Editor MMP File

MMP File Window

+ The MMP file tab in the MMP editor window shows the source text of the mmp file. Changes made directly in the mmp file are reflected in related tabs of the MMP editor and changes made in editor tabs are written to the mmp file. Errors are identified in red and markers are placed in mmp files at the locations errors exist.

Figure 1 - MMP Editor MMP File

Related references

MMP Editor Options

MMP Editor Options Window

+ The MMP editor options window allows you to edit compiler, linker, and runtime settings. The MMP editor options window is shown in Figure 1.

Figure 1 - MMP Editor Options window

Name	Function
+ + Runtime	+ + This group allows you to define various runtime options. + Capabilities - Click the Choose... button to select Capabilities. A capability is an access token that corresponds to permission to access sensitive system resources. Platform security permits access to sensitive APIs according to capabilities. Capabilities are used to specify what functionality an application is trusted to use; they are allocated to the application at build time and are policed at run time. Once the capabilities are assigned to the application, they cannot be changed. Thus an application has a set of unalterable capabilities that describe what access the application has to the APIs. + There are three suggested ways to establish which capabilities an application requires. + + The first method is initially to allocate capabilities based on the general operations that the application performs. For example, an instant messaging application would probably require NetworkServices to access the Internet and ReadUserData to read the user’s contacts. + The second method is to use the Symbian Developer Library, which lists the capabilities required by each API. Note that some APIs may be marked as “Dependent”, meaning that the need for the capability depends on the parameters being passed. For example, accessing a file in an application’s private data area requires no capabilities, but accessing a file in \sys\bin requires the AllFiles capability. + The third method is to run the application in the emulator, analyzing the debug file (in the system temporary directory) for capability violations. The output will state the API that caused the violation and what capability was expected. + + Minimum heap size - Set the heap size that you need. + Maximum heap size - Set the heap size that you need. + Stack size - Set the stack size that you need. + Process priority - Select the process priority from the dropdown list. + Secure ID - Enter the Secure ID. The SID is used to determine which private directory a process can access. It is also used to identify the caller applications. An application's SID is defined within its .mmp file, and is used to uniquely identify the application. SID values are requested from the Symbian Signed Web site (www.symbiansigned.com). The Software Installer (SWI) is responsible for ensuring that SIDs are locally unique, i.e., that no two applications have the same SID value on a particular target device. + Vendor ID - Enter the Vendor ID. This ID uniquely identifies the source of the application. If an application needs a VID, it must be certified. Noncertified applications must use a VID of 0 (KNullUid), which is the value applied by default. + Enable debugging (Symbian 9.4+) - Activate to enable on-device debugging for Symbian 9.4 and later. When activated, the DEBUGGABLE_UDEBONLY flag is added to the project .MMP file. + Paging Mode (Symbian 9.3+) - specify the paging mode to: not specified, paged, or unpaged.
+ + Compiler Settings	+ + User includes - Use the Add, Edit, and Remove buttons to add, edit, or remove the paths to the user header files used to compile source files. Use the Up and Down buttons to arrange the list of paths. + System includes - Use the Add, Edit, and Remove buttons to add, edit, or remove the paths to the system header files used to compile source files. Use the Up and Down buttons to arrange the list of paths. + Macros - Use the Add, Edit, and Remove buttons to add, edit, or remove a macro identifier. Use the Up and Down buttons to arrange the list of macro identifiers. + Compiler options - Use the Add, Edit, and Remove buttons to add, edit, or remove compiler options. In the Edit Compiler Options dialog, select the tool chain (for example: ARMCC, CW, GCC, GCCE, or MSVC) and enter your custom options. + Linker options - Use the Add, Edit, and Remove buttons to add, edit, or remove linker options. In the Edit Linker Options dialog, select the tool chain (for example: ARMCC, CW, GCC, GCCE, or MSVC) and enter your custom options. + Per-variant include dependencies - Check this option to include dependencies for a specific variant when building a target. For example build a release variant with optimized code, a debug variant with debugging info and a profiling variant with timing hooks. + Disable optimizations in debug builds - Check this option to disable optimizations when building a debug version of your application. Since optimization changes the code created by the compiler, it is best to optimize your code after you have fully tested and debugged it. If a program works in a debug build, but fails in a release build, it is likely that one of the compiler optimizations is exposing a defect in your source code. To isolate the problem, you should disable selected optimizations for each source code file, until you locate the file and the optimization that is causing the problem.
Linker	Linker definition file - Select a linker definition file or click Browse... to locate a definition file. + Export unfrozen - Check this option to tell the build process that exports are not yet frozen. + Don't export library - Check this option to not export a copy of the library. + No strict .def file - Check this option to specify no strict linker definition file. + Compress target executable - Check this option to compress the target executable. + Link as internal name - Specify an internal name. + Win32 base address - Specify the Win32 base address.
Kernel	ASSP ABI - Check this option to build the ASSP application binary interface. + ASSP exports - Check this option to enable ASSP exports.

Related references

MMP Editor Resource Block

+ The MMP editor resource block dialog allows you to add or remove resource files to your project. The Edit Resource Block dialog is shown in Figure 1. You can add, remove or edit resource files to be included with your project.

Figure 1 - MMP Editor Resource Block Dialog

Name	Function
+ + Project RSS files	+ + Select or browse to the resource file to be included in all builds.
+ + RSS file path	+ + Enter the path to the resource file.
Target file name	Enter the target file name.
Target file path	Select the target file path, such as the executable directory or /resource directory on the target device.
UID 2	Enter the unique identifier. UID2 may need to be a specific value for some kinds of DLLs, especially those used by plug-in frameworks.
UID 3	Enter the unique identifier. In the current implementation of platform security, UID3 is used as the Secure ID if SECUREID is not specified in the .mmp file. If it is specified, UID3 will be used to identify the application as its original purpose. + However, the SID is used to determine which private directory a process can access as well as to identify the caller applications, whereas the UID is used to uniquely identify an application. It is theoretically possible that these two identifiers could have different values, but to avoid confusion Symbian recommends that a SECUREID not be specified in the application's MMP file; UID3 should always be specified instead.
Generate header file	Check this option to generate a header file for the resource files.

Related references

MMP Editor Sources

MMP Editor Sources Window

+ The MMP editor sources window lists the C++ and resource files that you can select to be compiled. The MMP editor sources window is shown in Figure 1.

Figure 1 - MMP Editor Sources window

Name	Function
+ + C/C++ sources	+ + Select the C/C++ files to be compiled with your project.
Missing C/C++ sources	Shows a list of missing source files referenced by project MMP files.
+ + Resources	+ + Add, remove, or edit resources, bitmaps, and languages to compile with your project.

Related references

MMP Selection

+ The MMP Selection dialog displays a list of mmp project files that your source files should be added to for debugging specific components.

Figure 1 - MMP Selection Dialog

New Symbian OS MMP File

New Symbian MMP File

+ Use the Symbian MMP File wizard (figure 1) to create a new MMP project file for the currently selected project. Symbian projects are defined by an .mmp file which specifies the essential project elements of a Symbian project. All details of the project lifecycle are handled by the IDE. There is no editable makefile the user can edit to modify the build behavior of the project.

Creating a New Symbian MMP File

To open the New wizard to create a MMP File: +
- Select the File > New > Other... menu item (Figure 1)
+
+
+
Figure 1 - Select a wizard page in the New window
+
OR
+
+
- Select the File > New > Symbian MMP File... menu item (Figure 2)
+

+
+
Figure 2 - MMP File page in the New MMP File window
+

On the Select the wizard page, select Symbian > Symbian MMP File, then click Next (Figure 1)
On the MMP File page, enter the destination project folder and specify file name
Click Finish

The new MMP file is created in the destination folder and shown in the MMP editor.

Related references

Exporting Remote Connections

You can export remote connection settings for sharing and import settings created by others using the Import/Export commands.

Exporting Remote Connections
Importing Remote Connections

To export one or more remote connections:

Click the File > Export... menu option.
Select the Remote Connections > Remote Connections Data wizard in the Select page (Figure 1), then click Next.

Figure 1. Select page showing Remote Connections Data wizard

Choose file and remote connections to export (Figure 2) in the Export Remote Connections Data page.

Figure 2. Enable remote connections to export to chosen file

Click Finish to save the selected remote connections to the file.

Related references

Importing Remote Connections

You can export remote connection settings for sharing and import settings created by others using the Import/Export commands.

Exporting Remote Connections
Importing Remote Connections

To import one or more remote connections:

Click the File > Import... menu option.
Select the Remote Connections > Remote Connections Data wizard in the Select page (Figure 1), then click Next.

Figure 1. Select page showing Remote Connections Data wizard

Choose file and remote connections to export (Figure 2) in the Import Remote Connections Data page.

Figure 2. Enable remote connections to import

Click Finish to import the selected remote connections into Carbide.

Related references

Remote Connections view

Use the Remote Connections view to monitor, create, edit, or remove common connection settings for remote agents. Remote agents provide support for debugging, profiling, trace, and more. The connection types currently supported include:

Bluetooth — available for debug support
Serial — mainly for boards with a serial interface
USB — available for both debug and trace support

The columns in the Remote Connections view include:

Connection/Services - connection name defined by you and remote agent type
Type - connection type, i.e. Bluetooth, USB, TCP/IP, etc.
Status - current connection status, i.e. Available, Not Accessible, Ready, etc.
Description - provides information on the current connection test status.

Figure 1 - Remote Connections view

When the view is closed or another perspective opened, a small display appears in the trim area in the lower-right corner of the workspace showing the current active remote connection. Click the connection name to open the drop-down menu where you can open the Remote Connections view or switch between connections.

Figure 2. Available remote connection trim indicator

Remote Connections view toolbar icons

The following commands appear on the toolbar within the Remote Connections view:

Item	Icon	Explanation
Toggle periodic service testing		Toggles service testing on or off.
Refresh Connections	+ +	Click to update the connection list status.
New Connection	+ +	Click to open the New Connection wizard to add a connection.
Edit Connection	+ +	Click to edit the selected remote connection.
View menu		Select the connection types to monitor for remote connections.

Remote Connections view Status icons

The following status indicators appear in the Remote Connections view:

Item	Icon	Explanation
Connection	+ +	Indicates an inactive remote connection setting.
Not Active	+ +	Indicates an inactive connection type.
Ready / Available	+ +	Indicates an active remote connection is ready or that a particular connection type is available.
Not Accessible	+ +	Cannot access the connection type within the connection setup. This could be due to one of the following conditions: + + Nokia Ovi/PC Suite is not installed (Carbide uses their drivers to connect to remote devices) + User did not select Ovi/PC Suite mode on the device + CODA (Carbide On-device Debug Agent) is not installed on the device + + If all the above is setup the remote device should automatically appear when it is connected to the PC. The Description field contains useful debug information that can help solve the issue as well.

Remote Connections view context menu options

Based on the current selection, one or more of the following commands appear on the context menu when you right-click within the Remote Connections view. For example, if no connections are defined, only the New Connection command is available on the context menu.

Figure 3 - Remote Connections context menu

Item	Icon	Explanation
New Connection...	+ +	Select to open the New Connection wizard to add a connection.
Rename		Select to rename the currently selected connection.
Edit Settings...	+ +	Select to edit the selected remote connection settings.
Delete	+ +	Select to delete the selected connection from the connection list.
Help for...	+ +	Select to open the Help view for connection information.
Make Current		Make the selected connection the current connection.

Related references

Install Remote Agents pane

Install Remote Agents

Use the Install Remote Agents pane to select the latest remote agent version to download and install to the device.

Figure 2 - New Connection wizard Install remote agents page

Table 1. Install Remote Agents pane

Item	Explanation
Install remote agents	A list of the most current versions of remote agents sorted by SDK and version. Select the version most compatable with the device. For example, a device running S60 5.0 needs a version of the CODA software compiled for that SDK. + Additional information about the selected entry is displayed to the right to help you choose the correct version of CODA for the target device.
Save	Click Save to store a local copy of the currently selected CODA to disk. You can then manually install the file to your devices using the method of your choice.
Install	Click Install to download and install the CODA selected in the Install remote agents list. A progress bar is shown if the install operation requires more than a few seconds to complete. + NOTE Drivers installed by PC Suite or Ovi Suite are required in order for Install to download a remote agent onto the target device. + NOTE The SIS and SISX file types must be associated with an installer application like Nokia PC Suite or Ovi Suite in order to install them onto the device. Use the Save command above to perform a manual install to the device if you don't have an installer application.

Item

Explanation

Install remote agents

A list of the most current versions of remote agents sorted by SDK and version. Select the version most compatable with the device. For example, a device running S60 5.0 needs a version of the CODA software compiled for that SDK.

Additional information about the selected entry is displayed to the right to help you choose the correct version of CODA for the target device.

Save

Click Save to store a local copy of the currently selected CODA to disk. You can then manually install the file to your devices using the method of your choice.

Install

Click Install to download and install the CODA selected in the Install remote agents list. A progress bar is shown if the install operation requires more than a few seconds to complete.

NOTE Drivers installed by PC Suite or Ovi Suite are required in order for Install to download a remote agent onto the target device.

NOTE The SIS and SISX file types must be associated with an installer application like Nokia PC Suite or Ovi Suite in order to install them onto the device. Use the Save command above to perform a manual install to the device if you don't have an installer application.

Related references

Install Remote Agents pane

Use the Install Remote Agents pane to select the latest remote agent version to download and install to the device.

Figure 2 - New Connection wizard Serial Connection Settings page

Table 3. Serial Connection Setting page - Install Remote Agents tab

Item	Explanation
Install Remote Agents	A list of the most current versions of remote agents sorted by SDK and version. Select the version most compatable with the device. For example, a device running S60 3.1.0 needs a version of the CODA software compiled for that SDK. + Additional information about the selected entry is displayed to the right to help you choose the correct version of CODA for the target device.
Save	Click Save to store a local copy of the currently selected CODA to disk. You can then manually install the file to your devices using the method of your choice.
Install	Click Install to download and install the CODA selected in the Install latest CODA list. A progress bar is shown if the install operation requires more than a few seconds to complete. + NOTE The SIS and SISX file types must be associated with an installer application like Nokia PC Suite in order to install them onto the device. Use the Save command above to perform a manual install to the device if you don't have an installer application.

Item

Explanation

Install Remote Agents

A list of the most current versions of remote agents sorted by SDK and version. Select the version most compatable with the device. For example, a device running S60 3.1.0 needs a version of the CODA software compiled for that SDK.

Additional information about the selected entry is displayed to the right to help you choose the correct version of CODA for the target device.

Save

Click Save to store a local copy of the currently selected CODA to disk. You can then manually install the file to your devices using the method of your choice.

Install

Click Install to download and install the CODA selected in the Install latest CODA list. A progress bar is shown if the install operation requires more than a few seconds to complete.

NOTE The SIS and SISX file types must be associated with an installer application like Nokia PC Suite in order to install them onto the device. Use the Save command above to perform a manual install to the device if you don't have an installer application.

Related references

Adding, Editing, and Deleting Connections

Use the Remote Connections view to monitor, create, edit, or remove common remote connection settings.

Edit connection name and type
Set Connection Settings pane
Install Remote Agents pane

Edit connection name and type

Use the Edit connection name and type page to assign a name and connection type to the new connection setup.

Figure 1 - New Connection wizard Edit connection name and type page

Table 1. Edit connection name and type page - options

Item	Explanation
Connection Type	Select the type of connection this setup will use.
Connection Name	Enter a name for the connection.
Connection Settings	Select the connection port to use for this connection setting.

Set Connection Settings pane

Use the Set Connection Settings pane to compare the version of remote agent installed on the device with the latest version available for Carbide. In this pane you can:

Set the device OS used by the device and supported by the selected remote agent
Allow easy serial port selection when connecting to a device
Verify that you have the latest remote agent installed on a device

Figure 2 - New Connection wizard Serial Connection Settings page

Table 2. Serial Connection Setting page - Set Connection Settings tab

Item	Explanation
Device OS (used to determine installer version)	Select the OS used on the device.
Select a service to test	Click to select a listed service for testing.
Initiate Service Testing	Click Initiate Service Testing to query the remote agent software on the device for its version number. It then compares the version number found with the latest version available for Carbide. A progress bar will appear should the Check CODA version operation requires more than a few seconds. + NOTE The PC must have an internet connection to perform a remote agent version check. + Once the comparison is complete the Status text is updated with the result and further instructions as required. + + If a connection fails, the errors normally fall into these two categories: + + connection failure - this usually indicates the chosen COM port is not open. Try selecting a different COM port, specifically one with a name attached to it (COM4 - BthModem0) for the type of connection you are using (USB or Bluetooth). Repeat as necessary until you get a successful response. + CODA not responding - this indicates that the COM port is open but CODA is not responding. First, verify that CODA is up and running on the device. Second, CODA may be listening on a different COM port, so choose another named COM port and try again. + +

Item

Explanation

Device OS (used to determine installer version)

Select the OS used on the device.

Select a service to test

Click to select a listed service for testing.

Initiate Service Testing

Click Initiate Service Testing to query the remote agent software on the device for its version number. It then compares the version number found with the latest version available for Carbide. A progress bar will appear should the Check CODA version operation requires more than a few seconds.

NOTE The PC must have an internet connection to perform a remote agent version check.

Once the comparison is complete the Status text is updated with the result and further instructions as required.

If a connection fails, the errors normally fall into these two categories:

connection failure - this usually indicates the chosen COM port is not open. Try selecting a different COM port, specifically one with a name attached to it (COM4 - BthModem0) for the type of connection you are using (USB or Bluetooth). Repeat as necessary until you get a successful response.
CODA not responding - this indicates that the COM port is open but CODA is not responding. First, verify that CODA is up and running on the device. Second, CODA may be listening on a different COM port, so choose another named COM port and try again.

Install Remote Agents pane

Use the Install Remote Agents pane to select the latest remote agent version to download and install to the device.

Figure 2 - New Connection wizard Serial Connection Settings page

Table 3. Serial Connection Setting page - Install Remote Agents tab

Item	Explanation
Install Remote Agents	A list of the most current versions of remote agents sorted by SDK and version. Select the version most compatable with the device. For example, a device running S60 5.x needs a version of the CODA software compiled for that SDK. + Additional information about the selected entry is displayed to the right to help you choose the correct version of CODA for the target device.
Save	Click Save to store a local copy of the currently selected CODA to disk. You can then manually install the file to your devices using the method of your choice.
Install	Click Install to download and install the CODA selected in the Install latest CODA list. A progress bar is shown if the install operation requires more than a few seconds to complete. + NOTE The SIS and SISX file types must be associated with an installer application like Nokia PC Suite in order to install them onto the device. Use the Save command above to perform a manual install to the device if you don't have an installer application.

Item

Explanation

Install Remote Agents

A list of the most current versions of remote agents sorted by SDK and version. Select the version most compatable with the device. For example, a device running S60 5.x needs a version of the CODA software compiled for that SDK.

Additional information about the selected entry is displayed to the right to help you choose the correct version of CODA for the target device.

Save

Click Save to store a local copy of the currently selected CODA to disk. You can then manually install the file to your devices using the method of your choice.

Install

Click Install to download and install the CODA selected in the Install latest CODA list. A progress bar is shown if the install operation requires more than a few seconds to complete.

Related references

Editing connections

Use the Remote Connections view to monitor, create, edit, or remove common remote connection settings.

Edit connection name and type
Set Connection Settings pane
Install Remote Agents pane

Edit connection name and type

Use the Edit connection name and type page to assign a name and connection type to the new connection setup.

Figure 1 - New Connection wizard Edit connection name and type page

Table 1. Edit connection name and type page - options

Item	Explanation
Conection Type	Select the type of connection this setup will use.
Connetion name	Enter a name for the connection.
Supported Services	Shows a list of services supported by the connection type chosen.

Set Connection Settings pane

Use the Set Connection Settings pane to compare the version of remote agent installed on the device with the latest version available for Carbide. In this pane you can:

Set the device OS used by the device and supported by the selected remote agent
Allow easy serial port selection when connecting to a device
Verify that you have the latest remote agent installed on a device

Figure 2 - New Connection wizard Set Connection Settings tab

Table 2. Bluetooth Setting page - Set Connection Settings tab

Item	Explanation
Serial Port	A dropdown list of serial ports with known identifiers for selecting the communication port used by the PC to communicate with the device. A named COM port (COM4 - BthModem0) indicates an active port. Unnamed port numbers have usually not been opened and assigned by the PC.
Baud Rate	a dropdown list of baud rates common to serial connections.
Device OS	A dropdown list of device OSes that are supported by the remote agent software. Select the OS used by the device before running a check.
Select a service to test	Click to select a listed service for testing.
Test Service Status	Click Initiate service testing to query the remote agent software on the device for its version number. It then compares the version number found with the latest version available for Carbide. A progress bar will appear should the Check CODA version operation requires more than a few seconds. + NOTE The PC must have an internet connection to perform a remote agent version check. + Once the comparison is complete the Status text is updated with the result and further instructions as required. + + If a connection fails, the errors normally fall into these two categories: + + connection failure - this usually indicates the chosen COM port is not open. Try selecting a different COM port, specifically one with a name attached to it (COM4 - BthModem0) for the type of connection you are using (USB or Bluetooth). Repeat as necessary until you get a successful response. + CODA not responding - this indicates that the COM port is open but CODA is not responding. First, verify that CODA is up and running on the device. Second, CODA may be listening on a different COM port, so choose another named COM port and try again. + +

Install Remote Agents pane

Use the Install Remote Agents pane to select the latest remote agent version to download and install to the device.

Figure 2 - New Connection wizard Install remote agents tab

Table 3. Bluetooth Setting page - Install Remote Agents tab

Item	Explanation
Install remote agents	A list of the most current versions of remote agents sorted by SDK and version. Select the version most compatable with the device. For example, a device running S60 3.1.0 needs a version of the CODA software compiled for that SDK. + Additional information about the selected entry is displayed to the right to help you choose the correct version of CODA for the target device.
Save	Click Save to store a local copy of the currently selected CODA to disk. You can then manually install the file to your devices using the method of your choice.
Install	Click Install to download and install the CODA selected in the Install latest CODA list. A progress bar is shown if the install operation requires more than a few seconds to complete. + NOTE The SIS and SISX file types must be associated with an installer application like Nokia PC Suite in order to install them onto the device. Use the Save command above to perform a manual install to the device if you don't have an installer application.

Item

Explanation

Install remote agents

Additional information about the selected entry is displayed to the right to help you choose the correct version of CODA for the target device.

Save

Click Save to store a local copy of the currently selected CODA to disk. You can then manually install the file to your devices using the method of your choice.

Install

Click Install to download and install the CODA selected in the Install latest CODA list. A progress bar is shown if the install operation requires more than a few seconds to complete.

Related references

Setup Connection

Use the Edit Connection page to assign a connection type, name, and connection settings to the new connection setup.

Figure 1 - New Connection wizard Setup Connection tab

Table 1. Setup Connection page - options

Item	Explanation
Connection Type	Select the type of connection and its supported services from the drop down list of options. The types of connections include: + + Bluetooth - serial port connection through Bluetooth + Serial - serial port connection through a COM serial port + USB - serial port connection through USB that supports CODA 4.x + + And the supported services may include: + + CODA + Tracing + and others +
Connection Name	Enter a name for the connection.
Connection Settings	Shows a list of services supported by the connection type chosen. + + Bluetooth - serial port connection through Bluetooth + Serial - serial port connection through a COM serial port + USB - serial port connection through USB that supports CODA 4.x +

Item

Explanation

Connection Type

Select the type of connection and its supported services from the drop down list of options. The types of connections include:

Bluetooth - serial port connection through Bluetooth
Serial - serial port connection through a COM serial port
USB - serial port connection through USB that supports CODA 4.x

And the supported services may include:

CODA
Tracing
and others

Connection Name

Enter a name for the connection.

Connection Settings

Shows a list of services supported by the connection type chosen.

Bluetooth - serial port connection through Bluetooth
Serial - serial port connection through a COM serial port
USB - serial port connection through USB that supports CODA 4.x

Related references

Test Connection

Use the Set Connection Settings pane to compare the version of remote service installed on the device with the latest version available for Carbide. A remote service is any software on the device that can communicate with Carbide. This includes CODA (Carbide On-device Debug Agent), Trace, Performance Investigator, and other services. In this pane you can:

Set the device OS used by the device and supported by the remote service
Verify that Carbide can communicate with the remote service via the chosen connection setting
Verify that you have the latest version of the remote service installed on the device

Options presented may differ based on the type of connection setting chosen.

Figure 1 - Test Connection pane in the New Connection dialog

Table 1 Test Connection pane — items

Item	Explanation
Device OS (used to determine installer version)	A dropdown list of device OSes that are supported by CODA. Select the OS used by the device before running a check.
Select a service to test	Select the remote service type to query on the remote device.
Initiate service testing	Click Initiate service testing to query the remote software on the device for its version number. It then compares the version number found with the latest version available for Carbide. A progress bar will appear when the operation requires more than a few seconds. + NOTE The PC must have an internet connection to perform a remote service version check. + Once the comparison is complete the Status text is updated with the result and further instructions as required. + + If a connection fails, the errors normally fall into these two categories: + + connection failure - this usually indicates the chosen COM port is not open. Try selecting a different COM port, specifically one with a name attached to it (COM4 - BthModem0) for the type of connection you are using (USB or Bluetooth). Repeat as necessary until you get a successful response. + Service not responding - this indicates that the COM port is open but the remote service is not responding. First, verify that remote service is up and running on the device. Second, the remote service may be listening on a different COM port, so choose another named COM port and try again. +

Item

Explanation

Device OS (used to determine installer version)

A dropdown list of device OSes that are supported by CODA. Select the OS used by the device before running a check.

Select a service to test

Select the remote service type to query on the remote device.

Initiate service testing

Click Initiate service testing to query the remote software on the device for its version number. It then compares the version number found with the latest version available for Carbide. A progress bar will appear when the operation requires more than a few seconds.

NOTE The PC must have an internet connection to perform a remote service version check.

Once the comparison is complete the Status text is updated with the result and further instructions as required.

If a connection fails, the errors normally fall into these two categories:

connection failure - this usually indicates the chosen COM port is not open. Try selecting a different COM port, specifically one with a name attached to it (COM4 - BthModem0) for the type of connection you are using (USB or Bluetooth). Repeat as necessary until you get a successful response.
Service not responding - this indicates that the COM port is open but the remote service is not responding. First, verify that remote service is up and running on the device. Second, the remote service may be listening on a different COM port, so choose another named COM port and try again.

Related references

On-Device Connections

Use the New Connection wizard to verify and update Carbide software services on a device. Click the New Connection... icon () in the Remote Connections view toolbar to open. Current services available include CODA, Tracing, and others. The following tabs are present:

Setup Connection - define connection type, name and settings
Test Connection - verify connection operates as intended
Install Remote Agents - download and install remote agents

Figure 1 - New Connection dialog

Related references

Building an executable based on the project sources
Debugging the DLL using the Carbide debugger

NOTE There must be at least one recognized SDK installed before you can create a project. See the Symbian SDKs preference panel 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 add it to the Discovered Symbian OS SDK list.

Other references

Emulator Application Projects
Building the DLL object code based on the project sources
Debugging the DLL using the Carbide debugger

NOTE There must be at least one recognized SDK installed before you can create a project. See the Symbian SDKspreference panel 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 add it to the Discovered Symbian OS SDK list.

NOTE There must be at least one recognized SDK installed before you can create a project. See the Symbian SDKspreference panel 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 add it to the Discovered Symbian SDK list.

In this tutorial you'll create a simple DLL project using the New Symbian OS C++ Project wizard, attach it to the HelloWorld project created here, then debug it.

In this tutorial you'll create a simple DLL project using the New Symbian C++ Project wizard, attach it to the HelloWorld project created here, then debug it.

Creating a DLL project from a template

Click the File > New > Symbian OS C++ Project menu option.
-
The New Symbian OS C++ Project window appears to guide you through project creation process.
+
Click the File > New > Symbian C++ Project menu option.
+
The New Symbian C++ Project window appears to guide you through project creation process.
Select a template from the available options, then click Next.
-
Select the template for the type of project you want to create. For this example we chose the Generic Symbian OS > Baisc dynamically linked library (DLL) template. Note that as you select a template a brief description appears below the list explaining it attributes.
+
Select the template for the type of project you want to create. For this example we chose the Generic Symbian > Baisc dynamically linked library (DLL) template. Note that as you select a template a brief description appears below the list explaining it attributes.
Use the New Symbian OS C++ Project page to define the project name and build system.
+
Use the New Symbian C++ Project page to define the project name and build system.
1. Type a name into the Project name text box.
  @@ -43,14 +43,14 @@
2. Click Next.
In the Symbian OS SDKs page, select the SDK and build configurations for the project.
+
In the Symbian SDKs page, select the SDK and build configurations for the project.

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.
(Optional) Click Next to provide Basic Settings like author, copyright and other info for your project.
(Optional) Click Next to rename the Project Directories used to organize the project.
Click Finish.
-
Carbide uses the selected project template and your settings to create the DLL project in the Project Explorer view.
+
Carbide uses the selected project template and your settings to create the DLL project in the Project Explorer view.

diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/projects/tutorials/new_proj_dll_example_02.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/projects/tutorials/new_proj_dll_example_02.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/projects/tutorials/new_proj_dll_example_02.htm Wed Oct 06 10:31:32 2010 -0500 @@ -33,7 +33,7 @@

-
Once compiling is complete use the Project Explorer, Problems, Console, and Executables views to locate and resolve any problems generated during the build. See Step 2 here for more details.
+
Once compiling is complete use the Project Explorer, Problems, Console, and Executables views to locate and resolve any problems generated during the build. See Step 2 here for more details.

Defining a launch configuration for running or debugging the application
Controlling and debugging the running program using the Carbide debugger

NOTE There must be at least one recognized SDK installed before you can create a project. See the Symbian SDKspreference panel 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 add it to the Discovered Symbian OS SDK list.

NOTE There must be at least one recognized SDK installed before you can create a project. See the Symbian SDKspreference panel 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 add it to the Discovered Symbian SDK list.

Other references

DLL Projects
Remote Target Debugging (Run-mode)

Creating projects from a template

Click the File > New > Symbian OS C++ Project menu option.
-
The New Symbian OS C++ Project window appears to guide you through project creation process.
+
Click the File > New > Symbian C++ Project menu option.
+
The New Symbian C++ Project window appears to guide you through project creation process.
Select a template from the available options, then click Next.

Select the template for the type of project you want to create. For this example we chose the S60 > GUI Application template. Note that as you select a template a brief description appears below the list explaining it attributes.
Use the New Symbian OS C++ Project page to define the project name and build system.
+
Use the New Symbian C++ Project page to define the project name and build system.
1. Type a name into the Project name text box.
  @@ -43,13 +43,13 @@
2. Click Next.
In the Symbian OS SDKs page, select the SDK and build configurations for the project.
+
In the Symbian SDKs page, select the SDK and build configurations for the project.

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.
(Optional) Click Next to provide Basic Settings like author, copyright and other info for your project.
(Optional) Click Next to rename the Project Directories used to organize the project.
Click Finish.
-
Carbide uses the selected project template and your settings to create a new project in the Project Explorer view.
+
Carbide uses the selected project template and your settings to create a new project in the Project Explorer view.

Once you have a project in hand, the next thing to do is compile or build it into object code.

Building projects consists of a sbs or abld-based build system that wraps build functionality around existing SDK build tools that invoke makmake commands (e.g. makmake bldfiles and sbs build).

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 Creating New Projects from Templates. You can later change the Active Build Configuration. The Build Configurations also provides a command (Project > Build All Configurations) to build all the selected build configurations in a batch.

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.

The plug-ins provide extra functionality to set up suitable build configurations for Symbian C++ projects. The initial selection of a build configuration is done when you create a project, as described in Creating New Projects from Templates. You can later change the Active Build Configuration. The Build Configurations also provides a command (Project > Build All Configurations) to build all the selected build configurations in a batch.

Building Symbian C++ projects can involve the use of Symbian specific tools, such as the Symbian resource compiler. For detailed information on such tools, see the documentation for the SDK that you are using.

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 Properties for <project_name> window to control how the project is built. The following methods build a project:

-
Choosing any of the above actions causes Carbide to build the selected project. A Build Project dialog (below) and a progress bar appear during a lengthy build operation. All build output is shown in a Console view while build errors and warnings appear in the Problems view.
+
Choosing any of the above actions causes Carbide to build the selected project. A Build Project dialog (below) and a progress bar appear during a lengthy build operation. All build output is shown in a Console view while build errors and warnings appear in the Problems view.

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.

The project is also built if you make a change to it and then click Debug. It may be useful to automatically save modified resources before a manual build process by enabling the Save automatically before build option in the Window > Preferences > General > Workspace preference panel.

NOTE If you want to turn off building before launching, uncheck the Build (if required) before launching option in the Window > Preferences > Run/Debug > Launching preference panel.
-
When performing a build, output is displayed in the Console view. If you do not want to clear the console before each build you need to uncheck the option Always clear console before building in the Console panel. This option is enabled by default. You can access this panel by selecting Window > Preferences > C/C++ > Build > Console preference panel (below).
+
When performing a build, output is displayed in the Console view. If you do not want to clear the console before each build you need to uncheck the option Always clear console before building in the Console panel. This option is enabled by default. You can access this panel by selecting Window > Preferences > C/C++ > Build > Console preference panel (below).

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.

Executables view

Examine the Console view for more specific details on an error or warning message
-
Use the Console view to see where a specific problem occured during the build.
+
Use the Console view to see where a specific problem occured during the build.
Examine the Executables view for missing source files
-
Use the Executables 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.
+
Use the Executables 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.

Configure project for debugging

In this example we demonstrate how to debug applications on a remote device using the Symbian OS Device (Install SIS) remote debug agent. This enables you to test programs on the actual device it will operate on while observing its behavior using the Carbide debugger. The steps to do this include:

In this example we demonstrate how to debug applications on a remote device using the Symbian Device (Install SIS) remote debug agent. This enables you to test programs on the actual device it will operate on while observing its behavior using the Carbide debugger. The steps to do this include:

Connect target device to PC
Install CODA remote agent (v3.2.7) or later on the target device

Debug project on target device

Connect target device to PC
Install CODA remote agent (v3.2.7) or later on the target device

Carbide.c++ perspective

+ The Carbide C/C++ perspective is a set of tools and layout of views provided for Symbian development. This perspective is designed to work with Symbian C++ projects. The commonly used views include:

Project Explorer view - displays C/C++ projects located in the current workspace
Symbian Project Navigator view - shows all files that belong to the + current build configuration
Editor view - one or more source code editor windows
Outline view - displays an outline of a structured C/C++ file that is currently open in the editor view
Carbide.c++ Portal editor - provides Carbide news, release information, additional extensions, and support options
Problems view - displays build errors
Console view - shows the output of a process and allows you to provide keyboard input to a +process
Executables view - provides a dynamic list of executables and their related source files
Remote Connections view – use to monitor, create, edit, or remove common connection settings

Carbide.c++ perspective

Figure 1 - Carbide C/C++ perspective

NOTE Click the icon to show additional options that may not be visible in the perspective view.

For more information on perspectives see Workbench User Guide > Concepts > Perspectives, and for views see C/C++ Development User Guide > Reference + > C/C++ Views and Editors.

+ For more details on the Symbian Build Configurations, see + Active Configurations.

Related references

Carbide.c++ Portal view

The Carbide.c++ Portal view provides a single point of information on Carbide news, new releases, additional extensions, and support. The Carbide.c++ Portal view is shown by clicking Help > Carbide.c++ Portal.

Figure 1. Customize page in the Carbide.c++ Portal view

If the Show Installed option is checkmarked, the list only shows the extensions currently installed. To show more information on a specific extension click the (Show Overview) icon (Figure 2).

Figure 2. Extension information popup

Install section

The Install section provides options for installing additional Carbide extensions.

Table 1. Install options

Item	Explanation
Install...	Installs only the checked items in the extension list.
Refresh	Refreshes the plug-in list.
Select all	Marks all extensions for installation.
Deselect all	Unchecks all extensions to prevent installation.
Advanced install...	Launches the Install New Software wizard.

Migrate section

The Migrate section provides options for saving or restoring the custom settings.

Table 2. Migrate options

Item	Explanation
Export...	Click to export the current feature configuration.
Import...	Click to import a saved feature configuration settings file.

Settings section

The Settings section provides access to several common ways to customize the Carbide program.

Table 3. Settings options

Item	Explanation
Capabilities	Click to open the Capabilities preference panel where you can control which product components.
Code Style	Click to open the Code Style preference panel to customize the C/C++ editor appearance and behavior.
Key Bindings	Click to open the Keys preference panel to customize program key bindings.
Proxies	Click to open the Network Connections preference panel to change proxy settings.

Related references

Console View

Console view

The Console view displays the output of a process and allows you to provide keyboard input to a process. There are numerous consoles available, see the Open Console dropdown list for those available to you. Most are enabled from various project panels in Carbide.

Figure 1 - Console view showing build console information

To view RDebug::Printf output in the Console view when targeting devices, ensure that the following Debugger options are matched with settings in the epoc.ini file.

Set LogToDebugger 1 to use the View program output option
Set LogToFile 1 to enable the View emulator output option

Table 1 Console view—items

Item	Icon	Explanation
Scroll Lock		Toggles the scrolling of the console view contents.
Clear Console		Clears all content in the Console view.
Pin Console		Toggles the behavior of the console. When enabled the current console content is fixed all the time instead of scrolling out of sight. When disabled, the console changes according to the action. +
Display Selected Console		Changes the contents of the current console view to show the selected console output.
Open Console		Opens a new console to display the log for: + + Platform Security Diagnostics + New Windows System Messages Console + New Emulation Program Output Console + New CODA Program Output Console + New CODA Communications Log Console + New Symbian Rom Log Console + New Emulator Output Console + CVS + New Console View + + Remember that program output is console output from the running binary and communications log is the messages sent between CODA and the on-device debug agent. + NOTE You can pin any message log view so that it does not lose focus.

Executables view

The Executables view provides a dynamic list of executables and their related source files. The Executables view makes it easy to:

target all binaries for debugging because the symbolics are automatically loaded when a bld.inf is imported or a project is created from a template
debug a binary that is not part of a project in the workspace by importing it into the Executables view to load the symbolics
debug a process running on a device by attaching to the process and importing the binaries associated with the process into the Executables view to load the symbolics. For example, you to debug a library loaded by the process, you would need to import the libary and the process executable.
remove binaries when a project is closed or deleted from the workspace
remove binaries imported from outside the workspace by clicking the Remove the selected executables icon () or deleting the binary from the Executables project in the Project Explorer view
locate and manage which source and resource files are associated with each executable. Paths shown in black text have been resolved, those in gray text cannot be found.
identify and correct any path issues with missing source files (shown in gray text). Double-click the missing source file to open a Locate File editor view which enables you to find the missing file.
view routines and header files used by the source file. Click the tree control to expand or collapse a list of included header files and routine names for fast navigation.
find and set breakpoints, watchpoints, and eventpoints in source files. Double-click a source file to open it in an editor view and to review the status of its breakpoints.

In addition, an Executables project is created in the Project Explorer view. The binaries shown in the Executables project can be deleted which also removes them from the Executables view. For binaries outside the workspace you must import them into the Executables view so their symbolics can be used during the debug session. You can also drag and drop executables into the view.

NOTE To debug ROM DLLs with Symbian Device or in stop mode, always specify the ROM Log file in the project's launch configuration.

Figure 1 - Executables view

The Executables view consists of the Executable Name and Source File Name panes describled in the table below. Use the Columns button in the toolbar to show or hide specific columns in each pane. Columns can be sorted and rearranged in the order desired.

Table 1. Executables view information

Pane	Explanation
Executable Name	Displays a list of executables in the workspace as well as other files added by the user. Select an executable to update the Source File Name pane with related files. The executable information shown can include: + + Executable Name - (default) Name of the exectable file. + Executable Project - (default) The project associated with the executable. + Executable Location - (default) The current location of the executable. + Executable Size - The executable size shown in bytes. + Executable Date - The source file′s modification date. + Executable Type - The executable type (.exe, etc.) + + Click the Columns icon () to set which columns to show in this pane.
Source File Name	Displays a list of source files for the selected executable as extracted from the symbol table. The source file information shown can include: + + Source File Name - (default) Name of the source file used by the executable. If no binary files are in the project the message No source files found in <project_name> is shown. + Source File Location - (default) The current location of the source file. If the path is shown in gray text the source file was not located. To locate it, double-click to open a new editor, then click Locate File... to locate the missing file. The new path is compared to the old one and all files located in the same directory are automatically updated to use the new path. + Source File Original Location - (default) The original location of the source file which may be different than the current location. + Source File Size - The executable size shown in bytes. + Source File Date - The source file′s modification date. + Source File Type - The source type (.h, .inc, etc.) + + Expand a file′s tree control to view the functions and header files used by the file. Double-click to open the source file for editing or to set breakpoints. + Click the Columns icon () to set which columns to show in this pane.

Pane

Explanation

Executable Name

Displays a list of executables in the workspace as well as other files added by the user. Select an executable to update the Source File Name pane with related files. The executable information shown can include:

Executable Name - (default) Name of the exectable file.
Executable Project - (default) The project associated with the executable.
Executable Location - (default) The current location of the executable.
Executable Size - The executable size shown in bytes.
Executable Date - The source file′s modification date.
Executable Type - The executable type (.exe, etc.)

Click the Columns icon () to set which columns to show in this pane.

Source File Name

Displays a list of source files for the selected executable as extracted from the symbol table. The source file information shown can include:

Source File Name - (default) Name of the source file used by the executable. If no binary files are in the project the message No source files found in <project_name> is shown.
Source File Location - (default) The current location of the source file. If the path is shown in gray text the source file was not located. To locate it, double-click to open a new editor, then click Locate File... to locate the missing file. The new path is compared to the old one and all files located in the same directory are automatically updated to use the new path.
Source File Original Location - (default) The original location of the source file which may be different than the current location.
Source File Size - The executable size shown in bytes.
Source File Date - The source file′s modification date.
Source File Type - The source type (.h, .inc, etc.)

Expand a file′s tree control to view the functions and header files used by the file. Double-click to open the source file for editing or to set breakpoints.

Click the Columns icon () to set which columns to show in this pane.

Executables view toolbar icons

The table below lists the unique icons displayed in the Executables view toolbar.

Table 2. Executables view toolbar options

Command	Name	Description
	Refresh the list of executables	Click to refresh the executables list.
	Import an executable file	Click to select and import an executable not in the workspace into the executables list.
+ + +	Remove the selected executables	Click to remove one or more selected executables from the executables list. You will see a alert if the executable cannot be removed.
	Columns	Opens the Configure Columns dialog for configuring which columns appear in the Executable and Source File panes.

Other references

MIF Editor

MBM/MIF Editor

The MIF Editor allows you to create or edit the .mif files list of scalable icons (.svg) + included in a S60 v3.0 and later GUI projects as well as standard .bmp files. A .mif file is a MSX Interchange Format (MIF) file that should be built by the project.

NOTE This editor is only supported by the S60 3.0 and later SDKs.

NOTE For resources that are included after creating a project, you should ensure that the output location is set correctly by viewing the file properties. The output location is set to "{EPOCROOT}\epoc32\include" by default, so if an alternate location is required you can set this in the file properties.

Figure 1 - MIF File in the Symbian Project Navigator view

The MIF Editor appears when a MIF file is + opened for editing. To open the editor double-click on a .mif file in the Symbian Project Navigator view (figure 1), or select a scalable icon makefile (for example, Icons_scalable_dc.mk), right-click and select the Add MBM/MIF Entry command.

Figure 2 - MBM/MIF Editor

Table 1. MBM/MIF Editor —Items

Item	Explanation
Target File	Specifies the EPOCROOT relative path for the compiled images. Click the Default button to set the target file based on the SDK and project name.
Header File	Shows the generated header file. Select the Header option in the Header Generation group to create a default .mbg file. The path cannot be edited in this field.
Header Generation	Options include: + + No header - If selected, no .mbg header will be generated. + Header - If selected, a .mbg header will be generated. +
Up	Select an image in the list and click Up to move the selection one position up in the list.
Down	Select an image in the list and click Down to move the selection one position down in the list.
Pair Image and Mask	Select two adjacent unpaired BMP image entries in the list and click this button to combine the images together into image/mask pairs.
Split Image and Mask	Select a paired BMP image in the list and click this button to split the image into image and mask entries.
Swap Image and Mask	Select a paired BMP image in the list and click this button to swap the image and mask files and format information in paired image entries.
Add From Project	Click this button to open the Add Images from Project dialog to reference available images in the project.
Add From Filesystem	Click this button to open the Add Images From Filesystem dialog to locate and reference existing images in the filesystem or copy images to the project.
Remove	Select an image and click Remove to remove image entry from the list. This does not delete file from directory.
Color depth	Select the bit depth used to encode the image at build time.
Mask depth	Select the bit depth used to encode the mask at build time. Options include: + + n/a - Do not apply mask depth to images + 1 - A 1-bit mask treats pixels as "on/off" bits, where black is opaque and white is transparent. + 8 - An 8-bit mask is treated as alpha values, where black is transparent and white is opaque. +
Color format	Select Color to encode the image(s) as color or select Grayscale to encode the image(s) as grayscale.
Set from image	Click this button to auto-detect the image depth, mask depth, and color/grayscale setting from the image contents.
Preview	A preview of the image as it will appear at runtime.

Project Explorer View

Project Explorer view

The Project Explorer view (Figure 1) displays relevant C/C++ projects located in the current workspace using a tree structure. Use this view to manage all the projects located in the current workspace. The view is customizable and takes advantage of working sets.

The content of a project is dependent upon how it was created in the workspace.

Project Explorer view

Figure 1 - Project Explorer view showing projects in the current workspace

The directories that appear in the project include:

sis—the storage location for the final output files. The output file is linked from the top level of the project with a file of the same name. Both the binary and link files can be expanded to show the source files used to build the program.
Includes—a listing of all the include files used to build the project.
Executables - a listing of debuggable executables imported into the Executables view
User specified—many other directories like src, inc, data, and others are used to store specific types of project files. The names used for the directories are defined in the Project Directories page when the project is created.

+
NOTE Only the directories specified by the mmp file are created during import.
+

The files that appear in the project directories can be either:

files ()—these files are located in the workspace within the project directories. Double-click a file icon to open it for editing.
folder links—these are links pointing to folders that enable the project to support cvs related sources.

See C/C++ Development User Guide > Reference > C/C++ Views and Editors > Project Explorer view for more info.

Related references

Carbide C/C++ Perspective

Symbian Project Navigator view

The Symbian Project Navigator view shows all files that belong to the +current build configuration. This view lists the Symbian projects in your current workspace and their corresponding *.inf file (typically bld.inf). The *.inf file contains the related MMP project files, which are also listed in a tree structure. You can collapse or expand the list for each MMP to see which sources belong to each MMP.

To open this view select Window > Show View > Symbian Project Navigator, or select Window > Show View > Other ... and expand the Carbide.c++ folder then choose Symbian Project Navigator.

Figure 1 shows the Symbian Project Navigator view.

Figure 1 - Symbian Project Navigator view

Table 1. Symbian Project Navigator view — shortcut menu

Item	Icon	Explanation
Toggle SOURCEPATH		Toggles the display between showing the SOURCEPATH folders contained in the MMP file and showing the Bld.inf structure.
Toggle MMPs		Toggle the display to show all MMP files or the MMP files associated with the current build configuration.
Toggle MMP Order	+ + +	Toggle to show the MMPs list in alphabetical or build order. The default setting is build order.

Related references

Symbian View
Debug View

Select Qt modules to include in project
Set application UID

NOTE There must be at least one recognized SDK installed before you can create a project. See the Symbian SDKs panel 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 it to the Discovered Symbian OS SDK list.

Launch the New Qt Project Wizard

Select the File > New > New Qt Project menu item to open the New Qt Symbian OS C++ Project dialog.

Select the File > New > New Qt Project menu item to open the New Qt Symbian C++ Project dialog.

Figure 1. Qt project wizard - New Qt Symbian OS C++ Project page

Figure 1. Qt project wizard - New Qt Symbian C++ Project page

Other references

Qt Project Support
Select Qt modules to include in project
Set application UID

Select type of Qt project

Use the Select a type of project page in the New Qt Project Wizard to choose a Qt project template that will be used to generate the new project, then click Next. Note that the templates shown are filtered to

Figure 1. Qt project wizard - New Qt Symbian OS C++ Project page

Figure 1. Qt project wizard - New Qt Symbian C++ Project page

Other references

Qt Project Support
Select Qt modules to include in project
Set application UID

Enter project name and location

Use the New Qt Symbian OS C++ Project page in the Qt Project Wizard to define the projects name and where it should be saved, then click Next. In Qt projects, the name of the project folder must match the project name.

Use the New Qt Symbian C++ Project page in the Qt Project Wizard to define the projects name and where it should be saved, then click Next. In Qt projects, the name of the project folder must match the project name.

Figure 1. Qt project wizard - New Qt Symbian OS C++ Project page

Figure 1. Qt project wizard - New Qt Symbian C++ Project page

Set application UID

NOTE If everything is built correctly, the QtCore.lib should be in your SDK's <platform> <target> UDEB directory. If this library is missing, then the SDK will not show up as a supported SDK-target in the build configurations.

Select SDKs for build targets

Use the Build Targets page of the Qt Project Wizard to select one or more Qt SDKs to include in the project, then click Next.

Select Qt modules to include in project
Set application UID

Select Qt modules to include in project

Use the Qt Modules page to select one or more Qt modules to include with the project, then click Next.

Select Qt modules to include in project
Set application UID

Set application UID

Use the Basic Settings page of the Qt Project Wizard to define an Application UID to the executable. Click Random to generate a unique UID for program testing purposes. Click Finish when ready to create the project.

Choose build targets

Select .pro file to import

Use the Build Targets page in the File Import Wizard to select which SDKs and build configurations to associate with the project, then click Finish. The .pro file is imported and a new project created in the Project Explorer view.

Figure 1. File Import wizard - Build Targets page

Item

Qt Perspective

The Qt C/C++ perspective defines a set of common views that make developing Qt programs faster and easier. It is essentially the same as the Carbide C/C++ perspective except that the Symbian Project Navigator view is removed, and the following views added:

Qt C/C++ Action Editor
Qt C/C++ Object Inspector

Appears for projects that require a 32-bit unique ID to identify the vendor of the - executable. In versions of Symbian OS with platform security, a program can + executable. In versions of Symbian 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. diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/reference/MBMEditor.html --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/MBMEditor.html Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/MBMEditor.html Wed Oct 06 10:31:32 2010 -0500 @@ -7,7 +7,7 @@

The MBM Editor allows you to specify the bitmaps that - should be included in a Symbian OS multi-bitmap (MBM) file. Use of MBM files for general purpose graphics is restricted to using .bmp files and works for versions 2.x and later releases of the Symbian OS SDKs. For more + should be included in a Symbian multi-bitmap (MBM) file. Use of MBM files for general purpose graphics is restricted to using .bmp files and works for versions 2.x and later releases of the Symbian SDKs. For more information, see MBM File and Creating a MBM File.

The MBM Editor is shown when an MBM file is diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/reference/MenusToc.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/MenusToc.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/MenusToc.htm Wed Oct 06 10:31:32 2010 -0500 @@ -10,8 +10,8 @@

Open Command Window

Show in Explorer

Software Configuration Management

Symbian OS Class

Symbian OS C++ Project

Symbian Class

Symbian C++ Project

diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/reference/NewClassWizard.html --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/NewClassWizard.html Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/NewClassWizard.html Wed Oct 06 10:31:32 2010 -0500 @@ -14,10 +14,10 @@

The New C++ Class wizard allows a developer to add a new C++ class to existing or new header and source files. This wizard is supplied by the C/C++ - Development Toolkit (CDT), and is not customised for Symbian OS development. + Development Toolkit (CDT), and is not customised for Symbian development. However, as it is not currently described in the C/C++ Development Toolkit User Guide, you may find this extra information about it useful.

See Adding a Symbian OS Class for information on adding Symbian-based classes to a project.

See Adding a Symbian Class for information on adding Symbian-based classes to a project.

To invoke the wizard, click File > New > Class from the menu bar. The New C++ Class window appears.

@@ -92,7 +92,7 @@

Related tasks

diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/reference/ProjectPreferences.html --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/ProjectPreferences.html Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/ProjectPreferences.html Wed Oct 06 10:31:32 2010 -0500 @@ -9,7 +9,7 @@

TheProperties for <project_name> window allows you to change a project's build configurations, macros, and other project settings.

- To change the settings for a project, right-click the project from the Project Explorer or Symbian Project Navigator views, and choose Properties from the context menu. The Properties for <project_name> window then show all the project settings. If + To change the settings for a project, right-click the project from the Project Explorer or Symbian Project Navigator views, and choose Properties from the context menu. The Properties for <project_name> window then show all the project settings. If you alter the settings, then the settings are applied as defaults for all files in the project.

The Carbide.c++ panels include:

diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/reference/ProjectTypeandSDK.html --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/ProjectTypeandSDK.html Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/ProjectTypeandSDK.html Wed Oct 06 10:31:32 2010 -0500 @@ -6,7 +6,7 @@

Symbian OS SDKs

Symbian SDKs

You can set the SDKs and Build Configurations in this page. The available SDKs shown are determined by the settings in the SDK Preferences page.

@@ -33,7 +33,7 @@

Filter SDKs based on selected template

By default, the Symbian OS SDKs page only displays the templates related to the SDKs used by the project. Uncheck to view all available templates.

By default, the Symbian SDKs page only displays the templates related to the SDKs used by the project. Uncheck to view all available templates.

Use the ROM Builder pane to specify commands and a working directory for building a GUI ROM Image. The tool used to build GUI ROM images is called buildrom and can typically be found in your SDK path, for example in the \Symbian\9.4\S60_5rd\Epoc32\tools directory. The tool used to build text shell images is called ROM. The ROM image generated from the ROM build process specifies a base address for the image to run at. This might be an address in RAM or ROM. The image must be downloaded to the device at this address.

Building a ROM requires that the following are available, or have been successfully created:

Symbian OS components making up a set of releasables
Symbian components making up a set of releasables
a Bootstrap binary image
a text file specifying how the ROM image is to be built.

BldMake Arguments

Enter arguments into the various text boxes to customize the bldmake process. See the Symbian OS documentation for a complete list of arguments for these commands.

Enter arguments into the various text boxes to customize the bldmake process. See the Symbian documentation for a complete list of arguments for these commands.

Abld Arguments

Enter arguments into the various text boxes to customize the abld process. See the Symbian OS documentation for a complete list of arguments for these commands.

Enter arguments into the various text boxes to customize the abld process. See the Symbian documentation for a complete list of arguments for these commands.

NOTE To create a SYM file for UREL builds, enter -debug into the makefile text box in the Abld Arguments group.

The Paths and Symbols pane shows the paths and symbols used to the build the project index. This is a read-only list based on the setting of the Build configuration for the indexer option in the C/C++ General > Indexer panel. Carbide now caches the paths and symbols which persist between debug sessions. If any of the files like bld.inf, MMP, or any of their include files change, the list is automatically recalculated and CDT notified.

To change what appears in the list:

In the MMP Editor - add macros, user, or system include
In the MMP Editor - add macros, user, or system include
Using the Macro File defined in the Macro Settings panel

You can also specify a macro file using the Macro Settings page in the Properties for project dialog.

Partial Upgrade Files

The SIS Builder supports the generation of partial upgrade .SIS files. A dialog appears when a SIS file exceeds 250k in size that describes the partial upgrade feature with a link to the SIS Builder page. Partial upgrade files enable Carbide to generate and download to the device only those portions of the application that have changed, enabling faster debug cycles. It does this using the SIS partial upgrade (PU) flag to mark the SIS file as a replacement or addition to the original SIS file. Debugging of large applications using Symbian OS Device (Install SIS) is enhanced as the entire application no longer needs to be installed on the device each time a change is made.

When the Partial update option is checked for a SIS file, both a complete and partial SIS files are generated. This ensures that the full SIS file is kept in sync with the partial upgrade SIS file. The partial upgrade SIS files are placed in the same folder as the full SIS file when stored in a project directory, or in the root of the project directory when the SIS file exists outside of the project. You can see where a partial upgrade file is created by examining the Partial upgrade sis/sisx path in the Installation tab of the launch configuration. Links to the partial upgrade files are added to the project within the Project Explorer view.

The SIS Builder supports the generation of partial upgrade .SIS files. A dialog appears when a SIS file exceeds 250k in size that describes the partial upgrade feature with a link to the SIS Builder page. Partial upgrade files enable Carbide to generate and download to the device only those portions of the application that have changed, enabling faster debug cycles. It does this using the SIS partial upgrade (PU) flag to mark the SIS file as a replacement or addition to the original SIS file. Debugging of large applications using Symbian Device (Install SIS) is enhanced as the entire application no longer needs to be installed on the device each time a change is made.

NOTE Internally, the .PKG file format of a partial upgrade file is identical to a complete .PKG file with two exceptions, 1) the file list only includes the names of files changed, and 2) the PU flag is set.

Partial upgrade files are deleted and only full SIS/SISX files are generated when:

Set PKG File for Build Configuration

The Set PKG File for Build Configuration dialog appears when an Symbian OS Device (Install SIS) build configuration does not include a PKG file. Use it to assign a PKG file to the project's current build configuration that will be used to create a project's SIS installation file. If you define a launch configuration used for on-device debugging with the CODA debug agent, you will need to specify a PKG file for the project. A PKG file primarily provides a list of program and resource files to install on the device.

The Set PKG File for Build Configuration dialog appears when an Symbian Device (Install SIS) build configuration does not include a PKG file. Use it to assign a PKG file to the project's current build configuration that will be used to create a project's SIS installation file. If you define a launch configuration used for on-device debugging with the CODA debug agent, you will need to specify a PKG file for the project. A PKG file primarily provides a list of program and resource files to install on the device.

Figure 1 - Set PKG File for Build Configuration

Table 1 Items

Certificate

Enter or browse to certificate.

NOTE On Symbian OS 9.x builds, if the key/cert pair are not defined, makekeys will be called and temporary ones will be generated for you to "self-sign" the application. Self-signed applications should be in the +

NOTE On Symbian 9.x builds, if the key/cert pair are not defined, makekeys will be called and temporary ones will be generated for you to "self-sign" the application. Self-signed applications should be in the 0xE0000000-0xEFFFFFFF range.

Certificate – Enter or browse to certificate
Key — Enter or browse to key

NOTE All Symbian OS Device (Install SIS) build configuration require a PKG file. If none is found in the active project then you will be asked to choose one.

NOTE All Symbian Device (Install SIS) build configuration require a PKG file. If none is found in the active project then you will be asked to choose one.

Related reference

NOTE You can also rebuild a project's index by selecting a project, then right-click and select the Rebuild Index menu item.

Indexer preference panel

Figure 1 - C/C++ Indexer in Preferences

The project indexer is accessed by selecting a project in the Project Explorer or Symbian Project Navigator view and selecting Project > Properties > C/C++ General > Indexer (figure 2).

Indexer properties panel

Figure 2 - Indexer panel in Properties for project_name

ABLD Actions

Use the ABLD menu option to invoke an specific abld command on the selected project or file. ABLD is available under Symbian Build > ABLD or by right-clicking a project or file in the Project Explorer, Symbian Project Navigator, and Disassembly views and choosing ABLD > command. When executed any arguments specified in the Carbide Build Configurations pane for the command are passed to the selected tool.

Figure 1 - Available ABLD actions

The available commands include:

Build All Configurations

Select a project in the Project Explorer or Symbian Project Navigator view, then:

Click Project > Build All Configurations (CTRL+ALT+A) , or
Right-click the project name and select Symbian Build > Build All Configurations

Build Package (.pkg) File

Select a .PKG file in a project′s /sis folder in the Project Explorer view and right-click to display the context menu. Select Symbian Build > Build PKG File to build the package file and create the .sis installation file. This option is also available from an editor view when the file is open. The makesis tool uses the package file and packs all the required resources together into a SIS installation file. The Console view displays the processing output. The .sis and .sisx files will appear in the project's /sis folder.

Figure 1. Build PKG File context menu

Other references

Build Symbian Component

Select a .mmp or .mk file in the Project Explorer or Symbian Project Navigator view, then right-click and select Symbian Build > Build Symbian Component (CTRL+ALT+P) to build the selected component file or makefile. You can also right-click the file in an editor view to use the same option.

Figure 1. Build Symbian Component menu item

Clean Symbian Component

You can select a MMP or MK file in the Project Explorer or Symbian Project Navigator view and right-click to select Symbian Build > Clean Symbian Component (CTRL+ALT+X) to clean the selected MMP project file or makefile. You can also right-click the file in an editor view to use the same option. The cleaning process removes the object and make files, and output files. The files that are removed by this command include all the intermediate files created during compilation and all the executables and import libraries created by the linker.

Figure 1. Clean Symbian Component context menu

Other references

Compile

Select a .c, .cpp, or .cia source file in the Project Explorer or Symbian Project Navigator view, right-click the file and choose Symbian Build > Compile (CTRL+ALT+C) to compile it. This is also available from within a C/C++ editor view. You can use the shift or control key to select one or more of these file types across the same or different projects. The build progress is displayed in the Console view.

Compile source

Figure 1 - Right-click to compile a source file

Other references

Freeze Exports

Right-click a project in the Project Explorer or Symbian Project Navigator view, then choose Symbian Build > Freeze Exports. This command calls the appropriate abld command and a .def file is generated. This enables released versions of DLLs to freeze their exports, ensuring backward compatibility of a library.

Figure 1. Choosing Freeze Exports on a project

Other references

Freeze Symbian Component

Right-click a Symbian OS MMP file in the Project Explorer, or Symbian Project Navigator view, then choose Symbian Build > Freeze Symbian Component (CTRL+ALT+F). You can also right-click the file in an editor view to use the same option. This command only freezes the selected MMP file and not the entire project.

Right-click a Symbian MMP file in the Project Explorer, or Symbian Project Navigator view, then choose Symbian Build > Freeze Symbian Component (CTRL+ALT+F). You can also right-click the file in an editor view to use the same option. This command only freezes the selected MMP file and not the entire project.

Figure 1. Choosing Freeze Symbian Component on a file

Other references

Carbide Menus

Carbide has several menu options unique to developing Symbian OS applications and other shortcuts. Most project related commands are grouped under the Symbian Build option in context menus, while others appear under specific menus like Run or Project.

Carbide has several menu options unique to developing Symbian applications and other shortcuts. Most project related commands are grouped under the Symbian Build option in context menus, while others appear under specific menus like Run or Project.

File > New menu options
- Qt Project
- Symbian OS C++ Class
- Symbian OS C++ Project
- Symbian OS MMP File
- Symbian C++ Class
- Symbian C++ Project
- Symbian MMP File
Right-click object > Symbian Build menu options diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/reference/menus/preprocess_source.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/menus/preprocess_source.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/menus/preprocess_source.htm Wed Oct 06 10:31:32 2010 -0500 @@ -9,7 +9,7 @@
Preprocess
-
Right-click to select a .c, .cpp, or .cia source file in the Project Explorer or Symbian Project Navigator view, and choose Symbian Build > Preprocess to preprocess the file. You define the preprocess command in the Preprocess preference panel. This is also available from within a C/C++ editor view. You can use the shift or control key to select one or more of these file types across the same or different projects. The preprocess progress is displayed in the Console view.
+
Right-click to select a .c, .cpp, or .cia source file in the Project Explorer or Symbian Project Navigator view, and choose Symbian Build > Preprocess to preprocess the file. You define the preprocess command in the Preprocess preference panel. This is also available from within a C/C++ editor view. You can use the shift or control key to select one or more of these file types across the same or different projects. The preprocess progress is displayed in the Console view.

Figure 1. Choosing to Preprocess a file

Other references
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/reference/olderproject_updater.html --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/olderproject_updater.html Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/olderproject_updater.html Wed Oct 06 10:31:32 2010 -0500 @@ -10,7 +10,7 @@ The Carbide.c++ File Updater window appears when you open older Carbide.c++ projects that require updating. This most often occurs when new features are added to the project file format. The example in figure 1 shows the Carbide.c++ File Updater window with a v1.1 project that needs updating. In this case the updater updates the template projects from Carbide.c++ 1.1 to the latest template version. Projects that are already up-to-date are not affected by the updater process. New projects automatically use the most current project format.

If your projects have up-to-date bld.inf and MMP files, it is recommended that you delete the existing Carbide.c++ projects and simply re-import them from the bld.inf file. This ensures that the project file format is up-to-date.
-
You can also select projects in the Project Explorer or Symbian Project Navigator views and choose Project > Update Projects command to display the Carbide.c++ File Updater window.
+
You can also select projects in the Project Explorer or Symbian Project Navigator views and choose Project > Update Projects command to display the Carbide.c++ File Updater window.

Figure 1 - Carbide.c++ File Updater

UI Designer Projects
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/reference/perspective_debug.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/perspective_debug.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/perspective_debug.htm Wed Oct 06 10:31:32 2010 -0500 @@ -16,12 +16,12 @@
Debug view - displays information about a suspended process during a debug session
Variables view - allows manipulation of variables used in source code
Breakpoints view - allows manipulation of breakpoints and watchpoints
Symbian OS Data view - shows kernel data in the Symbian OS running on the device being debugged
Executables view - provides a dynamic list of executables and their related source files
Symbian Data view - shows kernel data in the Symbian running on the device being debugged
Executables view - provides a dynamic list of executables and their related source files
Editor view - one or more source code editor windows
Outline view - displays an outline of a structured C/C++ file that is currently open in the editor view
Console view - displays the output of a process, like the execution of your program, or other outputs
Console view - displays the output of a process, like the execution of your program, or other outputs
Tasks view - displays tasks that you manually add

And can include:

C/C++ Views and Editors

Related references

If not enabled, the Symbian command line build system handles all dependency tracking by generating the dependency information in the makefiles. Because it does this for all project files, regardless of the number of changes, it can result in a performance penalty. A single edit in a MMP file forces a complete regeneration of the makefile dependency information for all project files.

Manage dependency tracking (improves build speed)	Enable to have Carbide manage the dependency tracking for source and resource files. Carbide does this by separating out the generation of dependency information from the makefile and managing the entire process. All builds now can quickly compare whether new dependency information is required due to changes in a source file and only build those that need updating. - If not enabled, the Symbian OS command line build system handles all dependency tracking by generating the dependency information in the makefiles. Because it does this for all project files, regardless of the number of changes, it can result in a performance penalty. A single edit in a MMP file forces a complete regeneration of the makefile dependency information for all project files.
Show a dialog to modify build actions when modified MMPs are detected	Explanation
Keep Symbian OS project files (bld.inf/mmp) in sync with project changes	Keep Symbian project files (bld.inf/mmp) in sync with project changes	Select this option to update project files (bld.inf and mmp) when you add, remove, rename or move files and directories in your current workspace.
Time interval for auto-refreshing OS View	Determines how often to refresh data in the Symbian OS Data view which is available to the developer when using CODA or stop-mode debugging.	Determines how often to refresh data in the Symbian Data view which is available to the developer when using CODA or stop-mode debugging.

diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/reference/pref_carb_diagnostic_logs.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/pref_carb_diagnostic_logs.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/pref_carb_diagnostic_logs.htm Wed Oct 06 10:31:32 2010 -0500 @@ -22,7 +22,7 @@ Diagnostic Logs - A list of the log files that can be generated. Log files are stored in the project but are not visible in the Project Explorer or C/C++ Project views. + A list of the log files that can be generated. Log files are stored in the project but are not visible in the Project Explorer or C/C++ Project views. Clear Logs diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/reference/pref_carb_symbian_sdk.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/pref_carb_symbian_sdk.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/pref_carb_symbian_sdk.htm Wed Oct 06 10:31:32 2010 -0500 @@ -21,7 +21,7 @@

One thing to note is that Carbde.c++ no longer requires the devices.xml file to recognize and use SDKs. Insteads it now caches this information for later use. If the SDK contains an entry for the devices.xml Carbide will use it.

To access Symbian SDKs preferences preference panel, select Window > Preferences > Carbide.c++ > Symbian SDKs.

NOTE There must be at least one recognized SDK installed before you can create a project. If the SDK you have installed is not recognized, you may still be able to add it to the Discovered Symbian OS SDK list. See Carbide.c++ Requirements for a list of supported SDKs.

NOTE There must be at least one recognized SDK installed before you can create a project. If the SDK you have installed is not recognized, you may still be able to add it to the Discovered Symbian SDK list. See Carbide.c++ Requirements for a list of supported SDKs.

Symbian SDKs preference panel

Figure 1. Symbian SDKs preference panel

@@ -30,7 +30,7 @@ diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/reference/pref_cpp_code_style.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/pref_cpp_code_style.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/pref_cpp_code_style.htm Wed Oct 06 10:31:32 2010 -0500 @@ -9,7 +9,7 @@

Carbide supports the use of code styles in projects via the C/C++ Code Style preference panel. Use a code style profile to set specific smart typing features, like indentation, tabs or spaces, and many more options. There are several built-in code styles like GNU, Whitesmith, and others, while Carbide supplies these additional styles:

Symbian OS — settings are based on the Symbian OS C++ coding standards
Symbian — settings are based on the Symbian C++ coding standards
S60 — settings are based on the C++ Developer's Library > C++ Coding Conventions
Qt — settings for Qt projects

diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/reference/reference.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/reference.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/reference.htm Wed Oct 06 10:31:32 2010 -0500 @@ -11,8 +11,8 @@

Reference

This section provides reference information on the Carbide IDE including:

INF Editor
MMP Editor
INF Editor
MMP Editor
Preference Panels
- Build
- Views
  - Breakpoints
  - Carbide.c++ Portal
  - Console
  - Carbide.c++ Portal
  - Console
  - Debug
  - Disassembly
  - Executables
  - Executables
  - Expressions
  - Memory
  - Modules
  - Project Explorer
  - Project Explorer
  - Registers
  - Remote Connections
  - Remote Connections
  - Signals
  - Symbian OS Data
  - Symbian Data
  - Variables
- File Transfer Pane
- Executables Pane
- Installation Pane
- ROM Log (Symbian OS Device only)
- ROM Log (Symbian Device only)
- Source—specifies the location of source files used when debugging a C or C++ application
- Common—specifies the location to store your run configuration, how to access it and what perspective to open when running an application
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/reference/view_install_extensions.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_install_extensions.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_install_extensions.htm Wed Oct 06 10:31:32 2010 -0500 @@ -10,11 +10,11 @@
Install Extensions view

The Install Extensions view enables the user to locate and install Carbide plug-ins into a core Carbide.c++ installation. The Install Extensions view links to an online site that lists available plug-ins for installation. Plug-ins are grouped by type for
-
The Install Extensions view appears as part of the C/C++ Perspective. It can be added to a perspective by clicking Window > Show View > Install Extensions.
+
The Install Extensions view appears as part of the C/C++ Perspective. It can be added to a perspective by clicking Window > Show View > Install Extensions.

Figure 1. Install Extensions view

Click on the (Show Overview) icon to show an information popup with additional information on the selected plug-in.
-
+

Figure 2. Install Extensions Plug-in Information popup

Table 1 Install Extensions view—items

Symbian SDK's

Lists all the installed and recognized SDKs that are supported by the IDE. SDKs no longer supported by Carbide are not shown. You can double-click the SDK ID or Location entry to edit them directly.

Checked SDKs indicate build configurations available for creating projects. Unchecked SDKs are not displayed when creating new projects.

SDKs shown in RED indicate a problem, usually no EPOCROOT or unsupported Symbian OS version.

SDKs shown in RED indicate a problem, usually no EPOCROOT or unsupported Symbian version.

If you see a BAD_SDK_ROOT error message in the Location column, it indicates you have a build configuration with an SDK ID unknown to Carbide. To correct this you can either 1) remove the bad configurations from all the projects in your current workspace or 2) fix the location with the proper path and rescan your SDKs. If you delete an SDK with BAD_SDK_ROOT before removing it's configuration the SDK will continue to appear in the Symbian SDKs until the configurations are fixed or removed.

Click on a SDK name to see its EPOCROOT location and build configuration status in the SDK Information area.

@@ -63,7 +63,7 @@

Related references

Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/reference/view_module.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_module.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_module.htm Wed Oct 06 10:31:32 2010 -0500 @@ -9,7 +9,7 @@

Modules View

The Modules view displays a list of modules loaded while debugging your program. The listed modules can be selected to show related information. You can open the Modules view in the Carbide C/C++ perspective by selecting Window > Show view > Other..., then expand the Debug folder and select Modules. In the Debug perspective select Window > Show view > Modules.

The Modules view is only loaded during a debug session and closes when the debug session ends. Select the running man icon to list the Type, Symbols, and Symbols file for the executable. Select the stack of books icon to list the Type, Symbols, Symbols file, and Base address for the shared library.

Figure 1 shows the Modules view.

diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/reference/view_sym_os_data_chunks.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_sym_os_data_chunks.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_sym_os_data_chunks.htm Wed Oct 06 10:31:32 2010 -0500 @@ -9,8 +9,8 @@ -

Symbian OS Data view: Chunks

Symbian Data view: Chunks

Overview
Processes

The Chunks tab (Figure 4) provides a flat list of corresponding kernel objects. The list will display “sortable” attributes of that type of object in columns. The “sortable attribute” means you can sort the list by that attribute. For example, you may want to sort the list by the owning process name. Sort the list of any column by clicking on the column header.

NOTE Chunks data is not available during CODA debugging.

Figure 4. Chunks Pane of Symbian OS View

Figure 4. Chunks Pane of Symbian View

Attaching to a Process

If you double click on a thread item in the Thread tab, or right-click and choose Debug, the owning process of the thread will be attached. The thread with an attached process will appear in bold. You can also select a thread and click the bug icon in the Symbian OS Data toolbar. You can also view properties for the attached process by clicking the "Show properties of the selected item" icon () in the Symbian OS Data toolbar or right-click the thread and choose Properties.

If you double click on a thread item in the Thread tab, or right-click and choose Debug, the owning process of the thread will be attached. The thread with an attached process will appear in bold. You can also select a thread and click the bug icon in the Symbian Data toolbar. You can also view properties for the attached process by clicking the "Show properties of the selected item" icon () in the Symbian Data toolbar or right-click the thread and choose Properties.

NOTE If an executable is not part of a project in the workspace use the Executables view to import an executable to make it visible to the debugger. Once included in the Executables list, the symbolics for that executable can be loaded and breakpoints resolved and hit. Open a source file in an editor view or use the Breakpoints view to verify that the executable breakpoints have been resolved.

IMPORTANT In stop mode debugging when debugging multiple processes at the same time, selecting a process in the Debug pane and clicking Terminate disconnects the attached process on the board, leaving all other processes running. It does not terminate the debug session. However, if there is only one debug process when you click Terminate the CPU is suspended until the next debug session.

WARNING Detaching from a system process or any process not initiated by the program you are attempting to debug may cause the device to stop working, forcing a restart of the device.

Other references

Symbian OS Data view: Libraries

The Symbian OS Data view displays the processes and threads for the suspended debug session based on the selection in the Debug view. Read-only data is displayed for ARM build configurations.

Symbian Data view: Libraries

The Symbian Data view displays the processes and threads for the suspended debug session based on the selection in the Debug view. Read-only data is displayed for ARM build configurations.

Data to be viewed includes:

Overview

NOTE Information for the Chunks and Libraries tabs is not available when debugging with the CODA debug agent.

Libraries Tab

The Libraries pane (Figure 5) in the Symbian OS view provides information on libraries in the Symbian OS residing on the target.

The Libraries pane (Figure 5) in the Symbian view provides information on libraries in the Symbian residing on the target.

NOTE Library data is not available during CODA debugging.

Figure 5. Libraries Pane of Symbian OS view

Figure 5. Libraries Pane of Symbian view

Attaching to a Process

If you double click on a thread item in the Thread tab, or right-click and choose Debug, the owning process of the thread will be attached. The thread with an attached process will appear in bold. You can also select a thread and click the bug icon in the Symbian Data toolbar. You can also view properties for the attached process by clicking the "Show properties of the selected item" icon () in the Symbian Data toolbar or right-click the thread and choose Properties.

WARNING Detaching from a system process or any process not initiated by the program you are attempting to debug may cause the device to stop working, forcing a restart of the device.

Other references

Symbian OS Data view: Overview

The Symbian OS Data view displays the processes and threads for the suspended debug session based on the selection in the Debug view. Read-only data is displayed for ARM build configurations. To open the Symbian OS Data view select Window > Show View > Symbian OS Data when the Debug perspective is visible or select Window > Show View > Other..., then expand the Carbide.c++ folder and select Symbian OS Data when the Carbide C/C++ perspective is visible. Click Ok to display the Symbian OS Data window (Figure 1).

NOTE The Symbian OS Data view works with the debugger and will only display data during a live debug session. The Symbian OS Data view is not supported for emulator debugging, and will not show anything during emulator debug.

The Symbian OS Data view reveals kernel data in the Symbian OS running on the device being debugged. The kernel data displayed is always that of the device with the currently selected thread or process in Debug view. If you are debugging two devices at the same time, the content of the view will change when focus is switched from a thread on one device to a thread on another device. The kernel data includes more than just processes and threads.

For the stop mode debugger and the crash debugger, all the data listed above is supported. For the Application and Symbian OS Device debuggers, the chunks and libraries views are not supported. The Symbian OS Data view is not supported for the emulator debugger and will show nothing during an emulator debug session. During a stop mode debug session or a CODA debug session, you are able to select a process or a thread in the Symbian OS Data view and attach the debugger to it for source level debugging if the binary is listed in the Executables view. Binaries listed in the Executable view can be source level debugged. Binaries not listed in the Executables view can only be assembly code debugged in the Disassembly view.

Symbian Data view: Overview

The Symbian Data view displays the processes and threads for the suspended debug session based on the selection in the Debug view. Read-only data is displayed for ARM build configurations. To open the Symbian Data view select Window > Show View > Symbian Data when the Debug perspective is visible or select Window > Show View > Other..., then expand the Carbide.c++ folder and select Symbian Data when the Carbide C/C++ perspective is visible. Click Ok to display the Symbian Data window (Figure 1).

NOTE The Symbian Data view works with the debugger and will only display data during a live debug session. The Symbian Data view is not supported for emulator debugging, and will not show anything during emulator debug.

The Symbian Data view reveals kernel data in the Symbian running on the device being debugged. The kernel data displayed is always that of the device with the currently selected thread or process in Debug view. If you are debugging two devices at the same time, the content of the view will change when focus is switched from a thread on one device to a thread on another device. The kernel data includes more than just processes and threads.

For the stop mode debugger and the crash debugger, all the data listed above is supported. For the Application and Symbian Device debuggers, the chunks and libraries views are not supported. The Symbian Data view is not supported for the emulator debugger and will show nothing during an emulator debug session. During a stop mode debug session or a CODA debug session, you are able to select a process or a thread in the Symbian Data view and attach the debugger to it for source level debugging if the binary is listed in the Executables view. Binaries listed in the Executable view can be source level debugged. Binaries not listed in the Executables view can only be assembly code debugged in the Disassembly view.

NOTE Any executable must be included in the Executables view before it can be debugged.

When the Time interval for auto-refreshing OS View option is enabled (which is on by default except for crash debugger), the data in the Symbian OS Data view will be auto-refreshed. Note that "auto-refresh" has a different meaning in different debuggers. During a stop mode debug session, the view will refresh data whenever the debugged program on the device is stopped and shows data as stale (greyed out) when the program is running. During a CODA debug session, the View will refresh data at a time interval regardless of whether the debugged program is stopped or not. The time interval is specified by an option in the Carbide.c++ global preference panel, which is five seconds by default.

When the Time interval for auto-refreshing OS View option is enabled (which is on by default except for crash debugger), the data in the Symbian Data view will be auto-refreshed. Note that "auto-refresh" has a different meaning in different debuggers. During a stop mode debug session, the view will refresh data whenever the debugged program on the device is stopped and shows data as stale (greyed out) when the program is running. During a CODA debug session, the View will refresh data at a time interval regardless of whether the debugged program is stopped or not. The time interval is specified by an option in the Carbide.c++ global preference panel, which is five seconds by default.

When auto-refresh is turned off, the debugger will not automatically refresh data in the View and will show the data as stale (greyed out). However you can manually refresh the data by clicking on the "Refresh" button in the View. Usually you may want to turn off the auto-refresh if you think it is slowing down your debug operations such as stepping.

Symbian OS Data pages +

Symbian Data pages

The Symbian OS Data view consists of five tabs. Each tabbed pane is described below. In all panes, the Name Filter field is a standard Eclipse UI control that allows you to find an item by filtering out items by name using wildcards (*, ?) and camel case naming conventions. Camel case refers to using mixed case multiple names merged together in coding like SecInvInit and DosServer. In all panes, you can select an item and view its properties (attributes). In panes with columns you can click a column title to toggle between ascending and descending sorting.

The Symbian Data view consists of five tabs. Each tabbed pane is described below. In all panes, the Name Filter field is a standard Eclipse UI control that allows you to find an item by filtering out items by name using wildcards (*, ?) and camel case naming conventions. Camel case refers to using mixed case multiple names merged together in coding like SecInvInit and DosServer. In all panes, you can select an item and view its properties (attributes). In panes with columns you can click a column title to toggle between ascending and descending sorting.

Data to be viewed includes:

Overview

This tab (shown in Figure 1) provides a tree view of ownership of all processes, threads, and chunks in the OS. In contrast, the other tabs provide a flat list of corresponding kernel objects such as process, thread, chunk, library, etc.

Figure 1. Symbian OS Data view

Table 1 - Symbian OS Data view toolbar buttons

Figure 1. Symbian Data view

Table 1 - Symbian Data view toolbar buttons

The Processes tab (Figure 2) provides a flat list of corresponding kernel objects. Click a column title to sort the list by the title attribute in alternating ascending and descending order. For example, you may choose to sort the process list by Name, ID, or by Priority.

Figure 2. Processes Pane of Symbian OS View

Figure 2. Processes Pane of Symbian View

The process(es) being debugged will be shown in bold font. You can debug (attach debugger to) any process in the Processes tab by selecting it and clicking the "Debug" button or just by double clicking on it. In that case a new process item will show up in the Debug View if the process is not being debugged. Otherwise, you will get a message saying it's already under debug.

Threads

The Threads tab (Figure 3) provides a flat list of corresponding kernel objects. The list will display “sortable” attributes of that type of object in columns. The “sortable attribute” means you can sort the list by that attribute. For example, you may want to sort the list by the owning process name. Sort the list of any column by clicking on the column header. The thread(s) being debugged will be shown in bold font.

NOTE You can debug (attach debugger to) any thread in the Thread tab by double clicking on it or selecting it and clicking the Debug button. In that case, a new thread item will show up in Debug view if the thread is not being debugged.

Figure 3. Threads Pane of Symbian OS View

Figure 3. Threads Pane of Symbian View

Chunks

Chunks are an area of contiguous linear memory. It is the unit of memory allocation where a region of RAM is mapped into contiguous logical addresses. Chunks are allocated during boot for such things as the Kernel's data and stack.

NOTE Chunks data is not available during CODA debugging.

Figure 4. Chunks Pane of Symbian OS View

Figure 4. Chunks Pane of Symbian View

Libraries Tab

The Libraries pane (Figure 5) in the Symbian OS view provides information on libraries in the Symbian OS residing on the target.

The Libraries pane (Figure 5) in the Symbian view provides information on libraries in the Symbian residing on the target.

NOTE Library data is not available during CODA debugging.

Figure 5. Libraries Pane of Symbian OS View

Figure 5. Libraries Pane of Symbian View

Attaching to a Process

If you double click on a thread item in the Thread tab, or right-click and choose Debug, the owning process of the thread will be attached. The thread with an attached process will appear in bold. You can also select a thread and click the bug icon in the Symbian Data toolbar. You can also view properties for the attached process by clicking the "Show properties of the selected item" icon () in the Symbian Data toolbar or right-click the thread and choose Properties.

WARNING Detaching from a system process or any process not initiated by the program you are attempting to debug may cause the device to stop working, forcing a restart of the device.

Other references

Symbian OS Data view: Process

Symbian Data view: Process

Overview
Processes

Figure 2. Processes Pane of Symbian OS view

Figure 2. Processes Pane of Symbian view

Other references

Symbian OS Data view: Threads

Symbian Data view: Threads

Overview
Processes

Figure 3. Threads Pane of Symbian OS view

Figure 3. Threads Pane of Symbian view

Other references

Symbian OS Data view

Symbian Data view

NOTE Any executable must be included in the Executables view before it can be debugged.

Symbian OS Data pages +

Symbian Data pages

Data to be viewed includes:

Overview

Figure 1. Symbian OS Data view

Table 1 - Symbian OS Data view toolbar buttons

Figure 1. Symbian Data view

Table 1 - Symbian Data view toolbar buttons

Figure 2. Processes Pane of Symbian OS View

Figure 2. Processes Pane of Symbian View

Threads

Figure 3. Threads Pane of Symbian OS View

Figure 3. Threads Pane of Symbian View

Chunks

NOTE Chunks data is not available during CODA debugging.

Figure 4. Chunks Pane of Symbian OS View

Figure 4. Chunks Pane of Symbian View

Libraries Tab

The Libraries pane (Figure 5) in the Symbian OS view provides information on libraries in the Symbian OS residing on the target.

The Libraries pane (Figure 5) in the Symbian view provides information on libraries in the Symbian residing on the target.

NOTE Library data is not available during CODA debugging.

Figure 5. Libraries Pane of Symbian OS View

Figure 5. Libraries Pane of Symbian View

Attaching to a Process

If you double click on a thread item in the Thread tab, or right-click and choose Debug, the owning process of the thread will be attached. The thread with an attached process will appear in bold. You can also select a thread and click the bug icon in the Symbian Data toolbar. You can also view properties for the attached process by clicking the "Show properties of the selected item" icon () in the Symbian Data toolbar or right-click the thread and choose Properties.

WARNING Detaching from a system process or any process not initiated by the program you are attempting to debug may cause the device to stop working, forcing a restart of the device.

Other references

Here are all the views available within the Carbide IDE and debugging environments.

Carbide C/++ perspective views:

Debug perspective views:

Breakpoints view
Console view
Console view
Debug view
Disassembly view
Expressions view
Memory view
Modules view
Registers view
Symbian OS Data view
Symbian Data view
Signels view
Variables view

The tabs shown in the Debug dialog vary depending upon the type of launch configuration highlighted in the configurations list. See Launch Configuration Overview for more information on the various launch configuration types.

Click Debug to start a new debug session using the selected launch configuration.

Debug window

Figure 1 - Debug dialog (Symbian OS Emulation configuration shown)

Figure 1 - Debug dialog (Symbian Emulation configuration shown)

Table 1. Debug dialog — common items

Carbide.c++ Release Notes

Carbide.c++ Release Notes 3.0.0

The Carbide.c++ is a comprehensive development tool suite for Symbian OS that is based on the Eclipse framework. The C++ Development Toolkit (CDT), provides the foundation for project and build tools management, as well as the primary interface for the debugger to communicate with the IDE.

This is a collection of important information concerning last-minute - changes and other topics that deserve special attention. Please - read these notes carefully before using the Carbide tools so you - understand the current limitations and workarounds for known - issues.

What's new
K nown issues
Bug Fixes
Technical support

What's New in 3.0.0

The following features for Symbian development are provided within Carbide.c++:

Eclipse 3.6 — The Eclipse 3.6 project (Helios) provides the foundation, or integration platform, on which Carbide.c++ is built. New features include: Breakpoint detail pane for editing properties, Expression View Columns, Rectangular cut/paste, Synchronize View for applying patches. See What's New in 3.6 for more information.
CDT 7.0 — The final version of CDT is included as part of the Helios release. New Disassembly view with unlimited scrolling et al, new Templates view, compiler error/warning output highlighting, Regular Expression Error parser, Save build log to file, new key binding for "Run last make target". See the CDT 7.0 News and Noteworthy page for more information.
Eclipse Debugger for C/C++ — Carbide now uses the Eclipse Debugger for C/C++ (EDC) as the default device debugger. EDC provided an entirely new Debug view with all of the standard debug features like variables, breakpoints, watchpoints, disassembly, and all the other views required to run a debugging session. In addition, EDC provides the framework to add new debug features like snapshots.
TCF Debug Agents – Using Eclipse’s Target Configuration Framework, a new set of debug agents are used with the new EDC debugger to provide a completely new end-to-end debug environment.
Plug-n-Play Debug Discovery – a new method where Carbide can detect a debug target (phone device, PlatSim, etc) and automatically connect and configure the target so debugging can be initiated.
Snapshots – Save the state of a debug session for later review. Multiple snapshots are stored in a debug album to be shared with others or used for comparing different debug sessions.
New SDK Manager – Now automatically adds Symbian SDKs found on subst'ed drives and will link corresponding internally installed Qt SDKs. There are only two properties for SDKs now, the unique ID and location - no more messing around with OS or SDK versions!
Improved Raptor support – The Build Configuration Filter selects which platforms are visible when creating new projects or build configurations. This preference panel populates the build configurations when importing new projects. Users can now create their own custom variants for any Raptor build alias.
CODA replaces TRK as the debug agent on remote devices. CODA (Carbide On-device Debug Agent) uses the TCF interface to provide improved communication support between the Carbide debugger and the remote device. Can be downloaded and installed using the Install Remote Agents tab in the New Connection dialog. Requires both Carbide.c++ 3.x and EDC.
New Carbide.c++ portal view – The new Carbide.c++ Portal view provides easier access to -
- Welcome and getting started information including videos, blogs, and much more
- Installing and updating Symbian SDKs using the SDK Manager
- Customizing the Carbide workspace to better suit your needs
- Support information
-
Streamlined UI — Carbide's UI has been streamlined and minimized to a core set of functionality, mainly that of creating Symbian projects, building and debugging them. Context menus have been reworked to show a minimum set of options. If your favorite option is missing, you can use the Capability preference panel or the Customize Perspective dialog to add favorite commands back onto the context menus.

Performance improvements — We continue to address known performance issues as they reveal themselves. This release provides improvements for: + +
Carbide.c++ Release Notes 3.0.0
+
The Carbide.c++ is a comprehensive development tool suite for Symbian that is based on the Eclipse framework. The C++ Development Toolkit (CDT), provides the foundation for project and build tools management, as well as the primary interface for the debugger to communicate with the IDE.
+
This is a collection of important information concerning last-minute changes and other topics that deserve special attention. Please read these notes carefully before using the Carbide tools so you understand the current limitations and workarounds for known issues.
+
- What's new
- Known issues
- Bug Fixes
- Technical support
+
What's New in 3.0.0
+
The following features for Symbian development are provided within Carbide.c++:
+
- Eclipse 3.6 - The Eclipse 3.6 project (Helios) provides the foundation, or integration platform, on which Carbide.c++ is built. New features include: Breakpoint detail pane for editing properties, Expression View Columns, Rectangular cut/paste, Synchronize View for applying patches. See What's New in 3.6 for more information.
- CDT 7.0 - The final version of CDT is included as part of the Helios release. New Disassembly view with unlimited scrolling et al, new Templates view, compiler error/warning output highlighting, Regular Expression Error parser, Save build log to file, new key binding for "Run last make target". See the CDT 7.0 News and Noteworthy page for more information.
- Eclipse Debugger for C/C++ - Carbide now uses the Eclipse Debugger for C/C++ (EDC) as the default device debugger. EDC provided an entirely new Debug view with all of the standard debug features like variables, breakpoints, watchpoints, disassembly, and all the other views required to run a debugging session. In addition, EDC provides the framework to add new debug features like snapshots.
- TCF Debug Agents - Using Eclipse's Target Configuration Framework, a new set of debug agents are used with the new EDC debugger to provide a completely new end-to-end debug environment.
- Plug-n-Play Debug Discovery - a new method where Carbide can detect a debug target (phone device, PlatSim, etc) and automatically connect and configure the target so debugging can be initiated.
- Snapshots - Save the state of a debug session for later review. Multiple snapshots are stored in a debug album to be shared with others or used for comparing different debug sessions.
- New SDK Manager - Now automatically adds Symbian SDKs found on subst'ed drives and will link corresponding internally installed Qt SDKs. There are only two properties for SDKs now, the unique ID and location - no more messing around with OS or SDK versions!
- Improved Raptor support - The Build Configuration Filter selects which platforms are visible when creating new projects or build configurations. This preference panel populates the build configurations when importing new projects. Users can now create their own custom variants for any Raptor build alias.
- CODA replaces TRK as the debug agent on remote devices. CODA (Carbide On-device Debug Agent) uses the TCF interface to provide improved communication support between the Carbide debugger and the remote device. Can be downloaded and installed using the Install Remote Agents tab in the New Connection dialog. Requires both Carbide.c++ 3.x and EDC.
- + New Carbide.c++ portal view - The new Carbide.c++ Portal view provides easier access to +
  - Welcome and getting started information including videos, blogs, and much more
  - Installing and updating Symbian SDKs using the SDK Manager
  - Customizing the Carbide workspace to better suit your needs
  - Support information
  +
- Streamlined UI - Carbide's UI has been streamlined and minimized to a core set of functionality, mainly that of creating Symbian projects, building and debugging them. Context menus have been reworked to show a minimum set of options. If your favorite option is missing, you can use the Capability preference panel or the Customize Perspective dialog to add favorite commands back onto the context menus.
+
- + Performance improvements - We continue to address known performance issues as they reveal themselves. This release provides improvements for: +
  - Cached SDK and SBS builds - once your SDKs and build configurations are set up subsequent Carbide launches are faster.
  - Stack frames - in the Debug view stack frames were displayed once the symbol tables were completely read. For large symbol files this sometimes slowed down the display and hence the ability to continue debugging. Now the Debug view will show a subset of stack frames after a set time and update the remainder once it has finished scanning the symbol file.
  - Executables view - eliminated several use cases that forced the Executables list to update too frequently.
  - Large symbol tables supported - The Carbide symbol reader has been rewritten to provide faster access to symbols and to handle very large symbol files (larger than 10GB).
  +
- The Variables view and debug hover provides smart formatting for:
  - Cached SDK and SBS builds – once your SDKs and build configurations are set up subsequent Carbide launches are faster.
  - Stack frames — in the Debug view stack frames were displayed once the symbol tables were completely read. For large symbol files this sometimes slowed down the display and hence the ability to continue debugging. Now the Debug view will show a subset of stack frames after a set time and update the remainder once it has finished scanning the symbol file.
  - Executables view — eliminated several use cases that forced the Executables list to update too frequently.
  - Large symbol tables supported — The Carbide symbol reader has been rewritten to provide faster access to symbols and to handle very large symbol files (larger than 10GB).
  -
- The Variables view and debug hover provides smart formatting for: -
  - Symbian data types and descriptors
  - Qt data types: QString, QByteArray, QSet, QHash, QMap, QVector, QList, QLinkedList and Qvariant.
  - Symbian data types and descriptors
  - Qt data types: QString, QByteArray, QSet, QHash, QMap, QVector, QList, QLinkedList and Qvariant.
  -
+
2.7.0
+
- The Leavescan plug-in has been deprecated and is no longer included in Carbide.c++ releases. Use Codescanner to replace the Leavescan functionality.
-
2.7.0
-
- The Leavescan plug-in has been deprecated and is no longer included in Carbide.c++ releases. Use Codescanner to replace the Leavescan functionality.
-
2.6.0
-
- GCCE 4.0 supported — required for future SBSv2 releases.
- Symbian^3 supported — new templates and improvements required for the public Symbian^3 SDK.
- Known Issues in v2.6.0: -
  GCCE4 support requires using a SBSv2 build alias (-c parameter) of armv5_udeb_gcce or armv5_urel_gcce. As of this writing, these aliases were not available in the SDK or SBSv2, but will appear in some future version. Carbide versions prior to 2.6 do not support GCCE4.
  -
  Users should consult the SDK documentation for GCCE and SBSv2 issues and installation requirements.
  -
  TRK: If you install the TRK app onto your phone's flash memory (Mass Storage) a Remote Connection may not find the TRK-service even though TRK is already connected to your PC. Workaround: Uninstall TRK then reinstall it onto your PHONE memory (C-drive). The TRK service should now be "Available".
  +
  2.6.0
  +
  - GCCE 4.0 supported - required for future SBSv2 releases.
  - Symbian^3 supported - new templates and improvements required for the public Symbian^3 SDK.
  - + Known Issues in v2.6.0: +
    GCCE4 support requires using a SBSv2 build alias (-c parameter) of armv5_udeb_gcce or armv5_urel_gcce. As of this writing, these aliases were not available in the SDK or SBSv2, but will appear in some future version. Carbide versions prior to 2.6 do not support GCCE4.
    +
    Users should consult the SDK documentation for GCCE and SBSv2 issues and installation requirements.
    +
    TRK: If you install the TRK app onto your phone's flash memory (Mass Storage) a Remote Connection may not find the TRK-service even though TRK is already connected to your PC. Workaround: Uninstall TRK then reinstall it onto your PHONE memory (C-drive). The TRK service should now be "Available".
  -
  2.5.0
  -
  - Plug-and-Play (PnP) On-device Debugging supported — debugging a target device just got easier. Using a USB cable, connect the PC to the target device, then launch Carbide.c++. Carbide locates the connected device and creates a remote connection setup to communicate with it. Build the program and launch it on the device to start the debugging session.
  - PnP Phone Launch Wizard - If the project does not already have a launch configuration, the PnP Launch Wizard makes it easy to create one for phones. In addition the new Configure Launch Configuration dialog provides a quick summary of the remote connection for easy review and modification.
  - Carbide automatically detects TRK on target phones and devices - Carbide now detects the presence of either Application or System TRK on a connected device when TRK 3.2.6 or later are installed. Earlier TRK versions do not support this recognition feature.
  - TRK improvements - TRK continues to evolve and now includes these improvements: -
    - Both Application and System TRK v3.2.6 support PnP debugging. Update and install using the Help > On Device Connections > Install Remote Agents pane in the New Connection dialog.
    - VERSION3 command now supported
    -
  - RVCT 4.0 (ARMv5) builds and some limited debugging is supported
  - Symbian ^3 SDK now supported
  -
  Known issues
  -
  Workarounds for known issues:
  -
  - Qt issues — If Qt does not seem to be working as expected, be sure to run the \configuration\qt\register_plugins.bat file to properly register the Qt plugins. This is especially important if you installed Carbide using a zip file and not an installer.
  - USB issues — There are known problems with some USB configurations. We are working to resolve these asap.
  -
  Technical support
  -
  The following support services are available:
  -
  - Visit the Symbian Foundation for Carbide.c++ and Symbian development information
  -
  Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
  License: http://www.eclipse.org/legal/epl-v10.html
  - +
+
2.5.0
+
- Plug-and-Play (PnP) On-device Debugging supported - debugging a target device just got easier. Using a USB cable, connect the PC to the target device, then launch Carbide.c++. Carbide locates the connected device and creates a remote connection setup to communicate with it. Build the program and launch it on the device to start the debugging session.
- PnP Phone Launch Wizard - If the project does not already have a launch configuration, the PnP Launch Wizard makes it easy to create one for phones. In addition the new Configure Launch Configuration dialog provides a quick summary of the remote connection for easy review and modification.
- Carbide automatically detects TRK on target phones and devices - Carbide now detects the presence of either Application or System TRK on a connected device when TRK 3.2.6 or later are installed. Earlier TRK versions do not support this recognition feature.
- + TRK improvements - TRK continues to evolve and now includes these improvements: +
  - Both Application and System TRK v3.2.6 support PnP debugging. Update and install using the Help > On Device Connections > Install Remote Agents pane in the New Connection dialog.
  - VERSION3 command now supported
  +
- RVCT 4.0 (ARMv5) builds and some limited debugging is supported
- Symbian ^3 SDK now supported
+
Known issues
+
Workarounds for known issues:
+
- Qt issues - If Qt does not seem to be working as expected, be sure to run the \configuration\qt\register_plugins.bat file to properly register the Qt plugins. This is especially important if you installed Carbide using a zip file and not an installer.
- USB issues - There are known problems with some USB configurations. We are working to resolve these asap.
+
Technical support
+
The following support services are available:
+
- Visit the Symbian Foundation for Carbide.c++ and Symbian development information
+
+ Copyright � 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
+ License: http://www.eclipse.org/legal/epl-v10.html +
- \ No newline at end of file + diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/sos_references.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/sos_references.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/sos_references.htm Wed Oct 06 10:31:32 2010 -0500 @@ -1,27 +1,27 @@ - - - - - - Developer Resources - - - - -
Developer Resources
-
The following developer references provide information on the S60 SDKs, Symbian SDKs, APIs, and a host of other useful sources. Visit them to enhance your Symbian knowledge.
-
NOTE WINS (Visual Studio) - SDKs are not supported. If you want to do emulation debugging you need a WINSCW SDK.
-
- Symbian Developer (http://developer.symbian.org)
- Symbian Foundation (http://www.symbian.org/)
- Forum Nokia
- Carbide.c++ IDE and plug-ins discussion forum
- newlc - a Symbian OS C++ developer portal
- allaboutsymbian - a community site and portal for phones running the Symbian OS
-
Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
License: http://www.eclipse.org/legal/epl-v10.html
- - - + + + + + + Developer Resources + + + + +
Developer Resources
+
The following developer references provide information on the S60 SDKs, Symbian SDKs, APIs, and a host of other useful sources. Visit them to enhance your Symbian knowledge.
+
NOTE WINS (Visual Studio) + SDKs are not supported. If you want to do emulation debugging you need a WINSCW SDK.
+
- Symbian Developer (http://developer.symbian.org)
- Symbian Foundation (http://www.symbian.org/)
- Forum Nokia
- Carbide.c++ IDE and plug-ins discussion forum
- newlc - a Symbian C++ developer portal
- allaboutsymbian - a community site and portal for phones running the Symbian
+
Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
License: http://www.eclipse.org/legal/epl-v10.html
+ + + \ No newline at end of file diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/ClassesToc.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/ClassesToc.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/ClassesToc.htm Wed Oct 06 10:31:32 2010 -0500 @@ -8,7 +8,7 @@
Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
License: http://www.eclipse.org/legal/epl-v10.html
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/CreatingNewProjects.html --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/CreatingNewProjects.html Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/CreatingNewProjects.html Wed Oct 06 10:31:32 2010 -0500 @@ -5,17 +5,17 @@ -
Creating New Symbian OS C++ Projects
+
Creating New Symbian C++ Projects
New projects are created using the New Project Wizard. Carbide includes a number of templates that make creating projects for different SDKs and executables quick and easy.
-
NOTE You must have at least one recognized SDK installed before you can create a project. See the Symbian SDKs panel 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 add it to the Discovered Symbian OS SDK list.
+
NOTE You must have at least one recognized SDK installed before you can create a project. See the Symbian SDKs panel 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 add it to the Discovered Symbian SDK list.

NOTE 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.
-
Creating New Symbian OS C++ Projects
+
Creating New Symbian C++ Projects
1. Select File > New > Symbian OS C++ Project to invoke the New Project wizard.
2. Select File > New > Symbian C++ Project to invoke the New Project wizard.
3. The New Symbian OS C++ Project wizard appears. Select a template to create a project that matches the intended final application.
4. The New Symbian C++ Project wizard appears. Select a template to create a project that matches the intended final application.
5. Select the SDKs and Build Configurations.
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.
Click Finish to create the project.

This generates the necessary files for the project based on the template selected and show them in the Project Explorer view.

@@ -92,7 +92,7 @@

Building Projects

Creating a Launch Configuration
-
Debugging a Symbian OS Program
+
Debugging a Symbian Program

Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
License: http://www.eclipse.org/legal/epl-v10.html
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/ImportingProjects.html --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/ImportingProjects.html Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/ImportingProjects.html Wed Oct 06 10:31:32 2010 -0500 @@ -7,17 +7,17 @@

- The command-line Symbian OS toolchain requires that projects are + The command-line Symbian toolchain requires that projects are defined with these formats:

-
Symbian OS-specific project file formats (bld.inf)
-
Symbian OS executable files (.exe)
+
Symbian-specific project file formats (bld.inf)
+
Symbian executable files (.exe)

The primary purpose of bld.inf files is to group together closely associated projects, such as a GUI application and a engine DLL used by that application.

- The Symbian OS plug-ins allow you to import projects defined with these + The Symbian plug-ins allow you to import projects defined with these formats into the workbench. This is useful if:

@@ -33,8 +33,8 @@
-
Projects for Symbian OS 9.3+
-
Versions of Symbian OS 9.3+ devkits include extensive use of PRJ_EXTENSIONS and PRJ_TESTEXTENSIONS. These top-level entries are extension makefile templates whose names are later filled in with target names, sources, and options. The intent is to make source editing easier and dependency checking possible during a build.
+
Projects for Symbian 9.3+
+
Versions of Symbian 9.3+ devkits include extensive use of PRJ_EXTENSIONS and PRJ_TESTEXTENSIONS. These top-level entries are extension makefile templates whose names are later filled in with target names, sources, and options. The intent is to make source editing easier and dependency checking possible during a build.

Currently if you import a bld.inf file but are not importing all of the components and one of these extensions are found:

a warning appears at the top of the wizard page
@@ -49,7 +49,7 @@

Click File > Import... to get a list of available import wizards
-
Select Symbian OS > Symbian OS Bld.inf file and click Next to go to the Import Bld.inf page +
Select Symbian > Symbian Bld.inf file and click Next to go to the Import Bld.inf page

@@ -61,7 +61,7 @@
Type the location of the bld.inf file to import, or browse to the file using the Browse button.

-
NOTE Depending upon which SDKs are installed, you may see both SBSv1 and SBSv2 builders available. It is recommended that SBSv2 be the primary choice as SBSv1 has been deprecated for future Symbian OS development.
+
NOTE Depending upon which SDKs are installed, you may see both SBSv1 and SBSv2 builders available. It is recommended that SBSv2 be the primary choice as SBSv1 has been deprecated for future Symbian development.

SBSv2 works with recent versions of Symbian^3 and Symbian ^4 SDKs. 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.

NOTE Choose SBSv2 whenever possible as SBSv1 is being phased out.
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. @@ -93,13 +93,13 @@
.cproject - an xml file that provides additional project information

.settings folder - contains files that provide build configuration and preference settings

-
The root directory is a path to the root of your project. All necessary tool components, developer libraries, and information about the SDK are stored in subdirectories under this root. The whole path leading to the SDK root directory must be declared to the Windows system via the Environment Variables settings. The variable name is EPOCROOT and the variable value is the full path where a Symbian OS SDK is installed in the Windows system.
+
The root directory is a path to the root of your project. All necessary tool components, developer libraries, and information about the SDK are stored in subdirectories under this root. The whole path leading to the SDK root directory must be declared to the Windows system via the Environment Variables settings. The variable name is EPOCROOT and the variable value is the full path where a Symbian SDK is installed in the Windows system.

The root directory should contain all project related files that you want to work with in Carbide. The default directory is calculated by parsing the bld.inf file and mmp file(s).

Click Finish to import the project
The - wizard creates the project in the Project Explorer view, where it can be built and edited as normal. If the wizard is unable to read the project files, then the page + wizard creates the project in the Project Explorer view, where it can be built and edited as normal. If the wizard is unable to read the project files, then the page describes the error that occurred. If an error occurs, you must fix the project file, and then re-import the bld.inf.

diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/ModifyingResources.html --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/ModifyingResources.html Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/ModifyingResources.html Wed Oct 06 10:31:32 2010 -0500 @@ -12,9 +12,9 @@ This section describes the steps for adding and modifying bitmap resources (MBM) of an existing project.

- Note that the Symbian OS plug-ins do not provide a graphical editor for the - Symbian OS resource (.rss) file format. Files of this type though - can be created and edited as text files. Any .rss files in a project are built using the Symbian OS + Note that the Symbian plug-ins do not provide a graphical editor for the + Symbian resource (.rss) file format. Files of this type though + can be created and edited as text files. Any .rss files in a project are built using the Symbian resource compiler.

Creating an MBM File
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/Multi-BitmapFile.html --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/Multi-BitmapFile.html Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/Multi-BitmapFile.html Wed Oct 06 10:31:32 2010 -0500 @@ -5,8 +5,8 @@
Creating an MBM File

- Symbian OS programs typically store bitmaps for application icons or - other purposes in the Symbian OS multi-bitmap (MBM) file format, as described + Symbian programs typically store bitmaps for application icons or + other purposes in the Symbian multi-bitmap (MBM) file format, as described in MBM File. The Edit MBM/MIF Contents or Edit MBM Contents window allows you to create an MBM file.

@@ -14,7 +14,7 @@

- In the Symbian Project Navigator view double-click a .mmp file (Figure 1) to open the MMP Editor (Figure 2). + In the Symbian Project Navigator view double-click a .mmp file (Figure 1) to open the MMP Editor (Figure 2).

Figure 1- MMP File

diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/RunModeToc.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/RunModeToc.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/RunModeToc.htm Wed Oct 06 10:31:32 2010 -0500 @@ -6,7 +6,7 @@
Run Mode Projects

The topics include:

-
Run Mode Debug Example (Symbian OS Device (Install SIS))
+
Run Mode Debug Example (Symbian Device (Install SIS))

Troubleshooting

Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
License: http://www.eclipse.org/legal/epl-v10.html
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/StopModeToc.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/StopModeToc.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/StopModeToc.htm Wed Oct 06 10:31:32 2010 -0500 @@ -9,7 +9,7 @@
Stop Mode Debug Example

Building a ROM Image File

ARM Registers
-
Symbian OS Data View
+
Symbian Data View

Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
License: http://www.eclipse.org/legal/epl-v10.html
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/WorkingwithSDKs.html --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/WorkingwithSDKs.html Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/WorkingwithSDKs.html Wed Oct 06 10:31:32 2010 -0500 @@ -5,7 +5,7 @@
Working with SDKs

The SDK support provided in the workbench allows the developer to choose - which of the installed SDKs to work with. From the chosen SDK, Symbian OS + which of the installed SDKs to work with. From the chosen SDK, Symbian plug-ins pick-up information such as header files, import libraries, documentation and other SDK specific information.

You can add and manage SDKs in the Symbian SDKs panel. The Symbian SDKs preference panel lists all available SDKs and allows you to rescan system drives for newly installed and supported SDKs.
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/WritingCode.html --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/WritingCode.html Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/WritingCode.html Wed Oct 06 10:31:32 2010 -0500 @@ -8,7 +8,7 @@
- This section explains how to work with Symbian OS C++ projects with the + This section explains how to work with Symbian C++ projects with the help of the tools provided.

diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_setting.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_setting.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_setting.htm Wed Oct 06 10:31:32 2010 -0500 @@ -10,8 +10,8 @@
Setting Breakpoints

Use the Set Breakpoint command (Ctrl+Shift+B) to set a breakpoint. A regular breakpoint suspends program execution. The debugger executes the line of source code that contains the regular breakpoint.
-
TIP If you find that a breakpoint is not being hit, verify that the EXE or DLL is listed in the Executables view.
-
TIP If debugging a server launched by a client, you must attach to the server process using the Symbian OS Data view in order to hit the breakpoints in the server. Alternately, you can launch the server and client as two independent EXEs using the same COM port and debug them that way.
+
TIP If you find that a breakpoint is not being hit, verify that the EXE or DLL is listed in the Executables view.
+
TIP If debugging a server launched by a client, you must attach to the server process using the Symbian Data view in order to hit the breakpoints in the server. Alternately, you can launch the server and client as two independent EXEs using the same COM port and debug them that way.

Figure 1 shows some source code and the marker bar to the left of the source code. The selected line shows the breakpoint dot that appears in the marker bar when a breakpoint is set.

Figure 1 - Setting Breakpoints in an editor view
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/carbide_tools.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/carbide_tools.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/carbide_tools.htm Wed Oct 06 10:31:32 2010 -0500 @@ -9,7 +9,7 @@
Creating Carbide Tools
-
Carbide.c++ provides a host of functionality when it comes to designing, writing, compiling, and debugging Symbian OS based applications for mobile devices. In addition there are tools for evaluating your applications performance, memory, and energy usage to make them run faster and use less resources.
+
Carbide.c++ provides a host of functionality when it comes to designing, writing, compiling, and debugging Symbian based applications for mobile devices. In addition there are tools for evaluating your applications performance, memory, and energy usage to make them run faster and use less resources.

However, while there are a lot of tools included with Carbide.c++ you may have ideas of your own that you'd like to develop and use. Since Carbide is based upon Eclipse, a highly extensible open framework, you can develop tools and employ them inside the Carbide environment where they can operate alongside the standard tools. Best of all, you can do this all within the famliiar Carbide IDE.

To effectively write Carbide tool plug-ins you will need:

diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/custom/carb_custom_menus.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/custom/carb_custom_menus.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/custom/carb_custom_menus.htm Wed Oct 06 10:31:32 2010 -0500 @@ -10,7 +10,7 @@
Customizing Carbide: Toolbars and Menus
-
You can customize which commands appear on toolbars and menus using the Customize Perspective dialog. For purposes of customizing Carbide there are two perspectives of interest, the Carbide C/C++ perspective where project management and editing occurs and the Debug perspective used for debugging a project.
+
You can customize which commands appear on toolbars and menus using the Customize Perspective dialog. For purposes of customizing Carbide there are two perspectives of interest, the Carbide C/C++ perspective where project management and editing occurs and the Debug perspective used for debugging a project.

Click Window > Customize Perspectve... to open the Customize Perspective dialog which allows you to customize the current perspective. There are four tabs enabling you to customize the Carbide commands in multiple ways. The tabs include:

Toolbar Visibility
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/custom/carb_custom_styles.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/custom/carb_custom_styles.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/custom/carb_custom_styles.htm Wed Oct 06 10:31:32 2010 -0500 @@ -20,7 +20,7 @@
GNU (Eclipse) – Based on the code style used in for the GNU Coding Standards used by the GNU project.

K&R (Eclipse) – Based on the code style used in The C Programming Language by Kernighan and Ritchie.

S60 – Based on the code style used in Nokia S60 source code examples.
-
Symbian OS (default) – Based on the code style used in Symbian source code examples.
+
Symbian (default) – Based on the code style used in Symbian source code examples.

Qt – Based on the code style used in the Qt source code examples.

Whitesmiths (Eclipse) – Based on the code style used in documentation for the first commercial C compiler, the Whitesmith's Compiler.

diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug.htm Wed Oct 06 10:31:32 2010 -0500 @@ -23,7 +23,7 @@
All of the following requirements are required to build, communicate, and control programs on a phone or target device.

Install PC Suite or Ovi Suite on your PC to ensure the correct drivers are installed for connecting to the phone or target device.
-
Install the correct version of Perl on your PC to support Symbian OS builds
+
Install the correct version of Perl on your PC to support Symbian builds

Install a supported SDK and make sure its the default

Configure the environmental variables

(Optional) Setup a virtual drive to use Techview and Cust Kits
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_01.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_01.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_01.htm Wed Oct 06 10:31:32 2010 -0500 @@ -9,7 +9,7 @@
Installing Perl
-
Perl is a high-level, general-purpose, interpreted, dynamic programming language which many Symbian OS build utilities and commands require.
+
Perl is a high-level, general-purpose, interpreted, dynamic programming language which many Symbian build utilities and commands require.

Installing Perl

diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_02.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_02.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_02.htm Wed Oct 06 10:31:32 2010 -0500 @@ -13,7 +13,7 @@
Installing an SDK
-
To create projects to create and develop Symbian OS programs at least one Software Development Kit (SDK) must be installed and recognized by Carbide.
+
To create projects to create and develop Symbian programs at least one Software Development Kit (SDK) must be installed and recognized by Carbide.

Installing an SDK

Download the following SDKs from Nokia at: http://www.forum.nokia.com/.
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_06.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_06.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/run_mode_debug_06.htm Wed Oct 06 10:31:32 2010 -0500 @@ -23,10 +23,10 @@

Install the SISX File on the Target Device
-
CODA (Carbide On-device Debug Agent) is delivered to the target device as a SISX file. It can be used with all Symbian OS launch configurations that require an on-device agent.
+
CODA (Carbide On-device Debug Agent) is delivered to the target device as a SISX file. It can be used with all Symbian launch configurations that require an on-device agent.

-
Symbian OS Device (Install SIS)— supports application debugging only and available to developers creating applications for devices. Developers do not have access to system level routines, system ROM, and other user application code. User cannot modify the LR and SR registers, and must use a SIS file to debug an application.
-
Symbian OS Device— supports both application and limited ROM debugging; including application executables and limited ROM based components (no device drivers). Also available to original equipment manufacturers (OEMs) for device creation and customization.
+
Symbian Device (Install SIS)— supports application debugging only and available to developers creating applications for devices. Developers do not have access to system level routines, system ROM, and other user application code. User cannot modify the LR and SR registers, and must use a SIS file to debug an application.
+
Symbian Device— supports both application and limited ROM debugging; including application executables and limited ROM based components (no device drivers). Also available to original equipment manufacturers (OEMs) for device creation and customization.

Installing using Bluetooth

diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/soft_attach_debug.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/soft_attach_debug.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/soft_attach_debug.htm Wed Oct 06 10:31:32 2010 -0500 @@ -98,8 +98,8 @@
Related references

Debug perspective
-
Executables view
-
Symbian OS Data view
+
Executables view
+
Symbian Data view

Registers view

Breakpoint view

diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug.htm Wed Oct 06 10:31:32 2010 -0500 @@ -15,10 +15,10 @@
Create project or Import the project's bld.inf file into Carbide.c++

Build your Project using an ARM compiler

Build ROM if required
-
Create a Symbian OS Simulator launch configuration
+
Create a Symbian Simulator launch configuration

Launch the debugger

-
With stop mode debugging you can use the Carbide.c++ IDE to debug any target type within the Symbian OS.
+
With stop mode debugging you can use the Carbide.c++ IDE to debug any target type within the Symbian.

Related Tasks

Stop Mode On-Device Debugging Preconditions
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug02.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug02.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug02.htm Wed Oct 06 10:31:32 2010 -0500 @@ -13,10 +13,10 @@
Create project or Import the project's bld.inf file into Carbide.c++

Build your Project using an ARM compiler

Build ROM if required
-
Create a Symbian OS Simulator launch configuration
+
Create a Symbian Simulator launch configuration

Launch the debugger

-
With stop mode debugging you can use the Carbide.c++ IDE to debug any target type within the Symbian OS.
+
With stop mode debugging you can use the Carbide.c++ IDE to debug any target type within the Symbian.

Related references

Stop Mode On-Device Debugging Preconditions
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/view_symbian_kernel_set.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/view_symbian_kernel_set.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/view_symbian_kernel_set.htm Wed Oct 06 10:31:32 2010 -0500 @@ -8,8 +8,8 @@ -
Setting Symbian OS Data View Refresh Rate
-
A global preference option in the Preferences window of Carbide.c++ allows a user to change the time interval for auto-refreshing kernel data in the Symbian OS View.
+
Setting Symbian Data View Refresh Rate
+
A global preference option in the Preferences window of Carbide.c++ allows a user to change the time interval for auto-refreshing kernel data in the Symbian View.

To set the refresh rate

@@ -18,17 +18,17 @@
Enter a time interval from 3 to 600 seconds for kernel data to be refreshed. 20 seconds is the default.

-
Figure 1. Symbian OS Kernel Data Refresh Rate
+
Figure 1. Symbian Kernel Data Refresh Rate

Related concepts

-
Symbian OS Kernel View
+
Symbian Kernel View

Working with the Debugger

Related references

Debug View
-
Symbian OS View Window
+
Symbian View Window

Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
License: http://www.eclipse.org/legal/epl-v10.html
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/index.html --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/index.html Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/index.html Wed Oct 06 10:31:32 2010 -0500 @@ -14,7 +14,7 @@
This section explains the different tasks that can be performed using the - Symbian OS plug-ins for Eclipse. It provides step-by-step instructions for + Symbian plug-ins for Eclipse. It provides step-by-step instructions for performing each task.

@@ -24,7 +24,7 @@

Next, program creation is described. This can be done either by creating a - new project through a wizard, or by importing an existing Symbian OS project + new project through a wizard, or by importing an existing Symbian project file.

@@ -36,7 +36,7 @@
You can then add and build code in the project. This is mostly done using the standard CDT tools and techniques. The plug-ins through also offer special - support for the Symbian OS specific file formats and multi-bitmap files (MBM), as described in Modifying + support for the Symbian specific file formats and multi-bitmap files (MBM), as described in Modifying Resources.

Working with SDKs
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/installing_extensions.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/installing_extensions.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/installing_extensions.htm Wed Oct 06 10:31:32 2010 -0500 @@ -6,7 +6,7 @@
Installing Extensions
-
Use the Install Extensions page in the Carbide Portal view to find, select, download, and install Carbide extensions to your work environment.
+
Use the Install Extensions page in the Carbide Portal view to find, select, download, and install Carbide extensions to your work environment.

Installing one or more extensions

@@ -23,7 +23,7 @@

Other references

-
Carbide Portal
+
Carbide Portal

Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
License: http://www.eclipse.org/legal/epl-v10.html
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/attach_to_process.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/attach_to_process.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/attach_to_process.htm Wed Oct 06 10:31:32 2010 -0500 @@ -10,16 +10,16 @@
Attaching to a Process

-
Use a Symbian OS Attach to Process launch configuration to attach the debugger to an already running Symbian OS process or thread on a target device. This is useful for debugging DLLs where the main process is unknown or for servers running in RAM in a client-server relationship where the client relies on the presence of the server process to operate.
-
One common debugging DLL use case is when the developer doesn't know which process calls the DLL. This makes it difficult to debug the DLL because you doesn't know which process to attach to nor start. Carbide enables DLL debugging by simply attaching the DLL to any running process as long as the DLL is included in the Executables view.
-
You can also attach to a process in the Symbian OS Data view when debugging.
-
NOTE You cannot attach to a process running on the emulator. It must be a target device running the Symbian OS and the CODA software.
+
Use a Symbian Attach to Process launch configuration to attach the debugger to an already running Symbian process or thread on a target device. This is useful for debugging DLLs where the main process is unknown or for servers running in RAM in a client-server relationship where the client relies on the presence of the server process to operate.
+
One common debugging DLL use case is when the developer doesn't know which process calls the DLL. This makes it difficult to debug the DLL because you doesn't know which process to attach to nor start. Carbide enables DLL debugging by simply attaching the DLL to any running process as long as the DLL is included in the Executables view.
+
You can also attach to a process in the Symbian Data view when debugging.
+
NOTE You cannot attach to a process running on the emulator. It must be a target device running the Symbian and the CODA software.

When attempting to find a process the debugger uses the UID3 to locate the process.

Attaching to any Running Process

-
In the Executables view, click the Import an executable file icon () to add an executable to the Executables view for debugging. -
The executable added appears in the Project Explorer view under an Executables project. This group includes all executables listed in the Executables view that are not linked to any project in the workspace.
+
In the Executables view, click the Import an executable file icon () to add an executable to the Executables view for debugging. +
The executable added appears in the Project Explorer view under an Executables project. This group includes all executables listed in the Executables view that are not linked to any project in the workspace.

Figure 1 - Executables list in Project Explorer view

NOTE The executable must include symbolics in order for debugging to work.
@@ -33,7 +33,7 @@

Figure 3 - Attach to Process window

Select a process, click OK.
-
In this example we've linked the prefs.dll program to the process BlackFlag.exe on the device. The Attach to Process dialog closes. Open the Symbian OS Data view to show the process and thread information.
+
In this example we've linked the prefs.dll program to the process BlackFlag.exe on the device. The Attach to Process dialog closes. Open the Symbian Data view to show the process and thread information.

NOTE Terminating an Attach to Process session actually kills the process on the device. This means you must restart the process on the device in order to attach to it again.

@@ -41,7 +41,7 @@

Debug View

Debug Window
-
Symbian OS View
+
Symbian View

Debugging DLLs with any Process

Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
License: http://www.eclipse.org/legal/epl-v10.html
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_adding_symbian_class.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_adding_symbian_class.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_adding_symbian_class.htm Wed Oct 06 10:31:32 2010 -0500 @@ -8,15 +8,15 @@ -
Adding Symbian OS Classes
-
Use the New Symbian OS C++ Class wizard to add Symbian templated classes to a project.
+
Adding Symbian Classes
+
Use the New Symbian C++ Class wizard to add Symbian templated classes to a project.

-
Adding a Symbian OS C++ Class to a Project
+
Adding a Symbian C++ Class to a Project

-
Right-click the project name and select the New > Symbian OS C++ Class menu item.
-
The New Symbian OS C++ Class wizard appears showing the Select project page (Figure 1).
+
Right-click the project name and select the New > Symbian C++ Class menu item.
+
The New Symbian C++ Class wizard appears showing the Select project page (Figure 1).

-
Figure 1 - Symbian OS C++ Class wizard window
+
Figure 1 - Symbian C++ Class wizard window

Select the project to add the new class to, then click Next.

The Name and Location page appears (Figure 2).

diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_build.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_build.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_build.htm Wed Oct 06 10:31:32 2010 -0500 @@ -11,8 +11,8 @@
Building Projects and Symbian Components

Building projects consists of a new sbs-based build system (Raptor) that wraps build functionality around existing SDK build tools which invoke makmake commands (e.g. bldmake bldfiles and sbs build).
-
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 Creating New Projects. You can later change the Active Build Configuration. A command is available (Project > Build All Configurations) to build all the selected build configurations in a batch.
-
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.
+
The plug-ins provide extra functionality to set up suitable build configurations for Symbian C++ projects. The initial selection of a build configuration is done when you create a project, as described in Creating New Projects. You can later change the Active Build Configuration. A command is available (Project > Build All Configurations) to build all the selected build configurations in a batch.
+
Building Symbian C++ projects can involve the use of Symbian specific tools, such as the Symbian resource compiler. For detailed information on such tools, see the documentation for the SDK that you are using.

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 Properties for <project_name> dialog to control how the project is built. The following methods build a project:

@@ -54,7 +54,7 @@ dependencies present.

Projects are also built if you make a change to it and then click Debug. It may be useful to automatically save modified resources before a manual build process by enabling the Save automatically before build option in the Window > Preferences > General > Workspace preference panel.

NOTE If you want to turn off building before launching, uncheck the Build (if required) before launching option in the Window > Preferences > Run/Debug > Launching preference panel.
-
When performing a build, output is displayed in the Console view. If you do not want to clear the console before each build you need to uncheck the option Always clear console before building in the Build Console panel. This option is enabled by default. You can access this panel by selecting Window > Preferences > C/C++ > Build > Build Console preference panel (figure 4).
+
When performing a build, output is displayed in the Console view. If you do not want to clear the console before each build you need to uncheck the option Always clear console before building in the Build Console panel. This option is enabled by default. You can access this panel by selecting Window > Preferences > C/C++ > Build > Build Console preference panel (figure 4).

Figure 4 - Build Console preference panel

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.
@@ -69,7 +69,7 @@
Compile Source

Creating Projects

Creating a Launch Configuration
-
Debugging a Symbian OS Program
+
Debugging a Symbian Program

Build Symbian Component

Clean Symbian Component

Build Package (.pkg) File
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_build_cmd_line.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_build_cmd_line.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_build_cmd_line.htm Wed Oct 06 10:31:32 2010 -0500 @@ -40,7 +40,7 @@

Creating Projects

Creating a Launch Configuration
-
Debugging a Symbian OS Program
+
Debugging a Symbian Program

Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
License: http://www.eclipse.org/legal/epl-v10.html
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_clean.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_clean.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_clean.htm Wed Oct 06 10:31:32 2010 -0500 @@ -9,7 +9,7 @@
Cleaning Projects
-
In the Project Explorer or Symbian Project Navigator views you can select a project, right-click and select Clean Project (CTRL+SHIFT+-) to remove the object and make files, and output files. The files that are removed by this command include all the intermediate files created during compilation and all the executables and import libraries created by the linker.
+
In the Project Explorer or Symbian Project Navigator views you can select a project, right-click and select Clean Project (CTRL+SHIFT+-) to remove the object and make files, and output files. The files that are removed by this command include all the intermediate files created during compilation and all the executables and import libraries created by the linker.

If you select a project and select the menu option Project > Clean... the Clean dialog appears (Figure 1). You can clean all projects or select individual projects to clean within the workspace. This method of cleaning projects performs the same operations as the Clean Project context menu option. If the Start a build immediately option is selected, then the selected project(s) are rebuilt after the clean operation.

Figure 1 - Clean project options
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_creating_sis_file.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_creating_sis_file.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_creating_sis_file.htm Wed Oct 06 10:31:32 2010 -0500 @@ -21,7 +21,7 @@

For non-Platform Security SDKs (pre-OS 9.x), makesis is called

-
Depending upon which tool is used, you will need to complete some entries in the SIS Builder pane of the Carbide Build Configurations panel of the project Properties dialog box. You can access this pane by selecting a project in the Project Explorer view and select Project > Properties > Carbide.c++ > Carbide Build Configurations. Fill in the necessary information to add PKG files to the project for downloading.
+
Depending upon which tool is used, you will need to complete some entries in the SIS Builder pane of the Carbide Build Configurations panel of the project Properties dialog box. You can access this pane by selecting a project in the Project Explorer view and select Project > Properties > Carbide.c++ > Carbide Build Configurations. Fill in the necessary information to add PKG files to the project for downloading.

@@ -30,7 +30,7 @@

diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_config.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_config.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_config.htm Wed Oct 06 10:31:32 2010 -0500 @@ -45,7 +45,7 @@

Figure 1 - Initial blank Debug launch configuration window
-
Select a type of launch configuration (for example, Symbian OS Emulation), then click the New launch configuration icon to create a new +
Select a type of launch configuration (for example, Symbian Emulation), then click the New launch configuration icon to create a new configuration of that type.
A new configuration appears in the Configuration list under the appropriate section using the project name and target to create the configuration name.
@@ -77,7 +77,7 @@
Source (Eclipse)

Common (Eclipse)
-
To debug something outside of the workspace, be sure to import the binary into the Executables view.
+
To debug something outside of the workspace, be sure to import the binary into the Executables view.

Click Debug
The IDE launches the executable. If the launch configuration is set to change perspective, it switches to the specified perspective.
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_dlls.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_dlls.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_dlls.htm Wed Oct 06 10:31:32 2010 -0500 @@ -11,18 +11,18 @@
Debugging DLLs

A binary that you want to debug must be built with symbolic information (a .sym file). You can debug a DLL just as you would any other executable with full support of the Carbide debugger. Basically, the following situations can occur:

-
If the DLL appears in the Executables view it can be debugged. Just set breakpoints inside the DLL sources before you start the debug session. The next time the project is debugged, the DLL is loaded and made available for debugging.
+
If the DLL appears in the Executables view it can be debugged. Just set breakpoints inside the DLL sources before you start the debug session. The next time the project is debugged, the DLL is loaded and made available for debugging.

NOTE Breakpoints inside a DLL are not resolved until the DLL is loaded into memory by the calling binary.

-
If the DLL is not built by the project you can import the DLL by clicking the Import an executable file icon () in the Executables view. Then, set your breakpoints and start the debug session.
+
If the DLL is not built by the project you can import the DLL by clicking the Import an executable file icon () in the Executables view. Then, set your breakpoints and start the debug session.

You can use the Modules view to determine if a particular DLL or binary is loaded and available for debugging.

Other references

-
Executables view
+
Executables view

Breakpoints

Auto-targeting Executables

diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_rom.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_rom.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_rom.htm Wed Oct 06 10:31:32 2010 -0500 @@ -9,13 +9,13 @@
Debugging in ROM
-
You will see symbolic information for other components when you are debugging in ROM using Symbian OS Device if those components were built with symbolic information and the ROM Log file is specified. If a function in the stack crawl is in a ROM module and the IDE is able to find a file containing symbolic information for that module, the IDE will load it automatically and display function names. The IDE will also allow source level debugging and let you set breakpoints in this module.
+
You will see symbolic information for other components when you are debugging in ROM using Symbian Device if those components were built with symbolic information and the ROM Log file is specified. If a function in the stack crawl is in a ROM module and the IDE is able to find a file containing symbolic information for that module, the IDE will load it automatically and display function names. The IDE will also allow source level debugging and let you set breakpoints in this module.

Some issues to pay attention to when debugging include:

-
In Symbian OS Device you must specify the ROM log file in the ROM Log tab of the Symbian OS Device or Symbian OS Device (Attach to Process) launch configurations
+
In Symbian Device you must specify the ROM log file in the ROM Log tab of the Symbian Device or Symbian Device (Attach to Process) launch configurations

-
NOTE You cannot debug ROM DLLs using Symbian OS Device (Install SIS).
+
NOTE You cannot debug ROM DLLs using Symbian Device (Install SIS).

Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
License: http://www.eclipse.org/legal/epl-v10.html
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_preprocess.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_preprocess.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_preprocess.htm Wed Oct 06 10:31:32 2010 -0500 @@ -9,7 +9,7 @@
Preprocessing Files
-
In the Project Explorer or Symbian Project Navigator views you can preprocess source files (.c, .cpp, .cia), header files (.h), and resource files (.rss) by right-clicking the source file and then selecting the Preprocess command. Use the Preprocess preference panel to specify the preprocessor settings.
+
In the Project Explorer or Symbian Project Navigator views you can preprocess source files (.c, .cpp, .cia), header files (.h), and resource files (.rss) by right-clicking the source file and then selecting the Preprocess command. Use the Preprocess preference panel to specify the preprocessor settings.

When preprocessing resource files that use more than one language, the Select Language dialog appears asking you to select the language to preprocess.

Figure 1 - Selecting a source file to preprocess
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/working_with_sis_pkg_files.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/working_with_sis_pkg_files.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/working_with_sis_pkg_files.htm Wed Oct 06 10:31:32 2010 -0500 @@ -9,7 +9,7 @@
Creating a PKG File
-
After creating a project for the application you are developing for a device, you will need to create a .pkg file if you are using Symbian OS Device (Install SIS). A .pkg file contains all the files that will need to be downloaded to the device. Once a .pkg file is available, you can add it to a project, and the IDE will use it and additional information entered in the SIS Builder pane to create an application's .sis installation file. By default, when creating a project, the .pkg file is located in the project's sis folder.
+
After creating a project for the application you are developing for a device, you will need to create a .pkg file if you are using Symbian Device (Install SIS). A .pkg file contains all the files that will need to be downloaded to the device. Once a .pkg file is available, you can add it to a project, and the IDE will use it and additional information entered in the SIS Builder pane to create an application's .sis installation file. By default, when creating a project, the .pkg file is located in the project's sis folder.

A minimal .pkg file consists of the following lines:

Header — provides the following information on a single line: diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/sdks/sdk_view_properties.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/sdks/sdk_view_properties.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/sdks/sdk_view_properties.htm Wed Oct 06 10:31:32 2010 -0500 @@ -15,7 +15,7 @@

Viewing SDK Properties

-
Select an SDK in the Symbian OS SDKs list in the Symbian SDKs preference panel
+
Select an SDK in the Symbian SDKs list in the Symbian SDKs preference panel

Click Properties
The SDK Properties dialog (Figure 1) appears. You can now review the OS version.

diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_debugging.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_debugging.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_debugging.htm Wed Oct 06 10:31:32 2010 -0500 @@ -8,11 +8,11 @@ -
Debugging a Symbian OS Program
-
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.
+
Debugging a Symbian Program
+
Use the Carbide.c++ debugger to debug a compiled Symbian program in an emulator or on-device. The same process works for other emulators and target devices as well.

NOTE This example uses the Symbian Emulator included with the Symbian^3 SDK. The steps are identical for on-device debugging, although a .sym file is not needed for emulator builds.

-
Debugging a Symbian OS program
+
Debugging a Symbian program

NOTE You can only debug compiled programs. Use the Build Project command to compile project sources into a binary file if you do not already have an executable in the project. A symbolics (.sym) file is also required 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.

Set a breakpoint in the MyProject program
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_deploying.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_deploying.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_deploying.htm Wed Oct 06 10:31:32 2010 -0500 @@ -11,7 +11,7 @@
Deploying Programs to Devices

Once you have completed the program and tested it with the emulator, it’s possible to create a new build configuration for your device, build it, then create a .sis file and deploy it to a device.

To upload a valid .sis file to the target device you need software that communicates with the target device from your PC. Every Symbian phone ships with this connectivity software, which we will refer to generically as Symbian Connect. The actual name for the software is vendor dependent, so refer to your phone’s documentation for the name.
-
For example, most phones from Nokia that use Symbian OS come with Ovi Suite , which allows you to synchronize and transfer data between your compatible phone and a compatible PC via a compatible data cable or a wireless connection.
+
For example, most phones from Nokia that use Symbian come with Ovi Suite , which allows you to synchronize and transfer data between your compatible phone and a compatible PC via a compatible data cable or a wireless connection.

Essentially, the Symbian Connect program provides a method of connecting a PC to the target device via USB, IrDA, Bluetooth, or other serial connection. Once you make a connection, you can upload your .sis file to the target device and install the program.

NOTE A simple guide is provided to show the basic steps necessary to upload a .sis file to a target device. The actual steps required by the specific Symbian Connect program that ships with the SDK you are using may differ, so always refer to that phone ’s documentation for details.

diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_example.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_example.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_example.htm Wed Oct 06 10:31:32 2010 -0500 @@ -17,7 +17,7 @@
Using a debugger to interactively control the program in the emulator

Follow the steps to successfully create the HelloCarbide program and debug it on the S60 Emulator.
-
NOTE There must be at least one recognized SDK installed before you can create a project. See the Symbian SDKs panel 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 add it to the Discovered Symbian OS SDK list.
+
NOTE There must be at least one recognized SDK installed before you can create a project. See the Symbian SDKs panel 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 add it to the Discovered Symbian SDK list.

Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
License: http://www.eclipse.org/legal/epl-v10.html
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_example_trk.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_example_trk.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_example_trk.htm Wed Oct 06 10:31:32 2010 -0500 @@ -9,22 +9,22 @@ -
Run Mode Debug Example (Symbian OS Device (Install SIS))
-
This example shows how to create and build an application and debug it on a device using the Symbian OS Device (Install SIS) on-device debug agent. The majority of steps are identical to the ones used to create a program and debug in an emulator, with some minor variations.
+
Run Mode Debug Example (Symbian Device (Install SIS))
+
This example shows how to create and build an application and debug it on a device using the Symbian Device (Install SIS) on-device debug agent. The majority of steps are identical to the ones used to create a program and debug in an emulator, with some minor variations.

-
Debugging a Run-mode Project using Symbian OS Device (Install SIS)
+
Debugging a Run-mode Project using Symbian Device (Install SIS)

Import the Bld.inf to create a project using the Import wizard

In this example we are importing a project called Music, a complex project that includes several EXEs (MusicPlayer, MusicShop, MusicVisualizer). For the import, we select an ARM target.

Go to the project Properties page and in the Carbide Build Configuration panel specify the PKG file in the SIS Builder tab

Build the project (Ctrl+B)
-
Verify that all the binaries built by the project appear in the Executables view.
+
Verify that all the binaries built by the project appear in the Executables view.

NOTE The symbolics are automatically loaded for the binaries that appear in the Executables view.

Set breakpoints in the project source files

In this example we will set one breakpoint in two different EXEs. The first is set in the file called MCEngine.cpp (MCServer.exe) and the second is set in MPlayerAppUI.cpp (MusicPlayer.exe).

Click the Debug icon () to launch the New Launch Configuration wizard
-
Select the Symbian OS Device (Install SIS) Launch Configuration from the Launch Types page, then click Next
+
Select the Symbian Device (Install SIS) Launch Configuration from the Launch Types page, then click Next

Figure 1 - Launch Types page showing selection

If you have more than one executable, select the Main Executable in the Executable Selection page of the wizard, then click Next
@@ -59,12 +59,12 @@

-
In addition, you can click the Symbian OS Data View to examine the processes running on the devise during the debug session.
+
In addition, you can click the Symbian Data View to examine the processes running on the devise during the debug session.

Related references

On-device Debugging Troubleshooting
-
Symbian OS View
+
Symbian View

Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
License: http://www.eclipse.org/legal/epl-v10.html
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_overview_trk.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_overview_trk.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_overview_trk.htm Wed Oct 06 10:31:32 2010 -0500 @@ -10,34 +10,34 @@
Run Mode Overview
-
This example shows how to create and build an application and debug it on a device using the Symbian OS Device (Install SIS) on-device debug agent. Click this link to the HelloCarbide cheatsheet that provides links to detailed steps. The majority of steps are identical to the ones used to create a program and debug in an emulator, with some minor variations.
+
This example shows how to create and build an application and debug it on a device using the Symbian Device (Install SIS) on-device debug agent. Click this link to the HelloCarbide cheatsheet that provides links to detailed steps. The majority of steps are identical to the ones used to create a program and debug in an emulator, with some minor variations.

See the Run Mode Debug Example for a walkthrough of the following steps which include:

Verify that your SDK or customer kit is recognized in the Symbian SDKs panel.

Create a project by importing a Bld.inf
-
Verify that all the symbolics for the binaries are visible in the Executables view
+
Verify that all the symbolics for the binaries are visible in the Executables view

Manage the project's PKG file, being sure to:
-
Create a PKG file for the application (if using Symbian OS Device (Install SIS))
+
Create a PKG file for the application (if using Symbian Device (Install SIS))

Include the PKG file as part of the project in the SIS Builder pane of your project Properties

Specify application keys (if not a self-signing application) in the SIS Properties dialog

Build the project using a target for on-device build configuration (GCCE or ARM)

Start the CODA software on the device
-
Create a Symbian OS Device (Install SIS) launch configuration to provide additional information to the debugger
+
Create a Symbian Device (Install SIS) launch configuration to provide additional information to the debugger

Launch the debugger to interactively control the program on the device

NOTE Carbide will install the SISX file on the device prior to launching the debugger.

At this point you can open sources files from the Executables view or project view in order to set breakpoints.

Related tasks

-
Attaching to a Symbian OS Process
+
Attaching to a Symbian Process

Related references

On-device Debugging Troubleshooting
-
Symbian OS View
+
Symbian View

Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
License: http://www.eclipse.org/legal/epl-v10.html
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_requirements.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_requirements.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_requirements.htm Wed Oct 06 10:31:32 2010 -0500 @@ -9,7 +9,7 @@
System Requirements
-
You use the Carbide.c++ IDE in conjunction with a recognized SDK to develop Symbian OS software.
+
You use the Carbide.c++ IDE in conjunction with a recognized SDK to develop Symbian software.

In practice, whether you use an SDK, a developer kit (DevKit), or both depends on the edition of Carbide.c++ you have (see Table 1). Further, if you use an OS devkit, it must use SBSv2.
@@ -49,7 +49,7 @@

Tool
SIS Builder	Use the Add control to add one or more SIS or PKG files to the project up to the maximum number Carbide supports. Note that the SIS Builder pane operates on a build configuration level. You will need to add files in this pane for every build configuration in the project. - In addition, any PKG file added here is picked up by the Installation tab in Symbian OS Device (Install SIS) configurations. However, as only one SIS file can be debugged at a time you must specify which SIS/PKG file to install for debugging purposes. This is handy if you have both a developer SIS file and a certified SIS file that you want to remain in sync during development. Both are always built but you only need to debug one. + In addition, any PKG file added here is picked up by the Installation tab in Symbian Device (Install SIS) configurations. However, as only one SIS file can be debugged at a time you must specify which SIS/PKG file to install for debugging purposes. This is handy if you have both a developer SIS file and a certified SIS file that you want to remain in sync during development. Both are always built but you only need to debug one. Figure 1 - SIS Builder tab
Other Software	A Symbian OS SDK and Perl: +	A Symbian SDK and Perl: Nokia Qt SDK diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_updating.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_updating.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_updating.htm Wed Oct 06 10:31:32 2010 -0500 @@ -15,7 +15,7 @@ Updating Carbide.c++ Updates to Carbide.c++ current features are available using the Install New Software feature. This feature now makes use of the P2 provisioning system released in Eclipse 3.4 which provides a more robust updating mechanism for currently installed features as well as the adding of new ones to the Carbide environment. - Carbide is a collection of difference software projects combined into a working environment for Symbian OS C/C++ development. At its base Carbide uses Eclipse and CDT projects from Eclipse.org. We then modify some of these base plug-ins to work with our Carbide plug-ins. This is important to know as any updates to those modified base plug-ins may cause Carbide not to work as intended. + Carbide is a collection of difference software projects combined into a working environment for Symbian C/C++ development. At its base Carbide uses Eclipse and CDT projects from Eclipse.org. We then modify some of these base plug-ins to work with our Carbide plug-ins. This is important to know as any updates to those modified base plug-ins may cause Carbide not to work as intended. IMPORTANT We recommend that you not install any updates for Carbide.c++ features except for those provided by Nokia via Install New Software. Replacing any standard Eclipse plugin with an updated version from a non-Nokia update site can result in Carbide.c++ no longer working as intended. Installing Carbide Updates diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_carbide_setup.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_carbide_setup.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_carbide_setup.htm Wed Oct 06 10:31:32 2010 -0500 @@ -9,10 +9,10 @@ Launch Configuration Setup - To communicate between the Carbide.c++ debugger and the on-device debug agent, using either Symbian OS Device (Install SIS) or Symbian OS Device, you must define a debug launch configuration that matches the installed debug agent. The two configurations available include: + To communicate between the Carbide.c++ debugger and the on-device debug agent, using either Symbian Device (Install SIS) or Symbian Device, you must define a debug launch configuration that matches the installed debug agent. The two configurations available include: - Symbian OS Device (Install SIS) — used to run or debug applications on a target device using CODA (Carbide On-device Debug Agent). CODA is an application that runs on released phones and allows you to debug your executables. The debugger will download a Symbian OS installation file to the phone and install it prior to launching. - Symbian OS Device — used to run or debug applications or ROM code on a target device using CODA. CODA is an application that runs on reference boards and prototype phones and allows you to debug your executables. The debugger will download files to the phone prior to launching. + Symbian Device (Install SIS) — used to run or debug applications on a target device using CODA (Carbide On-device Debug Agent). CODA is an application that runs on released phones and allows you to debug your executables. The debugger will download a Symbian installation file to the phone and install it prior to launching. + Symbian Device — used to run or debug applications or ROM code on a target device using CODA. CODA is an application that runs on reference boards and prototype phones and allows you to debug your executables. The debugger will download files to the phone prior to launching. By default, you can click the Debug icon () in the toolbar to launch the New Launch Configuration Wizard. This creates a launch configuration for the project based on project information and any additional input required, like COM port selection. It is the recommended method for creating new launch configurations. Or, use the Debug window to create a customized launch configuration. @@ -23,7 +23,7 @@ Choose the Run > Debug As menu item The Debug window appears. Select a Configuration type for on-device debugging and click New - Choose the Symbian OS Device or Symbian OS Device (Install SIS) configuration based on which debug agent is installed on the device, then click New. A new debug launch configuration appears in the Configuration list and the Main tab appears. + Choose the Symbian Device or Symbian Device (Install SIS) configuration based on which debug agent is installed on the device, then click New. A new debug launch configuration appears in the Configuration list and the Main tab appears. Enter the required information For debug launch configurations using CODA, the following pages require review and possible option settings: diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_connection_bluetooth.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_connection_bluetooth.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_connection_bluetooth.htm Wed Oct 06 10:31:32 2010 -0500 @@ -32,7 +32,7 @@ Figure 2. Bluetooth Configuration windows Local Services panel Click OK to close the Bluetooth Configuration window - Download the Symbian OS Device (Install SIS) or Symbian OS Device SISX file to the device + Download the Symbian Device (Install SIS) or Symbian Device SISX file to the device Related concepts diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_connection_usb.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_connection_usb.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_connection_usb.htm Wed Oct 06 10:31:32 2010 -0500 @@ -14,7 +14,7 @@ DKU-2 CA-53 - Carbide uses plug-and-play (PnP) to create a remote connection for the phone or target device once it's plugged in. Once a remote connection is created the Remote Connections view appears in Carbide. In addition, the current available connection is shown in the workspace's lower-right trim area. + Carbide uses plug-and-play (PnP) to create a remote connection for the phone or target device once it's plugged in. Once a remote connection is created the Remote Connections view appears in Carbide. In addition, the current available connection is shown in the workspace's lower-right trim area. Figure 1. Current available connection shown in workspace trim area NOTE PC Suite or Ovi Suite must be installed on your PC for the following steps to work. diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_bluetooth.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_bluetooth.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_bluetooth.htm Wed Oct 06 10:31:32 2010 -0500 @@ -9,7 +9,7 @@ Installing On-device Debug Agents using Bluetooth - Use Bluetooth to install the on-device debug agent, either Symbian OS Device (Install SIS) or Symbian OS Device, as a SISX file, to enable on-target debugging. The installation location of the on-device debug agent will vary based on the phone. Symbian OS Device (Install SIS) is usable on both consumer and RnD versions of the device. Symbian OS Device is only usable on RnD devices. + Use Bluetooth to install the on-device debug agent, either Symbian Device (Install SIS) or Symbian Device, as a SISX file, to enable on-target debugging. The installation location of the on-device debug agent will vary based on the phone. Symbian Device (Install SIS) is usable on both consumer and RnD versions of the device. Symbian Device is only usable on RnD devices. On some phones it will be the Installed folder, on others it may be in My Own folder. Refer to the documentation that came with the phone to learn where installed programs are stored. NOTE The following example shows how to install the SISX file from a PC running Windows XP SP2 using an internal Bluetooth device. The actions to install the SISX file may be different on your version of Windows. Refer to the OS documentation for information on transferring a file via a Bluetooth connection. @@ -38,7 +38,7 @@ Related references - On-Device Connections + On-Device Connections Debug Window (On-device Debugging) Overview Related tasks diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_pcsuite.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_pcsuite.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_pcsuite.htm Wed Oct 06 10:31:32 2010 -0500 @@ -41,7 +41,7 @@ Related reference - On-Device Connections + On-Device Connections Debug Window (On-device Debugging) Overview Related tasks diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_usb.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_usb.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_usb.htm Wed Oct 06 10:31:32 2010 -0500 @@ -40,7 +40,7 @@ Related reference - On-Device Connections + On-Device Connections Debug Window (On-device Debugging) Overview Related tasks diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_installation_instr.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_installation_instr.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_installation_instr.htm Wed Oct 06 10:31:32 2010 -0500 @@ -9,11 +9,11 @@ Installing an On-device Debug Agent - To use any version of the on-device debug agent on a target device it must be installed. We highly recommend using the On-Device Connections dialog to help connect and verify that the latest version of CODA (Carbide On-device Debug Agent) 4.x is installed on the device, especially to support plug-and-play (PnP) connections. + To use any version of the on-device debug agent on a target device it must be installed. We highly recommend using the On-Device Connections dialog to help connect and verify that the latest version of CODA (Carbide On-device Debug Agent) 4.x is installed on the device, especially to support plug-and-play (PnP) connections. Refer to the Bluetooth Connection Setup page for more information on using Bluetooth or the USB Connection Setup page if using USB. Related references - On-Device Connections + On-Device Connections On-Device Debugging Debug Window (On-device Debugging) Overview diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_overview.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_overview.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_overview.htm Wed Oct 06 10:31:32 2010 -0500 @@ -19,7 +19,7 @@ Related references Debug Window (On-device Debugging) Overview - On-Device Connections + On-Device Connections On-device Debugging Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. License: http://www.eclipse.org/legal/epl-v10.html diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_preconditions.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_preconditions.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_preconditions.htm Wed Oct 06 10:31:32 2010 -0500 @@ -15,17 +15,17 @@ Verify that your system has the following: - A current Symbian OS SDK is installed + A current Symbian SDK is installed Perl is installed RVCT or GCCE compiler USB support on your PC Nokia Ovi/PC Suite (or equivilent software) for connecting and installing applications to the device - Download and install the current CODA SISX file using the On-Device Connections dialog + Download and install the current CODA SISX file using the On-Device Connections dialog If CODA is not install, use the On-Device Connections > New Connection Wizard > Install remote agents pane. Specify the communication method with the on-target device during the debug session - Start CODA on the device. During startup of CODA on the device you must specify the communication method the on-device agent uses to debug the device. Currently, those methods include USB or a null serial cable. For USB, A USB cable must connect the PC to the device and a valid serial port assigned. Use On-Device Connections dialog to make the identification and connection setup quick and easy. + Start CODA on the device. During startup of CODA on the device you must specify the communication method the on-device agent uses to debug the device. Currently, those methods include USB or a null serial cable. For USB, A USB cable must connect the PC to the device and a valid serial port assigned. Use On-Device Connections dialog to make the identification and connection setup quick and easy. Related concepts diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_start_sisx.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_start_sisx.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_start_sisx.htm Wed Oct 06 10:31:32 2010 -0500 @@ -13,7 +13,7 @@ The location of the CODA (Carbide On-device Debug Agent) software varies based on the phone. On some phones it will be the Installed, Applications, or the My Own folder. Refer to the documentation that came with the phone to learn where installed programs are stored. Make sure CODA (Carbide On-device Debug Agent) is present on the device - To install CODA see Install Remote Agents tab in the New Connections dialog. + To install CODA see Install Remote Agents tab in the New Connections dialog. Launch the CODA program on the device Verify the connection is working on the device and within Carbide diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_troubleshooting.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_troubleshooting.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_troubleshooting.htm Wed Oct 06 10:31:32 2010 -0500 @@ -113,9 +113,9 @@ Check that Carbide.c++ and your USB Virtual COM port or BT Serial Port agree on the port settings. - Use the On-Device Connections dialog to quickly determine if you can communicate with the device in the Test Connection pane + Use the On-Device Connections dialog to quickly determine if you can communicate with the device in the Test Connection pane Open your Bluetooth or USB cable's connection settings: Start > Settings > Control panel > System > Hardware > Device Manager. In the Device Manager dialog, click open the Ports directory, then you will see all the com ports available on the machine. Here you will be able to see the COM port for Bluetooth or USB. Sometimes you will have two COM ports for Bluetooth, so you might have to try specifying either of them. - In the Carbide tools, open the launch configuration associated with the target device and verify that you have specified the correct launch configuration for TRK. For example, the launch configuration should be either Symbian OS Device (Install SIS) or Symbian OS Device configuration. + In the Carbide tools, open the launch configuration associated with the target device and verify that you have specified the correct launch configuration for TRK. For example, the launch configuration should be either Symbian Device (Install SIS) or Symbian Device configuration. In the Carbide tools, open the launch configuration associated with the target device. In the Connections tab make sure you specify the same COM port number as in the device manager. For Bluetooth, if two ports are listed in the device manager, then you need to try to both, to see which one works. For USB, don't select the COM port assigned to the serial port. Always select the COM port assigned to the virtual COM port ID for the phone that is specified in the Device Manager. Make sure the settings in these two dialogs are the same and that the launch configuration settings refer to the right COM port. You shouldn't have to touch the other settings, but they're Data Bits: 8; Parity: None; Stop Bits: 1; Flow Control: None.

Tool

SIS Builder

Use the Add control to add one or more SIS or PKG files to the project up to the maximum number Carbide supports. Note that the SIS Builder pane operates on a build configuration level. You will need to add files in this pane for every build configuration in the project.

In addition, any PKG file added here is picked up by the Installation tab in Symbian OS Device (Install SIS) configurations. However, as only one SIS file can be debugged at a time you must specify which SIS/PKG file to install for debugging purposes. This is handy if you have both a developer SIS file and a certified SIS file that you want to remain in sync during development. Both are always built but you only need to debug one.

In addition, any PKG file added here is picked up by the Installation tab in Symbian Device (Install SIS) configurations. However, as only one SIS file can be debugged at a time you must specify which SIS/PKG file to install for debugging purposes. This is handy if you have both a developer SIS file and a certified SIS file that you want to remain in sync during development. Both are always built but you only need to debug one.

Figure 1 - SIS Builder tab

Other Software

A Symbian OS SDK and Perl:

A Symbian SDK and Perl:

Nokia Qt SDK
- DKU-2
- CA-53
-
Carbide uses plug-and-play (PnP) to create a remote connection for the phone or target device once it's plugged in. Once a remote connection is created the Remote Connections view appears in Carbide. In addition, the current available connection is shown in the workspace's lower-right trim area.
+
Carbide uses plug-and-play (PnP) to create a remote connection for the phone or target device once it's plugged in. Once a remote connection is created the Remote Connections view appears in Carbide. In addition, the current available connection is shown in the workspace's lower-right trim area.

Figure 1. Current available connection shown in workspace trim area

NOTE PC Suite or Ovi Suite must be installed on your PC for the following steps to work.
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_bluetooth.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_bluetooth.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_bluetooth.htm Wed Oct 06 10:31:32 2010 -0500 @@ -9,7 +9,7 @@
Installing On-device Debug Agents using Bluetooth
-
Use Bluetooth to install the on-device debug agent, either Symbian OS Device (Install SIS) or Symbian OS Device, as a SISX file, to enable on-target debugging. The installation location of the on-device debug agent will vary based on the phone. Symbian OS Device (Install SIS) is usable on both consumer and RnD versions of the device. Symbian OS Device is only usable on RnD devices.
+
Use Bluetooth to install the on-device debug agent, either Symbian Device (Install SIS) or Symbian Device, as a SISX file, to enable on-target debugging. The installation location of the on-device debug agent will vary based on the phone. Symbian Device (Install SIS) is usable on both consumer and RnD versions of the device. Symbian Device is only usable on RnD devices.

On some phones it will be the Installed folder, on others it may be in My Own folder. Refer to the documentation that came with the phone to learn where installed programs are stored.

NOTE The following example shows how to install the SISX file from a PC running Windows XP SP2 using an internal Bluetooth device. The actions to install the SISX file may be different on your version of Windows. Refer to the OS documentation for information on transferring a file via a Bluetooth connection.
@@ -38,7 +38,7 @@
Related references
Related tasks
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_pcsuite.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_pcsuite.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_pcsuite.htm Wed Oct 06 10:31:32 2010 -0500 @@ -41,7 +41,7 @@
Related reference
Related tasks
diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_usb.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_usb.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_usb.htm Wed Oct 06 10:31:32 2010 -0500 @@ -40,7 +40,7 @@

Related reference

Related tasks

diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_installation_instr.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_installation_instr.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_installation_instr.htm Wed Oct 06 10:31:32 2010 -0500 @@ -9,11 +9,11 @@

Installing an On-device Debug Agent

To use any version of the on-device debug agent on a target device it must be installed. We highly recommend using the On-Device Connections dialog to help connect and verify that the latest version of CODA (Carbide On-device Debug Agent) 4.x is installed on the device, especially to support plug-and-play (PnP) connections.

Refer to the Bluetooth Connection Setup page for more information on using Bluetooth or the USB Connection Setup page if using USB.

Related references

diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_overview.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_overview.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_overview.htm Wed Oct 06 10:31:32 2010 -0500 @@ -19,7 +19,7 @@

Related references

diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_preconditions.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_preconditions.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_preconditions.htm Wed Oct 06 10:31:32 2010 -0500 @@ -15,17 +15,17 @@

Verify that your system has the following:
- A current Symbian OS SDK is installed
- A current Symbian SDK is installed
- Perl is installed
- RVCT or GCCE compiler
- USB support on your PC
- Nokia Ovi/PC Suite (or equivilent software) for connecting and installing applications to the device
Download and install the current CODA SISX file using the On-Device Connections dialog
Download and install the current CODA SISX file using the On-Device Connections dialog

If CODA is not install, use the On-Device Connections > New Connection Wizard > Install remote agents pane.

Specify the communication method with the on-target device during the debug session

Start CODA on the device. During startup of CODA on the device you must specify the communication method the on-device agent uses to debug the device. Currently, those methods include USB or a null serial cable. For USB, A USB cable must connect the PC to the device and a valid serial port assigned. Use On-Device Connections dialog to make the identification and connection setup quick and easy.

Related concepts

diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_start_sisx.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_start_sisx.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_start_sisx.htm Wed Oct 06 10:31:32 2010 -0500 @@ -13,7 +13,7 @@

The location of the CODA (Carbide On-device Debug Agent) software varies based on the phone. On some phones it will be the Installed, Applications, or the My Own folder. Refer to the documentation that came with the phone to learn where installed programs are stored.

Make sure CODA (Carbide On-device Debug Agent) is present on the device
-
To install CODA see Install Remote Agents tab in the New Connections dialog.
+
To install CODA see Install Remote Agents tab in the New Connections dialog.
Launch the CODA program on the device
Verify the connection is working on the device and within Carbide diff -r 16e8bfa397ad -r ff0156b93599 core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_troubleshooting.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_troubleshooting.htm Sat Oct 02 12:36:21 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_troubleshooting.htm Wed Oct 06 10:31:32 2010 -0500 @@ -113,9 +113,9 @@
Check that Carbide.c++ and your USB Virtual COM port or BT Serial Port agree on the port settings.
- Use the On-Device Connections dialog to quickly determine if you can communicate with the device in the Test Connection pane
- Use the On-Device Connections dialog to quickly determine if you can communicate with the device in the Test Connection pane
- Open your Bluetooth or USB cable's connection settings: Start > Settings > Control panel > System > Hardware > Device Manager. In the Device Manager dialog, click open the Ports directory, then you will see all the com ports available on the machine. Here you will be able to see the COM port for Bluetooth or USB. Sometimes you will have two COM ports for Bluetooth, so you might have to try specifying either of them.
- In the Carbide tools, open the launch configuration associated with the target device and verify that you have specified the correct launch configuration for TRK. For example, the launch configuration should be either Symbian OS Device (Install SIS) or Symbian OS Device configuration.
- In the Carbide tools, open the launch configuration associated with the target device and verify that you have specified the correct launch configuration for TRK. For example, the launch configuration should be either Symbian Device (Install SIS) or Symbian Device configuration.
- In the Carbide tools, open the launch configuration associated with the target device. In the Connections tab make sure you specify the same COM port number as in the device manager. For Bluetooth, if two ports are listed in the device manager, then you need to try to both, to see which one works. For USB, don't select the COM port assigned to the serial port. Always select the COM port assigned to the virtual COM port ID for the phone that is specified in the Device Manager.
- Make sure the settings in these two dialogs are the same and that the launch configuration settings refer to the right COM port. You shouldn't have to touch the other settings, but they're Data Bits: 8; Parity: None; Stop Bits: 1; Flow Control: None.

Getting Started

MBM File

Creating a DLL Project

Debugging DLLs

Other References

Breakpoints Overview

Build System Overview

Basic Build Commands

Command Line Arguments

Concepts

Using SCM in Carbide

Emulation Debugging

Related tasks

Related reference

Building the N-Gage project

For On-device Debugging

Deploying the N-Gage project to a device

Debugging the Game project

Precompiled Headers

General registers

Carbide On-device Debug Agent

Related tasks

Working with Debugger Data

Workspace Information

Other references

Breakpoint Status Indicators

Table 1 Breakpoint—type, icons, and states

Other references

Other references

Stepping into a routine

Adding Program Resources

License Information

COPYRIGHTS

Initial Contributors:

NOTICES

License Information

COPYRIGHTS

Initial Contributors:

NOTICES

INF Editor - Overview Tab

Other references

INF Editor - Create / Edit Makefile Entry

Table 1. Add/Edit Makefile entry — items

Other references

INF Editor - Add / Edit MMP File Entry

Table 1. Add MMP file entry — items

Other references

INF Editor - Exports Tab

Table 1. Export tab — items

Add Export dialog

Table 2. Add Export — items

Edit Export dialog

Table 3. Edit Export — items

Other references

INF Editor - BLD.INF Tab

Related references

Applications Launch Configuration

Other references

Attach to Process Launch Configuration

Other references

Emulator Launch Configuration

Symbian OS Reference Board Launch

Symbian Reference Board Launch

Other references

Available Launch Configurations

Other references

Symbian OS Emulator Launch

Symbian Emulator Launch

Other references

Symbian OS Device Launch

Symbian Device Launch

Other references

Launch Types

Other references

Emulation Debugger page

Table 1. Debugger page — emulation options

Run-mode Debugger page

Table 2. Debugger page — run-mode options

Stop-mode Debugger page

Table 3. Debugger page — stop-mode options