PAMP:Building

From OpenSource

NOTE Currently only the winscw and armv5 build targets are supported.

Contents 1 Prerequisites 2 General 3 Building 4 SIS-files

Prerequisites

NOTE Check these pre-requisites, even if you have them installed already, as fixes are needed.

• S60 SDK
• Open C
• Python for S60 (needed by mod_python)

General

Every individual ported component has a symbian subdirectory where the Symbian specific build and package files resides. Components that are written for Symbian in the first place, lack the symbian subdirectory, but otherwise the structure is similar.

Building

If you have pulled the source as explained here, all you need to do in order to build all components of pamp is to enter the top-level group directory and issue:

 bldmake bldfiles
 abld build platform build

where, for instance, platform is armv5 and build is urel. The bldmake bldfiles step is necessary only the first time.

The general procedure for building an individual component is as follows:

 cd component/symbian/group
 bldmake bldfiles
 abld build platform build

Furthermore, at various places in the pamp directory hierarchy there are additional group directories in which all components at the same level can be built in one go.

SIS-files

In order to generate all individual SIS-files and the composite SIS-file containing the relevant components, do as follows:

 cd top-level/pamp/sis
 make PLATFORM=platform BUILD=build CERTIFICATE=certificate KEY=key PASSPHRASE=passphrase sisx

where platform is, for instance, armv5, build is, for instance, urel, certificate is the path to the certificate-file, key is the path to the key-file, and passphrase is the used passphrase. Whether or not you need PASSPHRASE depends upon your certificate.

Each component has also a sis-directory of its own, where that component's SIS-file can be created.

 cd component/symbian/sis
 make PLATFORM=platform BUILD=build CERTIFICATE=certificate KEY=key PASSPHRASE=passphrase sisx

NOTE The full SIS-file dependences are not in place. To ensure that the SIS-file you get really contains the latest binaries, issue

 make clean

before building SIS-file.

If you issue sis instead of sisx then the sis-file will be created, but it will not be signed.