SDK Preferences

Use the Active Configuration option in the Carbide Build Configurations panel to specify the build target. Since a project can contain one or more build targets, the active configuration defines which build configuration to use when the project is run or debugged. A launch configuration consists of the following:

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

You can select a build configuration in the Active Configuration group or use the Project > Active Configuration menu option to set which build configuration to launch when running or debugging a program. The currently selected project can be launched by clicking the Run (

) or Debug (

) control on the tool bar to launch the project with the currently active build configuration. When no project is selected the last project debugged will be launched.

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

Other references

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.

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

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.

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

Select SDKs for build targets

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

Select Qt modules to include in project

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

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.

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.

The INF Editor is shown when an INF file is - opened from the Project Explorer view or Symbian Project Navigator view by double-clicking on the file. The INF Editor is shown in Figure 1.

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

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

Related tasks

Build Configurations

Name	Function
Available Symbian OS SDK's	Lists all the installed and recognized SDKs supported by the IDE. Only SDKs supported by the IDE are included in the list. - Checked SDKs indicate build configurations available for creating projects. Unchecked SDKs are not displayed when creating new projects. - SDKs shown in red indicate a problem, usually no EPOCROOT or missing build configurations. - Click on a SDK name to see its EPOCROOT location and build configuration status in the SDK Information area.
Remove SDK	Click to remove the selected SDK from the Available Symbian OS SDK's list.
Add New SDK	Click to add an SDK to the Available Symbian OS SDKs list.
SDK Properties	Click to view and edit the properties of the currently selected SDK in the Available Symbian OS SDKs list.
Listen for devices.xml changes outside of Carbide	Enable of have Carbide issue an alert prompting you to rescan your SDKs when changes to the devices.xml file are made outside of Carbide. When disabled the devices.xml file is not scanned for changes.
Rescan All SDKs	Click to rescan the drive for newly installed SDKs. The devices.xml file is scanned for SDKs and the list of available SDKs is updated if the devices.xml file has changed. - NOTE Carbide.c++ scans for available SDKs each time it is started.

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

Table 1 Build Configuration items

Other references

Creating New Symbian OS C++ Projects

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.
SBSv2	The SBSv2 pane is used to define which build configuration variant to use.
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.
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.

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.

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.

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
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 mode	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.
Additional SBSv2 arguments	Enter any additional arguments to pass to sbs.bat.
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.
Make engine	Enter the name of a different make engine to use when building.

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.
SBSv2	The SBSv2 pane is used to define which build configuration variant to use.
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.
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.

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
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 mode	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.
Additional SBSv2 arguments	Enter any additional arguments to pass to sbs.bat.
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.
Make engine	Enter the name of a different make engine to use when building.

Item	Explanation
Use built-in Nokia x86 environment variables for WINSCW builds	If enabled, Carbide adds the built-in x86 compiler environment variables to the build environment. + If the option is not + checked, the build process will build with whatever tools are defined in your environment. + A directory named x86Build at the root of the product installation contains the build tools, libraries, and env_update.exe.
Build test components when building from bld.inf	Enable to build all the projects defined by .MMP files listed under the PRJ_TESTMMPFILES section of the component description file. + If not enabled, only those projects defined by .MMP files listed under the PRJ_MMPFILES section of the component description file are built.
Run builds concurrently (improves compile time)	Enable to tell Carbide to generate concurrent builds up to the amount specified in the Build jobs field. This option can significantly reduce build times as it takes advantage of multi-core processors and hyperthreading to run multiple threads at once. + If not enabled, only a single build is run. Note that this may be required if your project contains circular dependencies or other issues that prevent concurrent builds from executing correctly.
Use default incremental builder	Enable to have Carbide determine if a build is required by checking the state of any file in the workspace.

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 (improves build speed)	Enable to have Carbide manage the dependency tracking for source and resource files. Carbide does this by separating out the generation of dependency information from the makefile and managing the entire process. All builds now can quickly compare whether new dependency information is required due to changes in a source file and only build those that need updating. + If not enabled, the Symbian OS command line build system handles all dependency tracking by generating the dependency information in the makefiles. Because it does this for all project files, regardless of the number of changes, it can result in a performance penalty. A single edit in a MMP file forces a complete regeneration of the makefile dependency information for all project files.
Show a dialog to modify build actions when modified MMPs are detected	Enable to have Carbide ask before starting a build what action to take when modified files are detected. When disabled, do not show a dialog but use the default action listed below.
Default action to take when mmp files are modified	Defines the default action Carbide should execute when it detects modified MMP files and the option above is disabled: + + None + Link Only + Compile and Link +
Do not offer to track dependencies for projects build on command-line	If you build a project from the command-line (with 'abld build') and then import the project into Carbide and attempt to build, Carbide will ask if you would like Carbide to manage source dependencies for you. Enabling this option insures Carbide will not ask you to manage dependencies (they will be done as normally done via 'abld build' command).

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 mode	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.
Additional SBSv2 arguments	Enter additional SBSv2 build arguments here.
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.

