# HG changeset patch # User fturovic # Date 1286379202 18000 # Node ID e08aff86e1bc9eeaea527b21913a6020d146efe3 # Parent ff0156b9359970c1549c6cddd30ddf4cccedb8b0 removed old files moved to new directory diff -r ff0156b93599 -r e08aff86e1bc core/com.nokia.carbide.cpp.doc.user/html/concepts/CarbidePerspective.html --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/CarbidePerspective.html Wed Oct 06 10:31:32 2010 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,43 +0,0 @@ - -Carbide.c++ perspective - - - -

Carbide.c++ perspective

- - -

- The Carbide C/C++ perspective is a set of tools and layout of views provided for Symbian OS development. This perspective is designed to work with Symbian OS C++ projects. The commonly used views include:

- -

-

Figure 1 - Carbide C/C++ perspective

-

NOTE Click the icon to show additional options that may not be visible in the perspective view.

-

For more information on perspectives see Workbench User Guide > Concepts > Perspectives, and for views see C/C++ Development User Guide > Reference - > C/C++ Views and Editors.

-

- For more details on the Symbian OS Build Configurations, see - Active Configurations.

-
Related references
- - - - - - - \ No newline at end of file diff -r ff0156b93599 -r e08aff86e1bc core/com.nokia.carbide.cpp.doc.user/html/reference/INF_Editor.html --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/INF_Editor.html Wed Oct 06 10:31:32 2010 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,53 +0,0 @@ - - -INF Editor - - - -

INF Editor - Overview Tab

- -

- The INF Editor allows you to view and modify Symbian project files and export files to be included in building your application. The settings displayed are those active for the active build configuration. However, changes made in the INF editor can be applied globally to all build configurations. Changes made in the INF editor are automatically written to the project's .INF file. You can view the .INF file by selecting the bld.inf tab located along the bottom of the INF editor.

-

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

-

-

Figure 1 - INF Editor

-

- - -
NameFunction
-

- Components

 -

- Add components such as MMP and make files to be part of the normal build process.

-
    -
  • Create New MMP File - creates a new MMP file at the bottom of the Component list.
    • -
  • Add Existing MMP File - imports a MMP file at the bottom of the Component list.
    • -
  • Add Existing Makefile - adds a smake file to the bottom of the Component list.
    • -
  • Edit - Select a component and click Edit to apply the Tidy attribute or specify the Build as ARM option.
    • -
  • Open - Select a component and click Open to open the component in an editor window.
    • -
  • Up - Select a component and click Up to move the component up in the list.
    • -
  • Down - Select a component and click Down to move the component down in the list.
    • -
  • Remove - Select a component and click Remove to remove the component from the build process.
    • -
-

- Test Components -

-

- Create, import, edit, open, move, or remove MMP and make files that are part of a test build process.

-
Other references
- - - - - - - - \ No newline at end of file diff -r ff0156b93599 -r e08aff86e1bc core/com.nokia.carbide.cpp.doc.user/html/reference/INF_Editor_addedit_make.html --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/INF_Editor_addedit_make.html Wed Oct 06 10:31:32 2010 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,47 +0,0 @@ - - -INF Editor - Create/Edit Make - - - -

INF Editor - Create / Edit Makefile Entry

- -

The Add Makefile entry dialog (figure 1) is used to add a makefile to the build process. Enter or browse to the make file in the File path field and, if desired, apply the Tidy attribute or specify the Build as ARM option to the make file.

-

-

Figure 1 - Add/Edit makefile entry

-
Table 1. Add/Edit Makefile entry — items
- - - - - - - - - - - - - - - - - - - - - -
NameFunction

File path

Type the path and filename for the makefile to create or click Browse to set a path.

Tidy

Specify the tidy attribute if the release that an .mmp file defines is internal to your component and not required by other components or for your component to execute.

Build as ARMSpecifies the build_as_arm statement, which instructs an ARMV5 or later build to build the project for the ARM instruction set and not the THUMB instruction set.
Makefile formatSet the format of the makefile to be created.
-
Other references
- - - - - - - - \ No newline at end of file diff -r ff0156b93599 -r e08aff86e1bc core/com.nokia.carbide.cpp.doc.user/html/reference/INF_Editor_addedit_mmp.html --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/INF_Editor_addedit_mmp.html Wed Oct 06 10:31:32 2010 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,47 +0,0 @@ - - -INF Editor - Add/Edit MMP - - - -

INF Editor - Add / Edit MMP File Entry

- - The Add MMP File Entry dialog (figure 1) is used to add a mmp file and apply the Tidy, Manual, and Support attributes. -

-

Figure 1 - Add MMP File Entry

-
Table 1. Add MMP file entry — items
- - - - - - - - - - - - - - - - - - - - - -
NameFunction

File path

Type the path and filename for the MMP file to create or click Browse to set a path.

Tidy

Specify the tidy attribute if the release that an .mmp file defines is internal to your component and not required by other components or for your component to execute.

ManualCheckmark to indicate a test that requires manual interaction to complete.
SupportCheckmark to not include the test in a batch file.
-
Other references
- - - - - - - - \ No newline at end of file diff -r ff0156b93599 -r e08aff86e1bc core/com.nokia.carbide.cpp.doc.user/html/reference/INF_Editor_exports.html --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/INF_Editor_exports.html Wed Oct 06 10:31:32 2010 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,97 +0,0 @@ - - -INF Editor Exports - - - -

INF Editor - Exports Tab

- -

- The INF Editor Exports pane lists files to be copied to the indicated destination path that are part of the normal build process. You can add files, edit paths, move files up or down in the list, or remove files from the list.

-

-

Figure 1 - INF Editor - Exports Pane

-
Table 1. Export tab — items
- - - - - - - - - - - - - -
NameFunction

Exports

Add, edit, arrange order, or remove files that will be part of the build process.

