Introduction in Getting Started

- 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. -

- 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 supplied with the development kit that you use. Please consult - that documentation for further information on Symbian OS concepts and - development processes.

Getting Started

+ 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. +

+ 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 supplied with the development kit that you use. Please consult + that documentation for further information on Symbian OS concepts and + development processes.

MBM File

- MBM, or multi-bitmap, is a Symbian OS-specific bitmap file format. This - file contains multiple bitmaps and it can contain both 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.

Related tasks

Related references

MBM File

+ MBM, or multi-bitmap, is a Symbian OS-specific bitmap file format. This + file contains multiple bitmaps and it can contain both 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.

Related tasks

Related references

Related concepts

Related tasks

Related references

Related concepts

Related tasks

Related references

- This section of the User Guide provides conceptual overview about working - with different types of projects, including importing an .inf file, modifying - existing projects and accessing help. -

Related concepts

Related tasks

Related references

+ This section of the User Guide provides conceptual overview about working + with different types of projects, including importing an .inf file, modifying + existing projects and accessing help. +

Related concepts

Related tasks

Related references

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.

Basic Build Commands

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

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 -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.

Other references

Build System Overview

Basic Build Commands

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

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 +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.

Other references

Concurrent Versions System (CVS)

Carbide.c++ supports the Concurrent Versions System (CVS) for immediate version control support. Other revision systems are also supported but require the downloading of an Eclipse plug-in to add that feature to Carbide. Visit the eclipse.org or eclipse-plugins.2y.net sites to locate the plug-ins you need.

For more informaton on using CVS within Carbide, see the Workbench User Guide > Concepts > Team programming with CVS.

Concurrent Versions System (CVS)

For more informaton on using CVS within Carbide, see the Workbench User Guide > Concepts > Team programming with CVS.

Data Viewer Plug-ins

Data Viewers are plug-ins that include an user interface to show a custom view of data. These plug-ins are often platform specific. Data editors are data viewers that also let you modify and write data.

The IDE will keep a registry of plug-ins that can view particular types. The plug-ins will register themselves with the IDE and indicate which formats and platforms they support. When a variable or memory address is selected, you can choose the plugin from the Data menu.

A Data Viewer plugin may also be designed without a custom user interface. This type of viewer would override the built in debugger methods of showing a variable value as text and parsing an edited value back into variable data.

Data Viewer Plug-ins

External Builds Support

The IDE can build an external makefile and debug its output. A linker plugin will enable the IDE to manage a command line and targets associated with a makefile. The command line is executed when a build step is initiated. The linker plugin will also supply the executable to use for debugging.

The linker plugin will provide a preference panel named External Build that is used to configure a target. The preference panel provides text fields for you to configure the command line for the target (which will enable building), specify the working directory and the output file used to launch a debugging session, and the debug platform.

The linker plugin is generic so that it can be used regardless of the target CPU and OS. The list of available debugger preference panels will be updated by the IDE when you select the debug platform.

The External Build Target preference panel will collect the following information:

External Builds Support

The External Build Target preference panel will collect the following information:

FPU Registers

The FPU Registers are the register contents of the floating-point unit (FPU) of the host computer. The exact listing of these registers depends on the host FPU and current build target.

Related concepts

Related tasks

Related references

FPU Registers

The FPU Registers are the register contents of the floating-point unit (FPU) of the host computer. The exact listing of these registers depends on the host FPU and current build target.

Related concepts

Related tasks

Related references

General Registers

The General Registers are the register contents of the central processing unit (CPU) of the host computer. The exact listing of these registers depends on the host CPU and current build target.

Related concepts

Related tasks

Related references

General Registers

The General Registers are the register contents of the central processing unit (CPU) of the host computer. The exact listing of these registers depends on the host CPU and current build target.

Related concepts

Related tasks

Related references

Host-specific Registers

The Registers view also lists additional register contents for registers specific to the host. The exact listing of these registers depends on the host computer and current build target.

Related concepts

Related tasks

Related references

Host-specific Registers

The Registers view also lists additional register contents for registers specific to the host. The exact listing of these registers depends on the host computer and current build target.

Related concepts

Related tasks

Related references

Carbide Macros

Carbide.c++ supports the macro _CARBIDE_CPP_ during the preprocessing of .mmp and .inf files. Use this macro in those files to include Carbide specific files during the preprocessing stage that are never recognized outside of the Carbide.c++ IDE.

#ifdef _CARBIDE_CPP_
- // Add any makmake statements that you want specific to Carbide.c++ only
-#endif

Tasks

Carbide Macros

#ifdef _CARBIDE_CPP_
+ // Add any makmake statements that you want specific to Carbide.c++ only
+#endif

Tasks

Always refer to the N-Gage documentation for more information on creating, deploying, and debugging N-Gage projects.

Precompiled Headers

Precompiled header support is available for Symbian OS 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.

Listing 1 shows an example of a precompiled header source file called -pch_test.pch++.

The resultant output file, pch_test.mch can be included in other source or prefix files as:

Precompiled Headers

Precompiled header support is available for Symbian OS 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.

Listing 1 shows an example of a precompiled header source file called +pch_test.pch++.

The resultant output file, pch_test.mch can be included in other source or prefix files as:

Symbol Hint

The symbol hint shows information about variable values. This information appears automatically while the debugger is active.
-Select the Show variable values in the source code option in the Display Settings preference panel to use the symbol hint.

Toggling the Symbol Hint

Turn on the symbol hint to view information about program variables in source views.

Using the Symbol Hint

During a debugging session, use the symbol hint to view information about program variables.

To use the symbol hint, rest the cursor over a variable in a source view. After a brief pause, the symbol hint appears and shows the current variable value.

Symbol Hint

The symbol hint shows information about variable values. This information appears automatically while the debugger is active.
+Select the Show variable values in the source code option in the Display Settings preference panel to use the symbol hint.

Toggling the Symbol Hint

Turn on the symbol hint to view information about program variables in source views.

Using the Symbol Hint

During a debugging session, use the symbol hint to view information about program variables.

To use the symbol hint, rest the cursor over a variable in a source view. After a brief pause, the symbol hint appears and shows the current variable value.

About Symbolics Files

A symbolics file contains debugging information that the IDE generates for a computer program. The debugger uses this information to control program execution. For example, the debugger uses the symbolics file to find the source code that corresponds to the executing object code of the computer program.

The IDE supports several types of symbolics files. Some programs generate separate symbolic files, while others do not. For example, when you use the Freescale CodeView on Windows program, the IDE places the symbolics file inside the generated binary file.

About Symbolics Files

Symbols, .pkg

Project Templates

Carbide.c++ provides many common templates to quickly create projects using specific SDKs or feature sets. Every template provides basic support for a specific type of project including sources, libraries, resources, etc. The type and number of templates available are controlled by the SDKs you have enabled.

Table 1. Available project templates

Related tasks

Project Templates

Table 1. Available project templates

Related tasks

Setting a Thread-specific Conditional Breakpoint

Project Type	Available Templates
Generic Symbian OS	- Basic console application (EXE) - used for any SDK - Basic dynamically linked library (DLL) - used for any SDK - Basic static library (LIB) - used for any SDK - Empty Project for Symbian - empty project with minimal bld.inf and MMP and no sources or libraries. For advanced users only. -
S60	- GUI Application - GUI Application with UI Designer - Open C Console application - project template based on industry-standard POSIX and middleware C libraries for S60 -
Tutorials	- S60 Birthday Tutorial with UI Designer - S60 Yahoo! Image Search Tutorial with UI Designer -

Project Type	Available Templates
Generic Symbian OS	+ Basic console application (EXE) - used for any SDK + Basic dynamically linked library (DLL) - used for any SDK + Basic static library (LIB) - used for any SDK + Empty Project for Symbian - empty project with minimal bld.inf and MMP and no sources or libraries. For advanced users only. +
S60	+ GUI Application + GUI Application with UI Designer + Open C Console application - project template based on industry-standard POSIX and middleware C libraries for S60 +
Tutorials	+ S60 Birthday Tutorial with UI Designer + S60 Yahoo! Image Search Tutorial with UI Designer +

Carbide's debugger supports thread-specific breakpoints. Depending on what the protocol supports, there are several different ways it's supported. You can setup a special condition on a breakpoint. Enter mwThreadID == threadID, where mwThreadID is a keyword recognized by the core debugger and threadID is the number that represents the ID of the thread that you want to stop.
-

Setting a Thread-specific Conditional Breakpoint

On-device Debugging

The on-device debug agent (Application TRK or System TRK) 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. An on-device debug agent provides:

Using the on-device debug 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 S60 3rd Edition devices, UIQ 3rd Edition devices, and Symbian TechView devkits.

NOTE The type of on-device debug agent you have is based upon which Carbide.c++ product you have licensed. System TRK is only available with the Professional or OEM version of the product.

Related tasks

On-device Debugging

NOTE The type of on-device debug agent you have is based upon which Carbide.c++ product you have licensed. System TRK is only available with the Professional or OEM version of the product.

Related tasks

Watchpoints Overview

A watchpoint is a marker set on a specific memory location which is designed to suspend program execution when the value at that location changes. Watchpoints are closely related to breakpoints and are shown in the Breakpoints view.

When a watchpoint is encountered during program execution, the debugger suspends execution and the Debug perspective appears so you can examine the executable's current state, check register and variable values, and use the stepping commands to walk line by line through the program to verify its operation. You can also change values and alter the flow of normal program execution. Setting watchpoints helps you debug your program and verify its efficiency.

Watchpoints Overview

Multi-core Debugging

The IDE allows simultaneous debugging of multiple projects. This feature provides multi-core debugging capability for some embedded processors. By configuring each project to operate on a single core, the IDE can debug multiple cores by debugging multiple projects.

Multi-core Debugging

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.

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.

Working with Memory

This section explains how to work with memory in a debugging session. Topics include:

Related tasks

Related References

Working with Memory

This section explains how to work with memory in a debugging session. Topics include:

Related tasks

Related References

Controlling Program Execution

This section explains how to use breakpoints, breakpoint actions, and watchpoints to manipulate execution of your program in the Carbide™ IDE:

After you set these items in your source code, you start a debugging session to use them. As program execution arrives at each of these items, the debugger can halt execution, perform a task, or update data.

Related concepts

Related references

Controlling Program Execution

This section explains how to use breakpoints, breakpoint actions, and watchpoints to manipulate execution of your program in the Carbide™ IDE:

Related concepts

Related references

Working with Variables

This section explains how to work with variables in a Carbide™ IDE debugging session. The following windows show various types of information about variables.

Related references

Working with Variables

This section explains how to work with variables in a Carbide™ IDE debugging session. The following windows show various types of information about variables.

Related references

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. 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.

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

Projects in one workspace cannot refer to projects in a different workspace. Thus, large projects spanning folders outside of the workspace are not handled at all. Storing all the project files in the workspace makes managing them easier from a project management perspective. Files accessible inside the workspace, like project source and resource files, are better supported than those outside the workspace (for example, SDK headers). Local History, CVS, MMP/bld.inf editors, etc. are available for files inside the workspace but not for those outside the workspace.

NOTE Carbide automatically updates MMP and INF files as changes are made within the MMP and INF editors.

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

Workspace Information

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

NOTE Carbide automatically updates MMP and INF files as changes are made within the MMP and INF editors.

Other references

Creating Conditional Breakpoints

Use the Properties for Breakpoint > Common > Conditional option to create conditional breakpoints. Where regular breakpoints suspend execution each time they are hit, a condition breakpoint evaluates an expression to determine if it is true or not. If the expression evaluates true, then program execuation is suspended and the Debug perpective shown. If the expression evaluates to false, execution continues.

You create a conditional breakpoint in the Conditional field by entering a valid expression. Valid expressions include:

Other references

Creating Conditional Breakpoints

You create a conditional breakpoint in the Conditional field by entering a valid expression. Valid expressions include:

Other references

Exporting Breakpoints and Watchpoints

Use the Export Breakpoints command to export selected breakpoints and watchpoints to a file with a .bkpt extension. All the breakpoints set in the source files of the project and the watchpoints are listed in the Export Breakpoints dialog. Click the specific breakpoints and watchpoints to export or use Select All to include all of them. Specify the destination file name and folder, then click Finish.

Other references

Exporting Breakpoints and Watchpoints

Option	Description	Default
Breakpoint List	Select the breakpoints and watchpoints that you wish to export, and deselect those that you do not.	not selected
To file	The file to export the breakpoints and watchpoints to, you can also click Browse... to search for a location to export.	There can be two possible defaults: - - If you have never exported breakpoints or watchpoints before it will be blank - If you have exported breakpoints and watchpoints before the last file name you exported to will be automatically inserted. -
Overwrite existing file without warning	- When selected, if the file you wish to export to already exists, it will be overwritten automatically by the wizard. -	not selected

Other references

Importing Breakpoints and Watchpoints

Option	Description	Default
Breakpoint List	Select the breakpoints and watchpoints that you wish to export, and deselect those that you do not.	not selected
To file	The file to export the breakpoints and watchpoints to, you can also click Browse... to search for a location to export.	There can be two possible defaults: + + If you have never exported breakpoints or watchpoints before it will be blank + If you have exported breakpoints and watchpoints before the last file name you exported to will be automatically inserted. +
Overwrite existing file without warning	+ When selected, if the file you wish to export to already exists, it will be overwritten automatically by the wizard. +	not selected

Use the Import Breakpoints command to import a .bkpt file containing breakpoint and watchpoint data and apply it to the current project. Right-click in the Breakpoints view and select Import Breakpoints... from the context menu. You have the options of updating all existing breakpoints with the stored data or simply creating a working set containing the imported data.

Other references

Importing Breakpoints and Watchpoints

Option	Description
From file	Enter the file name to import or click Browse to search for a .bkpt file to import.
Update existing breakpoints	- Update all existing project breakpoints found in the imported breakpoint data file. -
Create breakpoint working sets	Create a new breakpoint working set containing the imported breakpoint data.

Other references

Breakpoints Properties

Option	Description
From file	Enter the file name to import or click Browse to search for a .bkpt file to import.
Update existing breakpoints	+ Update all existing project breakpoints found in the imported breakpoint data file. +
Create breakpoint working sets	Create a new breakpoint working set containing the imported breakpoint data.

Use the Properties for Breakpoint window to examine and modify a specific breakpoints properties. By setting certain options its possible to create both conditional and temporary breakpoints.

Table 1. Breakpoint properties - common page

Other references

Breakpoints Properties

Property	Explanation
Class	Breakpoint class
Type	Breakpoint type. Regular is the default software breakpoint type.
File	The complete path and filename of the file where the breakpoint is located.
Line number	The breakpoints line number in the file.
Enabled	Indicates the current status of the breakpoint. When checkmarked, the breakpoint stops program execution if its condition is met. When unchecked, the breakpoint is ignored during the debug session.
Condition	The conditional expression associated with the item. This conditional expression must evaluate to true in order for the item to perform its specified action. If left blank, execution is suspended each time the breakpoint is hit. If a condition is entered,like n==10, execution only stops when the condition evaluates to true.
Ignore count	Defines when a breakpoint should be ignored during a debug session. The default count 0 indicates that the breakpoint should suspend execution each time it is hit. A value of 1 defines this breakpoint as a temporary breakpoint, which should be ignored after the first time it is encountered. -

Use the Properties for Breakpoint window to examine and modify a specific breakpoints properties. By setting certain options its possible to create both conditional and temporary breakpoints.

Table 1. Breakpoint properties - common page

Other references

Breakpoint Status Indicators

Property	Explanation
Class	Breakpoint class
Type	Breakpoint type. Regular is the default software breakpoint type.
File	The complete path and filename of the file where the breakpoint is located.
Line number	The breakpoints line number in the file.
Enabled	Indicates the current status of the breakpoint. When checkmarked, the breakpoint stops program execution if its condition is met. When unchecked, the breakpoint is ignored during the debug session.
Condition	The conditional expression associated with the item. This conditional expression must evaluate to true in order for the item to perform its specified action. If left blank, execution is suspended each time the breakpoint is hit. If a condition is entered,like n==10, execution only stops when the condition evaluates to true.
Ignore count	Defines when a breakpoint should be ignored during a debug session. The default count 0 indicates that the breakpoint should suspend execution each time it is hit. A value of 1 defines this breakpoint as a temporary breakpoint, which should be ignored after the first time it is encountered. +

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

Other references

Breakpoint Status Indicators

Type	Icon	State	Explanation
Enabled		Unresolved	The breakpoint is enabled but the symbols for the module are not loaded or the breakpoint was not able to be set within the current function.Breakpoint icon remains in unflagged state indicating unresolved status. - If the breakpoint has been set in the source file but not resolved: - - a debug session has not been launched to resolve the breakpoint. For example, you just set the breakpoint and have yet to launch a debug session. - the symbols file containing the breakpoint cannot be found. Ensure the module to debug is present in the Executable view list so the debugger can locate and load the executable for symbol resolution. - breakpoint is set on a source line without any executable code - breakpoint is located in a deadstripped function not present in the executable -
	Resolved	The breakpoint is currently enabled, the symbols for the module are loaded, and the breakpoint located in the executable being debugged. The debugger halts program execution at an enabled breakpoint. - - 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 - resolved and moved —the breakpoint is not found in the executable at the specified point. Debugger moves breakpoint forward in the current function until a line is found that can be resolved. Breakpoint icon moved to source line matching new breakpoint location and changed to flagged icon - -
Disabled		Unresolved	Indicates that the breakpoint is currently disabled but not located in the executable during a debug session. The debugger does not halt program execution at a disabled breakpoint.
	Resolved	Indicates that the breakpoint is currently disabled and resolved for the source line. The debugger does not halt program execution at a disabled breakpoint.

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

Table 1 Breakpoint—type, icons, and states

Other references

Creating Temporary Breakpoints and Watchpoints

Type	Icon	State	Explanation
Enabled		Unresolved	The breakpoint is enabled but the symbols for the module are not loaded or the breakpoint was not able to be set within the current function.Breakpoint icon remains in unflagged state indicating unresolved status. + If the breakpoint has been set in the source file but not resolved: + + a debug session has not been launched to resolve the breakpoint. For example, you just set the breakpoint and have yet to launch a debug session. + the symbols file containing the breakpoint cannot be found. Ensure the module to debug is present in the Executable view list so the debugger can locate and load the executable for symbol resolution. + breakpoint is set on a source line without any executable code + breakpoint is located in a deadstripped function not present in the executable +
	Resolved	The breakpoint is currently enabled, the symbols for the module are loaded, and the breakpoint located in the executable being debugged. The debugger halts program execution at an enabled breakpoint. + + 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 + resolved and moved —the breakpoint is not found in the executable at the specified point. Debugger moves breakpoint forward in the current function until a line is found that can be resolved. Breakpoint icon moved to source line matching new breakpoint location and changed to flagged icon + +
Disabled		Unresolved	Indicates that the breakpoint is currently disabled but not located in the executable during a debug session. The debugger does not halt program execution at a disabled breakpoint.
	Resolved	Indicates that the breakpoint is currently disabled and resolved for the source line. The debugger does not halt program execution at a disabled breakpoint.

Use the Properties for Breakpoint > Common > Ignore Count option to create temporary breakpoints or watchpoints. Where regular breakpoints or watchpoints suspend execution each time they are hit, a temporary one is removed once it is hit. The default value is 0, which suspends program execution each time the breakpoint or watchpoint are hit.

To set a temporary breakpoint or watchpoint, change the value of Ignore count to 1. The first time the breakpoint or watchpoint is hit execution is suspended, while any subsequent hits are ignored.

Other references

Creating Temporary Breakpoints and Watchpoints

Other references

Viewing Breakpoints and Watchpoints

Use the Breakpoints view (Figure 1) to examine a project's breakpoints and watchpoints, toggle individual breakpoints between enabled and disabled, set conditional breakpoints, export and import breakpoints, or remove them from one or more build configurations.

The Breakpoints view is available in the Debug perspective by default. To open it in another perspective, use the Window > Show View > Breakpoints menu option. Once open you have control over breakpoint states and how they are shown. For example:

Breakpoints view toolbar icons

Breakpoints view context menu options

The following commands appear on the context menu when you right-click within the Breakpoints view:

Other references

Viewing Breakpoints and Watchpoints

Item	Explanation
Go to File	Opens the associated file for the breakpoint in an editor, make it active and highlight the breakpoint location. If the file is already open, make it active and the highlight the breakpoint location.
Enable	Enables the selected breakpoints.
Disable	Disables the selected breakpoints.
Remove	Removes the selected breakpoints from the project and Breakpoints view.
Remove All	Removes all breakpoints from the project and Breakpoints view.
Select All	Selects all the breakpoints shown in the Breakpoints view.
Copy	Copies the selected breakpoint to the clipboard.
Paste	Always disabled.
Export Breakpoints	Opens the Export Breakpoints wizard to store the project's breakpoint data.
Import Breakpoints	Opens the Import Breakpoints wizard to import stored breakpoint data (.bkpt).
Add Watchpoint (C/C++)...
Properties	Opens the Properties for Breakpoint dialog.

Breakpoints view toolbar icons

Breakpoints view context menu options

The following commands appear on the context menu when you right-click within the Breakpoints view:

Other references

Other Useful Commands

Item	Explanation
Go to File	Opens the associated file for the breakpoint in an editor, make it active and highlight the breakpoint location. If the file is already open, make it active and the highlight the breakpoint location.
Enable	Enables the selected breakpoints.
Disable	Disables the selected breakpoints.
Remove	Removes the selected breakpoints from the project and Breakpoints view.
Remove All	Removes all breakpoints from the project and Breakpoints view.
Select All	Selects all the breakpoints shown in the Breakpoints view.
Copy	Copies the selected breakpoint to the clipboard.
Paste	Always disabled.
Export Breakpoints	Opens the Export Breakpoints wizard to store the project's breakpoint data.
Import Breakpoints	Opens the Import Breakpoints wizard to import stored breakpoint data (.bkpt).
Add Watchpoint (C/C++)...
Properties	Opens the Properties for Breakpoint dialog.

The Debug view has a few other commands that are useful under some debugging situations:

Disconnecting from a process

Use the Disconnect command (

) when debugging with Application TRK or System TRK to detach the debugger from a process on the device while leaving the device running.

When debugging in stop-mode it will detach the debugger and leave the CPU running on the device.

Instruction Stepping Mode

Activate to enable instruction stepping mode to examine a program as it steps into disassembled code.

Removing all processes

Other references

Other Useful Commands

The Debug view has a few other commands that are useful under some debugging situations:

Disconnecting from a process

Use the Disconnect command (

) when debugging with Application TRK or System TRK to detach the debugger from a process on the device while leaving the device running.

When debugging in stop-mode it will detach the debugger and leave the CPU running on the device.

Instruction Stepping Mode

Activate to enable instruction stepping mode to examine a program as it steps into disassembled code.

Removing all processes

Other references

Repositioning the Program Counter

Once you've suspended a program debug session, the Disassembly view provides commands for move or reposition the program counter (PC). These command include:

WARNING Use of the Move to Line and Resume at Line can leave a program in an unstable state. Use at your own risk.

Run to Line (C/C++)

Use the Run to Line command (

) to execute the program from the currently executed line to the selected line.

Move to Line (C/C++)

Use the Move to Line (C/C++) command (

) to move the program counter to the selected line, skipping all intermediate lines but not resume execution. This enables you to skip suspect code and continue stepping through your program.

Resume at Line (C/C++)

Use the Resume at Line (C/C++) command (

) to begin program execution at the selected line, skipping all lines between it and the currently executed line.

Other references

Repositioning the Program Counter

Once you've suspended a program debug session, the Disassembly view provides commands for move or reposition the program counter (PC). These command include:

WARNING Use of the Move to Line and Resume at Line can leave a program in an unstable state. Use at your own risk.

Run to Line (C/C++)

Use the Run to Line command (

) to execute the program from the currently executed line to the selected line.

Move to Line (C/C++)

Use the Move to Line (C/C++) command (

) to move the program counter to the selected line, skipping all intermediate lines but not resume execution. This enables you to skip suspect code and continue stepping through your program.

Resume at Line (C/C++)

Use the Resume at Line (C/C++) command (

) to begin program execution at the selected line, skipping all lines between it and the currently executed line.

Other references

Debugging Overview

The Debug view provides an overview of the debug session as it relates to the executing program.

Other references

Debugging Overview

The Debug view provides an overview of the debug session as it relates to the executing program.

Other references

Variables and Expressions Overview

Variables are symbols used in programs to store values or expressions that can change during the life of the program. Being able to view a variable's value is helpful when debugging a program. Expressions are the result of one or more variables being combined to produce a result based on the variable values and the way they are calculated. Variables are shown in the Variables view while expressions are shown in the Expressions view.

Variables and Expressions Overview

Viewing Expressions

The Expressions view allows manipulation of expressions. An expression is a snippet of code that is evaluated to produce a value. In Carbide they are defined using C/C++ expressions. Some expressions may need to be evaluated at a specific location in the program so that its variables can be referenced.

Expressions view toolbar icons

Expressions view context menu options

Item	Icons	Explanation
Show Type Names		Toggles the display of type names in the Expressions view.
Show Logical Structure		Not available in C/C++ yet.
Collapse All		Collapses all expanded expressions into the top level.
Remove Selected Expression		Click to remove all currently selected expressions from the expressions list.
Remove All Expressions		Click to remove all expressions from the expressions list.

Right-click in the Expression's pane in the Expressions view to access the context menu commands shown in Figure 2.

Other references

Viewing Expressions

Item	Explanation
Select All	Selects all the expressions shown in the Expressions view.
Copy Expressions	Copies the selected expressions to the clipboard.
Remove	Remove the selected expressions from the Expressions view list.
Remove All	Remove all expressions from the Expressions view list.
Find...	Opens a Find dialog to search the Expressions view list.
Change Value...	Opens the Set Value dialog where you can modify the value assigned to the selected expressions. Change the value and click OK. -
Add Watch Expression...	Opens the Add Watch Exression dialog for creation of a new expression. -
Disable	Disables automatic evaluation of the selected expression and appends (disabled) to the expression name. Useful when you have lots of expressions but are concentrating on only a few. The more expressions that need evaluaton, the longer it takes to update the Expressions view.
Enable	Enables automatic evaluation of the selected expression. Enables a disabled expression so that it is evaluated during the debug session.
Edit Watch Expression...	Opens the Edit Watch Expression dialog where you can modify the expression and enable it for automatic evaluation.
Reevaluate Watch Expression	Forces the expression to be reevaluated. Useful after the expressions has been edited or not evaluated due to being disabled.

Expressions view toolbar icons

Expressions view context menu options

Item	Icons	Explanation
Show Type Names		Toggles the display of type names in the Expressions view.
Show Logical Structure		Not available in C/C++ yet.
Collapse All		Collapses all expanded expressions into the top level.
Remove Selected Expression		Click to remove all currently selected expressions from the expressions list.
Remove All Expressions		Click to remove all expressions from the expressions list.

Right-click in the Expression's pane in the Expressions view to access the context menu commands shown in Figure 2.

Other references

Viewing Variables

