Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries over the next few weeks. Thanks for all your past and future contributions.

MMP file

From Wiki
Jump to: navigation, search
Article Metadata
Created: tote_b5 (26 Mar 2007)
Last edited: hamishwillee (12 Jan 2012)

Syntax overview

A .mmp project definition file specifies the properties of a project in a platform and compiler independent way. The makmake tool converts project definition files into makefiles for particular platforms. The abld.bat tool wraps calls to makmake, and can be more convenient to use than makmake directly.

A project definition file has extension .mmp.

Note that:

  • Each statement occupies a single line.
  • Use the C++ style comment syntax for comments.
  • A trailing backslash is used to indicate a line continuation. Therefore, specify directories without their trailing backslash, for example: Do SYSTEMINCLUDE \epoc32\include, rather than SYSTEMINCLUDE \epoc32\include\

Example project


From v9.0, a GUI application is an exe. This is specified with the targettype statement:


The target filename's extension can be either .app or .exe. This is specified using a target statement:

TARGET <appname>.exe


Specify the UID for the application in a uid statement:

UID 0x100039CE <UID3>

The UID2 value 0x100039CE should be used for all applications. The UID3 value is the unique identifier for the particular application.


Specify the languages that the application is localised for in the .mmp file:

LANG 01 02 03

Stack size

By default, processes have a stack size of 8K. This can be insufficient for some applications. To increase the size, use an epocstacksize statement:

// set stack to 20K
epocstacksize 0x5000

UI resource

Specify the application's UI resource file using a start resource statement:

TARGETPATH \Resource\Apps

The resource should be built into the \Resource\Apps directory. This is specified using the TARGETPATH part of the statement.

The header line tells the resource compiler to produce a file \epoc32\include\<appname>.rsg, which defines macro constants through which C++ programs can refer to resource structures.

Caption/icon resource

An application can specify localisable captions and icons to display on the shell using a LOCALISABLE_APP_INFO resource, either in the UI resource file or in a separate resource file.

Registration file

Specify the application's registration file using another start resource statement:

START RESOURCE  <appname>_reg.rss
TARGETPATH \private\10003a3f\apps

The registration file must be built to the private system directory \private\10003a3f\apps directory.

Note that for security reasons a registration file cannot be installed directly to this location on a target device. When creating a PKG file (software install package file) for an application, the registration file must be installed to the \private\10003a3f\import\apps\ directory.


A bitmap file containing icons for an application can be specified using a start bitmap statement:

START BITMAP    <appname>.mbm
TARGETPATH \Resource\Apps
SOURCE <color-depth> <source-bitmap-list>

Icon files, like the UI resource file, should be built into the \Resource\Apps directory.


An example of a real GUI application project file is given below:

TARGET HelloWorld.exe
UID 0x100039CE 0x10004299
VENDORID 0x70000001
epocstacksize 0x5000
SOURCE HelloWorld_Main.cpp
SOURCE HelloWorld_Application.cpp
SOURCE HelloWorld_Document.cpp
SOURCE HelloWorld_AppUi.cpp
SOURCE HelloWorld_AppView.cpp
SYSTEMINCLUDE \epoc32\include
TARGETPATH \Resource\Apps
START RESOURCE HelloWorld_reg.rss
TARGETPATH \private\10003a3f\apps
START BITMAP HelloWorld.mbm
TARGETPATH \Resource\Apps
SOURCE c8,1 icon24.bmp icon2m.bmp icon32.bmp icon3m.bmp
icon48.bmp icon4m.bmp
LIBRARY euser.lib apparc.lib cone.lib eikcore.lib
This page was last modified on 12 January 2012, at 02:59.
106 page views in the last 30 days.

Was this page helpful?

Your feedback about this content is important. Let us know what you think.


Thank you!

We appreciate your feedback.