Item	Explanation
Keep Symbian OS project files (bld.inf/mmp) in sync with project changes	Select this option to update project files (bld.inf and mmp) when you add, remove, rename or move files and directories in your current workspace.
When files are added to the project	The following options are available when files are added to a project: + + Ask before changing bld.inf/mmp - You are prompted to allow changes + Always change bld.inf/mmp - Changes are made wthout asking you to allow change + Never change bld.inf/mmp - No changes are made +
When files in the project are moved/renamed/deleted	The following options are available that effect the bld.inf or mmp files when files in a project are moved, renamed, or deleted: + + Ask before changing bld.inf/mmp - You are prompted to allow changes + Always change bld.inf/mmp - Changes are made wthout asking you to allow change + Never change bld.inf/mmp - No changes are made +
Indexing Options	The following options control how the project mmp files are indexed: + + Index only source files from mmp files being built (default) + Index source files from all mmp files +

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.

Item	Explanation
Diagnostic Logs	A list of the log files that can be generated. Log files are stored in the project but are not visible in the Project Explorer or C/C++ Project views.
Clear Logs	Click to erase all log files from the project. +

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

Name	Function
Available Symbian OS SDK's	Lists all the installed and recognized SDKs supported by the IDE. Only SDKs supported by the IDE are included in the list. + Checked SDKs indicate build configurations available for creating projects. Unchecked SDKs are not displayed when creating new projects. + SDKs shown in red indicate a problem, usually no EPOCROOT or missing build configurations. + Click on a SDK name to see its EPOCROOT location and build configuration status in the SDK Information area.
Remove SDK	Click to remove the selected SDK from the Available Symbian OS SDK's list.
Add New SDK	Click to add an SDK to the Available Symbian OS SDKs list.
SDK Properties	Click to view and edit the properties of the currently selected SDK in the Available Symbian OS SDKs list.
Listen for devices.xml changes outside of Carbide	Enable of have Carbide issue an alert prompting you to rescan your SDKs when changes to the devices.xml file are made outside of Carbide. When disabled the devices.xml file is not scanned for changes.
Rescan All SDKs	Click to rescan the drive for newly installed SDKs. The devices.xml file is scanned for SDKs and the list of available SDKs is updated if the devices.xml file has changed. + NOTE Carbide.c++ scans for available SDKs each time it is started.

Item	Explanation
Display Carbide.c++ news page at startup	Enable to always show the news view when Carbide is launched. Recommended to ensure you are kept aware of the latest Carbide news and related information. Disable to not show the page on launch. +
Subscribed news feeds	The list of subscribled news feeds.
Update news feed	Select the time period that the news reader checks for updated stories.

Item	Explanation
Display Carbide.c++ news page at startup	Enable to always show the news view when Carbide is launched. Recommended to ensure you are kept aware of the latest Carbide news and related information. Disable to not show the page on launch. -
Subscribed news feeds	The list of subscribled news feeds.
Update news feed	Select the time period that the news reader checks for updated stories.

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

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

Item	Icon	Explanation
New Memory View		Click to add a new Memory monitor view.
Pin Memory Monitor		Pin memory view.
Toggle Memory Monitors Pane		Toggles the current Memory monitors view between showing only a Memory Monitor pane and a Memory Monitor and Memory Rendering pane.
Toggle Split Pane		Alternately shows and hides the Memory Rendering pane.
Link Memory Monitor Panes		Enable to synchronize the current selection between the rendering of the same memory monitor .
Switch Memory Monitor		If different memory monitor views have been added, select from list of memory monitor views.
Add Memory Monitor / Add Rendering		Add a new memory address or variable to the Memory Monitors pane, or add a new rendering to the Memory Rendering pane.
Remove Memory Monitor / Remove Rendering		Remove the selected memory address or variable from the Memory Monitors pane, or remove the selected rendering from the Memory Rendering pane.
Remove All		Remove all memory monitors or renderings from the associated pane.

