Embedded Operating System Symbian Introduction

Symbian is an operating system, and C + + is its native programming language. It provides software developers with the full functionality of the operating system. Of course, familiarity with C + + has a direct impact on the developers ' use of it, because development under Symbian OS will use the advanced features and object-oriented design of C + + extensively. We think that everyone has a corresponding understanding of C + +, and have experienced some project development, therefore, in the future, such as the use of C + + category in the concept of vocabulary, it does not make a special explanation.

1. Understanding Symbian OS

Currently, Symbian OS phones on the market are based on 3 user interfaces developed for C + + programmers: Nokia Series 80, 60 and UIQ (and, of course, a few years ago, the hottest star S40) All support Java programming, so C + + doesn't seem so lonely. Based on the series 60 platform machines like Nokia 3650, 7650,nokia 9210 are using the S80 platform, this type of mobile phone is characterized by a complete mobile keyboard, can simulate PC operation; The UIQ platform's mobile phone screen is larger and can be equipped with a numeric keypad , you can interact with the stylus as you move, like Sony Ericsson P800. Say so much, in fact no matter is what mobile phone platform, the key is to understand Symbian development under the main characteristics. Slowly follow the path below.

2. Preparatory work

Download the appropriate SDK: You can download http://forum.nokia.com.cn/sch/index.html from the Nokai Development Forum.

You can choose to download the SDK version according to your needs.

Using Symbian OS also requires two tools that are Java Runtime and ActivePerl, and there are versions of the two tools that require you to understand the appropriate version requirements before downloading.

I use the following (if no special declaration is developed in this context)

Window SP4, vc++6.0

－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－

Java2run time.se v1.3.1 v1.4.1_02

ActivePerl Build 518 5.6.1

Series SDK 2.1 2.2Beta

－－－－－－－－－－－－－－－－－－－－－－－－－－－－－－

Note: Installation order I generally use the Java runtime/activeperl/series 60SDK, but also need to note that ActivePerl This compilation tool is best installed under c:/(generally I use is regardless of the system disk is what, all of the installed in the c:/, A more easy to manage, and save a lot of unnecessary trouble)!

Installation is complete, and then we'll be familiar with Symbian's catalogue.

First of all, in the process of using the Symbian OS SDK processing letter and directory is really inconvenient, so many problems in the development process from the letter and directory problems. Because I use the development tool is vc++6.0 English edition, so in order to develop conveniently, can do this: the directory. Copy the files in the/symbian/7.0s/series60_v21_c/series60tools/appwizard to the VC installation directory. /microsoft Visual Studio/common/msdev98/template, the advantage of doing this is that when you use VC, when you create a new project using the new command, Series 60 appears in the project Bar of the AppWizard dialog box.

Let's take a look at the directory structure of a Symbian OS project:

The first thing you should be familiar with is the build directory, which is designed to hold engineering documents for a variety of different platforms. After performing the abld makefile VC6 or abld makefile Cw_ide, it will be appropriate to generate MS VC6 or CW engineering files in this directory, noting that the CW engineering file is an XML. To pass through the import in the CW ... Import.

The second directory is the data directory. This directory stores RSS for the resource files of the UI program after compilation. The Series SDK generally copies the RSS to the/epoc32/data/z/system/apps/engineering directory name. If you want to use an MMC card to test your developed program, you should copy *.rss from the above directory and place it in the/system/apps/project directory name in the MMC card with your *.app.

The third directory is GCC. Most of the resources that are stored in this directory are those that the system needs, like some. Lib and. h, this generally we do not need to care too much.

The fourth directory is include this directory is most of the system header files, of course, the system in the build UI program will put the XXX.RSG file in this directory, the file in this document you will know with UE. Another subdirectory is the libc below include. This encapsulates standard C's compatible library of functions.