-
    -
  • Add - Click to add a file to the list of files to be exported as part of the build process.
    • -
  • Edit - Select a file and click Edit to change the source and destination paths for the file.
    • -
  • Up - Select a file and click Up to move the file up in the list.
    • -
  • Down - Select a file and click Down to move the file down in the list.
    • -
  • Remove - Select a file and click Remove to remove the file from the build process.
    • -

Test Exports

Add, edit paths, arrange order, or remove files that will be part of the test build process.

-

-

Add Export dialog

-

Click the Add control to open the Add Export dialog (figure 2) to add a file to be exported to the destination path when the project is built.

-

-

Figure 2 - Add Export dialog

-

-
Table 2. Add Export — items
- - - - - - - - - - - - - - - - - -
NameFunction

Source path

Path and name of file to be exported.

Destination path

Path location where file is to be exported.

Export is a zip fileCheck this option if the export is a zip file and you want to extract it on the destination path.
-

Edit Export dialog

-

Click the Edit control to open the Edit Export dialog (figure 3) to edit the source and destination path of the selected file.

-

-

Figure 3 - Edit Export dialog

-
Table 3. Edit Export — items
- - - - - - - - - - - - - - - - - -
NameFunction

Source path

Path and name of file to be exported.

Destination path

Path location where file is to be exported.

Export is a zip fileCheck this option if the export is a zip file and you want to extract it on the destination path.
-
Other references
- - - - - - - - \ No newline at end of file diff -r ff0156b93599 -r e08aff86e1bc core/com.nokia.carbide.cpp.doc.user/html/reference/INF_Editor_file.html --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/INF_Editor_file.html Wed Oct 06 10:31:32 2010 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,25 +0,0 @@ - - -BLD.INF File - - - -

INF Editor - BLD.INF Tab

- -

- The bld.inf pane shows the source text of the bld.inf file. This file is automatically updated with changes made in the INF editor Overview and Exports panes or changes can be made manually in this pane. Validation is provided in this window. For example, an error mark is displayed next to the line where an error occurs, as shown in Figure 1. Hover your mouse pointer over the error mark or red error markers in upper right column to display helpful error information.

-

-

Figure 1 - INF Editor - bld.inf Pane

-

-
Related references
- - - - - - - - \ No newline at end of file diff -r ff0156b93599 -r e08aff86e1bc core/com.nokia.carbide.cpp.doc.user/html/reference/MMP_Editor.html --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/MMP_Editor.html Wed Oct 06 10:31:32 2010 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,68 +0,0 @@ - - -MMP Editor - - - -

MMP Editor

- -

- The MMP Editor Overview tab allows you to view and modify your project definitions. Changes made in the MMP editor are automatically written to the project's .MMP file. You can view the .mmp file by selecting the project_name.mmp tab located along the bottom of the MMP editor.

-

- The MMP Editor is shown when an MMP file is - opened from the Project Explorer 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.

-

-

Figure 1 - MMP Editor Overview tab

- - - - - - - -
NameFunction
-

- Target name

 -

- Enter the name of the target file.

-

- Target type

-

- Select the type of target file from the dropdown list. The list of supported target types are provided by SBSv2 build system. The number and type of targets may change depending upon the chosen SDK.

-

- UID 2

-

UID 2 is a unique identifier number that identifies the type of interface that the project implements. The values are defined by Symbian:

-
    -
  • For GUI applications, it is always 0x100039CE
    • -
  • For static interface DLLs, the UID 2 is always 0x1000008d
    • -
  • For polymorphic DLLs, the UID2 is defined by the framework which is being implemented
    • -
-
-

- UID 3

-

- Application UID (or UID3) is used to uniquely identify the binary (EXE or DLL) within the system. The purpose of UID 3 is to prevent one executable from interfering the operation of another executable.

Common tasks

This group provides links to the User and System include path options located in the Options window.

-

- Project definition

-

- The Project definition group provides links to the Sources, Libraries, and Options windows. You can also select the Sources, Libraries, and Options tabs to open the related window.

-

Any changes made to the MMP file either in Carbide or using an external editor are detected. If the build is for emulation, these changes are detected and used automatically.

-

For other build types like GCCE you are presented with the Modified MMP Files Detected dialog (Figure 2) and asked which build action to take for each MMP file that has changed. Set the build option for each listed MMP file and click OK.

-

-

Figure 2 - Modified MMP Files Detected dialog

-

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
- - - - - - - - \ No newline at end of file diff -r ff0156b93599 -r e08aff86e1bc core/com.nokia.carbide.cpp.doc.user/html/reference/MMP_Editor_libraries.html --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/MMP_Editor_libraries.html Wed Oct 06 10:31:32 2010 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,51 +0,0 @@ - - -MMP Editor Libraries - - - -

MMP Editor > Libraries

- -

- The MMP editor libraries window lists the libraries used by the currently selected build configuration in the selected project. The MMP editor libraries window is shown in Figure 1. Click on a library group to expand the list of libraries and show the related control buttons. You can add, remove or edit the list of libraries for each group. You can also move libraries up or down in the list.

-

-

Figure 1 - MMP Editor Libraries window

-

- - - - - - - - - - - - - - -
NameFunction
-

- Libraries

 -

- Specify import libraries to be included in all builds.

-

- Static libraries

 -

- Specify additional static libraries to be used in all builds.

Debug librariesSpecify additional libraries to be used for debug builds only.
Win32 librariesSpecify additional libraries for Win32 builds only.
ASSP librariesSpecify libraries for ASSP builds. If you are not linking to the Symbian OS kernel you can ignore this section.
-
Related references
- - - - - - - - \ No newline at end of file diff -r ff0156b93599 -r e08aff86e1bc core/com.nokia.carbide.cpp.doc.user/html/reference/MMP_Editor_mmp_tab.html --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/MMP_Editor_mmp_tab.html Wed Oct 06 10:31:32 2010 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,27 +0,0 @@ - - -MMP Editor MMP File - - - -

MMP File Window

- -

- The MMP file tab in the MMP editor window shows the source text of the mmp file. Changes made directly in the mmp file are reflected in related tabs of the MMP editor and changes made in editor tabs are written to the mmp file. Errors are identified in red and markers are placed in mmp files at the locations errors exist.

