MBM Editor

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

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

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

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

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

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

- -

Name Function

Source Folder

diff -r 1c77dba7ce70 -r 90c95d26606c core/com.nokia.carbide.cpp.doc.user/html/reference/NewMMP_wizard.html --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/NewMMP_wizard.html Mon Jun 21 16:25:36 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/NewMMP_wizard.html Mon Jun 21 16:26:29 2010 -0500 @@ -7,7 +7,7 @@

Symbian OS MMP File

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

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

Creating a New Symbian OS MMP File

Select the File > New > Other... menu item (Figure 1)

-
+

Figure 1 - Select a wizard page in the New window

OR

-
+

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

On the Select the wizard page, select Symbian OS > Symbian OS MMP File, then click Next (Figure 1)

Project Directories in New Project Wizard

Project Directories

- -

- You can specify the name of the project directories, where the project - files are to be stored. -

- -

Figure 1 - Project Directories page

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

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.

Related tasks

Creating New Projects -

Project Directories in New Project Wizard

Project Directories

+ +

+ You can specify the name of the project directories, where the project + files are to be stored. +

+ +

Figure 1 - Project Directories page

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

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.

Related tasks

Creating New Projects +

Name and Location

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

Figure 1 - Name and Location page

Table 1 - Name and Locations page options

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.

Name and Location

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

Figure 1 - Name and Location page

Table 1 - Name and Locations page options

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.

Project and File Properties

C/C++ Project and File Properties

- The Properties window allows you to change the general - settings for a project and individual files.

Properties for <project_name>

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

The Carbide.c++ panels include:

Build Configurations
Macro Settings
Project Settings
other - additional panels may appear here as well. For example, CodeScanner and UI Designer, to name two.
other - additional panels may appear here as well. For example, CodeScanner.

Figure 1. Project for project_name dialog

To change the settings only for a particular file, right-click the file diff -r 1c77dba7ce70 -r 90c95d26606c core/com.nokia.carbide.cpp.doc.user/html/reference/add_from_filesys.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/add_from_filesys.htm Mon Jun 21 16:25:36 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/add_from_filesys.htm Mon Jun 21 16:26:29 2010 -0500 @@ -1,55 +1,55 @@ - - -MBM/MIF Editor - - - - -

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.

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

Figure 1 - Add Images from Filesystem

Table 1. Add Images—Items

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.

Other references

MBM Editor

MBM/MIF Editor

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.

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

Figure 1 - Add Images from Filesystem

Table 1. Add Images—Items

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.

Other references

MBM Editor

MBM/MIF 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.

Figure 1 - Add Images from Project

Other references

MBM Editor

MBM/MIF Editor

Add Images From Project

The Add Images from Project dialog allows you to add images currently included in the project. Select one or more images and click OK to add the image to the MMP file.

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

Figure 1 - Add Images from Project

Other references

MBM Editor

Carbide Build Configurations

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

Figure 1 - Carbide Build Configurations panel

Table 1 Carbide Build Configuration items

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.

Other references

Build Configurations

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

Figure 1 - Carbide Build Configurations panel

Table 1 Build Configuration items

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.

Other references

Carbide Macro Settings

Macro Settings

Carbide Macro Settings

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

Macro Settings

The Macro Settings properties page allows you to specify a file containing macros that CDT uses to parse the source code.

Figure 1 - Carbide Macros Settings panel

Table 1 Carbide Macros Settings items

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.

Figure 1 - Carbide Project Settings

Table 1 Carbide Project Settings items

Item	Explanation	Item	Explanation
Macro File

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.

sbsv1 tab

Figure 2 - SBSv1 Tab

Table 2 Symbian Build System v1 tab

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.

sbsv2 tab

Figure 3 - SBSv2 Tab

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

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.

Related tasks

Building Projects

Project Settings

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

Figure 1 - Project Settings

Table 1 Project Settings items

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.

sbsv1 tab

Figure 2 - SBSv1 Tab

Table 2 Symbian Build System v1 tab

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.

sbsv2 tab

Figure 3 - SBSv2 Tab

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

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.

Related tasks

Building Projects

Launch Configuration Filtering

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

Use the Launch Configuration preference panel to filter the launch configurations that appear in the configurations list in the Run or Debug window. This allows you to manage which configuration types are shown. By default, all launch configurations are shown. To open click the Windows > Preferences > Run/Debug > Launching > Launch Configurations option.

To hide specific launch configurations, enable the Filter checked launch configuration types option and check the configuration types that should be hidden in the Run and Debug dialogs. As shown in Figure 1, all the configurations checked and won't appear in the configurations list, including Snapshot Albums.

Launch Configurtion Filter preference panel

Figure 1 - Launch Configurations preference panel

Related references

Build Symbian Component

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

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

Figure 1. Build Symbian Component menu item

- - + + @@ -107,10 +107,10 @@ - - + + - + @@ -135,7 +135,7 @@ - +

MBM Editor

Table 1. MBM Editor —Items

Related concepts

Related tasks

MBM Editor

Table 1. MBM Editor —Items

Related concepts

Related tasks

References

New Class Wizard

New C++ Class Wizard

Symbian OS MMP File

Creating a New Symbian OS MMP File

Project Directories

Related tasks

Project Directories

Related tasks

Name and Location

Table 1 - Name and Locations page options

Name and Location

Table 1 - Name and Locations page options

C/C++ Project and File Properties

Add Images From Filesystem

Table 1. Add Images—Items

Other references

Add Images From Filesystem

Table 1. Add Images—Items

Other references

Add Images From Project

Other references

Add Images From Project

Other references

Carbide Build Configurations

Table 1 Carbide Build Configuration items

Other references

Build Configurations

Table 1 Build Configuration items

Other references

Carbide Macro Settings

Macro Settings

Table 1 Carbide Macros Settings items

Carbide Project Settings

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

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

Launch Configuration Filtering

Related references

Build Symbian Component