Item	Explanation
Select All	Selects all the expressions shown in the Expressions view.
Copy Expressions	Copies the selected expressions to the clipboard.
Remove	Remove the selected expressions from the Expressions view list.
Remove All	Remove all expressions from the Expressions view list.
Find...	Opens a Find dialog to search the Expressions view list.
Change Value...	Opens the Set Value dialog where you can modify the value assigned to the selected expressions. Change the value and click OK. +
Add Watch Expression...	Opens the Add Watch Exression dialog for creation of a new expression. +
Disable	Disables automatic evaluation of the selected expression and appends (disabled) to the expression name. Useful when you have lots of expressions but are concentrating on only a few. The more expressions that need evaluaton, the longer it takes to update the Expressions view.
Enable	Enables automatic evaluation of the selected expression. Enables a disabled expression so that it is evaluated during the debug session.
Edit Watch Expression...	Opens the Edit Watch Expression dialog where you can modify the expression and enable it for automatic evaluation.
Reevaluate Watch Expression	Forces the expression to be reevaluated. Useful after the expressions has been edited or not evaluated due to being disabled.

The Variables view allows manipulation of project variables and the variable hierarchy used in the source code. For example, you can change the variable format, change a variable value, add watch expressions, or add global variables.

Figure 1 shows the Variables view with Show Type Names option enabled. The default view shows the variables list and include the Name and Value for all the variables within scope. In addition, when you select a variable its value is also shown in a different pane within the view.

Variables view toolbar icons

Variables view context menu options

Item	Icons	Explanation
Show Type Names		Toggles the display of type names in the Variables view.
Show Logical Structure		Not available in C/C++ yet.
Collapse All		Collapses all expanded variables into the top level.
Add Global Variables		Click to open the Global Variables dialog where you can select one or more global variables to display in the Variables view. Global variables appear at the top of the variables list.
Remove Selected Global Variables		Click to remove all currently selected global variables from the variables list.
Remove All Global Variables		Click to remove all global variables from the variables list.
Menu		Enables you to modifiy the Layout to change the view orientation between: horizontal, vertical, or variables pane only. - In addition, use Show All Variables to toggle between showing only those variables that are in scope and live or show all local variables, even if redundant. With this option on you will see all of the variables including the multiple defined variables like “i” for your loops and ones that may no longer have accurate values.

Right-click in the Variables view to access the commands on the Variables view context menu.

Other references

Viewing Variables

Item	Explanation
Select All	Selects all the variables shown in the Variables view.
Copy Variables	Copies the selected variables to the clipboard.
Enable	Enables the selected variable.
Disable	Disables the selected variable.
Display as Array...
Cast To Type...	Opens the Cast to Type dialog where you can assign a new type to the variable.
Restore Original Type	Resets the selected variable to the original type assigned by the program.
View Memory	Opens a Memory view on the selected variable so you can examine it.
Find...	Opens a Find dialog to search for variables.
Change Value...	Opens the Set Value dialog where you can modify the value assigned to the selected variable. Change the value and click OK. -
Add Watchpoint (C/C++)...	Opens the Add Watchpoint dialog enabling you to define a watchpoint on the variable.
Add Global Variables...	Select to open the Global Variables dialog where you can select one or more global variables to display in the Variables view. Global variables appear at the top of the variables list.
Remove Global Variables	Remove the selected global variables from the Variables view.
Remove All Global Variables	Remove all global variables from the Variables view.
Create Watch Expression	Creates a watchpoint on the selected variable and displays it in the Watchpoint view.
Format	Change the selected variable's display format. The default setting is Natural, or the format assigned when the variable is defined. For example, the decimal value of 256 would appear as: - - Binary (0b100000) - Natural (256) - Decimal (256) - Hexadecimal (0x100) -

Variables view toolbar icons

Variables view context menu options

Item	Icons	Explanation
Show Type Names		Toggles the display of type names in the Variables view.
Show Logical Structure		Not available in C/C++ yet.
Collapse All		Collapses all expanded variables into the top level.
Add Global Variables		Click to open the Global Variables dialog where you can select one or more global variables to display in the Variables view. Global variables appear at the top of the variables list.
Remove Selected Global Variables		Click to remove all currently selected global variables from the variables list.
Remove All Global Variables		Click to remove all global variables from the variables list.
Menu		Enables you to modifiy the Layout to change the view orientation between: horizontal, vertical, or variables pane only. + In addition, use Show All Variables to toggle between showing only those variables that are in scope and live or show all local variables, even if redundant. With this option on you will see all of the variables including the multiple defined variables like “i” for your loops and ones that may no longer have accurate values.

Right-click in the Variables view to access the commands on the Variables view context menu.

Other references

Setting and Removing Watchpoints

You create a watchpoint to monitor a value in a specified memory location. The debugger halts program execution on the line of source code that triggered the watchpoint. This is different than a breakpoint, which halts program execution prior to executing the line of source code on which the breakpoint is set.

Setting watchpoints

Item	Explanation
Select All	Selects all the variables shown in the Variables view.
Copy Variables	Copies the selected variables to the clipboard.
Enable	Enables the selected variable.
Disable	Disables the selected variable.
Display as Array...
Cast To Type...	Opens the Cast to Type dialog where you can assign a new type to the variable.
Restore Original Type	Resets the selected variable to the original type assigned by the program.
View Memory	Opens a Memory view on the selected variable so you can examine it.
Find...	Opens a Find dialog to search for variables.
Change Value...	Opens the Set Value dialog where you can modify the value assigned to the selected variable. Change the value and click OK. +
Add Watchpoint (C/C++)...	Opens the Add Watchpoint dialog enabling you to define a watchpoint on the variable.
Add Global Variables...	Select to open the Global Variables dialog where you can select one or more global variables to display in the Variables view. Global variables appear at the top of the variables list.
Remove Global Variables	Remove the selected global variables from the Variables view.
Remove All Global Variables	Remove all global variables from the Variables view.
Create Watch Expression	Creates a watchpoint on the selected variable and displays it in the Watchpoint view.
Format	Change the selected variable's display format. The default setting is Natural, or the format assigned when the variable is defined. For example, the decimal value of 256 would appear as: + + Binary (0b100000) + Natural (256) + Decimal (256) + Hexadecimal (0x100) +

Right-click in the Breakpoints view and choose the Add Watchpoint (C/C++)... command to open the Add Watchpoint window. A watchpoint suspends program execution when the memory location that you specify is accessed with a write or read operation and it's based on the access setting. Use the Add Watchpoint window to specify the memory location, its memory size, unit size, and define whether the watchpoint triggers on a read, write, or on both operations. Watchpoints can also be added directly in the Variables, Outline, and the Memory Rendering views.

Table 1. Add Watchpoint options

Removing Watchpoints

Other references

Setting and Removing Watchpoints

Setting watchpoints

Name	Description
Expression to watch	If not already entered, you can enter any arbitrary memory location for watching.
Memory space	Not supported.
Units	Define the size of the units to monitor. This setting defaults to the size of the variable to watch. If an arbitrary memory address is entered, then the default unit size is set to 1 byte. Once you enable the units checkbox, you're must enter a value for it.
Access: Write/Read	Check the appropriate access type to trigger the watchpoint for the specified memory location. This setting is shown as a unique icon in the Breakpoints view next to the listed watchpoint. The following list shows the resolved version of the icons used to indicate the type of watchpoint set: - - Read only () - Write only () - Read/Write () -

Table 1. Add Watchpoint options

Removing Watchpoints

Other references

Watchpoint Status Indicators

Name	Description
Expression to watch	If not already entered, you can enter any arbitrary memory location for watching.
Memory space	Not supported.
Units	Define the size of the units to monitor. This setting defaults to the size of the variable to watch. If an arbitrary memory address is entered, then the default unit size is set to 1 byte. Once you enable the units checkbox, you're must enter a value for it.
Access: Write/Read	Check the appropriate access type to trigger the watchpoint for the specified memory location. This setting is shown as a unique icon in the Breakpoints view next to the listed watchpoint. The following list shows the resolved version of the icons used to indicate the type of watchpoint set: + + Read only () + Write only () + Read/Write () +

Use watchpoints (sometimes referred to as access breakpoints) to halt program execution when a specific global location is accessed. After you set a watchpoint at a key point in memory, you can halt program execution whenever that point in memory is written to or read from. You can then examine the call chain, check register and variable values, and step through your code. You can also change values and alter the flow of normal program execution.

A watchpoint must be both enabled and resolved during a debug session in order to halt program execution. The Breakpoints view indicates the status of any watchpoint using a set of common icons and checkmark status badge. These include:

In effect, a watchpoint that is enabled by the user and resolved by the debugger during program launch can halt program execution. The table below shows the various states that cause the debugger to halt program execution:

Table 1 Watchpoint—stop execution chart

Unlike a breakpoint, a watchpoint can detect when any part of your program affects memory. For example, if a write or write/read watchpoint is set, when the program writes a new value to the address or area of memory that has the watchpoint, the debugger suspends program execution.

Watchpoint	Resolved	Unresolved
Enabled	Stops execution	No
Disabled	No	No

NOTE You cannot set a watchpoint on a local variable, because the debugger cannot detect watchpoints for variables stored on the stack or in registers.

Table 2 Watchpoint—types and states

A project can have a different maximum number of watchpoints, depending on the build target. The IDE generally limits the acceptable range for watchpoints to memory that it can write-protect. This range also depends on the host and on the application.

Other references

Watchpoint Status Indicators

Type	State	Icon	Explanation
Write	enabled		The watchpoint is activated for write access operations on the specific memory location and if resolved, will halt program execution on a write operation at the watchpoint.
disabled		Watchpoint is disabled for the source line, debugger does not halt program execution on a write operation.
Read	enabled		The watchpoint is activated for read access operations on the specific memory location and if resolved, will halt program execution on a read operation at the watchpoint.
disabled		Watchpoint is disabled for the source line, debugger does not halt program execution on a read operation.
Write/Read	enabled		The watchpoint is activated for both read and write access operations on the specific memory location and if resolved, will halt program execution on any read or write operation at the watchpoint.
disabled		Watchpoint is disabled for the source line, debugger does not halt program execution on a read or write operation.

Table 1 Watchpoint—stop execution chart

Watchpoint	Resolved	Unresolved
Enabled	Stops execution	No
Disabled	No	No

NOTE You cannot set a watchpoint on a local variable, because the debugger cannot detect watchpoints for variables stored on the stack or in registers.

Table 2 Watchpoint—types and states

Other references

Enabling and Disabling Watchpoints

Type	State	Icon	Explanation
Write	enabled		The watchpoint is activated for write access operations on the specific memory location and if resolved, will halt program execution on a write operation at the watchpoint.
disabled		Watchpoint is disabled for the source line, debugger does not halt program execution on a write operation.
Read	enabled		The watchpoint is activated for read access operations on the specific memory location and if resolved, will halt program execution on a read operation at the watchpoint.
disabled		Watchpoint is disabled for the source line, debugger does not halt program execution on a read operation.
Write/Read	enabled		The watchpoint is activated for both read and write access operations on the specific memory location and if resolved, will halt program execution on any read or write operation at the watchpoint.
disabled		Watchpoint is disabled for the source line, debugger does not halt program execution on a read or write operation.

In the Breakpoints view use the checkboxes that appear next to a watchpoint to enable or disable that watchpoint. When enabled, if the value in the watchpoint location changes per the read/write condition, then program execution is suspended. If the watchpoint is disabled and the value changes, no action is taken by the debugger.

Enabling Watchpoints

Disabling Watchpoints

Other references

Enabling and Disabling Watchpoints

Enabling Watchpoints

Disabling Watchpoints

Other references

Watchpoints Overview

Table 1 Watchpoint—stop execution chart

Watchpoint	Resolved	Unresolved
Enabled	Stops execution	No
Disabled	No	No

NOTE You cannot set a watchpoint on a local variable, because the debugger cannot detect watchpoints for variables stored on the stack or in registers.

Table 2 Watchpoint—types and states

Related concepts

Related tasks

Related references

Watchpoints Overview

Type	State	Icon	Explanation
Write	enabled		The watchpoint is activated for write access operations on the specific memory location and if resolved, will halt program execution on a write operation at the watchpoint. -
disabled		Watchpoint is disabled for the source line, debugger does not halt program execution on a write operation. -
Read	enabled		The watchpoint is activated for read access operations on the specific memory location and if resolved, will halt program execution on a read operation at the watchpoint. -
disabled		Watchpoint is disabled for the source line, debugger does not halt program execution on a read operation. -
Write/Read	enabled		The watchpoint is activated for both read and write access operations on the specific memory location and if resolved, will halt program execution on any read or write operation at the watchpoint. -
disabled		Watchpoint is disabled for the source line, debugger does not halt program execution on a read or write operation. -

Table 1 Watchpoint—stop execution chart

Watchpoint	Resolved	Unresolved
Enabled	Stops execution	No
Disabled	No	No

NOTE You cannot set a watchpoint on a local variable, because the debugger cannot detect watchpoints for variables stored on the stack or in registers.

Table 2 Watchpoint—types and states

Related concepts

Related tasks

Related references

License Information

COPYRIGHTS

Type	State	Icon	Explanation
Write	enabled		The watchpoint is activated for write access operations on the specific memory location and if resolved, will halt program execution on a write operation at the watchpoint. +
disabled		Watchpoint is disabled for the source line, debugger does not halt program execution on a write operation. +
Read	enabled		The watchpoint is activated for read access operations on the specific memory location and if resolved, will halt program execution on a read operation at the watchpoint. +
disabled		Watchpoint is disabled for the source line, debugger does not halt program execution on a read operation. +
Write/Read	enabled		The watchpoint is activated for both read and write access operations on the specific memory location and if resolved, will halt program execution on any read or write operation at the watchpoint. +
disabled		Watchpoint is disabled for the source line, debugger does not halt program execution on a read or write operation. +

Copyright © 2009 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".

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:

NOTICES

Connection page

The Connection page specifies the method used to transfer files to the target device. Once a Serial Port type is chosen, the remaining options contain default values for the specific connection type. Users can change these remaining options to match the target device's communication specifications.

Table 1. Connection page —items

Other references

Connection page

Item	Explanation
Serial Port	Select the serial port option to use for this launch or launch configuration. Once set, this port will be used for all subsequent launch configurations until it is set again. Note that for USB and BT can be dynamically assigned, so its critical that the port ID assigned here matches the one the system is using to communicate with the target device. - If you are using a USB connection, the connected phone's name should appear in the menu to help identify which port is being used.
Baud Rate	Use the Baud Rate option to select the baud rate for communication. The default baud rate value is 115200 bits per second (bps).
Data Bits	Use the Data Bits option to select a common data bits size (4, 5, 6, 7, and 8). The default data bits value is 8.
Parity	Use the Parity option to select the parity setting (None, Odd, or Even). The default parity value is None.
Stop Bits	Use the Stop Bits option to select the stop bits setting (1, 1.5, 2). The default stop bits value is 1.
Flow Control	Use the Flow Control option to select the flow control setting (None, Hardware (RTS/CTS), and Software (XON/XOFF)). The default flow control value is None.

Table 1. Connection page —items

Other references

x86 Exceptions page

Item	Explanation
Serial Port	Select the serial port option to use for this launch or launch configuration. Once set, this port will be used for all subsequent launch configurations until it is set again. Note that for USB and BT can be dynamically assigned, so its critical that the port ID assigned here matches the one the system is using to communicate with the target device. + If you are using a USB connection, the connected phone's name should appear in the menu to help identify which port is being used.
Baud Rate	Use the Baud Rate option to select the baud rate for communication. The default baud rate value is 115200 bits per second (bps).
Data Bits	Use the Data Bits option to select a common data bits size (4, 5, 6, 7, and 8). The default data bits value is 8.
Parity	Use the Parity option to select the parity setting (None, Odd, or Even). The default parity value is None.
Stop Bits	Use the Stop Bits option to select the stop bits setting (1, 1.5, 2). The default stop bits value is 1.
Flow Control	Use the Flow Control option to select the flow control setting (None, Hardware (RTS/CTS), and Software (XON/XOFF)). The default flow control value is None.

Use the x86 Exceptions page in the Emulation 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.

Table 1. x86 Exceptions page —items

Other references

x86 Exceptions page

Item	Explanation
Exceptions to catch	Click to enable by exception which x86 exceptions the debugger should catch.
Check All	Enables catching all exceptions.
Clear All	Disables catching all exceptions.

Table 1. x86 Exceptions page —items

Other references

Executables page

Item	Explanation
Exceptions to catch	Click to enable by exception which x86 exceptions the debugger should catch.
Check All	Enables catching all exceptions.
Clear All	Disables catching all exceptions.

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.

Table 1. Executable page —items

Other references

Executables page

Item	Explanation
Load symbols for these executables and target them for debugging	Select the rule which governs the executable support used by this project for debugging. The options include: - - Executables in the workspace from this SDK — shows all executables in the workspace built using the specified SDK. This is the default setting. - Executables built by this project — shows only the executables built by this project using the specified SDK - Executables selected below — shows only the executables chosen by the user. Initial list display uses the All Executables listing. - All executables (slows launch) — shows all the executables in the workspace regardless of which SDK created them. Selecting this option will slow down Carbide launches as the list is populated. -
Executables list	Shows all the executables associated with this project.
Add...	Opens the Select an executable file dialog which can locate and select executable files and add them to the project's executables list.
Select All	Enables all the executables in the list for debugging.
Unselect All	Disables all the executables in the list from debugging.

Table 1. Executable page —items

Other references

File Transfer page

Item	Explanation
Load symbols for these executables and target them for debugging	Select the rule which governs the executable support used by this project for debugging. The options include: + + Executables in the workspace from this SDK — shows all executables in the workspace built using the specified SDK. This is the default setting. + Executables built by this project — shows only the executables built by this project using the specified SDK + Executables selected below — shows only the executables chosen by the user. Initial list display uses the All Executables listing. + All executables (slows launch) — shows all the executables in the workspace regardless of which SDK created them. Selecting this option will slow down Carbide launches as the list is populated. +
Executables list	Shows all the executables associated with this project.
Add...	Opens the Select an executable file dialog which can locate and select executable files and add them to the project's executables list.
Select All	Enables all the executables in the list for debugging.
Unselect All	Disables all the executables in the list from debugging.

The File Transfer page displays an auto-populated list of files for System TRK 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 Application TRK 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. System TRK users can use this panel to download any type of file, like bitmaps, HTML, sounds, and more, to the phone and applicable to Application TRK for transfering any files outside of the installation file.

Table 1. File Transfer page —items

Other references

File Transfer page

Item	Explanation
File transfer list	The File transfer list displays the project files that are moved to the target device for launch and debugging purposes. It contains these columns: - - Enabled—a checkmark indicates that the IDE should transfer the specified file to the target directory. If unchecked, do not transfer the file. - File to transfer—the path and filename to a file on the host machine to be transfered - Target directory—the path to the target directory where transfered files are placed on the device. - - - The target directories where files can be installed depends upon the type of device image you have on the device and which version of TRK you are using. - - Application TRK - public folders only on production device images - System TRK - public and protected folders, like c:\sys\bin, on RnD device images - -
Add	Click to add a file to the file transfer list.
Edit...	Click to edit the selected file in the file transfer list.
Remove	Click to remove the selected file from the file transfer list.

Table 1. File Transfer page —items

Other references

Installation page

Item	Explanation
File transfer list	The File transfer list displays the project files that are moved to the target device for launch and debugging purposes. It contains these columns: + + Enabled—a checkmark indicates that the IDE should transfer the specified file to the target directory. If unchecked, do not transfer the file. + File to transfer—the path and filename to a file on the host machine to be transfered + Target directory—the path to the target directory where transfered files are placed on the device. + + + The target directories where files can be installed depends upon the type of device image you have on the device and which version of TRK you are using. + + Application TRK - public folders only on production device images + System TRK - public and protected folders, like c:\sys\bin, on RnD device images + +
Add	Click to add a file to the file transfer list.
Edit...	Click to edit the selected file in the file transfer list.
Remove	Click to remove the selected file from the file transfer list.

The Installation page specifies the .sis file to install on the target device when using Application TRK. This is required when using the TRK debug agent with 9.x based SDK’s.

Table 1. Installation page —items

Other references

Installation page

Item	Explanation
Installation file -	Enter the complete path to the .sis or .pkg file to install on the target device or click Browse to use the standard file selection dialog.
Download directory	The directory on the target device to download the file into before installing it. The default directory value is C:\data\.
Install each launch even if installer file has not changed	Enable this option to force an update of the installed file even if no changes have been detected. This ensures a clean program install for each debug session.
Do not show installer UI on the phone	Use this option to specify if the installer UI on the target device is shown when installing the file. Disabling this option may require interaction with the installer UI on the target device, slowing down the install process. The default setting is on.
Install to drive	A list of common drives where files may be installed to. The default drive setting is C.
Partial upgrade sis/sisx path	Shows the path to the partial upgrade SIS file once it has been created.
Open SIS Builder settings...	Click to open the SIS Builder page of the Carbide Build Configurations properties panel where you can enable the partial upgrade feature for subsequent builds.

The Installation page specifies the .sis file to install on the target device when using Application TRK. This is required when using the TRK debug agent with 9.x based SDK’s.

Table 1. Installation page —items

Other references

ROM Image page

Item	Explanation
Installation file +	Enter the complete path to the .sis or .pkg file to install on the target device or click Browse to use the standard file selection dialog.
Download directory	The directory on the target device to download the file into before installing it. The default directory value is C:\data\.
Install each launch even if installer file has not changed	Enable this option to force an update of the installed file even if no changes have been detected. This ensures a clean program install for each debug session.
Do not show installer UI on the phone	Use this option to specify if the installer UI on the target device is shown when installing the file. Disabling this option may require interaction with the installer UI on the target device, slowing down the install process. The default setting is on.
Install to drive	A list of common drives where files may be installed to. The default drive setting is C.
Partial upgrade sis/sisx path	Shows the path to the partial upgrade SIS file once it has been created.
Open SIS Builder settings...	Click to open the SIS Builder page of the Carbide Build Configurations properties panel where you can enable the partial upgrade feature for subsequent builds.

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

Table 4. Launch configuration window—ROM Image tab items

Other references

ROM Image page

Item	Explanation
Parse Rom Log File	Check this option to parse the ROM log file.
Symbian Rom Log File	Enter or browse to the Rom log file that is generated when the Symbian OS image is built. This is necessary for debugging any Symbian OS module.
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.
Log unresolved modules	Check this option to log unresolved modules. If the actual binary in the log file doesn’t exist on the PC, then a warning message will be logged in a Rom Log console window.
Debug non-XIP executables	Check this option to target non-XIP executables. This allows the debugger to target a non-XIP module whenever it’s loaded.
Download Rom Image	Check this box to enable downloading.
Symbian Rom Image	Enter or browse to the Symbian OS image (.img file) that will be downloaded onto the target at the specified download address.
Download Address (hex)	Specify the address where the image is to be downloaded. This address is target-specific. The address should be in hexadecimal format with the 0x prefix.
Same as start address	Check this option to make the download address the same as the start address.
Ask for download at the start of each debug session	Select this option to prompt you to download the image at the start of the debug session.

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

Table 4. Launch configuration window—ROM Image tab items

Other references

ROM Log page

Item	Explanation
Parse Rom Log File	Check this option to parse the ROM log file.
Symbian Rom Log File	Enter or browse to the Rom log file that is generated when the Symbian OS image is built. This is necessary for debugging any Symbian OS module.
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.
Log unresolved modules	Check this option to log unresolved modules. If the actual binary in the log file doesn’t exist on the PC, then a warning message will be logged in a Rom Log console window.
Debug non-XIP executables	Check this option to target non-XIP executables. This allows the debugger to target a non-XIP module whenever it’s loaded.
Download Rom Image	Check this box to enable downloading.
Symbian Rom Image	Enter or browse to the Symbian OS image (.img file) that will be downloaded onto the target at the specified download address.
Download Address (hex)	Specify the address where the image is to be downloaded. This address is target-specific. The address should be in hexadecimal format with the 0x prefix.
Same as start address	Check this option to make the download address the same as the start address.
Ask for download at the start of each debug session	Select this option to prompt you to download the image at the start of the debug session.

Use the ROM Log page ina Sysem TRK launch configuration to specify where the ROM log file is stored and the Epoc32 directory.

Table 1. ROM Log page—items

Other references

ROM Log page

Item	Explanation
Parse Rom Log File	Activate the Parse ROM Log File option and specify the information that the debugger needs in order to show detailed stack information, set breakpoints, and show source level debugging information for ROM images.
Symbian Rom Log File	In the Symbian Rom Log File text field, browse to or enter the full path and name of the log file that corresponds to the ROM image on the target device. This log file is generated by default when the ROM image is built.
Symbian Epoc32 Directory	Specifies the epoc32 directory in which the ROM image and log files are stored. Since the log file may not contain full paths to the ROM components on the host PC, you need to enter this epoc32 directory. - NOTE Always include the epoc32 folder in this path.
Log unresolved modules	Activate the Log unresolved modules option to have the debugger output a list of components from the specified ROMBUILD log file that do not have debugger symbolic information. The list is displayed in the debugger console window at the beginning of the debug session. - NOTE You cannot perform source-level debugging on components that do not include symbolic information.

Use the ROM Log page ina Sysem TRK launch configuration to specify where the ROM log file is stored and the Epoc32 directory.

Table 1. ROM Log page—items

Other references

Creating Qt Projects

Item	Explanation
Parse Rom Log File	Activate the Parse ROM Log File option and specify the information that the debugger needs in order to show detailed stack information, set breakpoints, and show source level debugging information for ROM images.
Symbian Rom Log File	In the Symbian Rom Log File text field, browse to or enter the full path and name of the log file that corresponds to the ROM image on the target device. This log file is generated by default when the ROM image is built.
Symbian Epoc32 Directory	Specifies the epoc32 directory in which the ROM image and log files are stored. Since the log file may not contain full paths to the ROM components on the host PC, you need to enter this epoc32 directory. + NOTE Always include the epoc32 folder in this path.
Log unresolved modules	Activate the Log unresolved modules option to have the debugger output a list of components from the specified ROMBUILD log file that do not have debugger symbolic information. The list is displayed in the debugger console window at the beginning of the debug session. + NOTE You cannot perform source-level debugging on components that do not include symbolic information.

Use the Qt Project creation wizard to create new Qt-based projects based on Qt SDKs integrated into Symbian. The wizard walks you through the process of defining and creating a Qt project.

NOTE There must be at least one recognized SDK installed before you can create a project. See the SDK Preferences 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.

Other references

Creating Qt Projects

Use the Qt Project creation wizard to create new Qt-based projects based on Qt SDKs integrated into Symbian. The wizard walks you through the process of defining and creating a Qt project.

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.

Other references

Creating Qt Projects

Use the Qt Project creation wizard to create new Qt-based projects based on Qt SDKs integrated into Symbian. The wizard walks you through the process of defining and creating a Qt project.

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

Other references

Creating Qt Projects

Use the Qt Project creation wizard to create new Qt-based projects based on Qt SDKs integrated into Symbian. The wizard walks you through the process of defining and creating a Qt project.

Select type of Qt project