-

-

Figure 1 - MMP Editor MMP File

-

-
Related references
- - - - - - - - \ No newline at end of file diff -r ff0156b93599 -r e08aff86e1bc core/com.nokia.carbide.cpp.doc.user/html/reference/MMP_Editor_options.html --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/MMP_Editor_options.html Wed Oct 06 10:31:32 2010 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,77 +0,0 @@ - - -MMP Editor Options - - - -

MMP Editor Options Window

- -

- The MMP editor options window allows you to edit compiler, linker, and runtime settings. The MMP editor options window is shown in Figure 1.

-

-

Figure 1 - MMP Editor Options window

-

- - - - - - - - - - - - -
NameFunction
-

- Runtime

 -

- This group allows you to define various runtime options.

-

Capabilities - Click the Choose... button to select Capabilities. A capability is an access token that corresponds to permission to access sensitive system resources. Platform security permits access to sensitive APIs according to capabilities. Capabilities are used to specify what functionality an application is trusted to use; they are allocated to the application at build time and are policed at run time. Once the capabilities are assigned to the application, they cannot be changed. Thus an application has a set of unalterable capabilities that describe what access the application has to the APIs.

-

There are three suggested ways to establish which capabilities an application requires.

-
    -
  • The first method is initially to allocate capabilities based on the general operations that the application performs. For example, an instant messaging application would probably require NetworkServices to access the Internet and ReadUserData to read the user’s contacts.
    • -
  • The second method is to use the Symbian Developer Library, which lists the capabilities required by each API. Note that some APIs may be marked as “Dependent”, meaning that the need for the capability depends on the parameters being passed. For example, accessing a file in an application’s private data area requires no capabilities, but accessing a file in \sys\bin requires the AllFiles capability.
    • -
  • The third method is to run the application in the emulator, analyzing the debug file (in the system temporary directory) for capability violations. The output will state the API that caused the violation and what capability was expected.
    • -
-

Minimum heap size - Set the heap size that you need.

-

Maximum heap size - Set the heap size that you need.

-

Stack size - Set the stack size that you need.

-

Process priority - Select the process priority from the dropdown list.

-

Secure ID - Enter the Secure ID. The SID is used to determine which private directory a process can access. It is also used to identify the caller applications. An application's SID is defined within its .mmp file, and is used to uniquely identify the application. SID values are requested from the Symbian Signed Web site (www.symbiansigned.com). The Software Installer (SWI) is responsible for ensuring that SIDs are locally unique, i.e., that no two applications have the same SID value on a particular target device.

-

Vendor ID - Enter the Vendor ID. This ID uniquely identifies the source of the application. If an application needs a VID, it must be certified. Noncertified applications must use a VID of 0 (KNullUid), which is the value applied by default.

-

Enable debugging (Symbian OS 9.4+) - Activate to enable on-device debugging for Symbian OS 9.4 and later. When activated, the DEBUGGABLE_UDEBONLY flag is added to the project .MMP file.

-

Paging Mode (Symbian OS 9.3+) - specify the paging mode to: not specified, paged, or unpaged.

-

- Compiler Settings

 -

- User includes - Use the Add, Edit, and Remove buttons to add, edit, or remove the paths to the user header files used to compile source files. Use the Up and Down buttons to arrange the list of paths.

-

System includes - Use the Add, Edit, and Remove buttons to add, edit, or remove the paths to the system header files used to compile source files. Use the Up and Down buttons to arrange the list of paths.

-

Macros - Use the Add, Edit, and Remove buttons to add, edit, or remove a macro identifier. Use the Up and Down buttons to arrange the list of macro identifiers.

-

Compiler options - Use the Add, Edit, and Remove buttons to add, edit, or remove compiler options. In the Edit Compiler Options dialog, select the tool chain (for example: ARMCC, CW, GCC, GCCE, or MSVC) and enter your custom options.

-

Linker options - Use the Add, Edit, and Remove buttons to add, edit, or remove linker options. In the Edit Linker Options dialog, select the tool chain (for example: ARMCC, CW, GCC, GCCE, or MSVC) and enter your custom options.

-

Per-variant include dependencies - Check this option to include dependencies for a specific variant when building a target. For example build a release variant with optimized code, a debug variant with debugging info and a profiling variant with timing hooks.

-

Disable optimizations in debug builds - Check this option to disable optimizations when building a debug version of your application. Since optimization changes the code created by the compiler, it is best to optimize your code after you have fully tested and debugged it. If a program works in a debug build, but fails in a release build, it is likely that one of the compiler optimizations is exposing a defect in your source code. To isolate the problem, you should disable selected optimizations for each source code file, until you locate the file and the optimization that is causing the problem.

Linker

Linker definition file - Select a linker definition file or click Browse... to locate a definition file.

-

Export unfrozen - Check this option to tell the build process that exports are not yet frozen.

-

Don't export library - Check this option to not export a copy of the library.

-

No strict .def file - Check this option to specify no strict linker definition file.

-

Compress target executable - Check this option to compress the target executable.

-

Link as internal name - Specify an internal name.

-

Win32 base address - Specify the Win32 base address.

Kernel

ASSP ABI - Check this option to build the ASSP application binary interface.

-

ASSP exports - Check this option to enable ASSP exports.

-
Related references
- - - - - - - - \ No newline at end of file diff -r ff0156b93599 -r e08aff86e1bc core/com.nokia.carbide.cpp.doc.user/html/reference/MMP_Editor_resource_block.html --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/MMP_Editor_resource_block.html Wed Oct 06 10:31:32 2010 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,60 +0,0 @@ - - -MMP Editor Resource Block - - - -

MMP Editor Resource Block

- -

- The MMP editor resource block dialog allows you to add or remove resource files to your project. The Edit Resource Block dialog is shown in Figure 1. You can add, remove or edit resource files to be included with your project.

-

-

Figure 1 - MMP Editor Resource Block Dialog

-

- - - - - - - - - - - - - - - - - - - - - - -
NameFunction
-

