Basic Settings in New Project Wizard

- You can set some basic properties for the project in this page, like Application UID, Author and Copyright - notice for the project.

NOTE Fields appearing in window vary depending upon the type of project being created.

Name	Function
- - Application UID -	- - Specifies a 32-bit ID to identify the project.
- - Vendor ID -	- - Appears for projects that require a 32-bit unique ID to identify the vendor of the - executable. In versions of Symbian OS with platform security, a program can - read a VID at runtime to check that a binary comes from a particular source. In - most cases, the VID should be zero, meaning that source of the executable is - not required for any security checks. -
- - Author -	- - Specifies the name of the Author, who is creating this project. -
- - Copyright Notice -	- - Specifies the copyright notice to be added to the source code of the - project. -

NOTE Tooltips are available for the various fields. Simply hover the pointer over the field title to view the tooltip.

Related tasks

Basic Settings

+ You can set some basic properties for the project in this page, like Application UID, Author and Copyright + notice for the project.

NOTE Fields appearing in window vary depending upon the type of project being created.

Name	Function
+ + Application UID +	+ + Specifies a 32-bit ID to identify the project.
+ + Vendor ID +	+ + Appears for projects that require a 32-bit unique ID to identify the vendor of the + executable. In versions of Symbian OS with platform security, a program can + read a VID at runtime to check that a binary comes from a particular source. In + most cases, the VID should be zero, meaning that source of the executable is + not required for any security checks. +
+ + Author +	+ + Specifies the name of the Author, who is creating this project. +
+ + Copyright Notice +	+ + Specifies the copyright notice to be added to the source code of the + project. +

NOTE Tooltips are available for the various fields. Simply hover the pointer over the field title to view the tooltip.

Related tasks

- You can specify the name of the class and where the generated source and header - files are to be stored. -

Table 1 - Name and Locations page options

+ You can specify the name of the class and where the generated source and header + files are to be stored. +

Table 1 - Name and Locations page options

Other Settings

- Specify the name of the author and copyright notice information. + Specify the name of the author, version, and copyright notice information.

Add Images From Filesystem

The Add Images from Filesystem dialog allows you to search for and add images currently available in the filesystem. Select an image and click Ok to add the image.

Name	Function
- - Include -	- - Specifies the name of the include folder, where all the header - files for the project are located. -
- - Source -	- - Specifies the name of the source folder, where all the source files - for the project are located. -
Group	Specifies the name of the group folder, where all the group files for the project are located.
Data	Specifies the name of the data folder, where all the data files for the project are located.
Install	Specifies the name of the Install folder, where all the .sis files for the project are located.
Graphics	Specifies the name of the graphics folder, where all the graphic files for the project are located.

Name	Function
+ + Include +	+ + Specifies the name of the include folder, where all the header + files for the project are located. +
+ + Source +	+ + Specifies the name of the source folder, where all the source files + for the project are located. +
Group	Specifies the name of the group folder, where all the group files for the project are located.
Data	Specifies the name of the data folder, where all the data files for the project are located.
Install	Specifies the name of the Install folder, where all the .sis files for the project are located.
Graphics	Specifies the name of the graphics folder, where all the graphic files for the project are located.

Name	Function
- - Class name	- Class name to create. -
- - Source	- Specify directory to store source information.
Include	Specify directory to store header information.

Name	Function
+ + Class name	+ Class name to create.
Use default	Checkmark to use the suggested default names, or uncheck to customize the names.
+ + Source	+ Specify directory to store source information.
Include	Specify directory to store header information.
Force files to lowercase	Checkmark to force all filenames to use lowercase letters. Uncheck to use mixed case.

NOTE Information displayed under Help group will vary slightly depending upon whether this dialog was called from a MBM,MIF, or AIF editor.

Table 1. Add Images—Items

Add Images From Filesystem

Item	Explanation
Directory	Browse to the directory containing images you want to add.
Available directory images	Shows the images found in the directory. Select images to be added.
Detected image pairs	Lists the selected images and detected image pairs. -
Copy images into project	Enable this option to make a copy of selected images in the selected project location.
Overwrite existing	Enable this option to overwrite existing images with the same name.
Project location	Click the Choose... button to display the Select a folder dialog, then select a project folder to store the images.

The Add Images from Filesystem dialog allows you to search for and add images currently available in the filesystem. Select an image and click OK to add the image.

NOTE Information displayed under Help group will vary slightly depending upon whether this dialog was called from a MBM, MIF, or AIF editor.

Table 1. Add Images—Items

Other references

Add Images From Project

The Add Images from Project dialog allows you to add images currently available in the project. Select an image and click Ok to add the image.

Item	Explanation
Directory	Browse to the directory containing images you want to add.
Available directory images	Shows the images found in the directory. Select images to be added.
Detected image pairs	Lists the selected images and detected image pairs. +
Copy images into project	Enable this option to make a copy of selected images in the selected project location.
Overwrite existing	Enable this option to overwrite existing images with the same name.
Project location	Click the Choose... button to display the Select a folder dialog, then select a project folder to store the images.

NOTE Information displayed under Help group will vary slightly depending upon whether this dialog was called from a MBM,MIF, or AIF editor.

Add Images From Project

The Add Images from Project dialog allows you to add images currently available in the project. Select an image and click OK to add the image.

NOTE Information displayed under Help group will vary slightly depending upon whether this dialog was called from a MBM, MIF, or AIF editor.