Item	Icon	Explanation
New Memory View		Click to add a new Memory monitor view.
Pin Memory Monitor		Pin memory view.
Toggle Memory Monitors Pane		Toggles the current Memory monitors view between showing only a Memory Monitor pane and a Memory Monitor and Memory Rendering pane.
Toggle Split Pane		Alternately shows and hides the Memory Rendering pane.
Link Memory Monitor Panes		Enable to synchronize the current selection between the rendering of the same memory monitor .
Switch Memory Monitor		If different memory monitor views have been added, select from list of memory monitor views.
Add Memory Monitor / Add Rendering		Add a new memory address or variable to the Memory Monitors pane, or add a new rendering to the Memory Rendering pane.
Remove Memory Monitor / Remove Rendering		Remove the selected memory address or variable from the Memory Monitors pane, or remove the selected rendering from the Memory Rendering pane.
Remove All		Remove all memory monitors or renderings from the associated pane.

Item	Explanation
Name	Displays the name of the signal.
Pass	Where "yes" is displayed, the debugger lets your program see the signal. Your program can handle the signal, or else it may terminate if the signal is fatal and not handled.
Suspend	Where "yes" is displayed, the debugger suspends your program when this signal is handled.
Description	Displays a description of the signal.

Item	Explanation
Name	Displays the name of the signal.
Pass	Where "yes" is displayed, the debugger lets your program see the signal. Your program can handle the signal, or else it may terminate if the signal is fatal and not handled.
Suspend	Where "yes" is displayed, the debugger suspends your program when this signal is handled.
Description	Displays a description of the signal.

Item	Explanation
Use built-in Nokia x86 environment variables for WINSCW builds	If enabled, Carbide adds the built-in x86 compiler environment variables to the build environment. - If the option is not - checked, the build process will build with whatever tools are defined in your environment. - A directory named x86Build at the root of the product installation contains the build tools, libraries, and env_update.exe.
Build test components when building from bld.inf	Enable to build all the projects defined by .MMP files listed under the PRJ_TESTMMPFILES section of the component description file. - If not enabled, only those projects defined by .MMP files listed under the PRJ_MMPFILES section of the component description file are built.
Run builds concurrently (improves compile time)	Enable to tell Carbide to generate concurrent builds up to the amount specified in the Build jobs field. This option can significantly reduce build times as it takes advantage of multi-core processors and hyperthreading to run multiple threads at once. - If not enabled, only a single build is run. Note that this may be required if your project contains circular dependencies or other issues that prevent concurrent builds from executing correctly.
Use default incremental builder	Enable to have Carbide determine if a build is required by checking the state of any file in the workspace.

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 (improves build speed)	Enable to have Carbide manage the dependency tracking for source and resource files. Carbide does this by separating out the generation of dependency information from the makefile and managing the entire process. All builds now can quickly compare whether new dependency information is required due to changes in a source file and only build those that need updating. - If not enabled, the Symbian OS command line build system handles all dependency tracking by generating the dependency information in the makefiles. Because it does this for all project files, regardless of the number of changes, it can result in a performance penalty. A single edit in a MMP file forces a complete regeneration of the makefile dependency information for all project files.
Show a dialog to modify build actions when modified MMPs are detected	Enable to have Carbide ask before starting a build what action to take when modified files are detected. When disabled, do not show a dialog but use the default action listed below.
Default action to take when mmp files are modified	Defines the default action Carbide should execute when it detects modified MMP files and the option above is disabled: - - None - Link Only - Compile and Link -
Do not offer to track dependencies for projects build on command-line	If you build a project from the command-line (with 'abld build') and then import the project into Carbide and attempt to build, Carbide will ask if you would like Carbide to manage source dependencies for you. Enabling this option insures Carbide will not ask you to manage dependencies (they will be done as normally done via 'abld build' command).

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 mode	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.
Additional SBSv2 arguments	Enter additional SBSv2 build arguments here.
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.

Item	Explanation
Keep Symbian OS project files (bld.inf/mmp) in sync with project changes	Select this option to update project files (bld.inf and mmp) when you add, remove, rename or move files and directories in your current workspace.
When files are added to the project	The following options are available when files are added to a project: - - Ask before changing bld.inf/mmp - You are prompted to allow changes - Always change bld.inf/mmp - Changes are made wthout asking you to allow change - Never change bld.inf/mmp - No changes are made -
When files in the project are moved/renamed/deleted	The following options are available that effect the bld.inf or mmp files when files in a project are moved, renamed, or deleted: - - Ask before changing bld.inf/mmp - You are prompted to allow changes - Always change bld.inf/mmp - Changes are made wthout asking you to allow change - Never change bld.inf/mmp - No changes are made -
Indexing Options	The following options control how the project mmp files are indexed: - - Index only source files from mmp files being built (default) - Index source files from all mmp files -

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.