- Project RSS files

 -

- Select or browse to the resource file to be included in all builds.

-

- RSS file path

 -

- Enter the path to the resource file.

Target file nameEnter the target file name.
Target file pathSelect the target file path, such as the executable directory or /resource directory on the target device.
UID 2Enter the unique identifier. UID2 may need to be a specific value for some kinds of DLLs, especially those used by plug-in frameworks.
UID 3

Enter the unique identifier. In the current implementation of platform security, UID3 is used as the Secure ID if SECUREID is not specified in the .mmp file. If it is specified, UID3 will be used to identify the application as its original purpose.

-

However, the SID is used to determine which private directory a process can access as well as to identify the caller applications, whereas the UID is used to uniquely identify an application. It is theoretically possible that these two identifiers could have different values, but to avoid confusion Symbian recommends that a SECUREID not be specified in the application's MMP file; UID3 should always be specified instead.

Generate header fileCheck this option to generate a header file for the resource files.
-
Related references
- - - - - - - - \ No newline at end of file diff -r ff0156b93599 -r e08aff86e1bc 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 Wed Oct 06 10:31:32 2010 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,46 +0,0 @@ - - -MMP Editor Sources - - - -

MMP Editor Sources Window

- -

- The MMP editor sources window lists the C++ and resource files that you can select to be compiled. The MMP editor sources window is shown in Figure 1.

-

-

Figure 1 - MMP Editor Sources window

-

- - - - - - - - - -
NameFunction
-

- C/C++ sources

 -

- Select the C/C++ files to be compiled with your project.

Missing C/C++ sourcesShows a list of missing source files referenced by project MMP files.
-

- Resources

 -

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

-
Related references
- - - - - - - - \ No newline at end of file diff -r ff0156b93599 -r e08aff86e1bc core/com.nokia.carbide.cpp.doc.user/html/reference/MMP_selection.html --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/MMP_selection.html Wed Oct 06 10:31:32 2010 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,18 +0,0 @@ - - -MMP Selection - - - -

MMP Selection

- -

- The MMP Selection dialog displays a list of mmp project files that your source files should be added to for debugging specific components.

-

-

Figure 1 - MMP Selection Dialog

-

- - - - - \ No newline at end of file diff -r ff0156b93599 -r e08aff86e1bc 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 Wed Oct 06 10:31:32 2010 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,51 +0,0 @@ - - -New Symbian OS MMP File - - - -

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

-
    -
  1. To open the New wizard to create a MMP File: -
      -
    • Select the File > New > Other... menu item (Figure 1)
      • -
    -
    -

    -

    Figure 1 - Select a wizard page in the New window

    -

    OR

    -
    -
      -
    • Select the File > New > Symbian OS MMP File... menu item (Figure 2)
      • -
    -
    2. -
    -

    -

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

    -
    -
  2. On the Select the wizard page, select Symbian OS > Symbian OS MMP File, then click Next (Figure 1)
    3. -
  3. On the MMP File page, enter the destination project folder and specify file name
    4. -
  4. Click Finish
    5. -
-

The new MMP file is created in the destination folder and shown in the MMP editor.

-
-
Related references
- - - - - - - - \ No newline at end of file diff -r ff0156b93599 -r e08aff86e1bc core/com.nokia.carbide.cpp.doc.user/html/reference/trk/exporting_remote_conns.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/exporting_remote_conns.htm Wed Oct 06 10:31:32 2010 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,37 +0,0 @@ - - - - - - -Exporting Remote Connections - - - - -

Exporting Remote Connections

-

You can export remote connection settings for sharing and import settings created by others using the Import/Export commands.

- -

To export one or more remote connections:

-
    -
  1. Click the File > Export... menu option.
    2. -
  2. Select the Remote Connections > Remote Connections Data wizard in the Select page (Figure 1), then click Next.
    3. -

    -

    Figure 1. Select page showing Remote Connections Data wizard

    -
  3. Choose file and remote connections to export (Figure 2) in the Export Remote Connections Data page.
    4. -

    -

    Figure 2. Enable remote connections to export to chosen file

    -
  4. Click Finish to save the selected remote connections to the file.
    5. -
-
Related references
- - - - diff -r ff0156b93599 -r e08aff86e1bc core/com.nokia.carbide.cpp.doc.user/html/reference/trk/importing_remote_conns.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/importing_remote_conns.htm Wed Oct 06 10:31:32 2010 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,37 +0,0 @@ - - - - - - -Importing Remote Connections - - - - -

Importing Remote Connections

-

You can export remote connection settings for sharing and import settings created by others using the Import/Export commands.

- -

To import one or more remote connections:

-
    -
  1. Click the File > Import... menu option.
    2. -
  2. Select the Remote Connections > Remote Connections Data wizard in the Select page (Figure 1), then click Next.
    3. -

    -

    Figure 1. Select page showing Remote Connections Data wizard

    -
  3. Choose file and remote connections to export (Figure 2) in the Import Remote Connections Data page.
    4. -

    -

    Figure 2. Enable remote connections to import

    -
  4. Click Finish to import the selected remote connections into Carbide.
    5. -
-
Related references
- - - - diff -r ff0156b93599 -r e08aff86e1bc core/com.nokia.carbide.cpp.doc.user/html/reference/trk/view_remote_connection.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/view_remote_connection.htm Wed Oct 06 10:31:32 2010 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,181 +0,0 @@ - - - - - - -Remote Connections view - - - - - -

Remote Connections view

-

Use the Remote Connections view to monitor, create, edit, or remove common connection settings for remote agents. Remote agents provide support for debugging, profiling, trace, and more. The connection types currently supported include:

- -

The columns in the Remote Connections view include:

- -

-

Figure 1 - Remote Connections view

-

When the view is closed or another perspective opened, a small display appears in the trim area in the lower-right corner of the workspace showing the current active remote connection. Click the connection name to open the drop-down menu where you can open the Remote Connections view or switch between connections.

-

-

Figure 2. Available remote connection trim indicator