Other references

Carbide Build Configurations

The Carbide Build Configurations panel is used to specify the project's active build configuration and its related build properties.

Table 1 Carbide Build Configuration items

Other references

Carbide Build Configurations

Item	Explanation
Active Configuration	The Active Configuration drop down list allows you to select a configuration that is currently available for the selected project. The entries in the related sub-panes will change according to the selected configuration. The Configuration name consists of a target name and an SDK identifier in brackets.
Manage...	Click the Manage... button to add a new SDK/Configuration or remove an existing configuration.
SIS Builder	The SIS Builder pane is used to specify a .pkg file and .sis file options to create an application .sis file. These settings apply to the currently selected Configuration.
Environment	The Environment tab allows you to view the current User and System environment variables that will be used when any abld command is invoked.
Arguments	The Arguments tab allows you to add additional arguments to common build commands used by Carbide during the build process including: - - Bldmake Arguments - Abld Arguments - - See the Symbian OS documentation for a specific command for a complete list of valid arguments.
Paths and Symbols	The Paths and Symbols tab allows you to see which paths and symbols have been indexed for the project.
ROM Builder	The ROM Builder tab allows you to specify commands and a working directory for building a GUI ROM Image.

Use the Carbide Build Configurations panel to specify the project's active build configuration and its related build properties.

Table 1 Carbide Build Configuration items

Other references

Environment Variables

Item	Explanation
Active Configuration	The Active Configuration drop down list allows you to select a configuration that is currently available for the selected project. The entries in the related sub-panes will change according to the selected configuration. The Configuration name consists of a target name and an SDK identifier in brackets.
Manage...	Click the Manage... button to add a new SDK/Configuration or remove an existing configuration.
SIS Builder	The SIS Builder pane is used to specify a .pkg file and .sis file options to create an application .sis file. These settings apply to the currently selected Configuration.
Environment	The Environment tab allows you to view the current User and System environment variables that will be used when any abld command is invoked.
Arguments	The Arguments tab allows you to add additional arguments to common build commands used by Carbide during the build process including: + + Bldmake Arguments + Abld Arguments + + See the Symbian OS documentation for a specific command for a complete list of valid arguments.
Paths and Symbols	The Paths and Symbols tab allows you to see which paths and symbols have been indexed for the project.
ROM Builder	The ROM Builder tab allows you to specify commands and a working directory for building a GUI ROM Image.

The Environment Variables pane allows you to view the current User and System environment variables that will be used when any abld command is invoked. User variables are modified or added when a process is invoked. Read only system variables are listed. Variables and values in bold are items that have been modified from their default values.

Table 1 Environment variable items

Other references

Environment Variables

