This article describes the process of establishing, deploying, and running Series 60 sample applications with graphical user interface (GUI).
We assume that you have installed the Series 60 Software Development Kit (SDK) and install your own integrated development environment (IDE). These two installations are very easy.
The subject matter of this article includes: Development Process Overview - Detailed description of the simulator or target device, establishing and running the Series 60 project process, and many IDE guides, and developers can use the compilation option. Series 60 Simulator - Series 60 Simulator features and layouts, including debug version and distribution. It contains similarities between simulators and real Series 60 devices. Establish a program on the simulator - how to use a different vendor's IDE and PC command prompt to establish a HelloWorld project for the simulator. Run the simulator - Start multiple methods of the simulator, and how to locate and run the example helloworld application. Establish a program on the target device - how to establish a HelloWorld sample application for Series 60 devices, compile it to ARM binary executables. Deploying programs on the target device - how to pack multiple components of the application, select some method to transfer it to the Series 60 device, how to locate and execute it. One step from the development process will give you a basic step. This is a quick guide to establish tools and multiple IDEs using the Series 60 C program. You will see how to build and run the "Hello World" application for the Series 60 Simulator, and how to create, deploy, and run the app on the target device. This article provides all information to establish and run the HelloWorld example.
Series 60 C Software Development Kit (SDK)
Symbian OS is widely used in smart phone platforms, such as Series 60, Series 80, and Series 90 are three UI platforms from NOKIA and UIQ (UIQ Technology companies).
Series 60 SDK is built on some versions of Symbian OS C SDK released by Symbian. The SDK contains a lot of tools, API, class libraries, and documents that allow you to develop new applications.
As a developer, you may need to use multiple versions of Series 60 SDK (even from the SDK from different Symbian OS UI platforms). The most important question is to select the correct SDK version for the Series 60 product you choose.
NOKIA or Series 60 gets the license released SDK for the SERIES 60 platform specific version. That is, each Series 60 product is based on a particular platform version, and the SDK version is customized to develop on a platform version. Specific SDK versions may also be suitable for previous versions. This "backward compatibility" depends on the change of the API used by the API used by the Symbian OS version used as version-based, and the API used by the application developer, and the API between the different platform versions. Special acquisitions may also be introduced for product dedicated APIs to allow developers to access their Series 60 with different features of other products. For example, the Siemens SX1 smart phone contains an FM radio, so the corresponding SDK can contain "additional" API to maintain radios. In order to maximize compatibility between different products, you may want to avoid using this product-specific API. You will even choose to limit the use of a generic API, only use of the selected range of the selected range of a platform, does not change the API.
Using multiple SDKs using a Symbian OS SDK is very easy, and the installation process will make it available immediately. However, developers typically require multiple different versions of SDK, even different user interface platforms. You can install multiple SDK on the developed PC, where do you install them, how to choose to make some restrictions. Development process overview
SDK provides a PC platform-based simulator, so most development and test operations can be done without the target hardware device. We can create different debugging or released version of Series 60 projects (although there are still restrictions on the debug version on the current target device). In addition, the executable code of different binary formats (such as ARMI, ARM4, and Thumb) can also be established for the target device. The process of compilation and linking can be made using a command line tool or in a variety of IDEs. The IDE discussed in this article includes Microsoft Visual C 6, Metrowerks CodeWarrior, Borland C Builder 6 Movement and Borland C Builderx Movement.
Symbian designs a method of describing the development project with a platform-neutral manner. Two global files (Projectname.MMP and BLD.INF) are created in Symbian, where ProjectName is the name of the component or application to be developed (HelloWorld in the sample item). These two files can be used as any application option, the starting point of the IDE, and platform.
Bld.inf Specifies the name of all item components to be established, and each component is in its own .mmp file. These two files are plain text, usually you only have one .mmp file, which defines the application that will be established. If the item contains multiple components, such as including the application itself and a specific library, each component will have its own .mmp file. Each library and application have a .mmp file, and each file name is listed in the bld.inf file of the project.
There are two items documentation in the HelloWorld example: bld.inf and helloworld.mmp. Use these two files to build items and command files of any particular platform we need.
Typically, you use a Symbian tool called BLDMAKE to generate a command file called abld.bat as an input; then you can use abld.bat in the command line to perform a large number of items. Related operations. For example, abld.bat can be used to generate a specific platform and a project composition file (Makefiles) of a particular IDE. If the project source code exists, or has been completed, we can compile the project for one or more platforms using ABLD.
Since most developed projects are established and run in an IDE, you usually need to establish a suitable IDE project file.
When using Microsoft Visual C , you will use Abld.dsp and HelloWorld.DSW project files in the command line. .dsw is the workspace file opened in the IDE, which can point to one or more .dsp files.
For MetrowerKs CodeWarrior, you can use a normal way to create a project file in the IDE, or directly import the .mmp file into the IDE. The import process will establish the files required for the HellWarriRD.mcp.
Similarly, the Borland C Builder mobile version of the IDE can perform similar import transactions similar to the MetrowerKs IDE, but it is imported into the BLD.inf file instead of .mmp file. For example, Borland C BuilderX will establish a project file called HelloWorld.cbx. Opening a specific IDE project file will allow you to develop, build, run, and debug the application and have comprehensive support for IDE.
ABLD can also be used to compile and link at the command prompt at the developer working in the command line level.
All methods of establishing a specific IDE project file will be talked in the part of this article. Moreover, Figure 1-1 shows a project file (using the IDE import option or using the Symbian tool) using two universal Symbian OS project files.
Figure 1-1. Project files for specific IDEs and specific platforms obtained from the general Symbian file
Author: Tao Gang build time: 2004-12-02 Source: NEW YORK