Other references

Creating Qt Projects

Use the Qt Project creation wizard to create new Qt-based projects based on Qt SDKs integrated into Symbian. The wizard walks you through the process of defining and creating a Qt project.

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.

Other references

Creating Qt Projects

Item	Explanation
Project name	Enter the name of the new project.
Use default location	Enable the Use default location option to save the project in the current workspace. Unselect this option to save your project to another location.
Location	Enter the path in the Location field or click Browse button to locate the directory. Qt projects require that the location name match the project name.

Use the Qt Project creation wizard to create new Qt-based projects based on Qt SDKs integrated into Symbian. The wizard walks you through the process of defining and creating a Qt project.

Enter project name and location

Other references

Creating Qt Projects

Item	Explanation
Project name	Enter the name of the new project.
Use default location	Enable the Use default location option to save the project in the current workspace. Unselect this option to save your project to another location.
Location	Enter the path in the Location field or click Browse button to locate the directory. Qt projects require that the location name match the project name.

Use the Qt Project creation wizard to create new Qt-based projects based on Qt SDKs integrated into Symbian. The wizard walks you through the process of defining and creating a Qt project.

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.

Other references

Creating Qt Projects

Item	Explanation
SDKs and Build Configurations	Shows the list of available SDKs and build configurations to associate with this project upon import.
Filter build configurations that don't contain Qt support	Enable to filter out of the SDKs and Build Configurations list any SDK or build configurations that does not contain Qt support. If disabled, all SDKs are shown and available for selection, whether they support Qt or not. The default setting is enabled. The criteria for Qt support is the presence of qtcore.lib in the build configuration output directory.

Use the Qt Project creation wizard to create new Qt-based projects based on Qt SDKs integrated into Symbian. The wizard walks you through the process of defining and creating a Qt project.

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.

Other references

Creating Qt Projects

Item	Explanation
SDKs and Build Configurations	Shows the list of available SDKs and build configurations to associate with this project upon import.
Filter build configurations that don't contain Qt support	Enable to filter out of the SDKs and Build Configurations list any SDK or build configurations that does not contain Qt support. If disabled, all SDKs are shown and available for selection, whether they support Qt or not. The default setting is enabled. The criteria for Qt support is the presence of qtcore.lib in the build configuration output directory.

Use the Qt Project creation wizard to create new Qt-based projects based on Qt SDKs integrated into Symbian. The wizard walks you through the process of defining and creating a Qt project.

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.

Other references

Creating Qt Projects

Use the Qt Project creation wizard to create new Qt-based projects based on Qt SDKs integrated into Symbian. The wizard walks you through the process of defining and creating a Qt project.

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.

Other references

Creating Qt Projects

Use the Qt Project creation wizard to create new Qt-based projects based on Qt SDKs integrated into Symbian. The wizard walks you through the process of defining and creating a Qt project.

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.

Other references

Creating Qt Projects

Use the Qt Project creation wizard to create new Qt-based projects based on Qt SDKs integrated into Symbian. The wizard walks you through the process of defining and creating a Qt project.

Set application UID

Other references

Importing Qt Projects

Use the Qt Project import wizard to import Qt-based projects based on Qt SDKs integrated into Symbian. The wizard walks you through the process of importing a Qt project, stored as a .pro file.

Launching the importer

Choose the File > Import... menu option to launch the Import wizard. The Import wizard dialog appears.

Other references

Importing Qt Projects

Use the Qt Project import wizard to import Qt-based projects based on Qt SDKs integrated into Symbian. The wizard walks you through the process of importing a Qt project, stored as a .pro file.

Launching the importer

Choose the File > Import... menu option to launch the Import wizard. The Import wizard dialog appears.

Other references

Importing Qt Projects

Use the Qt Project import wizard to import Qt-based projects based on Qt SDKs integrated into Symbian. The wizard walks you through the process of importing a Qt project, stored as a .pro file.

Select type of Qt project

Use the Select page in the New Qt Project Wizard to choose a Qt project template that will be used to create the new project based on the .pro file, then click Next.

Other references

Importing Qt Projects

Use the Qt Project import wizard to import Qt-based projects based on Qt SDKs integrated into Symbian. The wizard walks you through the process of importing a Qt project, stored as a .pro file.

Select type of Qt project

Use the Select page in the New Qt Project Wizard to choose a Qt project template that will be used to create the new project based on the .pro file, then click Next.

Other references

Importing Qt Projects

Use the Qt Project import wizard to import Qt-based projects based on Qt SDKs integrated into Symbian. The wizard walks you through the process of importing a Qt project, stored as a .pro file.

Select .pro file to import

Use the Qt Project page in the File Import Wizard to browse for the .pro file to import, then click Next.

Other references

Importing Qt Projects

Use the Qt Project import wizard to import Qt-based projects based on Qt SDKs integrated into Symbian. The wizard walks you through the process of importing a Qt project, stored as a .pro file.

Select .pro file to import

Use the Qt Project page in the File Import Wizard to browse for the .pro file to import, then click Next.

Other references

Importing Qt Projects

Use the Qt Project import wizard to import Qt-based projects based on Qt SDKs integrated into Symbian. The wizard walks you through the process of importing a Qt project, stored as a .pro file.

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.

Other references

Importing Qt Projects

Use the Qt Project import wizard to import Qt-based projects based on Qt SDKs integrated into Symbian. The wizard walks you through the process of importing a Qt project, stored as a .pro file.

Select .pro file to import

Other references

Qt Projects Overview

Carbide supports the creation, importing, development, and debugging of programs based upon Qt.

Locating Qt Help

Qt Projects Overview

Carbide supports the creation, importing, development, and debugging of programs based upon Qt.

Locating Qt Help

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:

The Qt perspective watches the .pro file associated with the project and will update the derived project bld.inf and .mmp files to match. You can control this behavior with the Run qmake when .pro file changes option in the Qt Properties panel.

Other references

Qt Perspective

Other references

Qt Preference Panel

The Qt preference panel provides global settings for Qt-based projects. Use it to add, edit, remove, and assign the default Qt version for projects.

Other references

Qt Preference Panel

The Qt preference panel provides global settings for Qt-based projects. Use it to add, edit, remove, and assign the default Qt version for projects.

Other references

Qt Project Properties

The Qt Properties panel provides project-level settings for Qt projects. Qmake will be invoked whenever the .pro file changes so that the bld.inf and .mmp file will always be in sync.

Other references

Qt Project Properties

The Qt Properties panel provides project-level settings for Qt projects. Qmake will be invoked whenever the .pro file changes so that the bld.inf and .mmp file will always be in sync.

Other references

Qt Development Setup

There are some prerequisites to using Qt projects within the Carbide environment. This includes downloading the correct SDKs, building qmake to use the SDKs, and finally, building the libraries for your target environments.

You should have the Qt SDK for Symbian that works with the S60 SDK in order to develop applications with Carbide. These steps include:

Once completed, you should be able to import or create new projects using the Qt SDK for Symbian.

Other references

Qt Development Setup

You should have the Qt SDK for Symbian that works with the S60 SDK in order to develop applications with Carbide. These steps include:

Once completed, you should be able to import or create new projects using the Qt SDK for Symbian.

Other references

MMP Editor

- The MMP Editor 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, C/C++ Projects, 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.

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.

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

+ The MMP Editor 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, C/C++ Projects, 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.

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.

Related references

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.

Related references

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.

Related references

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.

Related references

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.

Related references

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.

Related references

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.

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.

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.

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.

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.

References

Related tasks

Arguments page

The Arguments pane allows you to add arguments to the bldmake and abld processes for the project. Carbide passes the arguments entered here to the command line tools during the build process. By default, the majority of arguments are left blank.

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

Table 1 Environment variable items

Other references

Arguments page

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

Table 1 Environment variable items

Other references

Carbide Macro Settings

The Carbide Macro Settings properties page allows you to specify a file containing macros that CDT will use when parsing the source code.

Table 1 Carbide Macros Settings items

Related references

Carbide Macro Settings

The Carbide Macro Settings properties page allows you to specify a file containing macros that CDT will use when parsing the source code.

Table 1 Carbide Macros Settings items

Related references

Set PKG File for Build Configuration

The Set PKG File for Build Configuration dialog appears when an Application TRK 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 TRK 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.

Table 1 Items

Related tasks

Related reference

Set PKG File for Build Configuration

Table 1 Items

Related tasks

Related reference

Launch Configuration Filtering

Use the Launch Configuration preference panel to filter the launch configurations that appear in the configurations list in the Run or Debug dialog. This allows you to manage which configuration types are shown. For example, enable the Filter checked launch configuration types option and check the configuration types that you do not want to appear in the Run and Debug dialogs. As shown in Figure 1, all the configurations related to TRK have been enabled and won't appear in the configurations list.

Related references

Related tasks

Launch Configuration Filtering

Related references

Related tasks

Leavescan Preferences

Use the

-Leavescan Preferences page in the Preferences window to define the location where the leavescan.exe program exists on the file system. Symbian OS has a standard convention for functions that may Leave. Therefore, any function that Leaves, or calls a function that Leaves (other than in a TRAP harness), must have a name ending in "L". Leavescan verifies that your code satisfies this convention.

Table 1. Leavescan Preferences —items

Related Tasks

Leavescan Preferences

Use the

+Leavescan Preferences page in the Preferences window to define the location where the leavescan.exe program exists on the file system. Symbian OS has a standard convention for functions that may Leave. Therefore, any function that Leaves, or calls a function that Leaves (other than in a TRAP harness), must have a name ending in "L". Leavescan verifies that your code satisfies this convention.

Table 1. Leavescan Preferences —items

Related Tasks

Memory Rendering Options

You can configure the Memory Rendering pane to display data in the memory location in a variety of ways. The following options are visible on the context menu for the Memory Rendering pane.

Table 1. Memory Rendering context menu options

Related concepts

Related tasks

Related References

Memory Rendering Options

You can configure the Memory Rendering pane to display data in the memory location in a variety of ways. The following options are visible on the context menu for the Memory Rendering pane.

Table 1. Memory Rendering context menu options

Related concepts

Related tasks

Related References

Build All Configurations

Select a project in the Project Explorer, C/C++ Projects, or Symbian Project Navigator view and use the Project menu or right-click to display the context menu. Select Build All Configurations (CTRL+ALT+A) to build all target build configurations enabled for the current project.

Other references

Build All Configurations

Other references

Compile

Select a .c, .cpp, or .cia source file in the Project Explorer, C/C++ Projects, or Symbian Project Navigator view, right-click the file and choose 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.

Other references

Compile

Other references

Freeze Exports

Right click a project in the Project Explorer, or Symbian Project Navigator view, then choose 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.

Other references

Freeze Exports

Other references

Freeze Symbian Component

Right-click a Symbian OS MMP file in the Project Explorer, or Symbian Project Navigator view, then choose Freeze Symbian Component (CTRL+ALT+F). This command only freezes the selected MMP file and not the entire project.

Other references

Freeze Symbian Component

Other references

Toggle HW Breakpoint

Use the Toggle HW Breakpoint command in stop-mode debugging to set or unset a hardware breakpoint on a device that supports hardware breakpoints. The debugger treats hardware breakpoints exactly like software breakpoints for purposes of debugging. If the device does not support hardware breakpoints, toggling the command will do nothing.

Other references

Toggle HW Breakpoint

Other references

Symbian OS C++ Class

Click File > New > Symbian OS C++ Class to launch the Symbian OS C++ Class wizard.

Other references

Symbian OS C++ Class

Click File > New > Symbian OS C++ Class to launch the Symbian OS C++ Class wizard.

Other references

Symbian OS MMP File

Click File > New > Symbian OS MMP File to launch the Symbian OS MMP File wizard.

Other references

Symbian OS MMP File

Click File > New > Symbian OS MMP File to launch the Symbian OS MMP File wizard.

Other references

Symbian OS C++ Project

Other references

Symbian OS C++ Project

Other references

On-Device Setup

Use the On-Device Setup menu option to open the On-Device Setup dialog for the downloading and installation of Carbide software to a device.

Other references

On-Device Setup

Use the On-Device Setup menu option to open the On-Device Setup dialog for the downloading and installation of Carbide software to a device.

Other references

Preprocess

Right-click to select a .c, .cpp, or .cia source file in the Project Explorer or Symbian Project Navigator view, and choose 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.

Other references

Preprocess

Other references

Run CodeScanner

CodeScanner is a static source code analysis tool for Symbian OS™ programs written in C++. Use Run CodeScanner to examine your project code and report any issues.

Static analysis tools delve deep into code, exploring line by line for the sources of defects. CodeScanner is specifically for use with Symbian OS™ code. As well as identifying C++ coding convention deviations, CodeScanner identifies incorrect descriptor usage, cleanup stack errors, UID clashes, and other subtle problems that are hard to track down.

Other references

Run CodeScanner

CodeScanner is a static source code analysis tool for Symbian OS™ programs written in C++. Use Run CodeScanner to examine your project code and report any issues.

Other references

Run Leavescan

