Development and Deployment Steps

The following figure illustrates the files that are created when you develop a Symbian C++ application.

Figure 1. Files created during development and deployment.

To develop a Symbian C++ application

  1. Start Carbide.c++.

  2. Use the Carbide.c++ wizard to create default build configuration, source and package files (yellow in the diagram). Then add content to the project manually.

  3. Use the Carbide.c++ build tools to create the output files (blue in the diagram).

  4. Use the Carbide.c++ package tools to create an installation file (green in the diagram).

HelloWorld build configuration, source and package files

The following tables describe the project files. In the example, the default locations for:

  • <Project Folder> is C:\Symbian\Carbide\workspace\HelloWorld

  • <SDK Folder> is Nokia_Symbian3_SDK_v0.5_2

Table 1. Build configuration files (see the yellow section in the diagram).
File extension Description Default location
bld.inf Master project file. Specifies .mmp and .mk files. <Project Folder>\group
.mmp Project definition file. Specifies .cpp, .rss and _reg.rss source files to be compiled. <Project Folder>\group
.mk Additional make file. In this example, it describes how to build the graphics files, that is, convert .svg to .mif. <Project Folder>\group

Table 2. Source files (see the yellow section in the diagram).
File extension Description Default location
.cpp Source files containing the classes used in the implementation of the application. <Project Folder>\src
.rss Resource source files used for GUI components in the application. <Project Folder>\data
.svg Graphics source file. In this example, defines the application icon in SVG (Scalable Vector Graphics) format. <Project Folder>\gfx
_reg.rss Registration resource file. Specifies the application information, such as the executable name and graphics. <Project Folder>\data
.xml Backup registration file. <Project Folder>\sis

Table 3. Package files (see the yellow section in the diagram).
File extension Description Default location
.pkg Package file. Specifies the information required to create the .sis installation file. <Project Folder>\sis

HelloWorld output files

In the following table,

  • <Build platform> is WINSCW for the emulator or GCCE for a target device.

  • <Build type> is udeb for a debug build and urel for a release build.

Table 4. Output files (see the blue section in the diagram).
File extension Description Default location
.exe Executable file.

C:\Nokia\devices\<SDK Folder>\epoc32\release\<Build platform>\<Build type>
.rsc Compiled resource file.

  • Target build is C:\Nokia\devices\<SDK Folder>\epoc32\data\z\resource\apps

  • Emulator build is C:\Nokia\devices\<SDK Folder>\epoc32\release\WINSCW\<Build type>\z\resource\apps
.mif Machine-readable files with all the SVG (tiny) icons packed into them.

  • Target build is C:\Nokia\devices\<SDK Folder>\epoc32\data\z\resource\apps

  • Emulator build is C:\Nokia\devices\<SDK Folder>\epoc32\release\WINSCW\<Build type>
_reg.rsc Compiled registration file.

  • Target build is C:\Nokia\devices\<SDK Folder>\epoc32\data\z\resource\apps

  • Emulator build is C:\Nokia\devices\<SDK Folder>\epoc32\release\WINSCW\<Build type>\z\private\10003a3f\import\apps

HelloWorld installation file

Table 5. Description of the installation file (see the green section in the diagram).
File extension Description Default location
.sis Unsigned installation file which must be signed before installing the application on the mobile device. <Project Folder>\sis
.sisx Signed installation file for installing the application on the device. <Project Folder>\sis
Parent topic: Tutorial 2: Creating an Application
© Nokia 2010.