1.1. Developing Series 60 applications1.1.1. getting started
Series 60 sdks are built by the specified Symbian OS C ++ sdks released by Symbian. An SDK contains tools, application interfaces, class libraries, and documents to facilitate developers to develop new applications.
Each series60 product is built on a specific release platform, and developers often need to work on sdks of Series 60 of different versions, or for different user interface platforms, use different sdks.
1.1.1.1. Development Process Overview
Most of the development and testing work can be done through the simulator on the PC platform, despite some restrictions on debugging on the target machine. In addition, to be able to build executable programs for the target device, there are several binary formats (such as armi, arm4, thumb ). You can use the command prompt tool or other ide tools to compile and link the process.
There are two common project files: projectname. MMP and BLD. INF. These two text files are used as the starting point for building options, specifying IDE and platform variables.
The bld. inf file specifies the names of all components in the project and their own. MMP files for each component. If a project consists of multiple components, such as the application itself and other specified function libraries, each component has its own MMP file, each library and application has an MMP file, and each file name will be listed in the BLD of the project. INF file.
Shows the process for generating project files for IDE and specific platforms from General Symbian files:
Figure 2-2-1-1
The following is an example of "Hello World.
1. The projects include bld. inf and helloworld. MMP. Using these two files as input, you can use the bldmake tool of Symbian to generate the abld. Bat command file. Then you can use the abld. BAT file to execute project-related actions in the command prompt. As shown in:
After execution, the corresponding
2. Many times projects are created and run in the IDE. In this case, you need to create related files for the IDE you selected. Here we mainly look at VC ++. We can use abld to create the hellowrold. DSP and helloworld. DSW files in the command prompt. However, 3rd does not support vc6 on the Internet. The specific reasons are as follows:
Later, I changed the default device to version 2.0, but there are still other problems. I found it online because the path is not installed in the System Disk directory.
However, it is very convenient to use vs2005. You can import data directly through the MMP _file or inf file.
3. Opening a project file with the specified ide will allow you to develop, build, run, and debug with the full support of IDE. For developers who are used to using command prompt, abld can still meet your compilation and link requirements.
4. It may be because of poor computer performance. I used vc2005 to run the helloworld program in symbian9.2. After the simulator appeared, it took only half a day to respond. At the beginning, I thought there was another problem and how could the problem be solved.
About vc6Helloworld compiled successfullyExample:
According to the above practice, there is always a flaw in the heart, so I decided to use the 2nd version to try, and finally succeeded. Write down the process for your reference:
1. preparations. First, ensure that the series60_v20 is installed on the system disk, that is, the C disk. I first installed it on the d drive, but it still works after I copied it to the C drive, so I don't have to reinstall it. Set environment variables:
Environment variable name |
Environment variable value |
Remarks |
Epocroot |
/Symbian/7.0 S/series60_v20/ |
The variable value cannot contain the drive disk symbol. |
Vc6_root |
D:/program files/Microsoft Visual Studio |
The installation path of my vc6 is used in the environment variable path. You can directly write the path in the path. |
Path |
% Vc6_root %/common/tools/winnt; % vc6_root %/common/msdev98/bin; % vc6_root %/common/tools; % vc6_root %/vc98/bin; C: /Symbian/7.0 S/series60_v20/epoc32/tools; C:/Symbian/7.0 S/series60_v20/epoc32/GCC/bin;... |
The first part is the path of the vc6 related directory, and the last part is the path related to series60_v20. Other paths unrelated to Symbian development are omitted by the ellipsis. |
If multiple devices are installed on the computer, make sure that the current device is in series60_v20. Next we will look at the commands for viewing devices and setting default devices. View the available devices and use the command devices. As shown in:
The command to change the default device is as follows:
2. run cmd to change the current directory. INF file and. the Directory of the MMP file. Here is the directory "C:/Symbian/7.0 S/series60_v20/examples/basics/helloworld ".
3. Enter "bldmake bldfiles" and press enter to generate the file "abld. Bat ".
4. Enter [abld build wins udeb], which is the simulator build project and contains debugging information that can be executed in binary. To build a project file for vc6, enter "abld makefile vc6 ]. Will generate vc6. DSW file and. DSP file, the file location depends on the location of the SDK on your computer, where my file is generated as "C: /Symbian/7.0 S/series60_v20/epoc32/build/Symbian/7.0 S/series60_v20/examples/basics/helloworld/wins"
5. Find the. DSW file, open the project, and run the output helloworld, as shown in:
Figure 2-2-1-2
1.1.1.2. Simulator
The benefits of using simulators for development, debugging, and testing are not described in detail. The simulator's appearance mainly depends on the target platform, the Series 60 version used, and the selected IDE. Although the simulator has brought us a lot of convenience in learning Symbian development, some differences between the simulator and the real machine cannot be overcome, such as cameras, vibrations, precise time, program performance, and memory management, therefore, in a sense, development and testing still require a real machine.
The s60 display can be logically divided into three areas: the Status area, the main area, and the control area. The status area displays information about the current program and general information about the device, such as signal strength and power. The main area displays program data. The control area refers to the two button labels at the bottom of the screen, which are used to indicate the selection of response operations. It's actually the same as a mobile phone. Let's take a look at the 3rd_fp1 Simulator Interface, as shown in:
Figure 2-2-1-3