Item	Explanation
Diagnostic Logs	A list of the log files that can be generated. Log files are stored in the project but are not visible in the Project Explorer or C/C++ Project views.
Clear Logs	Click to erase all log files from the project. -

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

New projects are created using the New Project Wizard. Carbide includes a number of templates that make creating projects for different SDKs and executables quick and easy.

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

NOTE When creating or importing projects the sources and SDK must be on the same drive. This is due to many of the internal SDK tools using an implicit working drive to calculate paths (e.g. \epoc32\tools). Avoid spaces in SDK paths since this will also cause problems.

Creating New Symbian OS C++ Projects

@@ -18,7 +18,7 @@

The New Symbian OS C++ Project wizard appears. Select a template related to an installed SDK.

A project template provides the initial source files and project settings appropriate for the chosen project type. A brief description of each template appears below the list. The project type determines the type of program that you are writing.

NOTE If the selected template requires user input, additional wizard pages will collect data from the user before creating the project.

Checkmark the Filter templates based on enabled SDKs option to only list SDKs enabled in the SDK Preferences panel. Uncheck this option to list SDKs that can be used with Carbide. Click Next.

Enter a name for your project.

Checkmark the Use default location option to save the project in the current workspace by default or uncheck it to save to another location. Enter the path in the Location field or click Browse button to locate the directory. Click Next.

@@ -68,7 +68,7 @@

Accept the defaults or enter the names for Include and Source folders to be created under the project root directory. Generated files will be copied to these directories.

Click Finish to create the project.

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

diff -r e17ab99b8f30 -r 2a5c0df13bad core/com.nokia.carbide.cpp.doc.user/html/tasks/EmulatorToc.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/EmulatorToc.htm Wed Jul 21 11:32:00 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/EmulatorToc.htm Wed Jul 21 13:50:58 2010 -0500 @@ -1,16 +1,16 @@ - -Classes - - - -
Emulator Projects
-
The topics include:
-
-
Setting Environment for x86 Compiler
-
Unsetting Built-in Environment
-
-
Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
License: http://www.eclipse.org/legal/epl-v10.html
- - - + +Classes + + + +
Emulator Projects
+
The topics include:
+
+
Setting Environment for x86 Compiler
+
Unsetting Built-in Environment
+
+
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 e17ab99b8f30 -r 2a5c0df13bad core/com.nokia.carbide.cpp.doc.user/html/tasks/ImportingProjects.html --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/ImportingProjects.html Wed Jul 21 11:32:00 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/ImportingProjects.html Wed Jul 21 13:50:58 2010 -0500 @@ -100,7 +100,7 @@
Click Finish to import the project
The - wizard creates the project in the Project Explorer view, where it can be built and edited as normal. If the wizard is unable to read the project files, then the page + wizard creates the project in the Project Explorer view, where it can be built and edited as normal. If the wizard is unable to read the project files, then the page describes the error that occurred. If an error occurs, you must fix the project file, and then re-import the bld.inf.

diff -r e17ab99b8f30 -r 2a5c0df13bad core/com.nokia.carbide.cpp.doc.user/html/tasks/WorkingwithSDKs.html --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/WorkingwithSDKs.html Wed Jul 21 11:32:00 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/WorkingwithSDKs.html Wed Jul 21 13:50:58 2010 -0500 @@ -8,13 +8,13 @@ which of the installed SDKs to work with. From the chosen SDK, Symbian OS plug-ins pick-up information such as header files, import libraries, documentation and other SDK specific information.
-
You can add and manage SDKs in the SDK Preferences panel. The SDK Preferences panel lists all +
You can add and manage SDKs in the SDK Preferences panel. The SDK Preferences panel lists all available SDKs and allows you to rescan the drive for newly installed and supported SDKs or remove an existing SDK. The changes in SDK Preferences are applicable to all projects under that workspace.

Related references

-
SDK Preferences
+
SDK Preferences

Adding SDKs

Searching SDKs

Viewing SDK Properties
diff -r e17ab99b8f30 -r 2a5c0df13bad 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 Wed Jul 21 11:32:00 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/code_style_reformatting_sources.htm Wed Jul 21 13:50:58 2010 -0500 @@ -10,7 +10,7 @@

To reformat a source file

-
Verify the correct code style is set in the Code Style preference panel
+
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)

diff -r e17ab99b8f30 -r 2a5c0df13bad 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 Wed Jul 21 11:32:00 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/code_style_workspace.htm Wed Jul 21 13:50:58 2010 -0500 @@ -13,7 +13,7 @@