-

Remote Connections view toolbar icons

-

The following commands appear on the toolbar within the Remote Connections view:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ItemIconExplanation
Toggle periodic service testing
Periodic testing icon
Toggles service testing on or off.
Refresh Connections
- -

Click to update the connection list status.

New Connection
- -
Click to open the New Connection wizard to add a connection.
Edit Connection
- -

Click to edit the selected remote connection.

View menu
View menu
Select the connection types to monitor for remote connections.
-

Remote Connections view Status icons

-

The following status indicators appear in the Remote Connections view:

- - - - - - - - - - - - - - - - - - - - - - - - - - -
ItemIconExplanation
Connection
- -

Indicates an inactive remote connection setting.

Not Active
- -
Indicates an inactive connection type.
Ready / Available
- -

Indicates an active remote connection is ready or that a particular connection type is available.

Not Accessible
- -

Cannot access the connection type within the connection setup. This could be due to one of the following conditions:

-
    -
  • Nokia Ovi/PC Suite is not installed (Carbide uses their drivers to connect to remote devices)
    • -
  • User did not select Ovi/PC Suite mode on the device
    • -
  • CODA (Carbide On-device Debug Agent) is not installed on the device
    • -
-

If all the above is setup the remote device should automatically appear when it is connected to the PC. The Description field contains useful debug information that can help solve the issue as well.

-

Remote Connections view context menu options

-

Based on the current selection, one or more of the following commands appear on the context menu when you right-click within the Remote Connections view. For example, if no connections are defined, only the New Connection command is available on the context menu.

-

-

Figure 3 - Remote Connections context menu

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ItemIconExplanation
New Connection...
- -
Select to open the New Connection wizard to add a connection.
Rename Select to rename the currently selected connection.
Edit Settings...
- -

Select to edit the selected remote connection settings.

Delete
- -

Select to delete the selected connection from the connection list.

Help for...
- -
Select to open the Help view for connection information.
Make Current Make the selected connection the current connection.
-
Related references
- - - - - diff -r ff0156b93599 -r e08aff86e1bc core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_conn_install_tab.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_conn_install_tab.htm Wed Oct 06 10:31:32 2010 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,49 +0,0 @@ - - - - - - -Install Remote Agents pane - - - - -

Install Remote Agents

-

Use the Install Remote Agents pane to select the latest remote agent version to download and install to the device.

-

-

Figure 2 - New Connection wizard Install remote agents page

-

Table 1. Install Remote Agents pane

- - - - - - - - - - - - - - - - - -
ItemExplanation
Install remote agents

A list of the most current versions of remote agents sorted by SDK and version. Select the version most compatable with the device. For example, a device running S60 5.0 needs a version of the CODA software compiled for that SDK.

-

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

SaveClick Save to store a local copy of the currently selected CODA to disk. You can then manually install the file to your devices using the method of your choice.
Install

Click Install to download and install the CODA selected in the Install remote agents list. A progress bar is shown if the install operation requires more than a few seconds to complete.

-

NOTE Drivers installed by PC Suite or Ovi Suite are required in order for Install to download a remote agent onto the target device.

-

NOTE The SIS and SISX file types must be associated with an installer application like Nokia PC Suite or Ovi Suite in order to install them onto the device. Use the Save command above to perform a manual install to the device if you don't have an installer application.

-

-
Related references
- - - - diff -r ff0156b93599 -r e08aff86e1bc core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_conn_settings_pane.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_conn_settings_pane.htm Wed Oct 06 10:31:32 2010 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,47 +0,0 @@ - - - - - - -Install Remote Agents pane - - - - -

Install Remote Agents pane

-

Use the Install Remote Agents pane to select the latest remote agent version to download and install to the device.

-

-

Figure 2 - New Connection wizard Serial Connection Settings page

-

Table 3. Serial Connection Setting page - Install Remote Agents tab

- - - - - - - - - - - - - - - - - -
ItemExplanation
Install Remote Agents

A list of the most current versions of remote agents sorted by SDK and version. Select the version most compatable with the device. For example, a device running S60 3.1.0 needs a version of the CODA software compiled for that SDK.

-

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

SaveClick Save to store a local copy of the currently selected CODA to disk. You can then manually install the file to your devices using the method of your choice.
Install

Click Install to download and install the CODA selected in the Install latest CODA list. A progress bar is shown if the install operation requires more than a few seconds to complete.

-

NOTE The SIS and SISX file types must be associated with an installer application like Nokia PC Suite in order to install them onto the device. Use the Save command above to perform a manual install to the device if you don't have an installer application.

-

-
Related references
- - - - - diff -r ff0156b93599 -r e08aff86e1bc core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_conn_wiz_add.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_conn_wiz_add.htm Wed Oct 06 10:31:32 2010 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,114 +0,0 @@ - - - - - - -Adding, Editing, and Deleting Connections - - - - -

Adding, Editing, and Deleting Connections

-

Use the Remote Connections view to monitor, create, edit, or remove common remote connection settings.

- -

Edit connection name and type

-

Use the Edit connection name and type page to assign a name and connection type to the new connection setup.

-

-

Figure 1 - New Connection wizard Edit connection name and type page

-

Table 1. Edit connection name and type page - options

- - - - - - - - - - - - - - - - - -
ItemExplanation
Connection TypeSelect the type of connection this setup will use.
Connection Name

Enter a name for the connection.

Connection Settings

Select the connection port to use for this connection setting.

-

Set Connection Settings pane

-

Use the Set Connection Settings pane to compare the version of remote agent installed on the device with the latest version available for Carbide. In this pane you can:

- -

-

Figure 2 - New Connection wizard Serial Connection Settings page

-

Table 2. Serial Connection Setting page - Set Connection Settings tab

- - - - - - - - - - - - - - - - - -
ItemExplanation
Device OS (used to determine installer version)Select the OS used on the device.
Select a service to testClick to select a listed service for testing.
Initiate Service Testing

