Common Symbian tools

Common Symbian tools: from Forum Nokia Wiki

This article describes common tools in Symbian, including compiling, packaging, and signing. These commands are usually not directly used by IDE development tools. However, understanding the details of these commands is of great help to our development and debugging. We can know the steps that the IDE tool has taken to complete compilation, packaging, and other operations, once a problem occurs in some links, we can quickly find out the root cause of the problem. After all, the IDE tool is also based on the command line tool. Mastering these commands will also bring us more flexibility.

Contents [Hide] 1. Build and compile 1.1 bldmake command 1.2 abld. bat 1.2.1 abld build 1.2.2 abld Resource 1.2.3 abld clean 1.3 bitmap resource Conversion Tool: bmconv.exe 1.3.1 generate a. MBM file from the. BMP file 1.3.2 view the. MBM File Content 1.3.3 export the. BMP file from the. mbmfile 1.4 build and compile the target platform software 2. Package the signature 2.1 makesis 2.2 makekeys 2.3 signsis 2.4 Software Package signature process 2.4.1 s60 Version 2 2.4.2 s60 Third Edition

Build and compile

Bldmake command

The bldmake tool is used to generate multiple makefiles Based on the build description file (BLD. inf) in the current directory, and then build components of different platforms using these makefiles. The following are common commands for bldmake:

• Bldmake bldfiles-generate makefile and Command Script based on the bld. inf file
• Bldmake clean-this command will delete the makefile that has already been produced. Generally, after we modify the MMP file or bld. inf, we need to clear the original makefile and generate it again.
• Bldmake INF-this command lists the parameters of the bld. inf file. You need to compile and customize bld. inf based on these parameters.

Abld. bat

Abld is a batch file generated by the bldmake Command Based on the bld. inf file. It is used to execute different component build commands. The following describes the common command parameters of abld. BAT:

Abld build

The abld build command is used to build the target components of different platforms. Usage: abld build [Option] Target Platform build type

Target Platform:

Generally, the target platforms include arm4, armi, thumb, gcce, armv5, winscw, wins, cw_ide, vc6, and vs2003. different SDK versions may support slightly different platform categories. it contains the visual device, simulator environment, and IDE environment.

Build type:

Each target platform includes several possible build types, such as udeb (debug version), urel (release version), and all (debug and release ).

Generate a release version using the gcce Compiler

abld build gcce urel

Build the simulator environment debugging version and display details

abld build -v winscw udeb

Abld Resource

Abld resource is used to compile resource files, such as. RSS. MBM. AIF. When we modify the resource file, we can run this command to compile the resource file.

abld resource

Abld clean

The abld clean command is used to delete all generated target files. You need to run this command to delete the old target files when you re-build the project.

Bitmap resource Conversion Tool: bmconv.exe

The bmconv tool provides bitmap files and. MB file conversion function, we can use this command to package several bitmap files. in the MBM file, you can also. export the BMP file from the MBM file.

Generate a. MBM file from the. BMP file

Compile two 12bit bits 1.bmp and 2.bmp into my. MBM

bmconv my.mbm /c121.bmp /c122.bmp

Compile the two 12bit map my.bmp and mymask.bmp into my. MBM and generate my. mbg.

bmconv /hmy.mbg my.mbm /c12my.bmp /c12mymask.bmp

View the. MBM File Content

The. MBM file is composed of one or more bitmaps. You can use the bmconv/V parameter to view the content of the. MBM file.

bmconv /v my.mbm

Export the. BMP file from the. mbmfile

bmconv /u input.mbm 1.bmp 2.bmp

Build and compile the target platform software

Use the bldmake and abld tools to compile and build the software on the target platform. The following describes how to use the software. Step 1: generate the makefile and tool script of the Target Platform

cd myapp/group bldmake clean bldmake bldfiles

Step 2: compile and generate the target platform File

abld clean abld build gcce urel

Package Signature

Makesis

The makesis command can be used to create the packaging and installation program (. SIS) of the target device file according to the. PKG file. The usage is easy to go To the PKG file directory and run makesis MyApp. PKG.

Tip: Run makesis-h to obtain the detailed syntax parameters of the. PKG file.

Package the compiled target file

makesis myapp.pkg

Makekeys

In s60 3rd, software signatures are mandatory (not mandatory in 2nd) and software installation is denied. general Software release tests can be achieved through self-Signed purposes (if you want to use extended capabilities or security-sensitive capabilities, you need Symbian sign) the makekeys command can help us create private keys and self-signed certificates. the usage is as follows:

Makekeys-Cert [-V] [-len key-length] [-Password]-dname distinguished-name-string private-key-file public-key-Cert

The dname parameter is an information string provided by the self-signed certificate to identify the organization. The abbreviated meaning of the string is as follows.

CN Common Name CN=Joe Bloggs OU Organisational Unit OU=Development OR Organisation OR=Acme Ltd LO Locality LO= ST State ST= CO Country CO=GB EM E-mail address EM=noone@nowhere.com

Generate private key and Certificate

makekeys -cert -password yourpasswd -dname "CN=Your Name EM=myemail@address CO=myOrg" mykey.key mycert.cer

Signsis

In the third version, use a separate signsis tool to sign the software. After creating the SIS software package and signing Certificate, use the signsis tool to sign the software.

Signsis usage: signsis input [Output [certificate key [passphrase]

Software Package signature process

In s60 version 2, we can directly run makesis MyApp. PKG to package the software. The software signature is not mandatory. Of course, it is necessary to sign the released software from the security perspective. The following describes the software self-Signed process of s60 version 2 and version 3.

S60 Second Edition

Step 1: generate the private key and Certificate

cd myapp/group makekeys -cert -password yourpasswd -dname "CN=Your Name EM=myemail@address CO=myOrg" mykey.key mycert.cer

Step 2: Enter the private key and certificate name in the. PKG file.

*"mykey.key","mycert.cer"

Step 3: Use the makesis command for packaging

makesis -p yourpasswd myapp.pkg mycert.cer mycert

S60 Third Edition

Step 1: generate the private key and Certificate

cd myapp/group makekeys -cert -password yourpasswd -dname "CN=Your Name EM=myemail@address CO=myOrg" mykey.key mycert.cer

Step 2: run the makesis command for packaging

makesis myapp.pkg

Step 3: sign the generated sisfile

signsis yoursis.sis myapp.sisx mykey.key yourpasswd