To set the workspace code style

-
Open the Code Style preference panel
+
Open the Code Style preference panel

Choose a profile from the Select a profile dropdown list

Click OK

diff -r e17ab99b8f30 -r 2a5c0df13bad core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug.htm Wed Jul 21 11:32:00 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug.htm Wed Jul 21 13:50:58 2010 -0500 @@ -11,7 +11,7 @@
This example shows how to create and build an application and debug it on a device using JTAG debug software and Lauterbach hardware.

The basic steps include:

-
Verify that your SDK or customer kit is recognized in the SDK preferences panel.
+
Verify that your SDK or customer kit is recognized in the SDK preferences panel.

Create project or Import the project's bld.inf file into Carbide.c++

Specify your ROM build settings for the selected project

Build your Project with the ARMV5 Debug Build Configuration
diff -r e17ab99b8f30 -r 2a5c0df13bad core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_precond.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_precond.htm Wed Jul 21 11:32:00 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/debugger/stop_mode_debug_precond.htm Wed Jul 21 13:50:58 2010 -0500 @@ -18,7 +18,7 @@
Install Board Support Package (BSP) for your target board

Install JTAG software and drivers for Trace32 support

Connect JTAG interface between PC and hardware
-
Verify that your SDK or customer kit is recognized in the SDK preferences panel.
+
Verify that your SDK or customer kit is recognized in the SDK preferences panel.

Build your ROM Image

diff -r e17ab99b8f30 -r 2a5c0df13bad 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 Wed Jul 21 11:32:00 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/memory/memory_monitor_adding.htm Wed Jul 21 13:50:58 2010 -0500 @@ -9,7 +9,7 @@
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.
+
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
@@ -49,7 +49,7 @@

Related References

-
Memory View
+
Memory View

Copyright © 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved.
License: http://www.eclipse.org/legal/epl-v10.html
diff -r e17ab99b8f30 -r 2a5c0df13bad 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 Wed Jul 21 11:32:00 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/memory/memory_monitor_removing.htm Wed Jul 21 13:50:58 2010 -0500 @@ -50,7 +50,7 @@

View Memory	Opens a Memory view on the selected variable so you can examine it.	Opens a Memory view on the selected variable so you can examine it.
Format
View program output	Enable to direct standard output messages to the Emulation Program Output Console in the Console view. +	Enable to direct standard output messages to the Emulation Program Output Console in the Console view. NOTE In the epoc.ini file the option LogToFile must also be set to 1.
View program output	Enable to direct standard output messages to the TRK Program Output Console in the Console view. +	Enable to direct standard output messages to the TRK Program Output Console in the Console view. NOTE In the epoc.ini file the option LogToFile must also be set to 1.
Modify SIS builder settings for build configuration	Opens the SIS Builder tab in the Build Configurations panel in the project Properties window where you can edit, add, or remove SIS files associated with the project.	Opens the SIS Builder tab in the Build Configurations panel in the project Properties window where you can edit, add, or remove SIS files associated with the project.

Related references

Active Build Configuration

Other references

Other references

Supported Target Types

Table 1. Supported target types for all versions of Carbide.c++

Using SCM in Carbide

For On-device Debugging

Deploying the N-Gage project to a device

Working with Debugger Data

Working with Memory

Related tasks

Workspace Information

Setting and Removing Watchpoints

Setting watchpoints

Table 1. Add Watchpoint options

Other references

Launch the New Qt Project Wizard

Select type of Qt project

Enter project name and location

Select SDKs for build targets

Select Qt modules to include in project

Set application UID

Select .pro file to import

Related references

Symbian OS SDKs

Related references

SDK Preferences

Related tasks

Build Configurations

Table 1 Build Configuration items

Other references

Other references

Other references

Other references

Other references

SIS Builder

Table 1 SIS Builder items

Partial Upgrade Files

Other references

SIS Builder

Table 1 SIS Builder items

Partial Upgrade Files

Other references

Macro Settings

Table 1 Macros Settings items

Related references

Related reference

Project Settings

Table 1 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

Build Configurations

Table 1 Build Configuration items

Other references

Macro Settings

Table 1 Macros Settings items

Related references

Project Settings

Table 1 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

Related reference

Related References

ABLD Actions

Build All Configurations

Build Package (.pkg) File

Other references

Build Symbian Component

Clean Symbian Component

Other references

Compile

Other references

Freeze Exports

Other references

Freeze Symbian Component

Other references

Preprocess