Click Initiate Service Testing to query the remote agent software on the device for its version number. It then compares the version number found with the latest version available for Carbide. A progress bar will appear should the Check CODA version operation requires more than a few seconds.

-

NOTE The PC must have an internet connection to perform a remote agent version check.

-

Once the comparison is complete the Status text is updated with the result and further instructions as required.

-

-

If a connection fails, the errors normally fall into these two categories:

-
    -
  • connection failure - this usually indicates the chosen COM port is not open. Try selecting a different COM port, specifically one with a name attached to it (COM4 - BthModem0) for the type of connection you are using (USB or Bluetooth). Repeat as necessary until you get a successful response.
    • -
  • CODA not responding - this indicates that the COM port is open but CODA is not responding. First, verify that CODA is up and running on the device. Second, CODA may be listening on a different COM port, so choose another named COM port and try again.
    • -
-

 

-

Install Remote Agents pane

-

Use the Install Remote Agents pane to select the latest remote agent version to download and install to the device.

-

-

Figure 2 - New Connection wizard Serial Connection Settings page

-

Table 3. Serial Connection Setting page - Install Remote Agents tab

- - - - - - - - - - - - - - - - - -
ItemExplanation
Install Remote Agents

A list of the most current versions of remote agents sorted by SDK and version. Select the version most compatable with the device. For example, a device running S60 5.x needs a version of the CODA software compiled for that SDK.

-

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

SaveClick Save to store a local copy of the currently selected CODA to disk. You can then manually install the file to your devices using the method of your choice.
Install

Click Install to download and install the CODA selected in the Install latest CODA list. A progress bar is shown if the install operation requires more than a few seconds to complete.

-

NOTE The SIS and SISX file types must be associated with an installer application like Nokia PC Suite in order to install them onto the device. Use the Save command above to perform a manual install to the device if you don't have an installer application.

-

 

-
Related references
- - - - - diff -r ff0156b93599 -r e08aff86e1bc core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_conn_wiz_edit.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_conn_wiz_edit.htm Wed Oct 06 10:31:32 2010 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,122 +0,0 @@ - - - - - - -Editing connections - - - - -

Editing connections

-

Use the Remote Connections view to monitor, create, edit, or remove common remote connection settings.

- -

Edit connection name and type

-

Use the Edit connection name and type page to assign a name and connection type to the new connection setup.

-

-

Figure 1 - New Connection wizard Edit connection name and type page

-

Table 1. Edit connection name and type page - options

- - - - - - - - - - - - - - - - - -
ItemExplanation
Conection TypeSelect the type of connection this setup will use.
Connetion name

Enter a name for the connection.

Supported Services

Shows a list of services supported by the connection type chosen.

-

Set Connection Settings pane

-

Use the Set Connection Settings pane to compare the version of remote agent installed on the device with the latest version available for Carbide. In this pane you can:

- -

-

Figure 2 - New Connection wizard Set Connection Settings tab

-

Table 2. Bluetooth Setting page - Set Connection Settings tab

- - - - - - - - - - - - - - - - - - - - - - - - - -
ItemExplanation
Serial Port A dropdown list of serial ports with known identifiers for selecting the communication port used by the PC to communicate with the device. A named COM port (COM4 - BthModem0) indicates an active port. Unnamed port numbers have usually not been opened and assigned by the PC.
Baud Ratea dropdown list of baud rates common to serial connections.
Device OS

A dropdown list of device OSes that are supported by the remote agent software. Select the OS used by the device before running a check.

Select a service to testClick to select a listed service for testing.
Test Service Status

Click Initiate service testing to query the remote agent software on the device for its version number. It then compares the version number found with the latest version available for Carbide. A progress bar will appear should the Check CODA version operation requires more than a few seconds.

-

NOTE The PC must have an internet connection to perform a remote agent version check.

-

Once the comparison is complete the Status text is updated with the result and further instructions as required.

-

-

If a connection fails, the errors normally fall into these two categories:

-
    -
  • connection failure - this usually indicates the chosen COM port is not open. Try selecting a different COM port, specifically one with a name attached to it (COM4 - BthModem0) for the type of connection you are using (USB or Bluetooth). Repeat as necessary until you get a successful response.
    • -
  • CODA not responding - this indicates that the COM port is open but CODA is not responding. First, verify that CODA is up and running on the device. Second, CODA may be listening on a different COM port, so choose another named COM port and try again.
    • -
-

 

-

Install Remote Agents pane

-

Use the Install Remote Agents pane to select the latest remote agent version to download and install to the device.

-

-

Figure 2 - New Connection wizard Install remote agents tab

-

Table 3. Bluetooth Setting page - Install Remote Agents tab

- - - - - - - - - - - - - - - - - -
ItemExplanation
Install remote agents

A list of the most current versions of remote agents sorted by SDK and version. Select the version most compatable with the device. For example, a device running S60 3.1.0 needs a version of the CODA software compiled for that SDK.

-

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

SaveClick Save to store a local copy of the currently selected CODA to disk. You can then manually install the file to your devices using the method of your choice.
Install

Click Install to download and install the CODA selected in the Install latest CODA list. A progress bar is shown if the install operation requires more than a few seconds to complete.

-

NOTE The SIS and SISX file types must be associated with an installer application like Nokia PC Suite in order to install them onto the device. Use the Save command above to perform a manual install to the device if you don't have an installer application.

-

 

-
Related references
- - - - - diff -r ff0156b93599 -r e08aff86e1bc core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_connection_wizard.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_new_connection_wizard.htm Wed Oct 06 10:31:32 2010 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,61 +0,0 @@ - - - - - - -Setup Connection - - - - -

Setup Connection

-

Use the Edit Connection page to assign a connection type, name, and connection settings to the new connection setup.

-

-

Figure 1 - New Connection wizard Setup Connection tab

-

Table 1. Setup Connection page - options

- - - - - - - - - - - - - - - - - -
ItemExplanation
Connection Type

Select the type of connection and its supported services from the drop down list of options. The types of connections include:

-
    -
  • Bluetooth - serial port connection through Bluetooth
    • -
  • Serial - serial port connection through a COM serial port
    • -
  • USB - serial port connection through USB that supports CODA 4.x
    • -
-

And the supported services may include:

-
    -
  • CODA
    • -
  • Tracing
    • -
  • and others
    • -
Connection Name

Enter a name for the connection.

Connection Settings

Shows a list of services supported by the connection type chosen.

-
    -
  • Bluetooth - serial port connection through Bluetooth
    • -
  • Serial - serial port connection through a COM serial port
    • -
  • USB - serial port connection through USB that supports CODA 4.x
    • -
-
Related references
- - - - - diff -r ff0156b93599 -r e08aff86e1bc core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_on_device_check_tab.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_on_device_check_tab.htm Wed Oct 06 10:31:32 2010 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,58 +0,0 @@ - - - - - - -Test Connection - - - - -

Test Connection

-

Use the Set Connection Settings pane to compare the version of remote service installed on the device with the latest version available for Carbide. A remote service is any software on the device that can communicate with Carbide. This includes CODA (Carbide On-device Debug Agent), Trace, Performance Investigator, and other services. In this pane you can:

- -

Options presented may differ based on the type of connection setting chosen.

-

-

Figure 1 - Test Connection pane in the New Connection dialog

-
Table 1 Test Connection pane — items
- - - - - - - - - - - - - - - - - -
ItemExplanation
Device OS (used to determine installer version)

A dropdown list of device OSes that are supported by CODA. Select the OS used by the device before running a check.

Select a service to testSelect the remote service type to query on the remote device.
Initiate service testing

Click Initiate service testing to query the remote software on the device for its version number. It then compares the version number found with the latest version available for Carbide. A progress bar will appear when the operation requires more than a few seconds.

-

NOTE The PC must have an internet connection to perform a remote service version check.

-

Once the comparison is complete the Status text is updated with the result and further instructions as required.

-

-

If a connection fails, the errors normally fall into these two categories:

-
    -
  • connection failure - this usually indicates the chosen COM port is not open. Try selecting a different COM port, specifically one with a name attached to it (COM4 - BthModem0) for the type of connection you are using (USB or Bluetooth). Repeat as necessary until you get a successful response.
    • -
  • Service not responding - this indicates that the COM port is open but the remote service is not responding. First, verify that remote service is up and running on the device. Second, the remote service may be listening on a different COM port, so choose another named COM port and try again.
    • -
-
Related references
- - - - diff -r ff0156b93599 -r e08aff86e1bc core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_on_device_setup.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/trk/wnd_on_device_setup.htm Wed Oct 06 10:31:32 2010 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,31 +0,0 @@ - - - - - - -On-Device Connections - - - - -

On-Device Connections

-

Use the New Connection wizard to verify and update Carbide software services on a device. Click the New Connection... icon (New Connection icon) in the Remote Connections view toolbar to open. Current services available include CODA, Tracing, and others. The following tabs are present:

- -

-

Figure 1 - New Connection dialog

-
Related references
- - - - diff -r ff0156b93599 -r e08aff86e1bc core/com.nokia.carbide.cpp.doc.user/html/reference/view_carbide_portal.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_carbide_portal.htm Wed Oct 06 10:31:32 2010 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,97 +0,0 @@ - - - - - - -Carbide.c++ Portal view - - - -

Carbide.c++ Portal view

-

The Carbide.c++ Portal view provides a single point of information on Carbide news, new releases, additional extensions, and support. The Carbide.c++ Portal view is shown by clicking Help > Carbide.c++ Portal.

-

-

Figure 1. Customize page in the Carbide.c++ Portal view

-

If the Show Installed option is checkmarked, the list only shows the extensions currently installed. To show more information on a specific extension click the Show Overview icon (Show Overview) icon (Figure 2).

-

-

Figure 2. Extension information popup

-

Install section

-

The Install section provides options for installing additional Carbide extensions.

-
Table 1. Install options
- - - - - - - - - - - - - - - - - - - - - - - - - -
ItemExplanation
Install...Installs only the checked items in the extension list.
Refresh

Refreshes the plug-in list.

Select allMarks all extensions for installation.
Deselect allUnchecks all extensions to prevent installation.
Advanced install...Launches the Install New Software wizard.
-

Migrate section

-

The Migrate section provides options for saving or restoring the custom settings.

-
Table 2. Migrate options
- - - - - - - - - - - - - -
ItemExplanation
Export...Click to export the current feature configuration.
Import...

Click to import a saved feature configuration settings file.

-

Settings section

-

The Settings section provides access to several common ways to customize the Carbide program.

-
Table 3. Settings options
- - - - - - - - - - - - - - - - - - - - - -
ItemExplanation
CapabilitiesClick to open the Capabilities preference panel where you can control which product components.
Code StyleClick to open the Code Style preference panel to customize the C/C++ editor appearance and behavior.
Key BindingsClick to open the Keys preference panel to customize program key bindings.
ProxiesClick to open the Network Connections preference panel to change proxy settings.
-
Related references
- - - - \ No newline at end of file diff -r ff0156b93599 -r e08aff86e1bc core/com.nokia.carbide.cpp.doc.user/html/reference/view_console.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_console.htm Wed Oct 06 10:31:32 2010 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,71 +0,0 @@ - - - - - - -Console View - - - -

Console view

-

The Console view displays the output of a process and allows you to provide keyboard input to a process. There are numerous consoles available, see the Open Console dropdown list for those available to you. Most are enabled from various project panels in Carbide.

-

-

Figure 1 - Console view showing build console information

-

To view RDebug::Printf output in the Console view when targeting devices, ensure that the following Debugger options are matched with settings in the epoc.ini file.

- -
Table 1 Console view—items
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ItemIconExplanation
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 CODA Program Output Console
    • -
  • New CODA 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 CODA and the on-device debug agent.

-

NOTE You can pin any message log view so that it does not lose focus.

-

 

