AIF File in Concepts

- The AIF, or application information file, is a Symbian OS-specific file - format. An AIF file contains information about captions, icons, capabilities - and MIME priority support used by the application. The MMP editor provides support for the AIF editor in the Sources > Resources group.

Related tasks

Related references

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

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

The plug-ins provide a new perspective, called the Carbide.c++ Perspective, on the Eclipse workbench. This perspective enhances the standard CDT C/C++ perspective by allowing you to select easily the SDKs and build target types @@ -24,7 +24,6 @@

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

Using SCM in Carbide

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

diff -r 32748ddc5cdb -r ab4f029618cb core/com.nokia.carbide.cpp.doc.user/html/concepts/tour.html --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/tour.html Tue Jun 22 12:08:33 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/tour.html Tue Jun 22 14:05:02 2010 -0500 @@ -52,12 +52,10 @@

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

- For more information, see Creating an MBM File and Creating an AIF File. -

+ For more information, see Creating an MBM File.

diff -r 32748ddc5cdb -r ab4f029618cb core/com.nokia.carbide.cpp.doc.user/html/context_help/carbide_ide_dialogs_help.xml --- a/core/com.nokia.carbide.cpp.doc.user/html/context_help/carbide_ide_dialogs_help.xml Tue Jun 22 12:08:33 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/context_help/carbide_ide_dialogs_help.xml Tue Jun 22 14:05:02 2010 -0500 @@ -349,19 +349,10 @@ - - - Use the AIF editor to specify the Symbian OS resource file and bitmaps that should be included in a Symbian OS application information (AIF) file. - - - - - Use the add image from project dialog to search for image files in your project. - @@ -370,7 +361,6 @@ Use the add image from file system dialog to search for image files on your file system. - diff -r 32748ddc5cdb -r ab4f029618cb core/com.nokia.carbide.cpp.doc.user/html/reference/AIFEditor.html --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/AIFEditor.html Tue Jun 22 12:08:33 2010 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,98 +0,0 @@ - - -AIF Editor in AIF Definition File - - - -

AIF Editor

- -

- The AIF Editor allows you to specify the Symbian OS - resource file and bitmaps that should be included in a Symbian OS application - information (AIF) file. Use of AIF files is restricted to using .bmp files and works for versions 2.x and later releases of the Symbian OS SDKs. For more information, see AIF File.

- The AIF Editor is shown when a new AIF file is created or an existing file is edited in the Resources group of the MMP editor's Sources tab. Refer to Creating an AIF File for more information.

- -

Table 1. AIF Editor —Items

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

Item	Explanation
Target File	Specifies the filename of the compiled AIF file, relative to the target path. Click the untitled.aif button to set the target file based on the SDK and project name.
Resource File Path	Choose a resource file from the current project, browse the file system or enter the path. For relative paths use the Carbide project as the reference point, not the MMP file location.
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.
Preview	A preview of the image as it will appear at runtime.

Related concepts

AIF File

Related tasks

Creating an AIF File

- - - - - \ No newline at end of file diff -r 32748ddc5cdb -r ab4f029618cb core/com.nokia.carbide.cpp.doc.user/html/reference/MMP_Editor_sources.html --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/MMP_Editor_sources.html Tue Jun 22 12:08:33 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/reference/MMP_Editor_sources.html Tue Jun 22 14:05:02 2010 -0500 @@ -28,7 +28,7 @@

Resources

- Add, remove, or edit resources, bitmaps, languages, and AIF files to be compiled with your project.

+ Add, remove, or edit resources, bitmaps, and languages to compile with your project.

Related references

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.

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

Figure 1 - Add Images from Filesystem

Table 1. Add Images—Items

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.

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

Figure 1 - Add Images from Project

Other references

Carbide Build Configurations
Build Configurations
SIS Builder
Environment
Paths and Symbols

Environment Variables

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.

Some variables have special meaning, including:

PATH — will always place "${EPOCROOT}\epoc32\tools;${EPOCROOT}\epoc32\gcc\bin;" at the front of the PATH regardless of what it is changed to
PATH, EPOCROOT, and *MW variables — cannot be undefined as they are required for system builds

Figure 1 - Environment Variables

Table 1 Environment variable items

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 -

Other references

Environment Variables

Some variables have special meaning, including:

PATH — will always place "${EPOCROOT}\epoc32\tools;${EPOCROOT}\epoc32\gcc\bin;" at the front of the PATH regardless of what it is changed to
PATH, EPOCROOT, and *MW variables — cannot be undefined as they are required for system builds

Figure 1 - Environment Variables

Table 1 Environment variable items

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 +

Other references

Paths and Symbols

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

To change what appears in the list:

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

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

Figure 1 - Paths and Symbols pane

Other references

Paths and Symbols

To change what appears in the list:

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

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

Figure 1 - Paths and Symbols pane

Other references

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

Figure 1 - Macros Settings panel

Table 1 Macros Settings items

Related references

Set PKG File for Build Configuration

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

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

Figure 1 - Set PKG File for Build Configuration

Table 1 Items

Related reference

SIS Properties

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

Figure 1 - SIS Properties dialog

Table 1 SIS Properties window items

Item

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.

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.

Related reference

SIS Properties

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

Figure 1 - SIS Properties dialog

Table 1 SIS Properties window items

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.

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

Related reference

Right-click the project name and select Symbian Build > Build All Configurations

To build all target build configurations enabled for the current project.

Figure 1. Build All Configurations menu

Other references

Set breakpoints at the start of any assembler instruction by right-clicking the left hand column to view the context menu options (Figure 2)

Figure 1 shows the Dissassembly view stopped at a breakpoint.

Figure 1 - Disassembly view

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.

MIF Editor

MBM/MIF Editor

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

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

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

Figure 1 - MIF File in the Symbian Project Navigator view

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

Figure 2 - MBM/MIF Editor

Table 1. MBM/MIF Editor —Items

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

MIF Editor

MBM/MIF Editor

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

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

Figure 1 - MIF File in the Symbian Project Navigator view

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

Figure 2 - MBM/MIF Editor

Table 1. MBM/MIF Editor —Items

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

Creating an AIF File in Modifying Resources

Creating an AIF File

- The AIF Definition File wizard creates a file that - specifies an AIF file to be built as part of the project. An AIF file is a - Symbian OS application information file, which describes an application's icons - and properties. For more information, see Concepts >AIF File.

NOTE AIF files are used only for projects created for Symbian OS versions - before v9.1.

- To create an AIF file

-
- Open the MMP file associated with the project in the Symbian Project Navigator (double-click on MMP file or right-click and select Open).
- -
-

Figure 1 - MMP File in Symbian Project Navigator

The MMP editor opens.

Figure 2 - Access to AIF Editor in MMP Editor

- Select the Sources tab and select AIF in the Resources group. -
Click Add button to open the AIF editor.

Figure 3 - AIF Editor

- Enter a name for the .aif file or click untitled.aif button to set a default name based on the SDK and project name.
Specify a resource file from the dropdown list or browse the filesystem.
Click the Add From Project or Add From Filesystem buttons to add image and mask bitmaps.
Set the Shared Image Properties (color depth, mask depth, and color format).
Select the two images (image and mask) and select Pair Image and Mask button.
Click Ok to create AIF file from the information you defined in the editor.

Figure 4- AIF Editor with information defined

Related concepts

AIF File

Related reference

AIF Editor

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

Note that the Symbian OS plug-ins do not provide a graphical editor for the Symbian OS resource (.rss) file format. Files of this type though @@ -20,7 +18,6 @@ resource compiler.

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

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

The Add/Remove Carbide Build Configuration window appears (Figure 2). Use the Add/Remove Carbide Build Configuration window to manage the build configurations that appear on the Build Configurations sub-menu for the current project. You can also click the Manage configurations for the current project icon () on the toolbar to open this dialog.

Figure 2 - Window for managing build configurations