Item	Explanation
New	Click to add a new environment variable. You must specify a name and a value.
Edit	Allows you to edit the name and value of an environment variable.
Undefine	Undefines the selected variable so that it is not used during a build. - NOTE Some variables, like PATH, EPOCROOT, and those beginning with MW* have special meaning and cannot be undefined.
Variable use	Shows the use for the selected variable. Uses include: - - Default – Take the variable as-is from the system, do not modify it. - Append – Add the value displayed to the end of the existing variable (the existing variable name is not displayed. - Prepend – Add the value displayed to the front of the existing variable (the existing variable name is not displayed. - Replace – Replace the value displayed with the existing variable. - Undefine – Not used during a build -

Table 1 Environment variable items

Other references

Paths and Symbols

Item	Explanation
New	Click to add a new environment variable. You must specify a name and a value.
Edit	Allows you to edit the name and value of an environment variable.
Undefine	Undefines the selected variable so that it is not used during a build. + NOTE Some variables, like PATH, EPOCROOT, and those beginning with MW* have special meaning and cannot be undefined.
Variable use	Shows the use for the selected variable. Uses include: + + Default – Take the variable as-is from the system, do not modify it. + Append – Add the value displayed to the end of the existing variable (the existing variable name is not displayed. + Prepend – Add the value displayed to the front of the existing variable (the existing variable name is not displayed. + Replace – Replace the value displayed with the existing variable. + Undefine – Not used during a build +

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

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

Other references

Paths and Symbols

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

Other references

SIS Builder

The SIS Builder pane is used to specify one or more .PKG and .SIS file options to create application and patch .SIS files. These settings apply to the currently selected Configuration.

Table 1 SIS Builder items

Item	Explanation
Add	Opens the SIS Properties window to add a PKG file to the list.
Edit	Opens the selected SIS file in the SIS Properties window for editing.
Remove	Removes the selected SIS file from the list.
Move Up	Moves the selected SIS file up in the list order.
Move Down	Moves the selected SIS file down in the list order.

Partial Upgrade Files

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

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

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

Partial upgrade files are deleted and only full SIS/SISX files are generated when: 1) the full SIS/SISX files do not already exist, 2) the PKG file is changed, and 3) the Partial upgrade option is disabled.

Other references

SIS Builder

The SIS Builder pane is used to specify one or more .PKG and .SIS file options to create application and patch .SIS files. These settings apply to the currently selected Configuration.

Table 1 SIS Builder items

Item	Explanation
Add	Opens the SIS Properties window to add a PKG file to the list.
Edit	Opens the selected SIS file in the SIS Properties window for editing.
Remove	Removes the selected SIS file from the list.
Move Up	Moves the selected SIS file up in the list order.
Move Down	Moves the selected SIS file down in the list order.

Partial Upgrade Files

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

Other references

Carbide Project Settings

Use the Carbide Project Settings window to specify whether all components or selected subcomponents listed in a build information file (bld.inf) should be built for the currently selected project. You can also specify whether to perform a clean or reallyclean command on the project before building a project.

Table 1 Carbide Project Settings items

Table 2 Symbian Build System v1 tab

Table 3 Symbian Build System v2 tab (only visible for Projects created with SBSv2 builder)

Related tasks

Carbide Project Settings

Item	Explanation
Bld.inf file	This is the path to the bld.inf file that lists the makefile and mmp components.
Bld.inf	Select this option to ensure all components are built for the selected project.
Selected Components	Select this option to specify which components of the bld.inf file to be built, including makefiles. The equivalent call to abld is abld build <subcomponent>. Use the Exclude extension makefiles and Exclude test components options to manage the items that appear in the list. - Toggle the state of each component to set its build state to true or not. A checkmark indicates a component is built. Click on a column title to sort the items by that columns contents. -
Exclude extension makefiles	Toggles the presense of extension makefiles in the Selected components list.
Exclude test components	Toggles the presense of test components in the Selected components list.
Enable project specific settings	Click to set project specific build settings. By default a project in the workspace uses the global build settings unless this option is enabled. See the Build preference panel for details on these options.
Configure Workspace Settings...	Opens the Build preference panel.

Item	Explanation
Clean level	Specifies the level of clean to perform on project files. The levels include: - - Level 0 (abld clean) - removes all the intermediate files created during compilation, and all the executables and import libraries created by the linker - Level 1 (abld reallyclean) - performs a clean operation, but also removes all exported files and makefiles - Level 2 (abld reallyclean, bldmake clean) - performs a reallyclean operation and then removes all files created by bldmake -
Manage dependency tracking	If checked, the Symbian command line build system will not generate dependencies for source and resource files. These will be managed by Carbide. This can reduce build times.
Show a dialog to modify build actions when modified MMPs are detected	If checked, you will be asked what action to take before a build if a MMP file has been modified. - If not checked, the default action is taken for all modified mmp files.
Default action to take when mmp files are modified	Select either None, Link only, or Compile and Link.

Item	Explanation
Clean level	Select the level of clean when cleaning a project. - abld clean erases all files created by a corresponding abld target command (all intermediate files created during compilation and all executables and import libraries created by the linker) - abld reallyclean does what abld clean does, and also removes files exported by abld export and makefiles generated by abld makefile, or the abld test equivalents
Keep going	This build option tells a particular command to keep going even if unrelated build steps report errors or files are missing.
Debug	This option generates symbolic debug information for release or debug builds, independent of the compiler optimization level. - By default, the build system generates symbolic debug information only for the debug builds. With this option, the generation of symbolic debug information is extended to release builds to support debugging of release binaries on ARM ABI compliant platforms.
Override default make engine	Check this box to enable an edit box to specify the make engine to use, for example, eMake from Electric Cloud.

Table 1 Carbide Project Settings items

Table 2 Symbian Build System v1 tab

Table 3 Symbian Build System v2 tab (only visible for Projects created with SBSv2 builder)

Related tasks

SIS Properties

Item	Explanation
Bld.inf file	This is the path to the bld.inf file that lists the makefile and mmp components.
Bld.inf	Select this option to ensure all components are built for the selected project.
Selected Components	Select this option to specify which components of the bld.inf file to be built, including makefiles. The equivalent call to abld is abld build <subcomponent>. Use the Exclude extension makefiles and Exclude test components options to manage the items that appear in the list. + Toggle the state of each component to set its build state to true or not. A checkmark indicates a component is built. Click on a column title to sort the items by that columns contents. +
Exclude extension makefiles	Toggles the presense of extension makefiles in the Selected components list.
Exclude test components	Toggles the presense of test components in the Selected components list.
Enable project specific settings	Click to set project specific build settings. By default a project in the workspace uses the global build settings unless this option is enabled. See the Build preference panel for details on these options.
Configure Workspace Settings...	Opens the Build preference panel.

Item	Explanation
Clean level	Specifies the level of clean to perform on project files. The levels include: + + Level 0 (abld clean) - removes all the intermediate files created during compilation, and all the executables and import libraries created by the linker + Level 1 (abld reallyclean) - performs a clean operation, but also removes all exported files and makefiles + Level 2 (abld reallyclean, bldmake clean) - performs a reallyclean operation and then removes all files created by bldmake +
Manage dependency tracking	If checked, the Symbian command line build system will not generate dependencies for source and resource files. These will be managed by Carbide. This can reduce build times.
Show a dialog to modify build actions when modified MMPs are detected	If checked, you will be asked what action to take before a build if a MMP file has been modified. + If not checked, the default action is taken for all modified mmp files.
Default action to take when mmp files are modified	Select either None, Link only, or Compile and Link.

Item	Explanation
Clean level	Select the level of clean when cleaning a project. + + abld clean erases all files created by a corresponding abld target command (all intermediate files created during compilation and all executables and import libraries created by the linker) + abld reallyclean does what abld clean does, and also removes files exported by abld export and makefiles generated by abld makefile, or the abld test equivalents +
Keep going	This build option tells a particular command to keep going even if unrelated build steps report errors or files are missing.
Debug	This option generates symbolic debug information for release or debug builds, independent of the compiler optimization level. + By default, the build system generates symbolic debug information only for the debug builds. With this option, the generation of symbolic debug information is extended to release builds to support debugging of release binaries on ARM ABI compliant platforms.
Override default make engine	Check this box to enable an edit box to specify the make engine to use, for example, eMake from Electric Cloud.

Use the SIS Properties dialog to specify SIS file creation and signing options for selected SIS file included in the project.

Table 1 SIS Properties window items

Related reference

SIS Properties

Item	Explanation
SIS File Creation Options	Define the SIS file created: - - PKG File — name of the PKG file to build. Click Browse to locate or else type in the file path and name. - Output File Name — unsigned file name that is generated from the PKG file selected - Content Search Location — root location where PKG files are specified to search - Generate partial upgrade when appropriate — enable to create package update files that only contain files changed since the last build -
Signing Options	Defines the signing options applied to the configuration. The options include: - - Don't sign sis file — builds sis file without signing it - Self sign sis file — signs the sis file without specifying the certificate/key pair - Sign sis file with certificate/key pair — signs the sis file using the specified certificate/key pair - - Enter the required information into the enabled fields based on the signing option selected above: - - Signed SIS File Name —Final output signed file name. Default is input PKG name with ‘sisx’ extension. - Password — Optional password - Additional options — Enter unfiltered options to be passed to the tool - Certificate – Enter or browse to certificate - Key — Enter or browse to key - - 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. - NOTE All Application TRK build configuration require a PKG file. If none is found in the active project then you will be asked to choose one.

Use the SIS Properties dialog to specify SIS file creation and signing options for the selected SIS file included in the project.

Table 1 SIS Properties window items

Related reference

Indexer

The C/C++ indexer uses the parser to create a database of your source and header files that provides the basis for C/C++ search, navigation features and content assist. The goal of indexing is to record all named elements in a project's source code and store them with their related data. The indexer parses each source file in your project and updates related indexes. By indexing your files with the indexer, useful features such as code completion and fast file search can be used. It is also possible to specify different indexer settings for each project in your workspace.

If you choose to perform the Full C/C++ Indexer option the indexer will consume the CPU for some time, but you will gain more benefit from the process after it completes. - However, if you do not require the benefits of indexing your project, select the No Indexer option to speed up the process of building your project.

The indexer runs on a background thread and reacts to resource change events such as:

The Preferences Indexer can be accessed by selecting Window > Preferences then expanding the C/C++ group and selecting Indexer (figure 1). The Project Properties Indexer can be accessed by selecting a project in the C/C++ Projects or Symbian Project Navigator view and selecting Project > Properties, then select C/C++ Indexer (figure 2).

Item	Explanation
SIS File Creation Options	Define the SIS file created: + + PKG File — name of the PKG file to build. Click Browse to locate or else type in the file path and name. + Output File Name — unsigned file name that is generated from the PKG file selected + Content Search Location — root location where PKG files are specified to search + Generate partial upgrade when appropriate — enable to create package update files that only contain files changed since the last build +
Signing Options	Defines the signing options applied to the configuration. The options include: + + Don't sign sis file — builds sis file without signing it + Self sign sis file — signs the sis file without specifying the certificate/key pair + Sign sis file with certificate/key pair — signs the sis file using the specified certificate/key pair + + Enter the required information into the enabled fields based on the signing option selected above: + + Signed SIS File Name —Final output signed file name. Default is input PKG name with ‘sisx’ extension. + Password — Optional password + Additional options — Enter unfiltered options to be passed to the tool + Certificate – Enter or browse to certificate + Key — Enter or browse to key + + 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. + NOTE All Application TRK build configuration require a PKG file. If none is found in the active project then you will be asked to choose one.

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

Related concepts

Related tasks

Indexer

Name	Function
Available indexers	Dropdown list of available index options. - - No Indexer - Project source files will not be indexed, therefore search features will not work accurately and code completion will not be available. - Fast C/C++ Indexer - Source files will be indexed and eat up a lot of CPU time and memory during the first generation of the indexer. This can take some time depending on the size of your project. Afterwards the indexer will only reindex the relevant parts you changed in your code and not the whole source tree. - Full C/C++ Indexer - Performs a complete parse of all source files and takes up the most amount of time to complete. -
Apply indexer to all projects now	Select this option to apply the Fast C/C++ Indexer option to all projects in your current workspace.
Rebuild the index when changing to a different build configuration	Select this option to rescan and index the source files for the current project when you change the active build configuration. The index will be built based on the active build configuration. All macros and header files used to build the index will be taken from the active build configuration.
Build the index only for the build configuration specified in the project's indexer settings - - Build the index only for the specified build configuration	The indexer will only be run for the build configuration specified in the Indexer panel in the project's property settings. All macros and header files used to build the index will be taken from the specified configuration. - - NOTE This option appears in the project properties indexer panel. A dropdown list is provided to select a build configuration for the currently selected project.

The C/C++ Indexer uses the parser to create a database of source and header files that provide the basis for C/C++ search, navigation features and content assist. The goal of indexing is to record all named elements in a project's source code and store them with their related data. The indexer parses each source file in your project and updates related indexes. By indexing your files with the indexer, useful features such as code completion and fast file search can be used. It is also possible to specify different indexer settings for each project in your workspace.

If you choose to perform the Full C/C++ Indexer option the indexer will consume the CPU for some time, but you will gain more benefit from the process after it completes. + However, if you do not require the benefits of indexing your project, select the No Indexer option to speed up the process of building your project.

The indexer runs on a background thread and reacts to resource change events such as:

The global Indexer is accessed by selecting Window > Preferences > C/C++ > Indexer (figure 1). The sections outlined in red appear as part of the project level indexer.

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

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

Related concepts

Related tasks

Launch Configuration Filters

Name	Function
Select indexer	Dropdown list of available index options. + + Fast C/C++ Indexer - Source files will be indexed and eat up a lot of CPU time and memory during the first generation of the indexer. This can take some time depending on the size of your project. Afterwards the indexer will only reindex the relevant parts you changed in your code and not the whole source tree. + Full C/C++ Indexer - Performs a complete parse of all source files and takes up the most amount of time to complete. + No Indexer - Project source files are not indexed, therefore search features will not work accurately and code completion will not be available. +
Apply indexer to all projects now	Select this option to apply the Fast C/C++ Indexer option to all projects in your current workspace.
Rebuild the index when changing to a different build configuration	Select this option to rescan and index the source files for the current project when you change the active build configuration. The index will be built based on the active build configuration. All macros and header files used to build the index will be taken from the active build configuration.
Build the index only for the build configuration specified in the project's indexer settings + + Build the index only for the specified build configuration	The indexer will only be run for the build configuration specified in the Indexer panel in the project's property settings. All macros and header files used to build the index will be taken from the specified configuration. + + NOTE This option appears in the project properties indexer panel. A dropdown list is provided to select a build configuration for the currently selected project.

The Launch Configuration Filters panel is used to filter out which launch configurations will not appear in the Run or Debug window used to define launch configurations. For example, select the Filter checked launch configuration types option and check the configuration types that you do not want to appear in the Run > Run... or Run > Debug... window, as shown in Figure 1.

Related references

Related tasks

- - -

Launch Configuration Filters

Use the Launch Configurations panel to filter out which launch configurations appear in the Run or Debug window used to define launch configurations. For example, select the Delete configurations when associated resource is deleted option and check the configuration types that you do not want to appear in the Run > Run... or Run > Debug... window, as shown in Figure 1.

Related references

Related tasks

+ + +

ABLD Actions

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

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

Figure 1 shows the Dissassembly view and the PC context menu that appears when you right-click in the data pane. Right-clicking the left border opens the breakpoint context menu.

Table 1. Disassembly view —context menu

Figure 2 shows the context menu that appears when you right-click in the Dissassembly pane. Right-clicking the left border opens the breakpoint context menu in Figure 3.

Table 1. Disassembly pane — context menu

Item	Icon	Explanation	Item	Icon	Explanation
Run to Line	+ +	Select Run to Line to execute the program from the currently executed line (the green line) to the selected line (the blue line).
Run to Line	- -	Select Run to Line to execute the program from the currently executed line (the green line) to the selected line (the blue line).
Move to Line	+ +	Select Move to Line to move the program counter to the selected line (the blue line) skipping all intermediate lines but not resume execution. This enables you to skip suspect code and continue stepping through your program. + WARNING Using this command can leave a program in an unstable state. Use at your own risk.
Resume at Line	+ +	Select Resume at Line to begin program execution at the selected line (the blue line), skipping all lines between it and the currently executed line (the green line). + WARNING Using this command can leave a program in an unstable state. Use at your own risk.
ABLD		Use the ABLD menu option to invoke an specific abld command on the selected project or file.
Move to Line	- - -	Select Move to Line to move the program counter to the selected line (the blue line) skipping all intermediate lines but not resume execution. This enables you to skip suspect code and continue stepping through your program. - WARNING Using this command can leave a program in an unstable state. Use at your own risk.
Resume at Line	- -	Select Resume at Line to begin program execution at the selected line (the blue line), skipping all lines between it and the currently executed line (the green line). - WARNING Using this command can leave a program in an unstable state. Use at your own risk.
Toggle Breakpoint	-	Right-click in left-hand column of the Disassembly view and select this option to toggle the breakpoint state between setting and removing the breakpoint.
Disable/Enable Breakpoint	-	Right-click in left-hand column of the Disassembly view and select the breakpoint option shown as determined by the current state of the breakpoint.
Breakpoint Properties	-	Select this option to open the Breakpoint Properties dialog.
Freeze Exports	+ + +	Calls the appropriate abld command to generate a .def file.
Build All Configurations	+ + +	Click Build All Configurations to build all enabled build configurations in the current project.
Toggle Breakpoint	+	Right-click in left-hand column of the Disassembly view and select this option to toggle the breakpoint state between setting and removing the breakpoint.
Disable/Enable Breakpoint	+	Right-click in left-hand column of the Disassembly view and select the breakpoint option shown as determined by the current state of the breakpoint.
Breakpoint Properties	+	Select this option to open the Breakpoint Properties dialog.

Opening the Disassembly view

Refresh

ArrayWindow

Array Window

An Array window allows manipulation of a contiguous block of memory, displayed as an array of elements. The window lists array contents sequentially, starting at -element 0.

The Array window title shows the base address bound to the array. The base address can bind to an address, a variable, or a register. An array bound to a local variable closes after the routine that defines the variable returns to the calling routine.

For array elements cast as structured types, a hierarchical control appears to the left of each element. Use these hierarchical controls to expand or collapse the display of each element’s contents.

Figure 1 shows an Array window. Table 1 explains the items in the window.

Figure 1 Array window

Table 1 Array window—items

Item	Icon	Explanation
Hierarchical control		Click to collapse the view of the information pane.
Bind To		Select the base address of the array: Address, Variable, or Register.
Array size		Enter the number of elements to display in the Array window.
Struct Member		Select a specific member to show in each element, or show all members.
Element		Shows the array elements in a hierarchical list.
Value		Shows the value of each array element.
Location		Shows the address in memory of each array element.

Opening an Array Window

Use the View Array command to manipulate a memory block in an Array window.

Select the array that you want to view.
Select Data > View Array.

A new Array window appears.

TIP Drag and drop a register or variable name into an Array window to set the base address. Use the View Memory As command to interpret memory displayed in an Array window as a different type.

Alternatively, use a contextual menu to open an Array window, as explained in Table 2.

Table 2 Opening an Array window by using a contextual menu

On this host…	Do this…
Windows	Right-click the array and select View Array.
Solaris	Click and hold on the array, then select View Array.
Linux	Click and hold on the array, then select View Array.

ArrayWindow

Array Window

The Array window allows manipulation of a contiguous block of memory, displayed as an array of elements. The window lists array contents sequentially, starting at +element 0.

Figure 1 shows an Array window. Table 1 explains the items in the window.

Figure 1 Array window

Table 1 Array window—items

Item	Icon	Explanation
Hierarchical control		Click to collapse the view of the information pane.
Bind To		Select the base address of the array: Address, Variable, or Register.
Array size		Enter the number of elements to display in the Array window.
Struct Member		Select a specific member to show in each element, or show all members.
Element		Shows the array elements in a hierarchical list.
Value		Shows the value of each array element.
Location		Shows the address in memory of each array element.

Opening an Array Window

Use the View Array command to manipulate a memory block in an Array window.

Select the array that you want to view.
Select Data > View Array.

A new Array window appears.

TIP Drag and drop a register or variable name into an Array window to set the base address. Use the View Memory As command to interpret memory displayed in an Array window as a different type.

Alternatively, use a contextual menu to open an Array window, as explained in Table 2.

Table 2 Opening an Array window by using a context menu

On this host…	Do this…
Windows	Right-click the array and select View Array.
Solaris	Click and hold on the array, then select View Array.
Linux	Click and hold on the array, then select View Array.

New > Class

- The New C++ Class wizard then appears. -

New C++ Class

- Specify the folder when the class should be created by typing the Source Folder name or by clicking Browse and + Specify the folder where the class should be created by typing the Source Folder name or by clicking Browse and selecting the source folder.

@@ -40,7 +39,7 @@
Click Add to choose the Base Classes from which the class has to be derived
-
+

To select a base type you are looking for, do the following:
1. Type the search string to locate the class, struct and other low-level types you are looking for
2. Click Finish to create a C++ class according to the specification, or click Cancel to cancel the task.


 
diff -r 226789abed73 -r 77469bd2d10b core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/eventpoints_disabling.htm
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/eventpoints_disabling.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/eventpoints_disabling.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -1,28 +1,28 @@
-
-
-
-
-
-
-Disabling an Eventpoint
-
-
-
-Disabling an Eventpoint
-Disable an eventpoint to prevent it from performing its specified action. The disabled eventpoint remains at the source-code line at which you set it, so that you can enable it later. Disabling the eventpoint is easier than clearing it and re-creating it from scratch.
-
-  To disable an eventpoint
-  
-    Select the eventpoint to disable
-    Select the eventpoint by name in the Breakpoints view, or click the cursor on the source-code line that contains the eventpoint.
-    Click Debug > Disable Eventpoint
-    The Disable Eventpoint menu appears.
-    From the menu, click the Disable Eventpoint command, where Eventpoint is the type of eventpoint that you want to disable
-    The enabled eventpoint icon changes to a disabled eventpoint icon (shown at left). The disabled eventpoint icon indicates that the eventpoint does not perform its specified action.

-
-  
-
-Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. 
License: http://www.eclipse.org/legal/epl-v10.html
-
-
-
+
+
+
+
+
+
+Disabling an Eventpoint
+
+
+
+Disabling an Eventpoint
+Disable an eventpoint to prevent it from performing its specified action. The disabled eventpoint remains at the source-code line at which you set it, so that you can enable it later. Disabling the eventpoint is easier than clearing it and re-creating it from scratch.
+
+  To disable an eventpoint
+  
+    Select the eventpoint to disable
+    Select the eventpoint by name in the Breakpoints view, or click the cursor on the source-code line that contains the eventpoint.
+    Click Debug > Disable Eventpoint
+    The Disable Eventpoint menu appears.
+    From the menu, click the Disable Eventpoint command, where Eventpoint is the type of eventpoint that you want to disable
+    The enabled eventpoint icon changes to a disabled eventpoint icon (shown at left). The disabled eventpoint icon indicates that the eventpoint does not perform its specified action.

+
+  
+
+Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. 
License: http://www.eclipse.org/legal/epl-v10.html
+
+
+
diff -r 226789abed73 -r 77469bd2d10b 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 Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/eventpoints_enabling.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -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.
-  
-
-Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. 
License: http://www.eclipse.org/legal/epl-v10.html
-
-
-
+
+
+
+
+
+
+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.
+  
+
+Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. 
License: http://www.eclipse.org/legal/epl-v10.html
+
+
+
diff -r 226789abed73 -r 77469bd2d10b 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 Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/eventpoints_setting.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -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.

-
-Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. 
License: http://www.eclipse.org/legal/epl-v10.html
-
-
-
+
+
+
+
+
+
+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.

+
+Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. 
License: http://www.eclipse.org/legal/epl-v10.html
+
+
+
diff -r 226789abed73 -r 77469bd2d10b 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 Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/eventpoints_viewing.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -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

-
-  
-
-Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. 
License: http://www.eclipse.org/legal/epl-v10.html
-
-
-
+
+
+
+
+
+
+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

+
+  
+
+Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. 
License: http://www.eclipse.org/legal/epl-v10.html
+
+
+
diff -r 226789abed73 -r 77469bd2d10b 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 Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/log_point_clear.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -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
-
-  Setting a Pause Point
-  Clearing a Pause Point 
-
- 
-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.
-  
-
-Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. 
License: http://www.eclipse.org/legal/epl-v10.html
-
-
+
+
+
+
+
+
+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 Pause Point
+  Clearing a Pause Point 
+
+ 
+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.
+  
+
+Copyright © 2009 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 226789abed73 -r 77469bd2d10b 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 Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/log_point_set.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -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 Pause Point
-  Clearing a Pause Point 
-
- 
-
-  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.
-Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. 
License: http://www.eclipse.org/legal/epl-v10.html
-
-
+
+
+
+
+
+
+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 Pause Point
+  Clearing a Pause Point 
+
+ 
+
+  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.
+Copyright © 2009 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 226789abed73 -r 77469bd2d10b 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 Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/pause_point_clear.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -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.

-    
-  
-
-  
-Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. 
License: http://www.eclipse.org/legal/epl-v10.html
-
-
+
+
+
+
+
+
+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.

+    
+  
+
+  
+Copyright © 2009 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 226789abed73 -r 77469bd2d10b 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 Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/pause_point_set.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -1,32 +1,32 @@
-
-
-
-
-
-
-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 
-
- 
-
-    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.
-    
-
-  
-  
-Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. 
License: http://www.eclipse.org/legal/epl-v10.html
-
-
+
+
+
+
+
+
+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 
+
+ 
+
+    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.
+    
+
+  
+  
+Copyright © 2009 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 226789abed73 -r 77469bd2d10b 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 Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/trace_collection_clear.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -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
-  
-
-Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. 
License: http://www.eclipse.org/legal/epl-v10.html
-
-
-
+
+
+
+
+
+
+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
+  
+
+Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. 
License: http://www.eclipse.org/legal/epl-v10.html
+
+
+
diff -r 226789abed73 -r 77469bd2d10b 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 Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/trace_collection_off.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -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
-  
-
-Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. 
License: http://www.eclipse.org/legal/epl-v10.html
-
-
-
+
+
+
+
+
+
+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
+  
+
+Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. 
License: http://www.eclipse.org/legal/epl-v10.html
+
+
+
diff -r 226789abed73 -r 77469bd2d10b 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 Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/eventpoints/trace_collection_on.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -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 steps:
-  
-    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
-  
-
-Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. 
License: http://www.eclipse.org/legal/epl-v10.html
-
-
-
+
+
+
+
+
+
+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
+  
+
+Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. 
License: http://www.eclipse.org/legal/epl-v10.html
+
+
+
diff -r 226789abed73 -r 77469bd2d10b core/com.nokia.carbide.cpp.doc.user/html/tasks/images/wnd_chooseBaseClass.png
Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/images/wnd_chooseBaseClass.png has changed
diff -r 226789abed73 -r 77469bd2d10b core/com.nokia.carbide.cpp.doc.user/html/tasks/index.html
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/index.html	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/index.html	Thu Feb 18 11:17:02 2010 -0600
@@ -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. 
-  
-  
-Working with SDKs
-Creating New Projects
-Importing Projects from a Bld.Inf File
-Exporting Project(s) to MMP/Bld.inf Files 
-Adding Classes
-Modifying Resources
-Building Projects
-
-
-
-
-Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. 
License: http://www.eclipse.org/legal/epl-v10.html
-
-   
-   
+
+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. 
+  
+  
+Working with SDKs
+Creating New Projects
+Importing Projects from a Bld.Inf File
+Exporting Project(s) to MMP/Bld.inf Files 
+Adding Classes
+Modifying Resources
+Building Projects
+
+
+
+
+Copyright © 2009 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 226789abed73 -r 77469bd2d10b core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/open_log_view.htm
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/open_log_view.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/processes/open_log_view.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -1,26 +1,28 @@
-
-
-
-
-
-
-Opening a Log View
-
-
-
-Opening a Log View
-Use the Debugger Settings preference panel to enable the message logging option. The Log view records these types of messages for a program during a debugging session:
-
-  the start of new tasks
-  routine entry and exit
-  Windows: DLL loading and unloading, and debug printf() messages
-
-Select the Log System Messages option in the Debugger Settings target settings preference panel.
-Select Project > Debug.
-
-  The Log view appears. It allows you to select, copy, and save logged text to a file for later analysis. 
-
-Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. 
License: http://www.eclipse.org/legal/epl-v10.html
-
-
-
+
+
+
+
+
+
+Opening a Log View
+
+
+
+Opening a Log View
+Use the Debugger Settings preference panel to enable the message logging option. The Log view records these types of messages for a program during a debugging session:
+
+  the start of new tasks
+  routine entry and exit
+  Windows: DLL loading and unloading, and debug printf() messages
+
+Select the Log System Messages option in the Debugger Settings target settings preference panel.
+
+  Select Project > Debug
+
+
+  The Log view appears. It allows you to select, copy, and save logged text to a file for later analysis. 
+
+Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. 
License: http://www.eclipse.org/legal/epl-v10.html
+
+
+
diff -r 226789abed73 -r 77469bd2d10b core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_creating_sis_file.htm
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_creating_sis_file.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_creating_sis_file.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -38,7 +38,7 @@
     SIS Properties 
     
       Complete the PKG File, and Signing Options settings in the SIS Properties dialog. By default, SIS files are output in the directory of the original SIS file.
-      
+      
       Figure 2 - SIS Properties dialog 
       
   
@@ -57,7 +57,7 @@
 
   Manually Deploying Programs to Devices
 
-Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. 
License: http://www.eclipse.org/legal/epl-v10.html
+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 226789abed73 -r 77469bd2d10b core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_console.htm
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_console.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_console.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -1,49 +1,49 @@
-
-
-
-
-
-
-Debugging Applications
-
-
-
-Debugging Applications
-You can debug one or more applications just as you would any other executable with full support of the Carbide debugger. There are two methods that one can use to debug an application:
-
-  For console applications, assign the Executable and leave the Emulator blank in the Debug window
-  In the Debug window or launch configuration, simply  point the Executable option  to the  executable and clear the Emulator option  as shown in Figure 1. This launches the  application when you start a debug session from the project. 
-
-
-  
-  Figure 1 - Launch ConsoleTest executable to debug the ConsoleTest project
-
-
-
-  For regular applications, assign the Executable and Remote process to launch in the Debug window
-
-
-  In the Debug window or launch configuration, simply point both the Executable   and  Remote process to launch options to the application. This launches the  application when you start a debug session from the application project.
-  
-  Figure 2 - Assign Executable and Remote Process
-
-Related concepts
-  
-    Projects
-    Project Resources 
-  
-  Related tasks
-  
-    Debugging DLLs 
-    Importing Symbian Executables 
-    Creating a Launch Configuration
-  
-  Related references
-  
-    Project Directories
-
-
-Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. 
License: http://www.eclipse.org/legal/epl-v10.html
-
-
+
+
+
+
+
+
+Debugging Applications
+
+
+
+Debugging Applications
+You can debug one or more applications just as you would any other executable with full support of the Carbide debugger. There are two methods that one can use to debug an application:
+
+  For console applications, assign the Executable and leave the Emulator blank in the Debug window
+  In the Debug window or launch configuration, simply  point the Executable option  to the  executable and clear the Emulator option  as shown in Figure 1. This launches the  application when you start a debug session from the project. 
+
+
+  
+  Figure 1 - Launch ConsoleTest executable to debug the ConsoleTest project
+
+
+
+  For regular applications, assign the Executable and Remote process to launch in the Debug window
+
+
+  In the Debug window or launch configuration, simply point both the Executable   and  Remote process to launch options to the application. This launches the  application when you start a debug session from the application project.
+  
+  Figure 2 - Assign Executable and Remote Process
+
+Related concepts
+  
+    Projects
+    Project Resources 
+  
+  Related tasks
+  
+    Debugging DLLs 
+    Importing Symbian Executables 
+    Creating a Launch Configuration
+  
+  Related references
+  
+    Project Directories
+
+
+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 226789abed73 -r 77469bd2d10b 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 Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/sdks/sdk_search.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -10,7 +10,7 @@
 
 Searching for SDKs
   Use the SDK Preferences panel to search for installed Symbian OS SDKs.
-
+
 Figure 1. SDK Preferences panel
 
   Searching for SDKs 
diff -r 226789abed73 -r 77469bd2d10b core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_requirements.htm
--- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_requirements.htm	Thu Feb 18 10:33:34 2010 -0600
+++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/start/carbide_requirements.htm	Thu Feb 18 11:17:02 2010 -0600
@@ -26,12 +26,12 @@
     An SDK or OS developer kit (DevKit) including:
       9.x or higher for Platform Security 
     
-    Targets: S60 5th and 3rd Ed., Qt, UIQ
+    Targets: S60 5th and 3rd Ed., Qt
       Debugger: Emulators, on-device debugging
     UI Designer: create graphical interfaces quickly using standard UI components
   
   
-    Targets: S60 5th and 3rd Ed., Qt, UIQ
+    Targets: S60 5th and 3rd Ed., Qt
     Debugger: Emulators, on-device debugging, device debugging in ROM, kernel debugging 
     Performance Investigator: application performance data, memory usage, power usage, button event reporting 
   
@@ -72,12 +72,6 @@
             Qt SDK for S60
           
         
-        UIQ SDKs (www.uiq.com)
-          
-            UIQ 3.1 
-            UIQ 3.0
-          
-        
       
       Perl (www.activestate.com)
     (required)              
@@ -100,7 +94,7 @@
 
    Carbide.c++ Overview
 
-Copyright © 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. 
License: http://www.eclipse.org/legal/epl-v10.html
+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