Symbian OS has a standard convention for functions that may Leave. Therefore, any function that Leaves, or calls a function that Leaves (other than in a TRAP harness), must have a name ending in L. Leavescan verifies that your code satisfies this convention. LeaveScan ignores calls in trapped functions, commented out code, ( // and /* and */). It also checks for calls to LD, LC and LX functions as well as normal L functions. It also checks for User::Leave(), ELeave, and User::LeaveIfError().

Other references

Run Leavescan

Other references

S60 UI Designer

Click File > New > S60 UI Design to launch the S60 UI Design wizard to add a new design to a project.

Other references

S60 UI Designer

Click File > New > S60 UI Design to launch the S60 UI Design wizard to add a new design to a project.

Other references

Changes to be performed by the updater are shown in the Text Compare area. You can use the yellow up and down arrows to move to the next or previous change to be performed. Click cancel if you do not want the change to be made. Click Finish to accept the changes.

Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
+ \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/reference/search/view_system_search.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/search/view_system_search.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/search/view_system_search.htm Thu May 20 13:57:30 2010 -0500 @@ -1,81 +1,81 @@ - - - - - - -System Search view - - - -

System Search view

The System Search view displays the results of a search based on the criteria used in the System Search page. This view (Figure 1) appears automatically when a directory search is performed. You can also open it using the Window > Show View > Other... option where it is found in the Show View dialog under the System Search category.

Figure 1. System Search view after a system search

The System Search view displays these columns:

Name — name of the matched file and the number of matches found within it
Type — the file type extension (.c, .c++, etc.)
Size — size of the file in bytes
Date Modified — last date the file was modified
Path — complete path to locate the file

These columns are sortable, simply click the column title to sort in ascending or descending order. Most reordering is based on strings and will be instant, but sorting by Size may take longer depending upon how many file matches have been made.

System Search view toolbar icons

The table below lists the icons displayed in the System Search view toolbar.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Icon	Item	Explanation
	Show Next Match	Opens the file in an editor if not already open and shows the first match in the file. If an editor is already open then show the next match in the file.
	Show Previous Match	Opens the file in an editor if not already open and shows the last match in the file. If an editor is already open then show the previous match in the file.
	Remove Selected Matches	Removes the currently selected files from the search list.
	Remove All Matches	Removes all files from the search list.
	Run the Current Search Again	Repeat the search using the same criteria.
	Cancel Current Search	Click to cancel the current search in progress.
	Show Previous Searches	Shows a menu with the 10 previous searches. Select a search to show its results in the view. Select History to manage the list of all previous searches or change the number of histories you can save. Choose Clear History to delete the stored searches.
	Pin the Search View	Toggles the pin state of the System Search view.
	Menu	Set filters for the view or open the System Search preference panel.

- - - - + + + + + + +System Search view + + + +

System Search view

Figure 1. System Search view after a system search

The System Search view displays these columns:

Name — name of the matched file and the number of matches found within it
Type — the file type extension (.c, .c++, etc.)
Size — size of the file in bytes
Date Modified — last date the file was modified
Path — complete path to locate the file

System Search view toolbar icons

The table below lists the icons displayed in the System Search view toolbar.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Icon	Item	Explanation
	Show Next Match	Opens the file in an editor if not already open and shows the first match in the file. If an editor is already open then show the next match in the file.
	Show Previous Match	Opens the file in an editor if not already open and shows the last match in the file. If an editor is already open then show the previous match in the file.
	Remove Selected Matches	Removes the currently selected files from the search list.
	Remove All Matches	Removes all files from the search list.
	Run the Current Search Again	Repeat the search using the same criteria.
	Cancel Current Search	Click to cancel the current search in progress.
	Show Previous Searches	Shows a menu with the 10 previous searches. Select a search to show its results in the view. Select History to manage the list of all previous searches or change the number of histories you can save. Choose Clear History to delete the stored searches.
	Pin the Search View	Toggles the pin state of the System Search view.
	Menu	Set filters for the view or open the System Search preference panel.

+ + + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/reference/search/wnd_system_search.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/search/wnd_system_search.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/search/wnd_system_search.htm Thu May 20 13:57:30 2010 -0500 @@ -1,60 +1,60 @@ - - - - - - -System Search - - - -

System Search

Use the System Search page of the Search window to perform a textual search of files by directory, on your hard drive. This enables you to search for files inside directories located outside of the project workspace. In addition, there are additional search choices including:

File Search - does a textual search of files in the workspace. This search comes from the Eclipse platform.
C/C++ Search - searches via the C++ index, not a simple textual search. This search comes from CDT.

Choose Search > System Search to open the Search window and perform a directory defined textual search. The results are then shown in the System Search view. Some of the search behaviors and apperance are controlled by settings in the System Search preference panel.

Figure 1. System Search page in the Search window

Table 1. System Search page options

- - - - - - - - - - - - - - - - - - - - - -

Item	Explanation
Search string	Enter text into the Search string text box to search for specific strings within files. Leave empty if you are only looking for files by name and not content. You can control how the text is interpreted using these options: - - Case sensitive — enable to make the search case sensitive - Regular expression — enable to use regular expression in the Search string text box -
File name patterns	Enter the file types to search for seperated by commas, or click Choose to select file types in the preset list in the Select Types dialog.
Folder	Enter text into the Folder text box or click Browse to search to search a specific folder. You can control how the folder search is conducted using these options: - - Search subfolders — enable to recusively search subfolders in the selected folder for matching files - Search hidden files — enable to also search the folder/subfolders hidden files -
Customize...	Specify which search tabs should appear in the Search window. - NOTE Use the Window > Customize Perspective > Commands page to hide specific commands you never use.

Other references

Search view
Search actions

- - - - + + + + + + +System Search + + + +

System Search

File Search - does a textual search of files in the workspace. This search comes from the Eclipse platform.
C/C++ Search - searches via the C++ index, not a simple textual search. This search comes from CDT.

Figure 1. System Search page in the Search window

Table 1. System Search page options

+ + + + + + + + + + + + + + + + + + + + + +

Item	Explanation
Search string	Enter text into the Search string text box to search for specific strings within files. Leave empty if you are only looking for files by name and not content. You can control how the text is interpreted using these options: + + Case sensitive — enable to make the search case sensitive + Regular expression — enable to use regular expression in the Search string text box +
File name patterns	Enter the file types to search for seperated by commas, or click Choose to select file types in the preset list in the Select Types dialog.
Folder	Enter text into the Folder text box or click Browse to search to search a specific folder. You can control how the folder search is conducted using these options: + + Search subfolders — enable to recusively search subfolders in the selected folder for matching files + Search hidden files — enable to also search the folder/subfolders hidden files +
Customize...	Specify which search tabs should appear in the Search window. + NOTE Use the Window > Customize Perspective > Commands page to hide specific commands you never use.

Other references

Search view
Search actions

+ + + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/reference/search/wnd_system_search_prefs.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/search/wnd_system_search_prefs.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/search/wnd_system_search_prefs.htm Thu May 20 13:57:30 2010 -0500 @@ -1,49 +1,49 @@ - - - - - - -System Search preferences - - - -

System Search preferences

Use the System Search preference panel to control System Search behaviors. Choose Window > Preferences > System Search to open the System Search preference panel.

Figure 1. System Search preference panel

Table 1. System Search page options

- - - - - - - - - - - - - - - - - - - - - - - - - -

Item	Explanation
Reuse editors to show matches	Enable this option to keep using the same editor for search results to reduce the number of open editors.
Ignore potential matches	Enable this option if you only want to see exact matches.
Emphasize potential matches	Enable this option to highlight potential matches in the System Search view. If the search engine isn't 100% sure about the match then it is considered a potential match.
Foreground color for potential matches	Enable this option to select the foreground color for potential matches.
Default perspective for the Search view	This option allows you to define which perspective should be brought to the front when there are new search results.

Other references

System Search page

- - - - + + + + + + +System Search preferences + + + +

System Search preferences

Use the System Search preference panel to control System Search behaviors. Choose Window > Preferences > System Search to open the System Search preference panel.

Figure 1. System Search preference panel

Table 1. System Search page options

+ + + + + + + + + + + + + + + + + + + + + + + + + +

Item	Explanation
Reuse editors to show matches	Enable this option to keep using the same editor for search results to reduce the number of open editors.
Ignore potential matches	Enable this option if you only want to see exact matches.
Emphasize potential matches	Enable this option to highlight potential matches in the System Search view. If the search engine isn't 100% sure about the match then it is considered a potential match.
Foreground color for potential matches	Enable this option to select the foreground color for potential matches.
Default perspective for the Search view	This option allows you to define which perspective should be brought to the front when there are new search results.

Other references

System Search page

+ + + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/reference/trk/exporting_remote_conns.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/exporting_remote_conns.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/exporting_remote_conns.htm Thu May 20 13:57:30 2010 -0500 @@ -1,37 +1,37 @@ - - - - - - -Exporting Remote Connections - - - - -

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

On-Device Setup
Install latest TRK

- - - + + + + + + +Exporting Remote Connections + + + + +

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

On-Device Setup
Install latest TRK

+ + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/reference/trk/importing_remote_conns.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/importing_remote_conns.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/importing_remote_conns.htm Thu May 20 13:57:30 2010 -0500 @@ -1,37 +1,37 @@ - - - - - - -Importing Remote Connections - - - - -

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

On-Device Setup
Install latest TRK

- - - + + + + + + +Importing Remote Connections + + + + +

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

On-Device Setup
Install latest TRK

+ + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/reference/trk/panel_filter.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/panel_filter.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/panel_filter.htm Thu May 20 13:57:30 2010 -0500 @@ -52,7 +52,7 @@

Setting a Build Configuration

- + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/reference/trk/panel_trk_overview.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/panel_trk_overview.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/panel_trk_overview.htm Thu May 20 13:57:30 2010 -0500 @@ -20,7 +20,7 @@

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

- + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_conn_settings_pane.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_conn_settings_pane.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_conn_settings_pane.htm Thu May 20 13:57:30 2010 -0500 @@ -1,47 +1,47 @@ - - - - - - -Install Remote Agents pane - - - - -

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 TRK software compiled for that SDK, which in the image above is Application TRK 2.8.7.

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

Save

Click Save to store a local copy of the currently selected TRK 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 TRK selected in the Install latest TRK 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

- - - - + + + + + + +Install Remote Agents pane + + + + +

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

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

Save

Click Save to store a local copy of the currently selected TRK 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 TRK selected in the Install latest TRK list. A progress bar is shown if the install operation requires more than a few seconds to complete.

Related references

+ + + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_conn_wiz_add.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_conn_wiz_add.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_conn_wiz_add.htm Thu May 20 13:57:30 2010 -0500 @@ -116,7 +116,7 @@

On-Device Setup

Install latest TRK

- + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/reference/view_breakpoints.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_breakpoints.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_breakpoints.htm Thu May 20 13:57:30 2010 -0500 @@ -1,80 +1,80 @@ - - - - - - -Breakpoints View - - - -

Breakpoints View

Use the Breakpoints view to set, examine, enable, disable, and remove breakpoints and watchpoints in one or more build configurations. Table 1 explains items in the view.

Figure 1 - Breakpoints view

Table 1. Breakpoints view—items

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Item	Icon	Explanation
Remove Selected Breakpoint		Removes the selected breakpoint from the breakpoints list.
Remove All Breakpoints		Removes all breakpoints from the breakpoints list.
Show Breakpoints Supported by Selected Target		Limits the breakpoints shown to only those supported in the current target.
Go to File for Breakpoint		Displays the breakpoint in an editor view, opening the source file if required.
Skip All Breakpoints		Toggles the debugger to skip all breakpoints regardless of their current enabled or disabled state, or hit all breakpoints.
Expand All		Expand all matches in the hierarchical view.
Collapse All		Collapse all matches in the hierarchical view.
Link with Debug View		When enabled, the breakpoint shown in the editor view is also highlighted in the Breakpoints view. When disabled, the breakpoint selected in the Breakpoints view does not change.
Menu		Click to display additional Breakpoint view options for paths and working sets.

Other references

- - - - + + + + + + +Breakpoints View + + + +

Breakpoints View

Use the Breakpoints view to set, examine, enable, disable, and remove breakpoints and watchpoints in one or more build configurations. Table 1 explains items in the view.

Figure 1 - Breakpoints view

Table 1. Breakpoints view—items

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Item	Icon	Explanation
Remove Selected Breakpoint		Removes the selected breakpoint from the breakpoints list.
Remove All Breakpoints		Removes all breakpoints from the breakpoints list.
Show Breakpoints Supported by Selected Target		Limits the breakpoints shown to only those supported in the current target.
Go to File for Breakpoint		Displays the breakpoint in an editor view, opening the source file if required.
Skip All Breakpoints		Toggles the debugger to skip all breakpoints regardless of their current enabled or disabled state, or hit all breakpoints.
Expand All		Expand all matches in the hierarchical view.
Collapse All		Collapse all matches in the hierarchical view.
Link with Debug View		When enabled, the breakpoint shown in the editor view is also highlighted in the Breakpoints view. When disabled, the breakpoint selected in the Breakpoints view does not change.
Menu		Click to display additional Breakpoint view options for paths and working sets.

Other references

+ + + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/reference/view_carbide_news.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_carbide_news.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_carbide_news.htm Thu May 20 13:57:30 2010 -0500 @@ -54,7 +54,7 @@

Carbide.c++ News preference panel

Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
+ \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/reference/view_cpp_projects.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_cpp_projects.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_cpp_projects.htm Thu May 20 13:57:30 2010 -0500 @@ -1,39 +1,39 @@ - - - - - - -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 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.

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

- - - + + + + + + +Project Explorer View + + + +

Project Explorer View

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

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

+ + + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/reference/view_executables.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_executables.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_executables.htm Thu May 20 13:57:30 2010 -0500 @@ -97,7 +97,7 @@

Debug perspective

- + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/reference/view_log.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_log.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_log.htm Thu May 20 13:57:30 2010 -0500 @@ -66,7 +66,7 @@

- + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/reference/view_module_wnd.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_module_wnd.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_module_wnd.htm Thu May 20 13:57:30 2010 -0500 @@ -18,7 +18,7 @@

Debug view

- + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/reference/view_reg_details.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_reg_details.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_reg_details.htm Thu May 20 13:57:30 2010 -0500 @@ -1,138 +1,138 @@ - - - - - - -Registers Details Window - - - -

Registers Details Window

The Register Details window (Windows OS) lets you view detailed information about individual bits of registers from 2 bits to 32 bits in size. This window shows information for both system registers and memory-mapped registers. To open the Register Details window, click View > Register Details or Window > Register Details Window.

The Register Details window has fields that describe the register, its bitfields, and the values of those bitfields. XML files in the Registers folder of your Carbide installation provide the information that appears in the window. The Registers folder is inside the Support folder. The Support folder is inside the Plugins folder of your Carbide installation.

Figure 1 shows the Register Details window. Table 1 explains items in the window.

Figure 1 Register Details window
-

Table 1. Register Details window—items

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Item	Icon	Explanation
Description File text box		Enter the name or full path to the XML file for the register you want to view, or click the Browse button to open a dialog box that you can use to specify the file.
Register Name		Shows the name of the register depicted in the window.
Address text box		Enter the starting address of the register values that you want to see in the Register Display. - An error message appears if you enter an invalid starting address.
Format list box		Specify the data format for bit values in the Register Display: - - Binary - Character - Decimal - Unsigned Decimal - Hexadeccimal - Default—have the IDE determine the best format -
Register Display		Shows a depiction of the register that you specify in the Description File text box, including individual register bits and their values.
Bitfield Name list box		Specify a bitfield to highlight in the Register Display. The Description portion of the window reflects available information for the bitfield. - Select None to have the Description portion of the window reflect information for the entire register and not a bitfield in that register.
Bit Value text box		Shows the current value of the bits in the Bitfield Name list box, according to the format that you specify in the Format list box. - Click the spin buttons to increment or decrement the current value, or enter a new value in the text box. - Changing the value changes only the Register Display. You must click the Write button to write the new value to the register itself.
Bit Value Modifier list box		Specify a new value for the selected bitfield, or view a brief explanation of specific bitfield values. - Changing the value changes only the Register Display. You must click the Write button to write the new value to the register.
Description		Shows a description of the register or a selected bitfield in the register. - Use the Description File text box to specify the register. - Use the Text View list box to view specific register information, such as register descriptions, bitfield descriptions, and register details.
Revert button		Click to change a modified value in the Register Display to its original value. - If you clicked the Write button to write a new value to the register, you cannot revert that value.
Read button		Click to have the Register Display reflect current bit values from the register itself.
Write button		Click to write the bit values in the Register Display to the register. - After you write new values to the register, you cannot revert them.
Reset Value button		Click to restore the default value for the selected bitfield. - The IDE disables this button if the selected bitfield does not have a default value.
Text View list box		Use to specify information that appears in the Description portion of the window.

Description File

Enter in this text box the name of the register that you want to see in the Register Display of the Register Details window. Alternatively, enter the full path to the register description file on your computer, or click the Browse button to open a dialog box that lets you specify the register description file. The text box is not case sensitive.

After you enter a name or path, the debugger searches for a matching register description file in the Registers folder of your Carbide installation and the project access paths. If the debugger finds a matching file, the Register Display updates the information in the Register Details window. If the debugger does not find a matching name, an error message appears.

For example, to view the contents of the Opcode register, you can:

type Opcode in the Description File text box and press Enter or Return, or
type the full path to the opcode.xml file in the Registers folder and press Enter or Return.

The debugger matches your entry with the opcode.xml file in the Registers folder. The Register Display in the Register Details window updates its information to show Opcode register details.

The debugger also updates the Register Display to show the current values in the register. If the debugger fails to update the display, an error message appears.

Register Display

This display shows the current contents of 32 bits of register data, starting at the address that you specify in the Address text box. The data appears according to the format that you specify in the Format list box.

The Register Display groups the 32 bits of data into register bitfields. Clicking one of the bits selects its associated bitfield. Additional information about the bitfield, such as its name and permissions, appears in the Description portion of the Register Details window.

Text View

Use this list box to change the information that appears in the Description portion of the Register Details window:

Auto—select to have the IDE determine which information to display in the window
Register Description—select to show information about the entire register, such as the name of the register itself and the meaning of its contents
Bitfield Description—select to show information about the selected bitfield in the Register Display, such as the name of the bitfield and its access permissions
Register Details—select to show in-depth information about the current register, such as its name, its bit values, and bit-value explanations
-

- - - + + + + + + +Registers Details Window + + + +

Registers Details Window

Figure 1 shows the Register Details window. Table 1 explains items in the window.

Figure 1 Register Details window
+

Table 1. Register Details window—items

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Item	Icon	Explanation
Description File text box		Enter the name or full path to the XML file for the register you want to view, or click the Browse button to open a dialog box that you can use to specify the file.
Register Name		Shows the name of the register depicted in the window.
Address text box		Enter the starting address of the register values that you want to see in the Register Display. + An error message appears if you enter an invalid starting address.
Format list box		Specify the data format for bit values in the Register Display: + + Binary + Character + Decimal + Unsigned Decimal + Hexadeccimal + Default—have the IDE determine the best format +
Register Display		Shows a depiction of the register that you specify in the Description File text box, including individual register bits and their values.
Bitfield Name list box		Specify a bitfield to highlight in the Register Display. The Description portion of the window reflects available information for the bitfield. + Select None to have the Description portion of the window reflect information for the entire register and not a bitfield in that register.
Bit Value text box		Shows the current value of the bits in the Bitfield Name list box, according to the format that you specify in the Format list box. + Click the spin buttons to increment or decrement the current value, or enter a new value in the text box. + Changing the value changes only the Register Display. You must click the Write button to write the new value to the register itself.
Bit Value Modifier list box		Specify a new value for the selected bitfield, or view a brief explanation of specific bitfield values. + Changing the value changes only the Register Display. You must click the Write button to write the new value to the register.
Description		Shows a description of the register or a selected bitfield in the register. + Use the Description File text box to specify the register. + Use the Text View list box to view specific register information, such as register descriptions, bitfield descriptions, and register details.
Revert button		Click to change a modified value in the Register Display to its original value. + If you clicked the Write button to write a new value to the register, you cannot revert that value.
Read button		Click to have the Register Display reflect current bit values from the register itself.
Write button		Click to write the bit values in the Register Display to the register. + After you write new values to the register, you cannot revert them.
Reset Value button		Click to restore the default value for the selected bitfield. + The IDE disables this button if the selected bitfield does not have a default value.
Text View list box		Use to specify information that appears in the Description portion of the window.

Description File

For example, to view the contents of the Opcode register, you can:

type Opcode in the Description File text box and press Enter or Return, or
type the full path to the opcode.xml file in the Registers folder and press Enter or Return.

The debugger matches your entry with the opcode.xml file in the Registers folder. The Register Display in the Register Details window updates its information to show Opcode register details.

The debugger also updates the Register Display to show the current values in the register. If the debugger fails to update the display, an error message appears.

Register Display

Text View

Use this list box to change the information that appears in the Description portion of the Register Details window:

Auto—select to have the IDE determine which information to display in the window
Register Description—select to show information about the entire register, such as the name of the register itself and the meaning of its contents
Bitfield Description—select to show information about the selected bitfield in the Register Display, such as the name of the bitfield and its access permissions
Register Details—select to show in-depth information about the current register, such as its name, its bit values, and bit-value explanations
+

+ + + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/reference/view_sym_proj_nav.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_sym_proj_nav.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_sym_proj_nav.htm Thu May 20 13:57:30 2010 -0500 @@ -46,7 +46,7 @@

- + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/reference/view_variables.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_variables.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/view_variables.htm Thu May 20 13:57:30 2010 -0500 @@ -1,86 +1,86 @@ - - - - - - -Variables View - - - -

Variables View

The Variables view allows manipulation of the variables or variable hierarchy used in source code. For example, you can change the variable format, change a variables value, add watchpoints, and add global variables.

Figure 1 shows the Variables view with Show Type Names option enabled.

Figure 1 - Variables view showing type names

Table 1. Variables view—items

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Item	Icons	Explanation
Show Type Names		Toggles the display of type names in the Variables view.
Show Logical Structure		Not available in C/C++ yet.
Collapse All		Collapses all expanded variables into the top level.
Add Global Variables		Click to open a window where you can select one or more global variables to display in the Variables view. Global variables appear at the top of the variables list.
Remove Selected Global Variables		Click to remove all currently selected global variables from the variables list.
Remove All Global Variables		Click to remove all global variables from the variables list.
Menu		Enables you to modifiy the Layout to change the view orientation between: horizontal, vertical, or variables pane only. - In addition, use Show All Variables to toggle between showing only those variables that are in scope and live or show all local variables, even if redundant. With this option on you will see all of the variables including the multiple defined variables like “i” for your loops and ones that may no longer have accurate values.

To open the Variables view

Click Window > Show View > Variables

The Variables view appears.

Related concepts

Related tasks

Related References

Expressions View
Variables View

- - - - + + + + + + +Variables View + + + +

Variables View

Figure 1 shows the Variables view with Show Type Names option enabled.

Figure 1 - Variables view showing type names

Table 1. Variables view—items

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Item	Icons	Explanation
Show Type Names		Toggles the display of type names in the Variables view.
Show Logical Structure		Not available in C/C++ yet.
Collapse All		Collapses all expanded variables into the top level.
Add Global Variables		Click to open a window where you can select one or more global variables to display in the Variables view. Global variables appear at the top of the variables list.
Remove Selected Global Variables		Click to remove all currently selected global variables from the variables list.
Remove All Global Variables		Click to remove all global variables from the variables list.
Menu		Enables you to modifiy the Layout to change the view orientation between: horizontal, vertical, or variables pane only. + In addition, use Show All Variables to toggle between showing only those variables that are in scope and live or show all local variables, even if redundant. With this option on you will see all of the variables including the multiple defined variables like “i” for your loops and ones that may no longer have accurate values.

To open the Variables view

Click Window > Show View > Variables

The Variables view appears.

Related concepts

Related tasks

Related References

Expressions View
Variables View

+ + + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/reference/views.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/views.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/views.htm Thu May 20 13:57:30 2010 -0500 @@ -1,20 +1,20 @@ - - - - - - -Working with Memory - - - -

Working with Memory

This section explains how to work with variables in a Carbide.c++ debugging session. The following views show various types of information about variables:

Memory view —shows the memory that your project manipulates as it executes
Registers view—shows the register contents of a processor

- - - - + + + + + + +Working with Memory + + + +

Working with Memory

This section explains how to work with variables in a Carbide.c++ debugging session. The following views show various types of information about variables:

Memory view —shows the memory that your project manipulates as it executes
Registers view—shows the register contents of a processor

+ + + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_carbide_pref_x86.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_carbide_pref_x86.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_carbide_pref_x86.htm Thu May 20 13:57:30 2010 -0500 @@ -1,25 +1,25 @@ - - - - - - -Unsetting Built-in Environment - - - -

Unsetting Built-in Environment

The Carbide.c++ > Build page in the Preferences window provides an option to use the local x86 build tools for each emulator build. A directory named x86Build at the root of the product installation contains the build tools, libraries, and env_update.exe file.

Uncheck the "Use built-in Nokia x86 environment variables for WINSCW builds" option if you do not want to use the built-in compiler.

Figure 1 shows the Build preferences window.

Figure 1 -Build preferences window showing Emulator Build Options

Related references

- - - - + + + + + + +Unsetting Built-in Environment + + + +

Unsetting Built-in Environment

Uncheck the "Use built-in Nokia x86 environment variables for WINSCW builds" option if you do not want to use the built-in compiler.

Figure 1 shows the Build preferences window.

Figure 1 -Build preferences window showing Emulator Build Options

Related references

+ + + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_debug_configuration.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_debug_configuration.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_debug_configuration.htm Thu May 20 13:57:30 2010 -0500 @@ -61,6 +61,6 @@

Launch Configuration Overview

Configuration Pages

- + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_debugger_prefs.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_debugger_prefs.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_debugger_prefs.htm Thu May 20 13:57:30 2010 -0500 @@ -1,60 +1,60 @@ - - - - - - -Carbide.c++ Debugger Preferences - - - - -

Carbide.c++ Debugger preferences

The Debug > -Carbide.c++ Debugger preference panel provides global debugger settings for the Carbide.c++ tools.

Figure 1 - Carbide.c++ Debugger preference panel

Table 1. Carbide.c++ Debugger panel—items

- - - - - - - - - - - - - - - - - - - - - - - - - -

Item	Explanation
Attempt to show the dynamic runtime type of objects	Enable this option to have the debugger deduce the actual type of an object at runtime and display it in the Variables view (applies to x86 only). By default, the debugger does not attempt to determine the type of an object at runtime and will simply show its declared type. Enabling this option can slow the start of a debug session.
Do not step into runtime support code	Select this option to avoid stepping into runtime support code. Runtime support code is generated by the compiler to support C++ features like new and delete. When enabled the debugger attempts to identify and skip this glue code and step directly into your code. If this option is disabled the debugger steps into this language support code. For example if you are debugging this line of code and step in: - MyClass* var = new MyClass(); - With this option selected the debugger will skip the code that implements the operator new and step into the constructor for MyClass. If this option is disabled the debugger would step into the code in new that allocates the object.
Default size for unbounded arrays	Enter the number of array objects to display by default.
Find source files outside the SDK	Enable to have the debugger automatically search for source files outside of the SDK. If disabled, the debugger will only look within the SDK epocroot directory.
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 TRK or stop-mode debugging.

To access the Carbide.c++ Debugger Preferences

Select the Window > Preferences menu item
-
The Preferences window (Figure 1) appears.
Expand the C/C++ and Debug sections
Select the Carbide.c++ Debugger item
-
The Carbide.c++ Debugger preference panel appears.
-

- - - + + + + + + +Carbide.c++ Debugger Preferences + + + + +

Carbide.c++ Debugger preferences

The Debug > +Carbide.c++ Debugger preference panel provides global debugger settings for the Carbide.c++ tools.

Figure 1 - Carbide.c++ Debugger preference panel

Table 1. Carbide.c++ Debugger panel—items

+ + + + + + + + + + + + + + + + + + + + + + + + + +

Item	Explanation
Attempt to show the dynamic runtime type of objects	Enable this option to have the debugger deduce the actual type of an object at runtime and display it in the Variables view (applies to x86 only). By default, the debugger does not attempt to determine the type of an object at runtime and will simply show its declared type. Enabling this option can slow the start of a debug session.
Do not step into runtime support code	Select this option to avoid stepping into runtime support code. Runtime support code is generated by the compiler to support C++ features like new and delete. When enabled the debugger attempts to identify and skip this glue code and step directly into your code. If this option is disabled the debugger steps into this language support code. For example if you are debugging this line of code and step in: + MyClass* var = new MyClass(); + With this option selected the debugger will skip the code that implements the operator new and step into the constructor for MyClass. If this option is disabled the debugger would step into the code in new that allocates the object.
Default size for unbounded arrays	Enter the number of array objects to display by default.
Find source files outside the SDK	Enable to have the debugger automatically search for source files outside of the SDK. If disabled, the debugger will only look within the SDK epocroot directory.
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 TRK or stop-mode debugging.

To access the Carbide.c++ Debugger Preferences

Select the Window > Preferences menu item
+
The Preferences window (Figure 1) appears.
Expand the C/C++ and Debug sections
Select the Carbide.c++ Debugger item
+
The Carbide.c++ Debugger preference panel appears.
+

+ + + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_diagnostic_logs_pref.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_diagnostic_logs_pref.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_diagnostic_logs_pref.htm Thu May 20 13:57:30 2010 -0500 @@ -34,7 +34,7 @@

Carbide Project Settings

- + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_import_bitmaps.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_import_bitmaps.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_import_bitmaps.htm Thu May 20 13:57:30 2010 -0500 @@ -1,58 +1,58 @@ - - - - - - -Import Bitmaps - - - -

Import Bitmaps

Use the Import window to import bitmap resources from the file system.

Figure 1 - Import Bitmaps window

Table 1. Import Bitmaps window—items

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Item	Explanation
From directory	Path to folder containing bitmaps files to import. Click Browse to choose a different location.
Filter Types...	Click to open a dialog and select filter options.
Select All	Click to select all files.
Deselect All	Click to deselect all files.
Into folder	Specify the location within the project to store the imported files.
Overwrite existing resources without warning	Enable to overwrite existing resources using the same names with the new ones being imported.
Create complete folder structure	Create a duplicate of the system folder structure at the project location set in the Into folder text box.
Create selected folders only	Create folder structures at the project location set in the Into folder text box only for the selected folders.

- - - + + + + + + +Import Bitmaps + + + +

Import Bitmaps

Use the Import window to import bitmap resources from the file system.

Figure 1 - Import Bitmaps window

Table 1. Import Bitmaps window—items

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Item	Explanation
From directory	Path to folder containing bitmaps files to import. Click Browse to choose a different location.
Filter Types...	Click to open a dialog and select filter options.
Select All	Click to select all files.
Deselect All	Click to deselect all files.
Into folder	Specify the location within the project to store the imported files.
Overwrite existing resources without warning	Enable to overwrite existing resources using the same names with the new ones being imported.
Create complete folder structure	Create a duplicate of the system folder structure at the project location set in the Into folder text box.
Create selected folders only	Create folder structures at the project location set in the Into folder text box only for the selected folders.

+ + + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_pref_code_style.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_pref_code_style.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_pref_code_style.htm Thu May 20 13:57:30 2010 -0500 @@ -1,27 +1,27 @@ - -Code Styles preferences - - - -

Code Styles preferences

- - -

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 preset code styles like GNU, while Carbide supplies these profiles:

Symbian OS — settings are based on the Symbian OS C++ coding standards PDF
S60 — settings are based on the S60 Platform: C++ Coding Conventions

Setting a code style sets it for the entire workspace. When a new file is created the currently selected code style rules are applied as you edit the file. You can apply a set of rules to a previously created source file by opening it in an editor view, then right-clicking and choosing Source > Format (CTRL+SHIFT+F).

Figure 1 - Code Style preference panel

Related references

- - - - + +Code Styles preferences + + + +

Code Styles preferences

+ + +

Symbian OS — settings are based on the Symbian OS C++ coding standards PDF
S60 — settings are based on the S60 Platform: C++ Coding Conventions

Figure 1 - Code Style preference panel

Related references

+ + + + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_preprocess_prefs.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_preprocess_prefs.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/wnd_preprocess_prefs.htm Thu May 20 13:57:30 2010 -0500 @@ -1,46 +1,46 @@ - - - - - - -Preprocess preferences - - - - -

Preprocess preferences

The Carbide.c++ > Preprocess page in the Preferences window provides global settings for the Carbide preprocessor.

Figure 1 - Preprocess preferences page

Table 1 Preprocess p references —items

- - - - - - - - - - - - - - - - - -

Item	Explanation
Send output to the build console	Enable to direct preprocessor output to a console view. -
Send output to the editor	Enable to direct preprocessor output to an editor. -
CPP arguments	Enter the preprocessor arguments used by the preprocessor. -

Other references

Preprocessing Files

- - - - + + + + + + +Preprocess preferences + + + + +

Preprocess preferences

The Carbide.c++ > Preprocess page in the Preferences window provides global settings for the Carbide preprocessor.

Figure 1 - Preprocess preferences page

Table 1 Preprocess p references —items

+ + + + + + + + + + + + + + + + + +

Item	Explanation
Send output to the build console	Enable to direct preprocessor output to a console view. +
Send output to the editor	Enable to direct preprocessor output to an editor. +
CPP arguments	Enter the preprocessor arguments used by the preprocessor. +

Other references

Preprocessing Files

+ + + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/ClassesToc.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/ClassesToc.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/ClassesToc.htm Thu May 20 13:57:30 2010 -0500 @@ -1,17 +1,17 @@ - -Classes - - - -

Classes

The topics include:

- - - - + +Classes + + + +

Classes

The topics include:

+ + + + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/ExportingtoMMP_BLDinf.html --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/ExportingtoMMP_BLDinf.html Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/ExportingtoMMP_BLDinf.html Thu May 20 13:57:30 2010 -0500 @@ -1,271 +1,271 @@ - - -Exporting project(s) to MMP/Bld.inf files in Tasks - - - - -

Exporting project(s) to MMP/Bld.inf files

- The command-line Symbian OS toolchain requires a component description - file (Bld.Inf) and one or more project definition files - (.mmp) to build a project. The export command allows you to create - these files for your projects.

- To export project(s) to a Bld.Inf and/or MMP - file:

- Click File > Export... to get a list of the - available export wizards: -
- OR
-
- Click Export from the pop-up menus of the - C/C++ Projects and Navigator views to get a - list of the available export wizards:
-
- -
-
-
Select Symbian MMP/Bld.Inf and click - Next to go to the Symbian Projects page: -
-
- -
-
-
- Select the project(s) you intend to export from the list of - Symbian Projects.
- Click Next to go to the SDKs and Build Configurations Selection page: -
- -
-
-
- Select at least one build configuration for each project in the - left-hand pane from the list of available SDKs and build configurations in the - right-hand pane. By default, all the build configurations chosen during the - last export are selected. If a project is being exported for the first time, no - build configurations are selected. -
- The build configurations chosen for a project are distinguished using - guard macros in the MMP file. The guard macros are placed around - the MMP file statements containing resources or build setting, - only valid for a subset of the chosen build configurations.
-
- There are cases where guard macros may not be able to distinguish - between two build configurations. The export wizard shows a conflict when two - such ambiguous build configurations are selected by the user.
-
- The combination of build configurations which results in a conflict - are as follows:
- -
- -
  - Any two build configurations that differ only in the build - variant (UDEB/UREL). For example, "UIQ 3.0 Phone (GCCE) Debug" and "UIQ 3.0 - Phone (GCCE) Release" configurations will result in a conflict, as they differ - only in the build variant.
  -
- -
  - Any two build configurations, of which one is user-defined based - on the other using the Manage option in the C/C++ - Build properties view of the project.
  -
  - For more information on managing build configurations, - refer to the CDT user guide.
  -
- -
- The wizard will change the build settings in the MMP - file based on the chosen build configuration. If more than one build - configuration which require different build settings are chosen, guard macros - are used to determine the build settings. For example, if you want to change - the SECUREID option for all the EKA2 build - configurations, the wizard will append the following lines into the - MMP file:
- #if def EKA2 SECUREID 0x00301 #endif - - Where EKA2 is the guard macro for all the build - configurations designed for the EKA2 kernel. The above MMP file - statements check whether the EKA2 guard macro is defined, and if - it is, change the SECUREID option accordingly. -

 
-	     
-		    Click Next to go to the MMP File and Bld.inf
-		      File page: 
-	      		    
-	        
-	       
-	      
-	        
-	           Type the MMP file location in the MMP
-		          File field, or click Browse to select the
-	           MMP file for each project listed above. 
-	           
-	             By default, the MMP file is exported to one of the
-		          following locations in the order listed below:	           
-	           
-	              The location where the project was exported the last time. 
-	              The group folder of the exported project, if it exists. 
-	              The exported project's root directory. 
-              
-	        
-	        
-	           If you select the Export Bld.inf file option, then
-		        type the Bld.Inf file location in the Bld.inf
-		          File field, or click Browse to select the
-	           Bld.Inf file. 
-	           
-	             If you do not select the Export Bld.inf file option,
-		          then you need not specify the Bld.Inf file location.	           
-	           
-	             By default, the Bld.Inf file is exported to one of the
-		           following locations in the order listed below:	           
-	           
-	             
-	               The location where the Bld.Inf was created when the
-		             project was last exported to an MMP file. 
-	              The MMP file location.
-              
-	        
-          
-	     
-       Click Next to go to the Other Makefiles page where you can specify extra Makefiles to invoke from bld.inf  
-  
-	 
-	   
-    
-       Click Next to open the Scalable Icon Makefiles page where you can specify the Makefiles used to generate scalable icon files.
-	   
-        Click Next to go to the PRJ_EXPORTS page, to specify the list of files to be copied from the source directories to
-            the releasables directories while building the project:
-            
-              
-              
-            
-          
-             Note that this page is displayed only if you have selected
-             the Export Bld.inf file option in the previous page.          
-        
-         
-            Type the Source and Target
-            locations of the file to be copied, and click Add to append
-            the source-target pair to the PRJ_EXPORTS list. You can use
-            Browse to specify the source file and its target location. If
-            the target location for the file is not specified, it will be copied to
-            epoc32\include directory. 
-          
-             Note that the contents of the PRJ_EXPORTS list is
-              exactly the same as it appears in the PRJ_EXPORTS section of the
-             Bld.Inf file.           
-        

-         
-            If you want to modify or delete any entry from the
-            PRJ_EXPORTS list, select the entry and click
-            Modify or Delete.        
-         
-            Click Next to go to the MMP Preview
-            page: 
-          
-              
-             
-       
-        
-         
-            Select a project from the list of projects to be exported, to see a
-            preview of the MMP file in the pane below. You can edit the
-            contents if required.        
-         
-            Click Finish to complete the export process. The
-            wizard will create the managed MMP file and Bld.inf
-            file in their specified locations.
-          
-             A managed MMP file contains the same content as a
-              standard MMP file would, but the contents are organised into
-              following managed sections using special tags:           
-      
-		   
-		     
-		      
-		        Binary Build Information	            
-             
-              
-                
-                  Search Path                 
-              
-              
-                
-                  Project Content Managed                 
-              
-              
-                
-                  Linkage                 
-              
-              
-                
-                  Customization                 
-              
-          
-      
-		  
-		    You will be notified in case of any errors during the updated
-		    process, which results in not creating the MMP or
-		    Bld.Inf files. 
-        
-


-     
-       The following MMP file generated by the wizard, shows how
-       its content is organised using managed sections:       
-     // HelloCarbide.mmp
-     /*& START_BINARY_BUILD &*/

-     // NOTE Content in this section is auto-generated, any changes are overwritten in the next update process.

-     CAPABILITY READUSERDATA

-     TARGET HelloCarbide.exe

-     TARGETTYPE exe

-     UID 0x00000000 0xe4d95f85

-     VENDORID 0x00000000

-     SECUREID 0xE4D95F85

-     /*& END_BINARY_BUILD &*/
-     /*& START_SEARCH_PATHS &*/

-     // NOTE Content in this section is auto-generated, any changes are overwritten in the next update process.

-     SYSTEMINCLUDE \epoc32\include \epoc32\include\variant \epoc32\include\oem

-     USERINCLUDE ..\inc ..\data

-     /*& END_SEARCH_PATHS &*/
-     /*& START_PROJECT_CONTENT &*/

-     // NOTE Content in this section is auto-generated, any changes are overwritten in the next update process.

-     SOURCEPATH ..\data

-     START RESOURCE HelloCarbide.rss

-     TARGETPATH resource\apps

-     HEADER

-     END

-     START RESOURCE HelloCarbide_reg.rss

-     TARGETPATH private\10003a3f\apps

-     HEADER

-     END

-     SOURCEPATH ..\src

-     SOURCE Waving.cpp HelloCarbideDocument.cpp HelloCarbideApplication.cpp

-     SOURCE HelloCarbideAppView.cpp HelloCarbideAppUi.cpp HelloCarbide.cpp

-     /*& END_PROJECT_CONTENT &*/
-     /*& START_LINKAGE_INFORMATION &*/

-     // NOTE Content in this section is auto-generated, any changes are overwritten in the next update process.

-     LIBRARY euser.lib apparc.lib cone.lib eikcore.lib avkon.lib commonengine.lib

-     LIBRARY efsrv.lib estor.lib

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

- + + +Exporting project(s) to MMP/Bld.inf files in Tasks + + + + +

Exporting project(s) to MMP/Bld.inf files

+ The command-line Symbian OS toolchain requires a component description + file (Bld.Inf) and one or more project definition files + (.mmp) to build a project. The export command allows you to create + these files for your projects.

+ To export project(s) to a Bld.Inf and/or MMP + file:

+ Click File > Export... to get a list of the + available export wizards: +
+ OR
+
+ Click Export from the pop-up menus of the + C/C++ Projects and Navigator views to get a + list of the available export wizards:
+
+ +
+
+
Select Symbian MMP/Bld.Inf and click + Next to go to the Symbian Projects page: +
+
+ +
+
+
+ Select the project(s) you intend to export from the list of + Symbian Projects.
+ Click Next to go to the SDKs and Build Configurations Selection page: +
+ +
+
+
+ Select at least one build configuration for each project in the + left-hand pane from the list of available SDKs and build configurations in the + right-hand pane. By default, all the build configurations chosen during the + last export are selected. If a project is being exported for the first time, no + build configurations are selected. +
+ The build configurations chosen for a project are distinguished using + guard macros in the MMP file. The guard macros are placed around + the MMP file statements containing resources or build setting, + only valid for a subset of the chosen build configurations.
+
+ There are cases where guard macros may not be able to distinguish + between two build configurations. The export wizard shows a conflict when two + such ambiguous build configurations are selected by the user.
+
+ The combination of build configurations which results in a conflict + are as follows:
+ +
- +
  + Any two build configurations that differ only in the build + variant (UDEB/UREL). For example, "UIQ 3.0 Phone (GCCE) Debug" and "UIQ 3.0 + Phone (GCCE) Release" configurations will result in a conflict, as they differ + only in the build variant.
  +
- +
  + Any two build configurations, of which one is user-defined based + on the other using the Manage option in the C/C++ + Build properties view of the project.
  +
  + For more information on managing build configurations, + refer to the CDT user guide.
  +
+ +
+ The wizard will change the build settings in the MMP + file based on the chosen build configuration. If more than one build + configuration which require different build settings are chosen, guard macros + are used to determine the build settings. For example, if you want to change + the SECUREID option for all the EKA2 build + configurations, the wizard will append the following lines into the + MMP file:
+ #if def EKA2 SECUREID 0x00301 #endif + + Where EKA2 is the guard macro for all the build + configurations designed for the EKA2 kernel. The above MMP file + statements check whether the EKA2 guard macro is defined, and if + it is, change the SECUREID option accordingly. +

 
+	     
+		    Click Next to go to the MMP File and Bld.inf
+		      File page: 
+	      		    
+	        
+	       
+	      
+	        
+	           Type the MMP file location in the MMP
+		          File field, or click Browse to select the
+	           MMP file for each project listed above. 
+	           
+	             By default, the MMP file is exported to one of the
+		          following locations in the order listed below:	           
+	           
+	              The location where the project was exported the last time. 
+	              The group folder of the exported project, if it exists. 
+	              The exported project's root directory. 
+              
+	        
+	        
+	           If you select the Export Bld.inf file option, then
+		        type the Bld.Inf file location in the Bld.inf
+		          File field, or click Browse to select the
+	           Bld.Inf file. 
+	           
+	             If you do not select the Export Bld.inf file option,
+		          then you need not specify the Bld.Inf file location.	           
+	           
+	             By default, the Bld.Inf file is exported to one of the
+		           following locations in the order listed below:	           
+	           
+	             
+	               The location where the Bld.Inf was created when the
+		             project was last exported to an MMP file. 
+	              The MMP file location.
+              
+	        
+          
+	     
+       Click Next to go to the Other Makefiles page where you can specify extra Makefiles to invoke from bld.inf  
+  
+	 
+	   
+    
+       Click Next to open the Scalable Icon Makefiles page where you can specify the Makefiles used to generate scalable icon files.
+	   
+        Click Next to go to the PRJ_EXPORTS page, to specify the list of files to be copied from the source directories to
+            the releasables directories while building the project:
+            
+              
+              
+            
+          
+             Note that this page is displayed only if you have selected
+             the Export Bld.inf file option in the previous page.          
+        
+         
+            Type the Source and Target
+            locations of the file to be copied, and click Add to append
+            the source-target pair to the PRJ_EXPORTS list. You can use
+            Browse to specify the source file and its target location. If
+            the target location for the file is not specified, it will be copied to
+            epoc32\include directory. 
+          
+             Note that the contents of the PRJ_EXPORTS list is
+              exactly the same as it appears in the PRJ_EXPORTS section of the
+             Bld.Inf file.           
+        

+         
+            If you want to modify or delete any entry from the
+            PRJ_EXPORTS list, select the entry and click
+            Modify or Delete.        
+         
+            Click Next to go to the MMP Preview
+            page: 
+          
+              
+             
+       
+        
+         
+            Select a project from the list of projects to be exported, to see a
+            preview of the MMP file in the pane below. You can edit the
+            contents if required.        
+         
+            Click Finish to complete the export process. The
+            wizard will create the managed MMP file and Bld.inf
+            file in their specified locations.
+          
+             A managed MMP file contains the same content as a
+              standard MMP file would, but the contents are organised into
+              following managed sections using special tags:           
+      
+		   
+		     
+		      
+		        Binary Build Information	            
+             
+              
+                
+                  Search Path                 
+              
+              
+                
+                  Project Content Managed                 
+              
+              
+                
+                  Linkage                 
+              
+              
+                
+                  Customization                 
+              
+          
+      
+		  
+		    You will be notified in case of any errors during the updated
+		    process, which results in not creating the MMP or
+		    Bld.Inf files. 
+        
+


+     
+       The following MMP file generated by the wizard, shows how
+       its content is organised using managed sections:       
+     // HelloCarbide.mmp
+     /*& START_BINARY_BUILD &*/

+     // NOTE Content in this section is auto-generated, any changes are overwritten in the next update process.

+     CAPABILITY READUSERDATA

+     TARGET HelloCarbide.exe

+     TARGETTYPE exe

+     UID 0x00000000 0xe4d95f85

+     VENDORID 0x00000000

+     SECUREID 0xE4D95F85

+     /*& END_BINARY_BUILD &*/
+     /*& START_SEARCH_PATHS &*/

+     // NOTE Content in this section is auto-generated, any changes are overwritten in the next update process.

+     SYSTEMINCLUDE \epoc32\include \epoc32\include\variant \epoc32\include\oem

+     USERINCLUDE ..\inc ..\data

+     /*& END_SEARCH_PATHS &*/
+     /*& START_PROJECT_CONTENT &*/

+     // NOTE Content in this section is auto-generated, any changes are overwritten in the next update process.

+     SOURCEPATH ..\data

+     START RESOURCE HelloCarbide.rss

+     TARGETPATH resource\apps

+     HEADER

+     END

+     START RESOURCE HelloCarbide_reg.rss

+     TARGETPATH private\10003a3f\apps

+     HEADER

+     END

+     SOURCEPATH ..\src

+     SOURCE Waving.cpp HelloCarbideDocument.cpp HelloCarbideApplication.cpp

+     SOURCE HelloCarbideAppView.cpp HelloCarbideAppUi.cpp HelloCarbide.cpp

+     /*& END_PROJECT_CONTENT &*/
+     /*& START_LINKAGE_INFORMATION &*/

+     // NOTE Content in this section is auto-generated, any changes are overwritten in the next update process.

+     LIBRARY euser.lib apparc.lib cone.lib eikcore.lib avkon.lib commonengine.lib

+     LIBRARY efsrv.lib estor.lib

+     /*& END_LINKAGE_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 c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/ImportingProjects.html --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/ImportingProjects.html Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/ImportingProjects.html Thu May 20 13:57:30 2010 -0500 @@ -121,7 +121,7 @@

Project Preferences

Project Types

- + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/ModifyingResources.html --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/ModifyingResources.html Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/ModifyingResources.html Thu May 20 13:57:30 2010 -0500 @@ -1,32 +1,32 @@ - -Modifying Resources in Tasks - - - -

Modifying Resources

- - -

- This section describes the steps for adding and modifying resources of an - existing project. The resources may be a bitmap resource (MBM) or an - application information file (AIF) definition file. -

- 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 - resource compiler.

- - -

- - - - + +Modifying Resources in Tasks + + + +

Modifying Resources

+ + +

+ This section describes the steps for adding and modifying resources of an + existing project. The resources may be a bitmap resource (MBM) or an + application information file (AIF) definition file. +

+ 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 + resource compiler.

+ + +

+ + + + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 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 Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/Multi-BitmapFile.html Thu May 20 13:57:30 2010 -0500 @@ -1,43 +1,43 @@ - -Creating an MBM File in Modifying Resources - - - -

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 - in MBM File. The Edit MBM/MIF Contents or Edit MBM Contents window allows you to create an MBM file.

- To create an MBM file

- In the Symbian Project Navigator view double-click a .mmp file (Figure 1) to open the MMP Editor (Figure 2). -
-
Figure 1- MMP File
-
- In the Sources tab under the Resources group, select Bitmaps

Figure 2 - MMP Editor

Click Add to display the Edit MBM Contents window (Figure 3)

Figure 3 - MBM Editor

You can now use the MBM Editor to add bitmaps, with and without masks, to the MBM file.

Enter a name for the mbm file in the Target file text box.
Add bitmap files to the editor by using the Add From Project or Add From Filesystem buttons.

Additional information for the MBM editor fields is provided in MBM Editor.

Related concepts

MBM File

- - - - + +Creating an MBM File in Modifying Resources + + + +

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 + in MBM File. The Edit MBM/MIF Contents or Edit MBM Contents window allows you to create an MBM file.

+ To create an MBM file

+ In the Symbian Project Navigator view double-click a .mmp file (Figure 1) to open the MMP Editor (Figure 2). +
+
Figure 1- MMP File
+
+ In the Sources tab under the Resources group, select Bitmaps

Figure 2 - MMP Editor

Click Add to display the Edit MBM Contents window (Figure 3)

Figure 3 - MBM Editor

You can now use the MBM Editor to add bitmaps, with and without masks, to the MBM file.

Enter a name for the mbm file in the Target file text box.
Add bitmap files to the editor by using the Add From Project or Add From Filesystem buttons.

Additional information for the MBM editor fields is provided in MBM Editor.

Related concepts

MBM File

+ + + + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/RmvngandVwngPropsosSDK.html --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/RmvngandVwngPropsosSDK.html Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/RmvngandVwngPropsosSDK.html Thu May 20 13:57:30 2010 -0500 @@ -41,7 +41,7 @@

Working with SDKs

SDK Properties

- + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/RunModeToc.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/RunModeToc.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/RunModeToc.htm Thu May 20 13:57:30 2010 -0500 @@ -1,16 +1,16 @@ - -Run Mode Projects - - - -

Run Mode Projects

The topics include:

- - - - + +Run Mode Projects + + + +

Run Mode Projects

The topics include:

+ + + + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/StopModeToc.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/StopModeToc.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/StopModeToc.htm Thu May 20 13:57:30 2010 -0500 @@ -1,18 +1,18 @@ - -Stop Mode Projects - - - -

Stop Mode Projects

The topics include:

- - - - + +Stop Mode Projects + + + +

Stop Mode Projects

The topics include:

+ + + + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/WorkingwithSDKs.html --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/WorkingwithSDKs.html Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/WorkingwithSDKs.html Thu May 20 13:57:30 2010 -0500 @@ -21,7 +21,7 @@

Editing SDK Properties

Adding Symbian Custom Kits

- + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/WritingCode.html --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/WritingCode.html Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/WritingCode.html Thu May 20 13:57:30 2010 -0500 @@ -1,24 +1,24 @@ - -Writing Code in Tasks - - - -

Writing Code

- - -

- This section explains how to work with Symbian OS C++ projects with the - help of the tools provided. -

Modifying Resources

- -

- - - - - + +Writing Code in Tasks + + + +

Writing Code

+ + +

+ This section explains how to work with Symbian OS C++ projects with the + help of the tools provided. +

Modifying Resources

+ +

+ + + + + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_clearing.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_clearing.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_clearing.htm Thu May 20 13:57:30 2010 -0500 @@ -1,74 +1,74 @@ - - - - - - -Removing Breakpoints - - - -

Removing Breakpoints

You can remove one or more breakpoints set for a debug session using the Breakpoints, Disassembly, or editor views.

Removing a Breakpoint

To remove a breakpoint in the Breakpoints view: -
- Right-click the breakpoint, click Remove
-

Click the Remove Selected Breakpoints () button

To remove a breakpoint in an editor or Disassembly views:

Double-click the breakpoint dot in the marker bar

- OR

Select the source line with the breakpoint, click Run > Toggle Line Breakpoint

Right-click the breakpoint dot in the marker bar and select Toggle Breakpoint

The breakpoint disappears in the Breakpoints view.

- -

Removing all Breakpoints

To remove all breakpoints in the Breakpoints view: -
- Right-click a breakpoint, click Remove All
-

Click the Remove All Breakpoints () button

To remove all breakpoint in an editor or Disassembly views: -
- Click the Run > Remove all Breakpoints menu item
-

All the breakpoints disappear in the Breakpoints, Disassembly, and editor views.

Related concepts

Breakpoints

Related tasks

Related references

Debug Perspective

- - - - - + + + + + + +Removing Breakpoints + + + +

Removing Breakpoints

You can remove one or more breakpoints set for a debug session using the Breakpoints, Disassembly, or editor views.

Removing a Breakpoint

To remove a breakpoint in the Breakpoints view: +
- Right-click the breakpoint, click Remove
+

Click the Remove Selected Breakpoints () button

To remove a breakpoint in an editor or Disassembly views:

Double-click the breakpoint dot in the marker bar

+ OR

Select the source line with the breakpoint, click Run > Toggle Line Breakpoint

Right-click the breakpoint dot in the marker bar and select Toggle Breakpoint

The breakpoint disappears in the Breakpoints view.

+ +

Removing all Breakpoints

To remove all breakpoints in the Breakpoints view: +
- Right-click a breakpoint, click Remove All
+

Click the Remove All Breakpoints () button

To remove all breakpoint in an editor or Disassembly views: +
- Click the Run > Remove all Breakpoints menu item
+

All the breakpoints disappear in the Breakpoints, Disassembly, and editor views.

Related concepts

Breakpoints

Related tasks

Related references

Debug Perspective

+ + + + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_conditional.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_conditional.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_conditional.htm Thu May 20 13:57:30 2010 -0500 @@ -1,57 +1,57 @@ - - - - - - -Setting Conditional Breakpoints - - - -

Setting Conditional Breakpoints or Watchpoints

You create a conditional (temporary) breakpoint or watchpoint in the Properties for C/C++ breakpoint dialog. Right-click a breakpoint or watchpoint in the Breakpoints view, then select Properties from the context menu. A conditional breakpoint or watchpoint has an associated conditional expression. The debugger evaluates the expression to determine whether to halt program execution at that breakpoint.

A conditional breakpoint or watchpoint behaves in two different ways:

If the expression evaluates to true (a non-zero value), the debugger halts program execution.
If the expression evaluates to false (a zero value), program execution continues without stopping.

Figure 1 Properties for C/C++ - breakpoint window

To set a conditional breakpoint

Find the breakpoint or watchpoint in the Breakpoints view -
- If the breakpoint is already set, then continue
- If the breakpoint is not set, set it in the source code now
-
Right-click the breakpoint and select Properties on the context menu

The Properties for C/C++ - breakpoint dialog appears (Figure 1). The Common panel is shown by default.

Enter an condition in the Condition text box

When entering a condition use the format: Variable <operator> value. For example, iCount == 5.

Enter an ignore count value in the Ignore count text box (optional)

The Ignore count specifies how many times the breakpoint or watchpoint hits the condition before execution stops. The default setting is zero, which means the first time the breakpoint is hit, execution halts. For example, to stop at the breakpoint on the second time it is hit, enter an Ignore count of 1.

Click OK

During subsequent debugging sessions, the debugger evaluates the expression to determine whether to halt program execution at the conditional breakpoint.

For more information on marker bar icons, see C/C++ Development User Guide > Concepts > Debug > Breakpoints.

Related concepts

Breakpoints

Related tasks

Related references

Breakpoints view

- - - - - + + + + + + +Setting Conditional Breakpoints + + + +

Setting Conditional Breakpoints or Watchpoints

A conditional breakpoint or watchpoint behaves in two different ways:

If the expression evaluates to true (a non-zero value), the debugger halts program execution.
If the expression evaluates to false (a zero value), program execution continues without stopping.

Figure 1 Properties for C/C++ - breakpoint window

To set a conditional breakpoint

Find the breakpoint or watchpoint in the Breakpoints view +
- If the breakpoint is already set, then continue
- If the breakpoint is not set, set it in the source code now
+
Right-click the breakpoint and select Properties on the context menu

The Properties for C/C++ - breakpoint dialog appears (Figure 1). The Common panel is shown by default.

Enter an condition in the Condition text box

When entering a condition use the format: Variable <operator> value. For example, iCount == 5.

Enter an ignore count value in the Ignore count text box (optional)

Click OK

During subsequent debugging sessions, the debugger evaluates the expression to determine whether to halt program execution at the conditional breakpoint.

For more information on marker bar icons, see C/C++ Development User Guide > Concepts > Debug > Breakpoints.

Related concepts

Breakpoints

Related tasks

Related references

Breakpoints view

+ + + + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_disable.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_disable.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_disable.htm Thu May 20 13:57:30 2010 -0500 @@ -1,48 +1,48 @@ - - - - - - -Disabling Breakpoints - - - -

Disabling Breakpoints

Disable a breakpoint to prevent it from affecting program execution. The disabled breakpoint remains at the source-code line at which you set it, so that you can enable it later. Disabling the breakpoint is easier than clearing it and re-creating it from scratch.

Figure 1 shows some source code and the selected line shows the breakpoint icon that appears in the marker bar when a breakpoint is disabled.

Figure 1 - Disabling breakpoints

Disabling a Breakpoint

In the Breakpoints view, uncheck the checkbox next to the breakpoint

-
or
-

In an editor or Disassembly view, right-click the breakpoint in the marker bar and select Disable Breakpoint

The enabled breakpoint dot () changes to a disabled breakpoint dot (). The disabled breakpoint dot indicates that the breakpoint does not halt program execution.

For more information on breakpoints, see C/C++ Development User Guide > Concepts > Debug > Breakpoints.

Related concepts

Breakpoints

Related tasks

Related references

Breakpoints view

- - - - + + + + + + +Disabling Breakpoints + + + +

Disabling Breakpoints

Figure 1 shows some source code and the selected line shows the breakpoint icon that appears in the marker bar when a breakpoint is disabled.

Figure 1 - Disabling breakpoints

Disabling a Breakpoint

In the Breakpoints view, uncheck the checkbox next to the breakpoint

+
or
+

In an editor or Disassembly view, right-click the breakpoint in the marker bar and select Disable Breakpoint

The enabled breakpoint dot () changes to a disabled breakpoint dot (). The disabled breakpoint dot indicates that the breakpoint does not halt program execution.

For more information on breakpoints, see C/C++ Development User Guide > Concepts > Debug > Breakpoints.

Related concepts

Breakpoints

Related tasks

Related references

Breakpoints view

+ + + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_enable.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_enable.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_enable.htm Thu May 20 13:57:30 2010 -0500 @@ -1,49 +1,49 @@ - - - - - - -Enabling Breakpoints - - - -

Enabling Breakpoints

Enable a breakpoint to have it halt program execution at the specific line in the source file. You can set a breakpoint using the Breakpoints, Disassembly, or editor views. An enabled breakpoint must still be resolved during a debug session before it can halt program execution. Enabling a breakpoint that you previously disabled is easier than clearing it and re-creating it from scratch.

-Figure 1 shows some source code and the selected line shows the breakpoint icon that appears in the marker bar when a breakpoint is enabled. -

Figure 1 - Enabling breakpoint

Enabling a Breakpoint

In the Breakpoints view, place a check in the checkbox next to the breakpoint

-
or
-

In an editor view, right-click the breakpoint in the marker bar and select Enable Breakpoint

-
If the source line has a breakpoint, the disabled breakpoint dot () changes to an enabled breakpoint dot (). The enabled breakpoint indicates that the breakpoint, if resolved, will halt program execution.
-

For more information on breakpoints, see C/C++ Development User Guide > Concepts > Debug > Breakpoints.

Related concepts

Breakpoints

Related tasks

Related references

Breakpoints view

- - - - + + + + + + +Enabling Breakpoints + + + +

Enabling Breakpoints

+Figure 1 shows some source code and the selected line shows the breakpoint icon that appears in the marker bar when a breakpoint is enabled. +

Figure 1 - Enabling breakpoint

Enabling a Breakpoint

In the Breakpoints view, place a check in the checkbox next to the breakpoint

+
or
+

In an editor view, right-click the breakpoint in the marker bar and select Enable Breakpoint

+
If the source line has a breakpoint, the disabled breakpoint dot () changes to an enabled breakpoint dot (). The enabled breakpoint indicates that the breakpoint, if resolved, will halt program execution.
+

For more information on breakpoints, see C/C++ Development User Guide > Concepts > Debug > Breakpoints.

Related concepts

Breakpoints

Related tasks

Related references

Breakpoints view

+ + + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_exporting.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_exporting.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_exporting.htm Thu May 20 13:57:30 2010 -0500 @@ -1,74 +1,74 @@ - - - - - - -Exporting Breakpoints - - - -

Exporting Breakpoints

Use the Export Breakpoints command to export selected breakpoints to a breakpoints file with a .bkpt extension. All breakpoints set in the source files of all projects in your current workspace will be listed in the Export Breakpoints window.

The Export Breakpoints wizard shown in Figure 1 helps you to export breakpoints from your project's source files.

Figure 1 - Export Breakpoints window

- - - - - - - - - - - - - - - - - - - - - - - -

Option

Description

Default

Breakpoint List

Select the breakpoints that you wish to export, and deselect those that you do not.

not selected

To file

The file to export the breakpoints to, you can also click Browse... to search for a location to export.

There can be two possible defaults:

If you have never exported breakpoints before it will be blank

If you have exported breakpoints before the last file name you exported to will be automatically inserted.

Overwrite existing file without warning

When selected, if the file you wish to export to already exists, it will be overwritten automatically by the wizard.

not selected

Exporting Breakpoints

Select File > Export... then select Breakpoints from the General group

-
or
-

Right-click in the Breakpoints view and select Export Breakpoints...

Related concepts

Breakpoints

Related tasks

Related references

Breakpoints view

- - - - + + + + + + +Exporting Breakpoints + + + +

Exporting Breakpoints

The Export Breakpoints wizard shown in Figure 1 helps you to export breakpoints from your project's source files.

Figure 1 - Export Breakpoints window

+ + + + + + + + + + + + + + + + + + + + + + + +

Option

Description

Default

Breakpoint List

Select the breakpoints that you wish to export, and deselect those that you do not.

not selected

To file

The file to export the breakpoints to, you can also click Browse... to search for a location to export.

There can be two possible defaults:

If you have never exported breakpoints before it will be blank

If you have exported breakpoints before the last file name you exported to will be automatically inserted.

Overwrite existing file without warning

When selected, if the file you wish to export to already exists, it will be overwritten automatically by the wizard.

not selected

Exporting Breakpoints

Select File > Export... then select Breakpoints from the General group

+
or
+

Right-click in the Breakpoints view and select Export Breakpoints...

Related concepts

Breakpoints

Related tasks

Related references

Breakpoints view

+ + + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_importing.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_importing.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_importing.htm Thu May 20 13:57:30 2010 -0500 @@ -1,72 +1,72 @@ - - - - - - -Importing Breakpoints - - - -

Importing Breakpoints

Use the Import Breakpoints command to import breakpoints previously exported and saved to a breakpoints file (.bkpt). The Import Breakpoints wizard helps you to import breakpoints from a file.

Figure 1 shows the Import Breakpoints window.

Figure 1 - Importing Breakpoints

- - - - - - - - - - - - - - - - - - - -

Option	Description
From file	Type the name of the file to import from, or click the Browse... button to search for a breakpoints file.
Automatically update existing breakpoints	- When selected, any breakpoints that already exist in your workspace will be overwritten by those being imported from the file. - -
Automatically create breakpoint working sets	- When selected, if an imported breakpoint indicates it belongs to a working set that does not exist in your workspace, the working set will be created for you and the breakpoint added to it. - -

Importing Breakpoints

Select File > Import... and then select Breakpoints in the General group

-
or
-

Right-click in the Breakpoints view and select Import Breakpoints...

Related concepts

Breakpoints

Related tasks

Related references

Breakpoints view

- - - - + + + + + + +Importing Breakpoints + + + +

Importing Breakpoints

Figure 1 shows the Import Breakpoints window.

Figure 1 - Importing Breakpoints

+ + + + + + + + + + + + + + + + + + + +

Option	Description
From file	Type the name of the file to import from, or click the Browse... button to search for a breakpoints file.
Automatically update existing breakpoints	+ When selected, any breakpoints that already exist in your workspace will be overwritten by those being imported from the file. + +
Automatically create breakpoint working sets	+ When selected, if an imported breakpoint indicates it belongs to a working set that does not exist in your workspace, the working set will be created for you and the breakpoint added to it. + +

Importing Breakpoints

Select File > Import... and then select Breakpoints in the General group

+
or
+

Right-click in the Breakpoints view and select Import Breakpoints...

Related concepts

Breakpoints

Related tasks

Related references

Breakpoints view

+ + + + diff -r c70ff7f19887 -r d1b0b4e203e9 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 Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_setting.htm Thu May 20 13:57:30 2010 -0500 @@ -1,62 +1,62 @@ - - - - - - -Setting Breakpoints - - - -

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.

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

Setting a Breakpoint in Editor or Disassembly Views

Double-click the marker bar to the left of the line of code where you want to place a breakpoint

-
or
-

Right-click in the marker bar and select Toggle Breakpoint

-
or
-

Click on the line of code and select Run > Toggle Breakpoint from the program menu bar

-
or
-

While selecting a line, press Ctrl+Shift+B

The active breakpoint dot appears () in the marker bar. If the breakpoint is resolved during the debug session, the debugger halts program execution at the line with the resolved breakpoint ().

NOTE Setting a breakpoint in a file affects execution of all build targets that include that file.

For more information on breakpoints, see C/C++ Development User Guide > Concepts > Debug > Breakpoints.

Related concepts

Breakpoints

Related tasks

Related references

Breakpoints view

- - - - + + + + + + +Setting Breakpoints + + + +

Setting Breakpoints

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

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

Setting a Breakpoint in Editor or Disassembly Views

Double-click the marker bar to the left of the line of code where you want to place a breakpoint

+
or
+

Right-click in the marker bar and select Toggle Breakpoint

+
or
+

Click on the line of code and select Run > Toggle Breakpoint from the program menu bar

+
or
+

While selecting a line, press Ctrl+Shift+B

The active breakpoint dot appears () in the marker bar. If the breakpoint is resolved during the debug session, the debugger halts program execution at the line with the resolved breakpoint ().

NOTE Setting a breakpoint in a file affects execution of all build targets that include that file.

For more information on breakpoints, see C/C++ Development User Guide > Concepts > Debug > Breakpoints.

Related concepts

Breakpoints

Related tasks

Related references

Breakpoints view

+ + + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_temporary.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_temporary.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_temporary.htm Thu May 20 13:57:30 2010 -0500 @@ -1,47 +1,47 @@ - - - - - - -Setting a Temporary Breakpoint - - - -

Setting a Temporary Breakpoint

Use the Temporary Breakpoint command to set temporary breakpoints. Unlike a regular breakpoint that halts execution each time you debug a project, a temporary breakpoint halts execution only once. The debugger removes the temporary breakpoint after halting program execution.

To set a temporary breakpoint at a line of source code

Set a breakpoint on the source line
Right-click breakpoint and select Breakpoint Properties in the context menu

The Properties for C/C++ breakpoint window appears (Figure 1).

Figure 1 Properties for C/C++ breakpoint window

Enter the value "1" into the Ignore count field
Click OK

The dash icon changes to an active breakpoint icon. After you debug the project, the debugger halts program execution at the line that has the active breakpoint icon. After execution halts, the active breakpoint icon reverts to a dash icon. -

Related concepts

Breakpoints
Watchpoints

Related tasks

Related references

Breakpoints view

- - - + + + + + + +Setting a Temporary Breakpoint + + + +

Setting a Temporary Breakpoint

To set a temporary breakpoint at a line of source code

Set a breakpoint on the source line
Right-click breakpoint and select Breakpoint Properties in the context menu

The Properties for C/C++ breakpoint window appears (Figure 1).

Figure 1 Properties for C/C++ breakpoint window

Enter the value "1" into the Ignore count field
Click OK

Related concepts

Breakpoints
Watchpoints

Related tasks

Related references

Breakpoints view

+ + + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_view_props.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_view_props.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/pgm_bp_view_props.htm Thu May 20 13:57:30 2010 -0500 @@ -1,58 +1,58 @@ - - - - - - -Viewing Breakpoint Properties - - - -

Viewing Breakpoint Properties

After you set a breakpoint, you can view and modify its Actions, Common, and Filtering properties. Table 1 explains breakpoint properties for the Common panel.

Figure 1 - Properties for C/C++ breakpoint window

Table 1. Breakpoint properties

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Property	Explanation
Type	The type of item, such as Auto Breakpoint.
File	The path to the file that contains the item.
Line number	Line number in file breakpoint applies to.
Enabled	Indicates the current status of the breakpoint. When checkmarked, the breakpoint stops program execution if its condition is met. When unchecked, the breakpoint is ignored during the debug session.
Condition	The conditional expression associated with the item. This conditional expression must evaluate to true in order for the item to perform its specified action.
Ignore count	Displays the number of times that program execution arrived at the breakpoint before the program stopped.

To view properties for a breakpoint

Right-click the breakpoint in the Breakpoints view and select Properties...
-
The Properties for C/C++ breakpoint window appears.
-
Click Actions, Common, or Filtering to view specific breakpoint property information

- - - - + + + + + + +Viewing Breakpoint Properties + + + +

Viewing Breakpoint Properties

After you set a breakpoint, you can view and modify its Actions, Common, and Filtering properties. Table 1 explains breakpoint properties for the Common panel.

Figure 1 - Properties for C/C++ breakpoint window

Table 1. Breakpoint properties

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Property	Explanation
Type	The type of item, such as Auto Breakpoint.
File	The path to the file that contains the item.
Line number	Line number in file breakpoint applies to.
Enabled	Indicates the current status of the breakpoint. When checkmarked, the breakpoint stops program execution if its condition is met. When unchecked, the breakpoint is ignored during the debug session.
Condition	The conditional expression associated with the item. This conditional expression must evaluate to true in order for the item to perform its specified action.
Ignore count	Displays the number of times that program execution arrived at the breakpoint before the program stopped.

To view properties for a breakpoint

Right-click the breakpoint in the Breakpoints view and select Properties...
+
The Properties for C/C++ breakpoint window appears.
+
Click Actions, Common, or Filtering to view specific breakpoint property information

+ + + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/save_breakpoints_view.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/save_breakpoints_view.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/save_breakpoints_view.htm Thu May 20 13:57:30 2010 -0500 @@ -1,38 +1,38 @@ - - - - - - -Saving the Breakpoints View - - - -

Saving the Contents of Breakpoints View

You can save the contents of the Breakpoints view. This feature is useful for saving sets of breakpoint data, then later re-opening those sets.

To save contents of the Breakpoints view

Click File > Save or File > Save As

Clicking File > Save As lets you specify the name and path to save the file that stores the contents.
-

Related concepts

Breakpoints

Related tasks

Related references

Breakpoints view

- - - - + + + + + + +Saving the Breakpoints View + + + +

Saving the Contents of Breakpoints View

You can save the contents of the Breakpoints view. This feature is useful for saving sets of breakpoint data, then later re-opening those sets.

To save contents of the Breakpoints view

Click File > Save or File > Save As

Clicking File > Save As lets you specify the name and path to save the file that stores the contents.
+

Related concepts

Breakpoints

Related tasks

Related references

Breakpoints view

+ + + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/show_breakpoints_view.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/show_breakpoints_view.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/breakpoints/show_breakpoints_view.htm Thu May 20 13:57:30 2010 -0500 @@ -1,36 +1,36 @@ - - - - - - -Opening the Breakpoints View - - - -

Opening a Breakpoints View

Use the Breakpoints view to show a list of breakpoints currently set in your project.

Figure 1 - Breakpoints view

To open a Breakpoints view

Click Window > Show View > Breakpoints (Alt+Shift+Q, B)

The Breakpoints view opens in the current perspective.

NOTE Double-click a breakpoint in the Breakpoints view to display its associated source-code line in an editor view.

Related concepts

Breakpoints

Related tasks

- - - - + + + + + + +Opening the Breakpoints View + + + +

Opening a Breakpoints View

Use the Breakpoints view to show a list of breakpoints currently set in your project.

Figure 1 - Breakpoints view

To open a Breakpoints view

Click Window > Show View > Breakpoints (Alt+Shift+Q, B)

The Breakpoints view opens in the current perspective.

NOTE Double-click a breakpoint in the Breakpoints view to display its associated source-code line in an editor view.

Related concepts

Breakpoints

Related tasks

+ + + + diff -r c70ff7f19887 -r d1b0b4e203e9 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 Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/carbide_tools.htm Thu May 20 13:57:30 2010 -0500 @@ -40,6 +40,6 @@

Carbide.c++ Plug-in Developer Guide

- + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/code_style_reformatting_sources.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/code_style_reformatting_sources.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/code_style_reformatting_sources.htm Thu May 20 13:57:30 2010 -0500 @@ -1,29 +1,29 @@ - -Reformatting a Source File - - - -

Reformatting a Source File

- - -

You can reformat a source file to use any of the preset code styles in the Code Style preference panel.

To reformat a source file

Verify the correct code style is set in the Code Style preference panel
Open an editor view with the source file you want to reformat
Right-click and choose Source > Format (CTRL+SHIFT+F)

Figure 1 -Selecting Source > Format from an editor view

Related references

- - - - + +Reformatting a Source File + + + +

Reformatting a Source File

+ + +

You can reformat a source file to use any of the preset code styles in the Code Style preference panel.

To reformat a source file

Verify the correct code style is set in the Code Style preference panel
Open an editor view with the source file you want to reformat
Right-click and choose Source > Format (CTRL+SHIFT+F)

Figure 1 -Selecting Source > Format from an editor view

Related references

+ + + + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/code_style_workspace.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/code_style_workspace.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/code_style_workspace.htm Thu May 20 13:57:30 2010 -0500 @@ -1,30 +1,30 @@ - -Code Styles preferences - - - -

Setting the Workspace Code Style

- - -

You can set the default code style for a workspace using the Code Style preference panel. Once set, the specified code style is applied to all new files and projects created in the workspace. To update a source file already in the workspace, see Reformatting a Source File.

Figure 1 -Select a profile from the Select a profile list

You can also create your own profiles based on the one's included with Carbide. Simply click Edit and change the options presented in the Profile <profile_name> window that appears.

To set the workspace code style

Open the Code Style preference panel
Choose a profile from the Select a profile dropdown list
Click OK

Related references

- - - - + +Code Styles preferences + + + +

Setting the Workspace Code Style

+ + +

Figure 1 -Select a profile from the Select a profile list

You can also create your own profiles based on the one's included with Carbide. Simply click Edit and change the options presented in the Profile <profile_name> window that appears.

To set the workspace code style

Open the Code Style preference panel
Choose a profile from the Select a profile dropdown list
Click OK

Related references

+ + + + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 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 Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/soft_attach_debug.htm Thu May 20 13:57:30 2010 -0500 @@ -111,7 +111,7 @@

Registers view

Breakpoint view

- + diff -r c70ff7f19887 -r d1b0b4e203e9 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 Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/view_symbian_kernel_set.htm Thu May 20 13:57:30 2010 -0500 @@ -31,7 +31,7 @@

Debug View

Symbian OS View Window

- + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_debug.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_debug.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/work_debug_act_debug.htm Thu May 20 13:57:30 2010 -0500 @@ -30,7 +30,7 @@

Working with the Debugger

Debug View

- + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/eventpoints_enabling.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/eventpoints_enabling.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/eventpoints_enabling.htm Thu May 20 13:57:30 2010 -0500 @@ -1,27 +1,27 @@ - - - - - - -Enabling an Eventpoint - - - -

Enabling an Eventpoint

Enable an eventpoint to have it perform its specified action during program execution. Enabling an eventpoint that you previously disabled is easier than clearing it and re-creating it from scratch.

To enable an eventpoint

Select the eventpoint that you want to enable

Select the eventpoint by name in the Breakpoints view, or click the cursor on the source-code line that contains the eventpoint.

Click Debug > Enable Eventpoint

The Enable Eventpoint menu appears.

From the menu, click the Enable Eventpoint command, where Eventpoint is the type of eventpoint that you want to enable
The disabled eventpoint icon changes to its original eventpoint icon. The enabled eventpoint icon indicates that the eventpoint will perform its specified action.

- - - - + + + + + + +Enabling an Eventpoint + + + +

Enabling an Eventpoint

Enable an eventpoint to have it perform its specified action during program execution. Enabling an eventpoint that you previously disabled is easier than clearing it and re-creating it from scratch.

To enable an eventpoint

Select the eventpoint that you want to enable

Select the eventpoint by name in the Breakpoints view, or click the cursor on the source-code line that contains the eventpoint.

Click Debug > Enable Eventpoint

The Enable Eventpoint menu appears.

From the menu, click the Enable Eventpoint command, where Eventpoint is the type of eventpoint that you want to enable
The disabled eventpoint icon changes to its original eventpoint icon. The enabled eventpoint icon indicates that the eventpoint will perform its specified action.

+ + + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/eventpoints_setting.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/eventpoints_setting.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/eventpoints_setting.htm Thu May 20 13:57:30 2010 -0500 @@ -1,35 +1,35 @@ - - - - - - -Setting a Conditional Eventpoint - - - -

Setting a Conditional Eventpoint

Use the Condition column of the Breakpoints view to set a conditional eventpoint. A conditional eventpoint has an associated conditional expression. The debugger evaluates the expression to determine whether the eventpoint performs its specified action.

A conditional eventpoint behaves in two different ways:

If the expression evaluates to true (a non-zero value), the eventpoint performs its specified action.
If the expression evaluates to false (a zero value), the eventpoint does not perform its specified action.

To set a conditional eventpoint

Set an eventpoint that you want to associate with a conditional expression
Click Windows > Show View > Breakpoints

A Breakpoints view appears.

Find the eventpoint that you want to associate with a conditional expression
Double-click the Condition column in alignment with the eventpoint
Enter an expression in the Condition text box

During subsequent debugging sessions, the debugger evaluates the expression to determine whether the eventpoint performs its specified action.

NOTE Alternatively, drag-and-drop an expression from a source view or from the Expression view into the Breakpoints view.
-

- - - - + + + + + + +Setting a Conditional Eventpoint + + + +

Setting a Conditional Eventpoint

A conditional eventpoint behaves in two different ways:

If the expression evaluates to true (a non-zero value), the eventpoint performs its specified action.
If the expression evaluates to false (a zero value), the eventpoint does not perform its specified action.

To set a conditional eventpoint

Set an eventpoint that you want to associate with a conditional expression
Click Windows > Show View > Breakpoints

A Breakpoints view appears.

Find the eventpoint that you want to associate with a conditional expression
Double-click the Condition column in alignment with the eventpoint
Enter an expression in the Condition text box

During subsequent debugging sessions, the debugger evaluates the expression to determine whether the eventpoint performs its specified action.

NOTE Alternatively, drag-and-drop an expression from a source view or from the Expression view into the Breakpoints view.
+

+ + + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/eventpoints_viewing.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/eventpoints_viewing.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/eventpoints_viewing.htm Thu May 20 13:57:30 2010 -0500 @@ -1,24 +1,24 @@ - - - - - - -Viewing Eventpoint Properties - - - -

Viewing Eventpoint Properties

After you set an eventpoint, you can view and modify its properties.

To view properties for an eventpoint

Select its name in the Breakpoints view
Click Breakpoints > Breakpoint Properties
-

- - - - + + + + + + +Viewing Eventpoint Properties + + + +

Viewing Eventpoint Properties

After you set an eventpoint, you can view and modify its properties.

To view properties for an eventpoint

Select its name in the Breakpoints view
Click Breakpoints > Breakpoint Properties
+

+ + + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/log_point_clear.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/log_point_clear.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/log_point_clear.htm Thu May 20 13:57:30 2010 -0500 @@ -1,30 +1,30 @@ - - - - - - -Log Point - - - -

Log Point

A Log Point logs or speaks a string or expression. A Log Point can also record messages to the Log window. You can configure the message that appears in the log window.

Related tasks

Clearing a Log Point

To clear a Log Point, follow these steps:

Select the Log Point that you want to clear.

Click the cursor on the line of source code that has the Log Point, or select the Log Point by name in the Breakpoints window.

Click Debug > Clear Eventpoint > Clear Log Point.

- - - + + + + + + +Log Point + + + +

Log Point

A Log Point logs or speaks a string or expression. A Log Point can also record messages to the Log window. You can configure the message that appears in the log window.

Related tasks

Clearing a Log Point

To clear a Log Point, follow these steps:

Select the Log Point that you want to clear.

Click the cursor on the line of source code that has the Log Point, or select the Log Point by name in the Breakpoints window.

Click Debug > Clear Eventpoint > Clear Log Point.

+ + + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/log_point_set.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/log_point_set.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/log_point_set.htm Thu May 20 13:57:30 2010 -0500 @@ -1,40 +1,40 @@ - - - - - - -Log Point - - - -

Log Point

A Log Point logs or speaks a string or expression. A Log Point can also record messages to the Log window. You can configure the message that appears in the log window.

Related tasks

Setting a Log Point

To set a Log Point, follow these steps:

Click the cursor on the line of source code at which you want to set the Log Point.
Click Debug > Set Eventpoint > Set Log Point.
Enter the text of your log message in the Message text box.
Check at least one of these checkboxes:

Log Message—check to have the IDE display your message in a Message window when program execution reaches the Log Point
Speak Message (Windows OS)—check to have the IDE use the sound capabilities of the host operating system to speak the message that you enter in the Message text box.

NOTE (Windows) Install the Speech software development kit (SDK) in order to have the Speak Message feature work correctly.

Treat as Expression—check to have the IDE evaluate the text you enter in the Message text box as an expression. For example, if you enter the name of a variable in the Message text, the debugger writes the value of that variable in the console output window.
Stop in Debugger—check to stop program execution in the debugger

Click the OK button to confirm your settings.

Example use: If you want to display the value of a variable each time some code is executed, set a log point, check the Log Message and Treat as expression boxes and enter the variable name in the edit box, then click OK.

- - - + + + + + + +Log Point + + + +

Log Point

A Log Point logs or speaks a string or expression. A Log Point can also record messages to the Log window. You can configure the message that appears in the log window.

Related tasks

Setting a Log Point

To set a Log Point, follow these steps:

Click the cursor on the line of source code at which you want to set the Log Point.
Click Debug > Set Eventpoint > Set Log Point.
Enter the text of your log message in the Message text box.
Check at least one of these checkboxes:

Log Message—check to have the IDE display your message in a Message window when program execution reaches the Log Point
Speak Message (Windows OS)—check to have the IDE use the sound capabilities of the host operating system to speak the message that you enter in the Message text box.

NOTE (Windows) Install the Speech software development kit (SDK) in order to have the Speak Message feature work correctly.

Treat as Expression—check to have the IDE evaluate the text you enter in the Message text box as an expression. For example, if you enter the name of a variable in the Message text, the debugger writes the value of that variable in the console output window.
Stop in Debugger—check to stop program execution in the debugger

Click the OK button to confirm your settings.

+ + + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/pause_point_clear.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/pause_point_clear.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/pause_point_clear.htm Thu May 20 13:57:30 2010 -0500 @@ -1,34 +1,34 @@ - - - - - - -Pause Point - - - -

Pause Point

A Pause Point suspends program execution long enough to refresh debugger data. For example, without setting a pause point, you must wait for the debugger to halt program execution before it can refresh data. Setting a Pause Point, however, lets you pause the debugging session to give the debugger time to refresh the data.

Related tasks

Setting a Log Point
Clearing a Log Point

Clearing a Pause Point

To clear a Pause Point, follow these steps:

Select the Pause Point that you want to clear.

Click the cursor on the line of source code that has the Pause Point, or select the Pause Point by name in the Breakpoints window.

Click Debug > Clear Eventpoint > Clear Pause Point.
-

- - - + + + + + + +Pause Point + + + +

Pause Point

Related tasks

Setting a Log Point
Clearing a Log Point

Clearing a Pause Point

To clear a Pause Point, follow these steps:

Select the Pause Point that you want to clear.

Click the cursor on the line of source code that has the Pause Point, or select the Pause Point by name in the Breakpoints window.

Click Debug > Clear Eventpoint > Clear Pause Point.
+

+ + + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/pause_point_set.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/pause_point_set.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/pause_point_set.htm Thu May 20 13:57:30 2010 -0500 @@ -1,32 +1,32 @@ - - - - - - -Pause Point - - - -

Pause Point

Related tasks

Setting a Log Point
Clearing a Log Point

Setting a Pause Point

To set a Pause Point, follow these steps:

Click the cursor on the line of source code at which you want to set the Pause Point.
Click Debug > Set Eventpoint > Set Pause Point.

- - - + + + + + + +Pause Point + + + +

Pause Point

Related tasks

Setting a Log Point
Clearing a Log Point

Setting a Pause Point

To set a Pause Point, follow these steps:

Click the cursor on the line of source code at which you want to set the Pause Point.
Click Debug > Set Eventpoint > Set Pause Point.

+ + + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/trace_collection_clear.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/trace_collection_clear.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/trace_collection_clear.htm Thu May 20 13:57:30 2010 -0500 @@ -1,25 +1,25 @@ - - - - - - -Clearing a Trace Collection - - - -

Clearing a Trace Collection

Clear a Trace Collection eventpoint when you are finished collecting trace data.

Clearing a Trace Collection On Eventpoint

To clear a Trace Collection eventpoint, follow these steps:

Select the Trace Collection eventpoint that you want to clear

Click the cursor on the line of source code that has the Trace Collection eventpoint, or select the Trace Collection eventpoint by name in the Breakpoints view.

Click Debug > Clear Eventpoint > Clear Trace Collection On

- - - - + + + + + + +Clearing a Trace Collection + + + +

Clearing a Trace Collection

Clear a Trace Collection eventpoint when you are finished collecting trace data.

Clearing a Trace Collection On Eventpoint

To clear a Trace Collection eventpoint, follow these steps:

Select the Trace Collection eventpoint that you want to clear

Click the cursor on the line of source code that has the Trace Collection eventpoint, or select the Trace Collection eventpoint by name in the Breakpoints view.

Click Debug > Clear Eventpoint > Clear Trace Collection On

+ + + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/trace_collection_off.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/trace_collection_off.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/trace_collection_off.htm Thu May 20 13:57:30 2010 -0500 @@ -1,24 +1,24 @@ - - - - - - -Trace Collection Off - - - -

Trace Collection Off

A Trace Collection Off eventpoint stops the collection of trace data. This eventpoint is useful when you want trace collection to stop when program execution reaches a line of source code that you specify.

Setting a Trace Collection Off Eventpoint

To set a Trace Collection Off eventpoint, follow these steps:

Click the cursor on the line of source code at which you want to set the Trace Collection Off eventpoint
Click Debug > Set Eventpoint > Set Trace Collection Off

- - - - + + + + + + +Trace Collection Off + + + +

Trace Collection Off

Setting a Trace Collection Off Eventpoint

To set a Trace Collection Off eventpoint, follow these steps:

Click the cursor on the line of source code at which you want to set the Trace Collection Off eventpoint
Click Debug > Set Eventpoint > Set Trace Collection Off

+ + + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/trace_collection_on.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/trace_collection_on.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/trace_collection_on.htm Thu May 20 13:57:30 2010 -0500 @@ -1,24 +1,24 @@ - - - - - - -Trace Collection On - - - -

Trace Collection On

A Trace Collection On eventpoint starts the collection of trace data. This eventpoint is useful when you want trace collection to start when program execution reaches a line of source code that you specify.

Setting a Trace Collection On Eventpoint

To set a Trace Collection On eventpoint, follow these ssteps:

Click the cursor on the line of source code at which you want to set the Trace Collection On eventpoint
Click Debug > Set Eventpoint > Set Trace Collection On

- - - - + + + + + + +Trace Collection On + + + +

Trace Collection On

Setting a Trace Collection On Eventpoint

To set a Trace Collection On eventpoint, follow these ssteps:

Click the cursor on the line of source code at which you want to set the Trace Collection On eventpoint
Click Debug > Set Eventpoint > Set Trace Collection On

+ + + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/index.html --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/index.html Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/index.html Thu May 20 13:57:30 2010 -0500 @@ -1,59 +1,59 @@ - -Tasks in Symbian OS Eclipse Development User Guide - - - -

- - - -

Tasks

- - -

- 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 - performing each task. -

- To develop a program requires that you have installed one or more - development kits. The Working with SDKs tasks describes the - tasks for setting up and selecting the kits to use with your project. -

- 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 - file. -

- You can either import a - bld.inf file, in which case all the projects specified in that - component are imported, or import a single - mmp file. The two cases are discussed separately below. -

- 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 for application information - files (AIF) and multi-bitmap files (MBM), as described in Modifying - Resources. -

- - - - - -

- + +Tasks in Symbian OS Eclipse Development User Guide + + + +

+ + + +

Tasks

+ + +

+ 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 + performing each task. +

+ To develop a program requires that you have installed one or more + development kits. The Working with SDKs tasks describes the + tasks for setting up and selecting the kits to use with your project. +

+ 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 + file. +

+ You can either import a + bld.inf file, in which case all the projects specified in that + component are imported, or import a single + mmp file. The two cases are discussed separately below. +

+ 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 for application information + files (AIF) and multi-bitmap files (MBM), as described in Modifying + Resources. +

+ + + + + +

+ \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/memory/memory_monitor_adding.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/memory/memory_monitor_adding.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/memory/memory_monitor_adding.htm Thu May 20 13:57:30 2010 -0500 @@ -1,57 +1,57 @@ - - - - - - -Adding a Memory Monitor - - - -

Adding a Memory Monitor

You can add one or more memory monitors to the Memory view. A memory monitor shows the contents of a different address or expression.

NOTE When using an emulator, the memory addresses are actually based on their location and formats dependent upon the host machine.

To add a Memory Monitor

Open a new memory monitor by: -
- Click the Add Memory Monitor () icon in the Monitors pane
- Right-click in the Monitors pane, then select Add Memory Monitor
- Right-click a variable in the Variables view, then select View Memory
-

The Add Memory Monitor window appears (Figure 1).

Figure 1 - Memory Monitor window

Enter the address or expression to monitor

Type the address or expression that specifies the memory section to monitor. Acceptable formats include:

Address -- *ptr
Expression -- (&y)+1024
Functions -- FNname
Hexadecimal -- 0x0847d3c
Variables -- &VarName

Click OK

The monitor appears in the monitor list and the Memory Renderings pane displays the contents of memory locations beginning at the specified address.

Related concepts

Working with Memory

Related tasks

Related References

Memory View

- - - - + + + + + + +Adding a Memory Monitor + + + +

Adding a Memory Monitor

You can add one or more memory monitors to the Memory view. A memory monitor shows the contents of a different address or expression.

NOTE When using an emulator, the memory addresses are actually based on their location and formats dependent upon the host machine.

To add a Memory Monitor

Open a new memory monitor by: +
- Click the Add Memory Monitor () icon in the Monitors pane
- Right-click in the Monitors pane, then select Add Memory Monitor
- Right-click a variable in the Variables view, then select View Memory
+

The Add Memory Monitor window appears (Figure 1).

Figure 1 - Memory Monitor window

Enter the address or expression to monitor

Type the address or expression that specifies the memory section to monitor. Acceptable formats include:

Address -- *ptr
Expression -- (&y)+1024
Functions -- FNname
Hexadecimal -- 0x0847d3c
Variables -- &VarName

Click OK

The monitor appears in the monitor list and the Memory Renderings pane displays the contents of memory locations beginning at the specified address.

Related concepts

Working with Memory

Related tasks

Related References

Memory View

+ + + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/memory/memory_monitor_removing.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/memory/memory_monitor_removing.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/memory/memory_monitor_removing.htm Thu May 20 13:57:30 2010 -0500 @@ -1,59 +1,59 @@ - - - - - - -Removing a Memory Monitor or Rendering - - - - -

Removing a Memory Monitor or Rendering

Remove a memory monitor or rendering when you have finished working with it.

To remove a Memory Monitor

Right-click the memory monitor and select Remove Memory Monitor

-
OR
-

Select the memory monitor to remove, click the Remove Rendering Monitor () button -
The Memory Monitor item is removed.

To remove a Memory Rendering

Select the memory rendering to remove
Click the Remove Memory Rendering () button

The Memory Rendering pane is removed.

Related concepts

Working with Memory

Related tasks

Related References

Memory View -

- - - - + + + + + + +Removing a Memory Monitor or Rendering + + + + +

Removing a Memory Monitor or Rendering

Remove a memory monitor or rendering when you have finished working with it.

To remove a Memory Monitor

Right-click the memory monitor and select Remove Memory Monitor

+
OR
+

Select the memory monitor to remove, click the Remove Rendering Monitor () button +
The Memory Monitor item is removed.

To remove a Memory Rendering

Select the memory rendering to remove
Click the Remove Memory Rendering () button

The Memory Rendering pane is removed.

Related concepts

Working with Memory

Related tasks

Related References

Memory View +

+ + + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/memory/memory_rendering_adding.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/memory/memory_rendering_adding.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/memory/memory_rendering_adding.htm Thu May 20 13:57:30 2010 -0500 @@ -1,50 +1,50 @@ - - - - - - -Adding a Memory Monitor - - - -

Adding a Memory Rendering

Add a memory rendering pane to display the memory monitor item in different formats. The formats available include:

Traditional
Hex
ASCII
Signed Integer
Unsigned Integer

Use the Add New button to choose a different memory monitor item.

To add a Memory Rendering

Right-click the Memory Renderings pane and select Add Rendering or click the Add Rendering(s) () button

The Add Memory Rendering dialog appears (Figure 1).

Figure 1 - Add Memory Rendering dialog

Select the type of memory rendering to display in the memory monitor
Click OK

The Memory Renderings pane displays a new tab of the memory monitor item using the specified format.

Related concepts

Working with Memory

Related tasks

Related References

Memory View

- - - - + + + + + + +Adding a Memory Monitor + + + +

Adding a Memory Rendering

Add a memory rendering pane to display the memory monitor item in different formats. The formats available include:

Traditional
Hex
ASCII
Signed Integer
Unsigned Integer

Use the Add New button to choose a different memory monitor item.

To add a Memory Rendering

Right-click the Memory Renderings pane and select Add Rendering or click the Add Rendering(s) () button

The Add Memory Rendering dialog appears (Figure 1).

Figure 1 - Add Memory Rendering dialog

Select the type of memory rendering to display in the memory monitor
Click OK

The Memory Renderings pane displays a new tab of the memory monitor item using the specified format.

Related concepts

Working with Memory

Related tasks

Related References

Memory View

+ + + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/memory/view_memory_show.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/memory/view_memory_show.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/memory/view_memory_show.htm Thu May 20 13:57:30 2010 -0500 @@ -1,38 +1,38 @@ - - - - - - -Opening the Memory View - - - -

Opening a Memory View

Use the Memory view to examine a portion of memory starting at a specific address on the host machine.

NOTE When using an emulator, the memory addresses are actually based on their location and formats dependent upon the host machine.

To open a Memory view

Click Window > Show View > Memory

The Memory view appears.

Related concepts

Working with Memory

Related tasks

Related References

Memory View

- - - - + + + + + + +Opening the Memory View + + + +

Opening a Memory View

Use the Memory view to examine a portion of memory starting at a specific address on the host machine.

NOTE When using an emulator, the memory addresses are actually based on their location and formats dependent upon the host machine.

To open a Memory view

Click Window > Show View > Memory

The Memory view appears.

Related concepts

Working with Memory

Related tasks

Related References

Memory View

+ + + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/opening_system_browser.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/opening_system_browser.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/opening_system_browser.htm Thu May 20 13:57:30 2010 -0500 @@ -1,33 +1,33 @@ - - - - - - -Opening the System Browser View - - - -

Opening the System Browser View

Use the System Views or System menu command to view and manipulate active processes on a selected machine. If multiple machines are available, select each machine from the System Views submenu to display multiple System Browser windows. If you choose a machine that is already open, the existing window will be brought to the front.

NOTE The System Browser view appears on platforms that support it.

-Table 1 explains how to open the System Browser view. -

Table 1 Opening the System Browser view

- - - - - - - - - - - - - -

Menu Bar Layout	Do this…
Views	Select View > System
Macintosh (also applies to Linux/Solaris)	Select View > System Views

- - - + + + + + + +Opening the System Browser View + + + +

Opening the System Browser View

NOTE The System Browser view appears on platforms that support it.

+Table 1 explains how to open the System Browser view. +

Table 1 Opening the System Browser view

+ + + + + + + + + + + + + +

Menu Bar Layout	Do this…
Views	Select View > System
Macintosh (also applies to Linux/Solaris)	Select View > System Views

+ + + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 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 Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_adding_symbian_class.htm Thu May 20 13:57:30 2010 -0500 @@ -40,7 +40,7 @@

Adding Classes

New C++ Classs Wizard

- + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 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 Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_build_cmd_line.htm Thu May 20 13:57:30 2010 -0500 @@ -1,48 +1,48 @@ - - - - - - -Setting Environment for x86 Compiler - - - - -

Setting Environment for x86 Compiler

You can build files and projects using the Carbide.c++ command-line tools.

The command-line tools are located in the plugins\x86Build folder and include:

\env_switch - contains the env_update.exe program which installs the environment variables used by the command-line tools. You must run the env_update.exe program before any of the command-line tools can operate. It is not required to run if building from Carbide.
\Symbian_Support - contains the libraries, headers, and other support files necessary to use the command-line toosl
\Symbian_Tools - contains the command-line tools compile (mwccsym2.exe), assembler (mwc++filt.exe), and linker (mwldsym2.exe) project files

Running a Command-Line Tool

Locate and launch env_update.exe to install the environment variables required by the command-line tools

Follow the onscreen instructions to install the correct environment variables.

In the Command Prompt window, enter the tool name and options to invoke the command-line tool

Concepts

Projects

Tasks

- - - + + + + + + +Setting Environment for x86 Compiler + + + + +

Setting Environment for x86 Compiler

You can build files and projects using the Carbide.c++ command-line tools.

The command-line tools are located in the plugins\x86Build folder and include:

\env_switch - contains the env_update.exe program which installs the environment variables used by the command-line tools. You must run the env_update.exe program before any of the command-line tools can operate. It is not required to run if building from Carbide.
\Symbian_Support - contains the libraries, headers, and other support files necessary to use the command-line toosl
\Symbian_Tools - contains the command-line tools compile (mwccsym2.exe), assembler (mwc++filt.exe), and linker (mwldsym2.exe) project files

Running a Command-Line Tool

Locate and launch env_update.exe to install the environment variables required by the command-line tools

Follow the onscreen instructions to install the correct environment variables.

In the Command Prompt window, enter the tool name and options to invoke the command-line tool

Concepts

Projects

Tasks

+ + + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_build_multi_projects.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_build_multi_projects.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_build_multi_projects.htm Thu May 20 13:57:30 2010 -0500 @@ -1,38 +1,38 @@ - - - - - - - Building Multiple Projects - - - -

Importing Projects With Inter-Dependencies

-If you are building a project that had external project dependencies, -such as an import library from a DLL you must make sure the projects -are built in the correct order to avoid missing dependencies.
-
-The best way to do this is to import projects with a bld.inf file. For -example, if you are building an executable that relies on a static -DLL's import library you need to build the project that generates -the import library first. If a project contains a bld.inf file -that contains all the required project MMP files you should import via -the INF file. Building projects after importing with INF files will -insure that other project dependencies get built properly.
-

Concepts

Projects

Tasks

- - - + + + + + + + Building Multiple Projects + + + +

Importing Projects With Inter-Dependencies

+If you are building a project that had external project dependencies, +such as an import library from a DLL you must make sure the projects +are built in the correct order to avoid missing dependencies.
+
+The best way to do this is to import projects with a bld.inf file. For +example, if you are building an executable that relies on a static +DLL's import library you need to build the project that generates +the import library first. If a project contains a bld.inf file +that contains all the required project MMP files you should import via +the INF file. Building projects after importing with INF files will +insure that other project dependencies get built properly.
+

Concepts

Projects

Tasks

+ + + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 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 Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_clean.htm Thu May 20 13:57:30 2010 -0500 @@ -1,32 +1,32 @@ - - - - - - -Building Projects - - - -

Cleaning Projects

In the Project Explorer, C/C++ Projects, 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... a Clean dialog will appear (Figure 1). You can clean all projects or select individual projects to clean. 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 Dialog

By default, performing a Clean Project complies with the global Clean level settings in the Build preference panel and inherited by the project on creation. You can also assign project specific clean settings in the Carbide Project Settings panel in the Properties for <project> dialog.

Concepts

Projects

Tasks

- - - + + + + + + +Building Projects + + + +

Cleaning Projects

Figure 1 - Clean Project Dialog

Concepts

Projects

Tasks

+ + + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 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 Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_dlls.htm Thu May 20 13:57:30 2010 -0500 @@ -1,32 +1,32 @@ - - - - - - -Importing Executables for Debugging - - - -

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.

-
NOTE Breakpoints inside a DLL will not be 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.

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

Other references

- - - + + + + + + +Importing Executables for Debugging + + + +

Debugging DLLs

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 will not be 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.

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

Other references

+ + + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_multiple_projects.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_multiple_projects.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_multiple_projects.htm Thu May 20 13:57:30 2010 -0500 @@ -25,7 +25,7 @@

Importing Executables for Debugging

Working with SDKs

- + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_freeze_def_file.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_freeze_def_file.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_freeze_def_file.htm Thu May 20 13:57:30 2010 -0500 @@ -1,32 +1,32 @@ - - - - - - -Freezing DLL Projects - - - -

Freezing DLL Projects

Use the Project > Freeze Exports menu command to freeze a entire project, normally a DLL, to ensure backward compatibility of a new release. The result is a .def file that can be imported into other projects. You cannot freeze a single file of the project, only the entire project. Also, once a project is frozen, only new exports can be added.

NOTE A .def file must be included in the project target to export a project. The IDE will not create one if it is missing.

Freezing an Active Project

Select the Project > Freeze Exports menu item or Right-click and select Freeze Exports from the context menu

The appropriate abld command is called in the background and a .def file is generated that can be imported into other projects.

Related concepts

Projects

Related tasks

Importing Projects

- - - + + + + + + +Freezing DLL Projects + + + +

Freezing DLL Projects

NOTE A .def file must be included in the project target to export a project. The IDE will not create one if it is missing.

Freezing an Active Project

Select the Project > Freeze Exports menu item or Right-click and select Freeze Exports from the context menu

The appropriate abld command is called in the background and a .def file is generated that can be imported into other projects.

Related concepts

Projects

Related tasks

Importing Projects

+ + + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_import_exe.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_import_exe.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_import_exe.htm Thu May 20 13:57:30 2010 -0500 @@ -1,56 +1,56 @@ - - - - - - -Importing a Symbian Executable - - - -

Importing a Symbian Executable

Use the File > Import > Symbian OS Executable feature to import an executable into the Executables view and debug it. This is useful when the binary is not part of any project in the workspace. An example of this may be a library that is called from an mmp file. The binary must be built with the same build configuration as the current build configuration that is being used (compiler must be the same).

NOTE You also need the symbolics (.sym) file for debugging ARM build configurations.

NOTE Binaries built by the project can be debugged by selecting executables to debug in the Executable tab of the launch configuration Debug window.

To import a Symbian Executable

Select the File > Import... menu item

The Import window appears (Figure 1).

Figure 1 - Import window

Expand Symbian OS and select Symbian OS Executable in the list, then click Next

The Import Executable window appears (Figure 2).

Enter the executable name in the Select Executable field or click Browse to locate the executable

Use the Select executable field to choose a single executable or Search directory field to select one or more Symbian executables to import from the specified directory.

Figure 2 - Import Executable window

Click Finish

The IDE imports the Symbian executable and displays it in the Executables view (figure 3).

Figure 3 - Executables view showing executable and source files

The new project is listed under the Project Explorer view, as shown in Figure 4.

Figure 4 - New executable listed

Related concepts

Projects
Project Resources

Related tasks

Related references

Project Directories
Executables view

- - - - + + + + + + +Importing a Symbian Executable + + + +

Importing a Symbian Executable

NOTE You also need the symbolics (.sym) file for debugging ARM build configurations.

NOTE Binaries built by the project can be debugged by selecting executables to debug in the Executable tab of the launch configuration Debug window.

To import a Symbian Executable

Select the File > Import... menu item

The Import window appears (Figure 1).

Figure 1 - Import window

Expand Symbian OS and select Symbian OS Executable in the list, then click Next

The Import Executable window appears (Figure 2).

Enter the executable name in the Select Executable field or click Browse to locate the executable

Use the Select executable field to choose a single executable or Search directory field to select one or more Symbian executables to import from the specified directory.

Figure 2 - Import Executable window

Click Finish

The IDE imports the Symbian executable and displays it in the Executables view (figure 3).

Figure 3 - Executables view showing executable and source files

The new project is listed under the Project Explorer view, as shown in Figure 4.

Figure 4 - New executable listed

Related concepts

Projects
Project Resources

Related tasks

Related references

Project Directories
Executables view

+ + + + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_new_build_config.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_new_build_config.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_new_build_config.htm Thu May 20 13:57:30 2010 -0500 @@ -1,40 +1,40 @@ - - - - - - -Adding/Removing Build Configurations - - - -

Adding/Removing Build Configurations

Use the Properties for <project_name> window to manage the active or build configurations associated with a project. In the Active Configuration group you can select which build configuration is current active as well as choose which build configurations appear in the Build Configurations sub-menu as choices.

Adding/Removing a Build Configuration

Open Carbide Build Configuration panel in the project's Properties window -
Select the Project > Properties menu item or right-click the project name in the Project Explorer view, then select Properties. The project Properties for <project_name> window appears. Then select Carbide Build Configurations.
-
-
Figure 1 - Active Configuration group in project Properties window
Click Manage... in the Active Configuration group (Figure 1) -
The Add/Remove Carbide Build Configuration window appears (Figure 2). Use the Add/Remove Carbide Build Configuration window to manage the build configurations that appear on the Build Configurations sub-menu for the current project. You can also click the Manage configurations for the current project icon () on the toolbar to open this dialog.
-
-
-
Figure 2 - Window for managing build configurations
-

Related concepts

Active Configuration

Related tasks

Setting an Active Configuration

- - - - + + + + + + +Adding/Removing Build Configurations + + + +

Adding/Removing Build Configurations

Adding/Removing a Build Configuration

Open Carbide Build Configuration panel in the project's Properties window +
Select the Project > Properties menu item or right-click the project name in the Project Explorer view, then select Properties. The project Properties for <project_name> window appears. Then select Carbide Build Configurations.
+
+
Figure 1 - Active Configuration group in project Properties window
Click Manage... in the Active Configuration group (Figure 1) +
The Add/Remove Carbide Build Configuration window appears (Figure 2). Use the Add/Remove Carbide Build Configuration window to manage the build configurations that appear on the Build Configurations sub-menu for the current project. You can also click the Manage configurations for the current project icon () on the toolbar to open this dialog.
+
+
+
Figure 2 - Window for managing build configurations
+

Related concepts

Active Configuration

Related tasks

Setting an Active Configuration

+ + + + diff -r c70ff7f19887 -r d1b0b4e203e9 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 Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_preprocess.htm Thu May 20 13:57:30 2010 -0500 @@ -1,24 +1,24 @@ - - - - - - -Preprocessing Files - - - -

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.

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

Other references

Projects
Preprocess Preferences

- - - + + + + + + +Preprocessing Files + + + +

Preprocessing Files

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

Other references

Projects
Preprocess Preferences

+ + + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_set_build_tgt.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_set_build_tgt.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_set_build_tgt.htm Thu May 20 13:57:30 2010 -0500 @@ -1,64 +1,64 @@ - - - - - - -Setting an Active Configuration - - - -

Setting an Active Configuration

If you have more than one build configuration in a project, use the Manage configurations icon on the toolbar or the Build Configuration menu item to select the build target used to create executables. The active build target is indicated by a check mark.

Setting the Active Configuration

From the - toolbar -
1. Select the project in the Project Explorer or C/C++ Projects view
2. In the toolbar click Manage configurations for the current project control () > configuration_name
-
-
From the Project menu -
- Click Project > Build Configurations > Set Active > configuration_name
-

-

- Figure 2 - Build Configuration menu
-

From the project's context menu -
- Right-click the project name, click Build Configurations > Set Active > configuration_name
-
From the Properties for <project_name> window -
1. Right-click the project name, select Properties
2. Select Carbide.c++ > Carbide Build Configurations panel
3. Select the active build configuration from the Active Configuration dropdown list
4. Click Apply
-

The IDE uses the chosen build configuration as its build target.

Related concepts

Active Configuration

Related tasks

Adding/Removing Build Configurations

- - - + + + + + + +Setting an Active Configuration + + + +

Setting an Active Configuration

Setting the Active Configuration

From the + toolbar +
1. Select the project in the Project Explorer or C/C++ Projects view
2. In the toolbar click Manage configurations for the current project control () > configuration_name
+
+
From the Project menu +
- Click Project > Build Configurations > Set Active > configuration_name
+

+

+ Figure 2 - Build Configuration menu
+

From the project's context menu +
- Right-click the project name, click Build Configurations > Set Active > configuration_name
+
From the Properties for <project_name> window +
1. Right-click the project name, select Properties
2. Select Carbide.c++ > Carbide Build Configurations panel
3. Select the active build configuration from the Active Configuration dropdown list
4. Click Apply
+

The IDE uses the chosen build configuration as its build target.

Related concepts

Active Configuration

Related tasks

Adding/Removing Build Configurations

+ + + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 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 Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/working_with_sis_pkg_files.htm Thu May 20 13:57:30 2010 -0500 @@ -47,7 +47,7 @@

SIS Builder pane

SIS Properties

- + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/registers/mem_reg_changing.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/registers/mem_reg_changing.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/registers/mem_reg_changing.htm Thu May 20 13:57:30 2010 -0500 @@ -1,41 +1,41 @@ - - - - - - -Changing Register Values - - - -

Changing Register Values

You can change register values in the Registers view during program execution in order to examine program behavior.

NOTE Changing a register value can cause unpredictable behavior in the running program.

Changing a Register Value

Right-click the value in the Registers view and select Change Value -
-
Figure 1 - Right-click register value to change
-
The Set Value window appears (Figure 2).
-
-
Figure 2 - Set Value window
-
-
Enter a new register value
-
Press OK

The register value changes in the Register view

Other references

- - - - + + + + + + +Changing Register Values + + + +

Changing Register Values

You can change register values in the Registers view during program execution in order to examine program behavior.

NOTE Changing a register value can cause unpredictable behavior in the running program.

Changing a Register Value

Right-click the value in the Registers view and select Change Value +
+
Figure 1 - Right-click register value to change
+
The Set Value window appears (Figure 2).
+
+
Figure 2 - Set Value window
+
+
Enter a new register value
+
Press OK

The register value changes in the Register view

Other references

+ + + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/registers/mem_reg_data_views.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/registers/mem_reg_data_views.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/registers/mem_reg_data_views.htm Thu May 20 13:57:30 2010 -0500 @@ -1,42 +1,42 @@ - - - - - - -Changing Register Data Views - - - -

Changing Register Data Views

You can change the register data in the Registers view to see register contents in a different format. For example, you can change the view of a register from binary to hexadecimal format.

To change register data views

Open a Registers view
Expand the hierarchical list to view the names and corresponding values of the register
Select the register value that you want to view in a different format

The value highlights.

Select Data > View as format, where format is the data format in which you want to view the register value. The register value changes format

Available formats depend on the selected register value.

Select Data > View as Default to restore the original data format

Related concepts

Registers

Related tasks

Related references

Registers View

- - - - + + + + + + +Changing Register Data Views + + + +

Changing Register Data Views

You can change the register data in the Registers view to see register contents in a different format. For example, you can change the view of a register from binary to hexadecimal format.

To change register data views

Open a Registers view
Expand the hierarchical list to view the names and corresponding values of the register
Select the register value that you want to view in a different format

The value highlights.

Select Data > View as format, where format is the data format in which you want to view the register value. The register value changes format

Available formats depend on the selected register value.

Select Data > View as Default to restore the original data format

Related concepts

Registers

Related tasks

Related references

Registers View

+ + + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/registers/mem_reg_open_wnd.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/registers/mem_reg_open_wnd.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/registers/mem_reg_open_wnd.htm Thu May 20 13:57:30 2010 -0500 @@ -1,33 +1,33 @@ - - - - - - -Opening a Registers View - - - -

Opening a Registers View

Open the Registers view to inspect and modify various register contents.

NOTE When using an emulator, the registers shown are those of the x86 processor on the host machine, not that of the target device.

To open a Registers view

Click Window > Show View > Registers

Registers view appears in the current perspective.

Figure 1 - Registers view

Other references

- - - - + + + + + + +Opening a Registers View + + + +

Opening a Registers View

Open the Registers view to inspect and modify various register contents.

NOTE When using an emulator, the registers shown are those of the x86 processor on the host machine, not that of the target device.

To open a Registers view

Click Window > Show View > Registers

Registers view appears in the current perspective.

Figure 1 - Registers view

Other references

+ + + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/registers/mem_reg_viewing.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/registers/mem_reg_viewing.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/registers/mem_reg_viewing.htm Thu May 20 13:57:30 2010 -0500 @@ -28,7 +28,7 @@

Changing Register Values

Registers View

- + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/sdks/sdk_add.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/sdks/sdk_add.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/sdks/sdk_add.htm Thu May 20 13:57:30 2010 -0500 @@ -67,7 +67,7 @@

SDK Preferences Panel

- + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/sdks/sdk_add_custkits.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/sdks/sdk_add_custkits.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/sdks/sdk_add_custkits.htm Thu May 20 13:57:30 2010 -0500 @@ -36,7 +36,7 @@

Working with SDKs

- + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/sdks/sdk_platform_filter.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/sdks/sdk_platform_filter.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/sdks/sdk_platform_filter.htm Thu May 20 13:57:30 2010 -0500 @@ -103,7 +103,7 @@

Working with SDKs

SDK Preferences Panel

- + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/sdks/sdk_search.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/sdks/sdk_search.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/sdks/sdk_search.htm Thu May 20 13:57:30 2010 -0500 @@ -30,7 +30,7 @@

View SDK Properties

SDK Preferences Panel

- + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 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 Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/sdks/sdk_view_properties.htm Thu May 20 13:57:30 2010 -0500 @@ -31,7 +31,7 @@

Searching SDKs

SDK Preferences Panel

- + diff -r c70ff7f19887 -r d1b0b4e203e9 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 Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_deploying.htm Thu May 20 13:57:30 2010 -0500 @@ -1,47 +1,47 @@ - - - - - - -Deploying Programs - - - -

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 Nokia PC 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.

Deploying .sis Files

Launch the phone’s Symbian Connect program
Select the method of connection

In this step you select the form of the serial connection to use, USB, Irda, Bluetooth, etc.

Select the .sis file to upload

NOTE Double-clicking the .sis file should launch the phone's Symbian Connect software.

Upload the .sis file using the Symbian Connect software
Install the program on the target device

To make the program available on the target device, you must install the program - stored in the.sis file. Try double-clicking the .sis file on the phone to install it. If that doesn't work try selecting Install from the phone's menu, - selecting the program name, then clicking Install.

Congratulations, you’ve now successfully uploaded a .sis file to your -target device.

Concepts

Projects

Tasks

- - - + + + + + + +Deploying Programs + + + +

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.

Deploying .sis Files

Launch the phone’s Symbian Connect program
Select the method of connection

In this step you select the form of the serial connection to use, USB, Irda, Bluetooth, etc.

Select the .sis file to upload

NOTE Double-clicking the .sis file should launch the phone's Symbian Connect software.

Upload the .sis file using the Symbian Connect software
Install the program on the target device

To make the program available on the target device, you must install the program + stored in the.sis file. Try double-clicking the .sis file on the phone to install it. If that doesn't work try selecting Install from the phone's menu, + selecting the program name, then clicking Install.

Congratulations, you’ve now successfully uploaded a .sis file to your +target device.

Concepts

Projects

Tasks

+ + + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 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 Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_example.htm Thu May 20 13:57:30 2010 -0500 @@ -1,24 +1,24 @@ - - - - - - -Application Emulator Debug Example using Templates - - - -

Application Emulator Debug Example using Templates

This example shows how to create, build, and debug a program for the emulator called HelloCarbide using Carbide project templates. Once debugged, you can create a new build compiled to run on a target device. If the Carbide.c++ edition you are using supports on-device debugging, then Carbide.c++ deploys the program to the target device automatically. The steps include:

Creating a project using Carbide project templates
Building an executable of the project sources
Defining a run/debug launch configuration to provide additional information to the debugger
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 SDK Preferences 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.

- - - + + + + + + +Application Emulator Debug Example using Templates + + + +

Application Emulator Debug Example using Templates

Creating a project using Carbide project templates
Building an executable of the project sources
Defining a run/debug launch configuration to provide additional information to the debugger
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 SDK Preferences 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.

+ + + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 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 Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_example_trk.htm Thu May 20 13:57:30 2010 -0500 @@ -66,7 +66,7 @@

On-device Debugging Troubleshooting

Symbian OS View

- + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_help.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_help.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_help.htm Thu May 20 13:57:30 2010 -0500 @@ -25,7 +25,7 @@

Carbide.c++ Overview

- + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_overview.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_overview.htm Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_overview.htm Thu May 20 13:57:30 2010 -0500 @@ -17,7 +17,7 @@

Carbide Help

Updating Carbide

- + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 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 Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_overview_trk.htm Thu May 20 13:57:30 2010 -0500 @@ -1,45 +1,45 @@ - - - - - - -Run Mode Overview - - - - -

Run Mode Overview

This example shows how to create and build an application and debug it on a device using the Application TRK 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 SDK preferences panel.
Create a project by importing a Bld.inf
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 Application TRK)
- 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 TRK on-device debug agent on the device
Create a Symbian OS Application TRK 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

Related references

- - - - + + + + + + +Run Mode Overview + + + + +

Run Mode Overview

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 SDK preferences panel.
Create a project by importing a Bld.inf
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 Application TRK)
- 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 TRK on-device debug agent on the device
Create a Symbian OS Application TRK 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

Related references

+ + + + diff -r c70ff7f19887 -r d1b0b4e203e9 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 Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_updating.htm Thu May 20 13:57:30 2010 -0500 @@ -50,7 +50,7 @@

Carbide.c++ Overview

- + diff -r c70ff7f19887 -r d1b0b4e203e9 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 Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_carbide_setup.htm Thu May 20 13:57:30 2010 -0500 @@ -47,6 +47,6 @@

Debug Window (On-device Debugging) Overview

Creating a Launch Configuration

- + diff -r c70ff7f19887 -r d1b0b4e203e9 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 Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_bluetooth.htm Thu May 20 13:57:30 2010 -0500 @@ -47,7 +47,7 @@

Connecting via Bluetooth

Connecting via USB

- + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 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 Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_install_usb.htm Thu May 20 13:57:30 2010 -0500 @@ -49,7 +49,7 @@

Connecting via Bluetooth

Connecting via USB

- + \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 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 Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/trk/trk_troubleshooting.htm Thu May 20 13:57:30 2010 -0500 @@ -119,7 +119,7 @@

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.

- + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp/.project --- a/core/com.nokia.carbide.cpp/.project Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp/.project Thu May 20 13:57:30 2010 -0500 @@ -20,6 +20,11 @@ + + org.eclipse.pde.ds.core.builder + + + org.eclipse.pde.PluginNature diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp/META-INF/MANIFEST.MF --- a/core/com.nokia.carbide.cpp/META-INF/MANIFEST.MF Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp/META-INF/MANIFEST.MF Thu May 20 13:57:30 2010 -0500 @@ -18,3 +18,4 @@ Bundle-ActivationPolicy: lazy Export-Package: com.nokia.carbide.cpp, com.nokia.carbide.cpp.logging +Service-Component: component.xml diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp/build.properties --- a/core/com.nokia.carbide.cpp/build.properties Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp/build.properties Thu May 20 13:57:30 2010 -0500 @@ -1,4 +1,3 @@ -source.. = src/ output.. = bin/ bin.includes = META-INF/,\ .,\ @@ -19,8 +18,8 @@ nokiaTOC.xml,\ introDATA.xml,\ themes/,\ - book.css -bin.excludes = src/com/nokia/carbide/cpp/cs/ + book.css,\ + component.xml src.includes = META-INF/,\ about.html,\ about.ini,\ @@ -40,3 +39,5 @@ introDATA.xml,\ themes/,\ book.css +source.. = src/ +bin.excludes = src/com/nokia/carbide/cpp/cs/ diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp/component.xml --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/core/com.nokia.carbide.cpp/component.xml Thu May 20 13:57:30 2010 -0500 @@ -0,0 +1,8 @@ + + + + + + + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp/plugin.properties --- a/core/com.nokia.carbide.cpp/plugin.properties Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp/plugin.properties Thu May 20 13:57:30 2010 -0500 @@ -16,4 +16,12 @@ theme.name.carbide = Carbide carbcPreference.common=carbide symbian cpp cplusplus -carbcPreference.diagnostics=diagnostic logs \ No newline at end of file +carbcPreference.diagnostics=diagnostic logs + +PreferencePages.Capabilities = Capabilities +PreferencePages.Capabilities.activityName = &Capabilities +PreferencePages.Capabilities.categoryName = &Capabilities +PreferencePages.Capabilities.activityPromptButton = &Prompt when enabling capabilities +PreferencePages.Capabilities.activityPromptButtonTooltip = Prompt when a feature is first used that requires enablement of capabilities +PreferencePages.Capabilities.captionMessage = Capabilities allow you to enable or disable various product components. These capabilities are grouped according to a set of predefined categories. + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp/plugin.xml --- a/core/com.nokia.carbide.cpp/plugin.xml Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp/plugin.xml Thu May 20 13:57:30 2010 -0500 @@ -66,7 +66,7 @@ + value="0,244,469,22" /> @@ -570,4 +570,20 @@ + + + + + + + + + + + + diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp/src/com/nokia/carbide/cpp/ProductPlugin.java --- a/core/com.nokia.carbide.cpp/src/com/nokia/carbide/cpp/ProductPlugin.java Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.cpp/src/com/nokia/carbide/cpp/ProductPlugin.java Thu May 20 13:57:30 2010 -0500 @@ -16,11 +16,9 @@ */ package com.nokia.carbide.cpp; -import org.eclipse.ui.plugin.*; -import org.eclipse.equinox.p2.ui.Policy; import org.eclipse.jface.resource.ImageDescriptor; +import org.eclipse.ui.plugin.AbstractUIPlugin; import org.osgi.framework.BundleContext; -import org.osgi.framework.ServiceRegistration; /** * The main plugin class to be used in the desktop. @@ -30,8 +28,6 @@ //The shared instance. private static ProductPlugin plugin; - private ServiceRegistration policyRegistration; - /** * The constructor. */ @@ -44,16 +40,12 @@ */ public void start(BundleContext context) throws Exception { super.start(context); - Policy policy = new Policy(); - policy.setRestartPolicy(Policy.RESTART_POLICY_PROMPT); - policyRegistration = context.registerService(Policy.class.getName(), policy, null); } /** * This method is called when the plug-in is stopped */ public void stop(BundleContext context) throws Exception { - policyRegistration.unregister(); super.stop(context); plugin = null; } diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.cpp/src/com/nokia/carbide/cpp/p2/CarbideP2Policy.java --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/core/com.nokia.carbide.cpp/src/com/nokia/carbide/cpp/p2/CarbideP2Policy.java Thu May 20 13:57:30 2010 -0500 @@ -0,0 +1,12 @@ +package com.nokia.carbide.cpp.p2; + +import org.eclipse.equinox.p2.ui.Policy; + +public class CarbideP2Policy extends Policy { + + public CarbideP2Policy() { + setRestartPolicy(RESTART_POLICY_PROMPT); + System.setProperty("eclipse.p2.unsignedPolicy", "allow"); + } + +} diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.discovery.ui/META-INF/MANIFEST.MF --- a/core/com.nokia.carbide.discovery.ui/META-INF/MANIFEST.MF Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.discovery.ui/META-INF/MANIFEST.MF Thu May 20 13:57:30 2010 -0500 @@ -4,6 +4,7 @@ Bundle-SymbolicName: com.nokia.carbide.discovery.ui;singleton:=true Bundle-Version: 1.0.0.qualifier Bundle-Activator: com.nokia.carbide.discovery.ui.Activator +Bundle-Localization: plugin Require-Bundle: org.eclipse.ui, org.eclipse.core.runtime, org.eclipse.equinox.p2.discovery;bundle-version="1.0.0", diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.discovery.ui/build.properties --- a/core/com.nokia.carbide.discovery.ui/build.properties Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.discovery.ui/build.properties Thu May 20 13:57:30 2010 -0500 @@ -4,4 +4,6 @@ META-INF/,\ .,\ icons/,\ - contexts.xml + contexts.xml,\ + OSGI-INF/l10n/bundle.properties,\ + plugin.properties diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.discovery.ui/plugin.properties --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/core/com.nokia.carbide.discovery.ui/plugin.properties Thu May 20 13:57:30 2010 -0500 @@ -0,0 +1,1 @@ +view.name=Install Extensions diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.discovery.ui/plugin.xml --- a/core/com.nokia.carbide.discovery.ui/plugin.xml Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.discovery.ui/plugin.xml Thu May 20 13:57:30 2010 -0500 @@ -4,14 +4,10 @@ - - diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.discovery.ui/src/com/nokia/carbide/discovery/ui/Activator.java --- a/core/com.nokia.carbide.discovery.ui/src/com/nokia/carbide/discovery/ui/Activator.java Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.discovery.ui/src/com/nokia/carbide/discovery/ui/Activator.java Thu May 20 13:57:30 2010 -0500 @@ -1,3 +1,19 @@ +/* +* Copyright (c) 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 "Eclipse Public License v1.0" +* which accompanies this distribution, and is available +* at the URL "http://www.eclipse.org/legal/epl-v10.html". +* +* Initial Contributors: +* Nokia Corporation - initial contribution. +* +* Contributors: +* +* Description: +* +*/ package com.nokia.carbide.discovery.ui; import org.eclipse.core.runtime.IStatus; @@ -28,7 +44,6 @@ */ public void start(BundleContext context) throws Exception { super.start(context); - plugin = this; } /* @@ -36,8 +51,8 @@ * @see org.eclipse.ui.plugin.AbstractUIPlugin#stop(org.osgi.framework.BundleContext) */ public void stop(BundleContext context) throws Exception { + super.stop(context); plugin = null; - super.stop(context); } /** diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.discovery.ui/src/com/nokia/carbide/discovery/ui/Messages.java --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/core/com.nokia.carbide.discovery.ui/src/com/nokia/carbide/discovery/ui/Messages.java Thu May 20 13:57:30 2010 -0500 @@ -0,0 +1,20 @@ +package com.nokia.carbide.discovery.ui; + +import org.eclipse.osgi.util.NLS; + +public class Messages extends NLS { + private static final String BUNDLE_NAME = "com.nokia.carbide.discovery.ui.messages"; //$NON-NLS-1$ + public static String DiscoveryView_CheckAllLabel; + public static String DiscoveryView_InstallLabel; + public static String DiscoveryView_MissingDirectoryURLError; + public static String DiscoveryView_RefreshLabel; + public static String DiscoveryView_StatusLineFmt; + public static String DiscoveryView_UncheckAllLabel; + static { + // initialize resource bundle + NLS.initializeMessages(BUNDLE_NAME, Messages.class); + } + + private Messages() { + } +} diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.discovery.ui/src/com/nokia/carbide/discovery/ui/messages.properties --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/core/com.nokia.carbide.discovery.ui/src/com/nokia/carbide/discovery/ui/messages.properties Thu May 20 13:57:30 2010 -0500 @@ -0,0 +1,6 @@ +DiscoveryView_CheckAllLabel=Check All Items +DiscoveryView_InstallLabel=Install Checked Items... +DiscoveryView_MissingDirectoryURLError=Could not find URL in configuration/server.properties file for key={0} +DiscoveryView_RefreshLabel=Refresh +DiscoveryView_StatusLineFmt={0} item(s) checked +DiscoveryView_UncheckAllLabel=Uncheck All Items diff -r c70ff7f19887 -r d1b0b4e203e9 core/com.nokia.carbide.discovery.ui/src/com/nokia/carbide/discovery/ui/view/DiscoveryView.java --- a/core/com.nokia.carbide.discovery.ui/src/com/nokia/carbide/discovery/ui/view/DiscoveryView.java Thu May 20 13:57:04 2010 -0500 +++ b/core/com.nokia.carbide.discovery.ui/src/com/nokia/carbide/discovery/ui/view/DiscoveryView.java Thu May 20 13:57:30 2010 -0500 @@ -27,7 +27,9 @@ import org.eclipse.jface.dialogs.ProgressMonitorDialog; import org.eclipse.jface.layout.GridDataFactory; import org.eclipse.jface.layout.GridLayoutFactory; +import org.eclipse.jface.viewers.ISelectionChangedListener; import org.eclipse.jface.viewers.IStructuredSelection; +import org.eclipse.jface.viewers.SelectionChangedEvent; import org.eclipse.jface.viewers.StructuredSelection; import org.eclipse.osgi.service.datalocation.Location; import org.eclipse.swt.SWT; @@ -39,6 +41,7 @@ import org.eclipse.ui.part.ViewPart; import com.nokia.carbide.discovery.ui.Activator; +import com.nokia.carbide.discovery.ui.Messages; @SuppressWarnings("restriction") public class DiscoveryView extends ViewPart { @@ -47,12 +50,14 @@ private CatalogViewer viewer; private Action refreshAction; - private BaseSelectionListenerAction selectAllAction; - private BaseSelectionListenerAction selectNoneAction; + private BaseSelectionListenerAction checkAllAction; + private BaseSelectionListenerAction checkNoneAction; private BaseSelectionListenerAction installAction; private boolean initialized; + private ISelectionChangedListener selectionListener; + public DiscoveryView() { } @@ -68,7 +73,8 @@ GridDataFactory.fillDefaults().grab(true, true).applyTo(viewer.getControl()); // Create the help context id for the viewer's control - PlatformUI.getWorkbench().getHelpSystem().setHelp(viewer.getControl(), "TestDiscovery.viewer"); + PlatformUI.getWorkbench().getHelpSystem().setHelp(viewer.getControl(), + "com.nokia.carbide.discovery.ui.view.DiscoveryView.viewer"); //$NON-NLS-1$ makeActions(); contributeToActionBars(); } @@ -110,7 +116,7 @@ is.close(); } catch (IOException e) { String message = - MessageFormat.format("Could not find URL in configuration/server.properties file for key={0}", key); + MessageFormat.format(Messages.DiscoveryView_MissingDirectoryURLError, key); Activator.logError(message, e); } return (String) properties.get(key); @@ -123,8 +129,8 @@ } private void fillLocalPullDown(IMenuManager manager) { - manager.add(selectAllAction); - manager.add(selectNoneAction); + manager.add(checkAllAction); + manager.add(checkNoneAction); } private void fillLocalToolBar(IToolBarManager manager) { @@ -135,13 +141,16 @@ private void makeActions() { refreshAction = new Action() { public void run() { + viewer.setSelection(StructuredSelection.EMPTY); + viewer.refresh(); viewer.updateCatalog(); } }; - refreshAction.setText("Refresh"); - refreshAction.setImageDescriptor(Activator.getImageDescriptor("icons/refresh.gif")); - selectAllAction = new BaseSelectionListenerAction("Select All Items") { + refreshAction.setText(Messages.DiscoveryView_RefreshLabel); + refreshAction.setImageDescriptor(Activator.getImageDescriptor("icons/refresh.gif")); //$NON-NLS-1$ + checkAllAction = new BaseSelectionListenerAction(Messages.DiscoveryView_CheckAllLabel) { public void run() { + viewer.setSelection(StructuredSelection.EMPTY); viewer.setSelection(getAllItemsSelection()); viewer.refresh(); } @@ -155,7 +164,7 @@ return !getAllItemsSelection().equals(selection); }; }; - selectNoneAction = new BaseSelectionListenerAction("Deselect All Items") { + checkNoneAction = new BaseSelectionListenerAction(Messages.DiscoveryView_UncheckAllLabel) { public void run() { viewer.setSelection(StructuredSelection.EMPTY); viewer.refresh(); @@ -165,7 +174,7 @@ return !selection.isEmpty(); }; }; - installAction = new BaseSelectionListenerAction("Install Checked Items...") { + installAction = new BaseSelectionListenerAction(Messages.DiscoveryView_InstallLabel) { public void run() { DiscoveryUi.install(viewer.getCheckedItems(), new ProgressMonitorDialog(DiscoveryView.this.getViewSite().getShell())); }; @@ -174,17 +183,29 @@ return !selection.isEmpty(); }; }; - installAction.setImageDescriptor(Activator.getImageDescriptor("icons/icon-discovery.png")); - viewer.addSelectionChangedListener(selectAllAction); - viewer.addSelectionChangedListener(selectNoneAction); + installAction.setImageDescriptor(Activator.getImageDescriptor("icons/icon-discovery.png")); //$NON-NLS-1$ + viewer.addSelectionChangedListener(checkAllAction); + viewer.addSelectionChangedListener(checkNoneAction); viewer.addSelectionChangedListener(installAction); + selectionListener = new ISelectionChangedListener() { + @Override + public void selectionChanged(SelectionChangedEvent event) { + IStructuredSelection selection = (IStructuredSelection) event.getSelection(); + IActionBars bars = getViewSite().getActionBars(); + bars.getStatusLineManager().setMessage( + selection.isEmpty() ? null : MessageFormat.format( + Messages.DiscoveryView_StatusLineFmt, selection.size())); + } + }; + viewer.addSelectionChangedListener(selectionListener); } @Override public void dispose() { - viewer.removeSelectionChangedListener(selectAllAction); - viewer.removeSelectionChangedListener(selectNoneAction); + viewer.removeSelectionChangedListener(checkAllAction); + viewer.removeSelectionChangedListener(checkNoneAction); viewer.removeSelectionChangedListener(installAction); + viewer.removeSelectionChangedListener(selectionListener); super.dispose(); } @@ -198,10 +219,12 @@ Display.getDefault().asyncExec(new Runnable() { @Override public void run() { - viewer.updateCatalog(); - viewer.setSelection(StructuredSelection.EMPTY); + if (viewer.getViewer().getContentProvider() != null) { + viewer.updateCatalog(); + } } }); } } + } \ No newline at end of file diff -r c70ff7f19887 -r d1b0b4e203e9 project/com.nokia.carbide.cpp.project.ui/src/com/nokia/carbide/cpp/internal/project/ui/perspective/CarbideCppPerspectiveFactory.java --- a/project/com.nokia.carbide.cpp.project.ui/src/com/nokia/carbide/cpp/internal/project/ui/perspective/CarbideCppPerspectiveFactory.java Thu May 20 13:57:04 2010 -0500 +++ b/project/com.nokia.carbide.cpp.project.ui/src/com/nokia/carbide/cpp/internal/project/ui/perspective/CarbideCppPerspectiveFactory.java Thu May 20 13:57:30 2010 -0500 @@ -18,7 +18,6 @@ import org.eclipse.cdt.internal.ui.wizards.CWizardRegistry; import org.eclipse.cdt.ui.CUIPlugin; -import org.eclipse.search.ui.NewSearchUI; import org.eclipse.ui.*; import org.eclipse.ui.console.IConsoleConstants; import org.eclipse.ui.navigator.resources.ProjectExplorer; @@ -30,6 +29,8 @@ private static final String EXECUTABLES_VIEW_ID = "org.eclipse.cdt.debug.ui.executablesView"; //$NON-NLS-1$ + private static final String INSTALL_VIEW_ID = "com.nokia.carbide.discovery.view"; //$NON-NLS-1$ + private static final String TOP_LEFT = "topLeft"; //$NON-NLS-1$ private static final String BOTTOM_LEFT = "bottomLeft"; //$NON-NLS-1$ private static final String BOTTOM_RIGHT = "bottom"; //$NON-NLS-1$ @@ -53,11 +54,8 @@ // Top left: Resource Navigator view and Bookmarks view placeholder IFolderLayout topLeft = layout.createFolder(TOP_LEFT, IPageLayout.LEFT, 0.25f, editorArea); topLeft.addView(ProjectExplorer.VIEW_ID); - topLeft.addView(IPageLayout.ID_RES_NAV); - topLeft.addPlaceholder(IPageLayout.ID_BOOKMARKS); - - // Bottom left: Outline view and Property Sheet view + // Bottom left: SPN View IFolderLayout bottomLeft = layout.createFolder(BOTTOM_LEFT, IPageLayout.BOTTOM, 0.5f, TOP_LEFT); bottomLeft.addView(SYMBIAN_PROJECT_NAVIGATOR_VIEW_ID); @@ -65,11 +63,6 @@ IFolderLayout bottomRight = layout.createFolder(BOTTOM_RIGHT, IPageLayout.BOTTOM, 0.75f, editorArea); bottomRight.addView(IPageLayout.ID_PROBLEM_VIEW); bottomRight.addView(IConsoleConstants.ID_CONSOLE_VIEW); - bottomRight.addView(IPageLayout.ID_PROP_SHEET); - bottomRight.addView(IPageLayout.ID_TASK_LIST); - bottomRight.addView(CUIPlugin.ID_INCLUDE_BROWSER); - bottomRight.addView(CUIPlugin.ID_CALL_HIERARCHY); - bottomRight.addView(CUIPlugin.ID_TYPE_HIERARCHY); bottomRight.addView(EXECUTABLES_VIEW_ID); // Top right: Outline view @@ -78,37 +71,27 @@ // Add action sets for search, c element and navigate layout.addActionSet(CUIPlugin.SEARCH_ACTION_SET_ID); - layout.addActionSet(CUIPlugin.ID_CELEMENT_CREATION_ACTION_SET); layout.addActionSet(IPageLayout.ID_NAVIGATE_ACTION_SET); // show view shortcuts - layout.addShowViewShortcut(IConsoleConstants.ID_CONSOLE_VIEW); // build console - layout.addShowViewShortcut(NewSearchUI.SEARCH_VIEW_ID); // searching - // standard workbench + layout.addShowViewShortcut(ProjectExplorer.VIEW_ID); + layout.addShowViewShortcut(SYMBIAN_PROJECT_NAVIGATOR_VIEW_ID); layout.addShowViewShortcut(IPageLayout.ID_OUTLINE); layout.addShowViewShortcut(IPageLayout.ID_PROBLEM_VIEW); - layout.addShowViewShortcut(ProjectExplorer.VIEW_ID); - layout.addShowViewShortcut(IPageLayout.ID_RES_NAV); - layout.addShowViewShortcut(IPageLayout.ID_PROP_SHEET); - layout.addShowViewShortcut(SYMBIAN_PROJECT_NAVIGATOR_VIEW_ID); + layout.addShowViewShortcut(IConsoleConstants.ID_CONSOLE_VIEW); // build console + layout.addShowViewShortcut(EXECUTABLES_VIEW_ID); + layout.addShowViewShortcut(INSTALL_VIEW_ID); // add show-in contributions layout.addShowInPart(ProjectExplorer.VIEW_ID); - layout.addShowInPart(IPageLayout.ID_RES_NAV); addCDTWizardShortcutIdsToLayout(layout); } @SuppressWarnings("restriction") private void addCDTWizardShortcutIdsToLayout(IPageLayout layout) { - // cdt project wizard ids - String[] ids = CWizardRegistry.getProjectWizardIDs(); - for (String id : ids) { - layout.addNewWizardShortcut(id); - } - // cdt folder wizard ids - ids = CWizardRegistry.getFolderWizardIDs(); + String[] ids = CWizardRegistry.getFolderWizardIDs(); for (String id : ids) { layout.addNewWizardShortcut(id); } diff -r c70ff7f19887 -r d1b0b4e203e9 qt/com.nokia.carbide.cpp.qt.ui/plugin.xml --- a/qt/com.nokia.carbide.cpp.qt.ui/plugin.xml Thu May 20 13:57:04 2010 -0500 +++ b/qt/com.nokia.carbide.cpp.qt.ui/plugin.xml Thu May 20 13:57:30 2010 -0500 @@ -51,9 +51,6 @@ id="com.nokia.carbide.cpp.CarbideCppPerspective"> - - -

Item	Explanation
Qt Versions	Shows a list of installed Qt versions installed and available for Qt projects.
Add...	Click Add to open the Add new Qt version dialog where you can specify a Qt SDK by name and location. - - Figure 2. Add new Qt version dialog
Edit...	Click Edit to open the Edit Qt Version dialog where you can modify the Qt SDK information for the selected Qt version. - - Figure 3. Edit Qt Version dialog
Remove	Click Remove to delete the selected Qt SDK from the Qt version list.
Default	Click Default to identify the selected Qt SDK as the default SDK to use for Qt projects.
Auto update QMAKESPEC when applying changes	Enable to automatically update QMAKESPEC when any changes are made to a Qt version. The default setting is enabled.
Auto update make command when applying changes	Enable to automatically update make when any changes are made to a Qt version. The default setting is enabled.

Item	Explanation
Use Qt version	Select the Qt version to associate with this project. Choose Default to always use the default Qt version as set in the Qt preference panel or select from any Qt version listed.
Run qmake when .pro file changes	Enable to keep the Carbide project and .pro file in sync during development. Qmake will be invoked whenever the .pro file changes so that the bld.inf and .mmp file will always be in sync. The default setting is enabled.

Name	Function
- - Target name	- - Enter the name of the target file. -
- - Target type -	- - Select the type of target file from the dropdown list.
- - Target path -	- - Enter the path to the target file. -
- - 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.
- - 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.
- - Common tasks -	- - This group provides links to the User and System include path options located in the Options window. -

Name	Function
+ + Target name	+ + Enter the name of the target file. +
+ + Target type +	+ + Select the type of target file from the dropdown list.
+ + Target path +	+ + Enter the path to the target file. +
+ + 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.
+ + 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.
+ + Common tasks +	+ + This group provides links to the User and System include path options located in the Options 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 OS kernel you can ignore this section.

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 OS kernel you can ignore this section.

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 OS 9.4+) - Activate to enable on-device debugging for Symbian OS 9.4 and later. When activated, the DEBUGGABLE_UDEBONLY flag is added to the project .MMP file. - Paging Mode (Symbian OS 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.

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 OS 9.4+) - Activate to enable on-device debugging for Symbian OS 9.4 and later. When activated, the DEBUGGABLE_UDEBONLY flag is added to the project .MMP file. + Paging Mode (Symbian OS 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.

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.

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.

Name	Function
- - Source Folder -	- - Specifies the source folder where the header and source files are - to be created. -
- - Namespace -	- - Select the checkbox to specify whether you want to add the new - class under a namespace or not. If yes, click Browse to select an existing - namespace or type a new namespace. -
- - Class Name -	- - Specifies the name of new C++ class. -
- - Base Classes -	- - Lists all the base types from which the new C++ class is derived. -
- - Method Stubs -	- - Specifies whether to generate stubs for constructor and destructors - of the class. -
- - Use Default -	- - Specifies whether the class declaration and definition are added to - default header and source files or not. -
- - Header -	- - Specifies the header file which contains the class declaration. -
- - Source -	- - Specifies the source file which contains the class definition. -
Use Default	Disable to select different Header and Source files to use as the template for the new class.

Name	Function
+ + Source Folder +	+ + Specifies the source folder where the header and source files are + to be created. +
+ + Namespace +	+ + Select the checkbox to specify whether you want to add the new + class under a namespace or not. If yes, click Browse to select an existing + namespace or type a new namespace. +
+ + Class Name +	+ + Specifies the name of new C++ class. +
+ + Base Classes +	+ + Lists all the base types from which the new C++ class is derived. +
+ + Method Stubs +	+ + Specifies whether to generate stubs for constructor and destructors + of the class. +
+ + Use Default +	+ + Specifies whether the class declaration and definition are added to + default header and source files or not. +
+ + Header +	+ + Specifies the header file which contains the class declaration. +
+ + Source +	+ + Specifies the source file which contains the class definition. +
Use Default	Disable to select different Header and Source files to use as the template for the new class.

Item	Explanation
Macro File	Enter the macro file path and name into the text box or click Browse to locate a macro file.
Use preprocessor symbols from mmp MACRO statements for parsers	Your code will be parsed by the CDT indexer. Enable this option to use MMP macros during parsing.
Show paths and symbols page...	Click to open the Paths and Symbols page under Carbide Build Configuration.

Item	Explanation
PKG File	Choose a PKG file relative to the project's file system or click Browse to locate a PKG file that will be used to create the SIS file. The default option is “none”, which indicates to not build a PKG file.
Signed SIS File Name	Final output signed file name. Default is PKG filename with ‘sisx’ extension.
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 - 0xE0000000-0xEFFFFFFF range.
Key	Enter or browse to key. -

Option	Explanation
Panes	Specifies how the memory space is rendered in the pane: - - Address - Binary - Text -
Endian	Choose one of the following: - - Big - Little -
Text	Choose one of the following: - - ISO-8859-1 - US-ASCII - UTF-8 -
Cell size	Specifies the byte size of the memory rendering. The choices include: - - 1 byte - 2 bytes - 4 bytes - 8 bytes -
Radix	Choose one of the following: - - Hex - Decimal Signed - Decimal Unsigned - Octal - Binary -

Getting Started

Getting Started

MBM File

Related tasks

Related references

MBM File

Related tasks

Related references

Modify

Related concepts

Related tasks

Related references

Modify

Related concepts

Related tasks

Related references

Projects

Related concepts

Related tasks

Related references

Projects

Related concepts

Related tasks

Related references

Build System Overview

Basic Build Commands

Command Line Arguments

Other references

Build System Overview

Basic Build Commands

Command Line Arguments

Other references

Concurrent Versions System (CVS)

Concurrent Versions System (CVS)

Data Viewer Plug-ins

Data Viewer Plug-ins

External Builds Support

External Builds Support

FPU Registers

Related concepts

Related tasks

Related references

FPU Registers

Related concepts

Related tasks

Related references

General Registers

Related concepts

Related tasks

Related references

General Registers

Related concepts

Related tasks

Related references

Host-specific Registers

Related concepts

Related tasks

Related references

Host-specific Registers

Related concepts

Related tasks

Related references

Carbide Macros

Tasks

Carbide Macros

Tasks

Precompiled Headers

Listing 1 .pch Precompiled Header example

Precompiled Headers

Listing 1 .pch Precompiled Header example

Symbol Hint

Toggling the Symbol Hint

To toggle the symbol hint

Using the Symbol Hint

Symbol Hint

Toggling the Symbol Hint

To toggle the symbol hint

Using the Symbol Hint

About Symbolics Files

About Symbolics Files