- - - - diff -r ff0156b93599 -r e08aff86e1bc core/com.nokia.carbide.cpp.doc.user/html/reference/view_executables.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_executables.htm Wed Oct 06 10:31:32 2010 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,105 +0,0 @@ - - - - - - -Executables view - - - -

Executables view

-

The Executables view provides a dynamic list of executables and their related source files. The Executables view makes it easy to:

- -

In addition, an Executables project is created in the Project Explorer view. The binaries shown in the Executables project can be deleted which also removes them from the Executables view. For binaries outside the workspace you must import them into the Executables view so their symbolics can be used during the debug session. You can also drag and drop executables into the view.

-

NOTE To debug ROM DLLs with Symbian OS Device or in stop mode, always specify the ROM Log file in the project's launch configuration.

-

-

Figure 1 - Executables view

-

The Executables view consists of the Executable Name and Source File Name panes describled in the table below. Use the Columns button in the toolbar to show or hide specific columns in each pane. Columns can be sorted and rearranged in the order desired.

-
Table 1. Executables view information
- - - - - - - - - - - - - -
PaneExplanation
Executable Name

Displays a list of executables in the workspace as well as other files added by the user. Select an executable to update the Source File Name pane with related files. The executable information shown can include:

-
    -
  • Executable Name - (default) Name of the exectable file.
    • -
  • Executable Project - (default) The project associated with the executable.
    • -
  • Executable Location - (default) The current location of the executable.
    • -
  • Executable Size - The executable size shown in bytes.
    • -
  • Executable Date - The source file′s modification date.
    • -
  • Executable Type - The executable type (.exe, etc.)
    • -
-

Click the Columns icon () to set which columns to show in this pane.

Source File Name

Displays a list of source files for the selected executable as extracted from the symbol table. The source file information shown can include:

-
    -
  • Source File Name - (default) Name of the source file used by the executable. If no binary files are in the project the message No source files found in <project_name> is shown.
    • -
  • Source File Location - (default) The current location of the source file. If the path is shown in gray text the source file was not located. To locate it, double-click to open a new editor, then click Locate File... to locate the missing file. The new path is compared to the old one and all files located in the same directory are automatically updated to use the new path.
    • -
  • Source File Original Location - (default) The original location of the source file which may be different than the current location.
    • -
  • Source File Size - The executable size shown in bytes.
    • -
  • Source File Date - The source file′s modification date.
    • -
  • Source File Type - The source type (.h, .inc, etc.)
    • -
-

Expand a file′s tree control to view the functions and header files used by the file. Double-click to open the source file for editing or to set breakpoints.

-

Click the Columns icon () to set which columns to show in this pane.

-

Executables view toolbar icons

-

The table below lists the unique icons displayed in the Executables view toolbar.

-
Table 2. Executables view toolbar options
- - - - - - - - - - - - - - - - - - - - - - - - - - -
CommandNameDescription
Refresh the list of executables
Click to refresh the executables list.
Import an executable file Click to select and import an executable not in the workspace into the executables list.
- -
- 		Remove the selected executablesClick to remove one or more selected executables from the executables list. You will see a alert if the executable cannot be removed.
ColumnsOpens the Configure Columns dialog for configuring which columns appear in the Executable and Source File panes.
-
Other references
- - - - - diff -r ff0156b93599 -r e08aff86e1bc core/com.nokia.carbide.cpp.doc.user/html/reference/view_mifdef_editor.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_mifdef_editor.htm Wed Oct 06 10:31:32 2010 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,106 +0,0 @@ - - -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.

-

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
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ItemExplanation
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.
    • -
UpSelect 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.
RemoveSelect 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.
PreviewA preview of the image as it will appear at runtime.
-

 

- - - - - \ No newline at end of file diff -r ff0156b93599 -r e08aff86e1bc core/com.nokia.carbide.cpp.doc.user/html/reference/view_proj_explorer.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_proj_explorer.htm Wed Oct 06 10:31:32 2010 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,39 +0,0 @@ - - - - - - -Project Explorer View - - - -

Project Explorer view

-

The Project Explorer view (Figure 1) displays relevant C/C++ projects located in the current workspace using a tree structure. Use this view to manage all the projects located in the current workspace. The view is customizable and takes advantage of working sets.

-

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

-

Project Explorer view

-

Figure 1 - Project Explorer view showing projects in the current workspace

-

The directories that appear in the project include:

- -
-

NOTE Only the directories specified by the mmp file are created during import.

-
-

The files that appear in the project directories can be either:

- -

See C/C++ Development User Guide > Reference > C/C++ Views and Editors > Project Explorer view for more info.

-
Related references
- - - - - \ No newline at end of file diff -r ff0156b93599 -r e08aff86e1bc core/com.nokia.carbide.cpp.doc.user/html/reference/view_sym_proj_nav.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/reference/view_sym_proj_nav.htm Wed Oct 06 10:31:32 2010 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,52 +0,0 @@ - - - - - - -Symbian Project Navigator view - - - - -

Symbian Project Navigator view

-

The Symbian Project Navigator view shows all files that belong to the -current build configuration. This view lists the Symbian projects in your current workspace and their corresponding *.inf file (typically bld.inf). The *.inf file contains the related MMP project files, which are also listed in a tree structure. You can collapse or expand the list for each MMP to see which sources belong to each MMP.

-

To open this view select Window > Show View > Symbian Project Navigator, or select Window > Show View > Other ... and expand the Carbide.c++ folder then choose Symbian Project Navigator.

-

Figure 1 shows the Symbian Project Navigator view.

-

-

Figure 1 - Symbian Project Navigator view

-
Table 1. Symbian Project Navigator view — shortcut menu
- - - - - - - - - - - - - - - - - - - - - -
ItemIconExplanation
Toggle SOURCEPATH
Toggles the display between showing the SOURCEPATH folders contained in the MMP file and showing the Bld.inf structure.
Toggle MMPs
Toggle the display to show all MMP files or the MMP files associated with the current build configuration.
Toggle MMP Order
- -
- 		Toggle to show the MMPs list in alphabetical or build order. The default setting is build order.
-
Related references
- - - - -