Build a Symbian Development Environment

Source: Internet
Author: User
Tags perl script

Installation 1:

My installation process:
Step 1: Install the Perl and Java runtime environments (j2re );
Step 2: Install carbide. c ++;
Step 3: Install s60 3rd Mr SDK, and then install extensions plug-in.
After the installation, click carbide. c ++ to bring up the dialog box:

The following problems occur after installation:

Carbide C ++ cannot be started normally, and the prompt is: JVM terminated code =-1


 

I use XP:

ActivePerl-5.6.1.638-MSWin32-x86.msi
Jdk-1_5_0_07-windows-i586-p.exe
Carbide.c00000000_v1.3.exe
S60-3.2-SDK-f.inc3.2130.zip

Install it in sequence.


Installation 2:


My version and installation method:
1. ActivePerl-5.6.1.635-MSWin32-x86.msi
2. Feature Pack 2, for C ++ 08.10.2007
3. Carbide C ++ 1.3
4、jdk-rj5_0_07-windows-i586-p.exe

Install JDK and ActivePerl first. After installation, you need to set system environment variables. The setting method is as follows:
Java_home = D:/Java/jdk1.5.0 _ 07
Path = % java_home %/bin; % PATH %
Classpath = % java_home %/lib/dt. jar; % java_home %/lib/tools. Jar
After setting up, you 'd better restart your computer, install the SDK, and finally install carbide C ++ 1.3.
In the last step, do not rush to open carbide C ++ 1.3. You need to change the TMP and TEMP environment variables in the system directory to a short path. For example, I changed it to R:/tmp or R:/temp, otherwise, the simulator cannot be enabled in carbide C ++. The rest is have good feeling.

(Because my mobile phone is in FP1 version of n81, I just downloaded FP1 yesterday and haven't tested it yet, but it is probably not a big problem .)



Installation 3:


1. Install related sdks and VC
Nokia divides the mobile phone into multiple series based on the screen size and price of the mobile phone. The current series are: Series 40, Series 60, Series 80, and Series 90. The 60 series uses Symbian OS 6.1 and then makes some modifications to the UI based on the characteristics of the mobile phone screen. The modified Symbian is called the Nokia 60 series platform. Models of the 60 series mobile phones include: nokia 6670, Nokia 6630, Nokia 6260, Nokia N-gage qd, Nokia 7610, Nokia 6620, Nokia 3620, Nokia 3660, Nokia 6600, Nokia 3600, Nokia 3650, Nokia 7650, Nokia n-Gage? .

Next we will take the 60 series as an example to introduce the SDK installation process.
1.1: Install the SDK
Step 1: register at the Nokia forum and download the latest SDK. The latest version of Series 60 SDK for Symbian OS Nokia edition SDK provided by Nokia is v1.2, and the latest version of Series 60 SDK for Symbian OS is V2.1.
Step 2: download the latest active Perl script. installer and the latest j2re (Java 2 Runtime Environment ).
Step 3: Install the SDK. We recommend that you create a separate directory for Symbian development, for example, D:/Symbian instead of C:/program files.
Step 4: install Active Perl and j2re in the default directory.
Step 5: Check the environment variable settings. Open the system environment variable tab and check whether there is epocroot. If so, manually change it to "/". The change should look like this:
Epocroot =/
Then, add the/epoc32/tools directory and the/epoc32/GCC/bin directory to the system path.
In fact, the Symbian SDK does not need to be installed at all. You can directly copy the epoc32 directory to a machine and set the Directory and environment variables as described above.

1.2: Configure VC
If we use VC 6.0, we must ensure that the system has installed at least the SP3 patch. Otherwise, the system will receive a warning. If we use. net2003, we can only install Series 60 SDK for Symbian OS V2.1, because Series 60 SDK for Symbian OS Nokia edition SDK v1.2 is in. net2003 cannot correctly build the project.
If you want to create a new project directly in vc6, you need to add avkonappwiz under the/Symbian/6.1/series60/series60tools/Application Wizard directory. awx and avkonappwiz. copy the HLP file to the template directory c:/program files/Microsoft Visual Studio/common/msdev98/template of vc6. In this way, we can see the Series 60 Appwizard v 1.9 option in the VC new project.
If you want to import a created Project to vc6.0, for example, convert the example helloworld In the SDK into a vc6 project, first, go to the/Symbian/6.1/series60/series60ex/helloworld directory. Here we can see that in Symbian, a project is usually organized by directory such as Inc, SRC, and group. The project file is usually stored in the group directory, therefore, you must first go here for compilation. Enter the directory in command prompt mode, and then execute:
Bldmake bldfiles
This command will generate an abld in the group directory. bat batch files, the directory/Symbian/6.1/series60/epoc32/build/Symbian/6.1/series60/epoc32/build/Symbian/6.1/series60/series60ex/helloworld/group will be generated under/Symbian/series60/epoc32, and generate a heap under the underlying directory. make file.
Then, run the generated abld. bat in the same directory:
Abld makefile vc6
The DSW file of vc6 is automatically generated at/Symbian/6.1/series60/epoc32/build/Symbian/6.1/series60/series60ex/helloworld/group/helloworld/wins. Then we can open the Symbian project in vc6.

2. Compile
We can directly use the tools provided by the SDK to compile the Symbian project, or use the integrated environment provided by vc6 to compile the converted Symbian project. The compiled results are stored in the/Symbian/6.1/series60/epoc32/release/wins/udeb/z/system/apps directory.

2.1 use the tools provided by the SDK to compile the Symbian Project
At the position in the previous section, we continue to enter:
Abld build wins udeb
This command will compile our program and generate our helloworld in the/Symbian/6.1/series60/epoc32/release/wins/udeb directory, then we can run the debug version of the simulator from the Start menu and run helloworld in the simulation.

2.2 Use vc6 to compile the Symbian Project
We directly open the DSW file generated after running abld makefile vc6, and VC automatically loads the converted project. Press F7 to compile the project directly. The compilation results are also stored in the/Symbian/6.1/series60/epoc32/release/wins/udeb directory. Then we open the debug version of the simulator and we can see the compiled project.

3. Run the program on your mobile phone
Take helloworld provided by SDK 1.2 as an example to create a. sisfile that can be installed on your mobile phone:
3. 1. Check the program
First, in the command line format, enter the directory where the MPs file of the helloworld project is located, enter bldmake bldfiles and abld build wins udeb, and then open the simulator to check whether the program has any errors.
3. 2. compile the project
After the program has no errors, enter abld build armi urel in the command line. After executing this command, the helloworld. app and helloworld. RSC files are generated in the Directory D:/Symbian/6.1/series60/epoc32/release/armi/urel.
3. Create a. PKG File
In D:/Symbian/6.1/series60/series60ex/helloworld/sis, use NotePad to create or modify the PKG file of the project. The content is as follows:

; Helloworld. PKG
;
; Language-standard language Definitions
& En
; Standard SIS file header
# {"Helloworld"}, (0x10005b91), 1, 0, 0
; Supports Series 60 v 1.2
(0x101f8202), 0, 0, 0, {"series60productid "}
;
"D:/Symbian/6.1/series60/epoc32/release/armi/urel/helloworld. app "-"! :/System/apps/helloworld. app"
"D:/Symbian/6.1/series60/epoc32/release/armi/urel/helloworld. RSC "-"! :/System/apps/helloworld. RSC"

In the preceding example, "d:/Symbian/6.1/series60/epoc32/release/armi/urel/helloworld. RSC" is the file to be packaged and installed ,"! :/System/apps/helloworld. RSC is the target installation location. Note that "!" is used in the target location. Instead of the actual drive letter. In this case, the mobile phone system prompts the user to select the desired location during user installation, which gives the user greater flexibility and can also be written as an absolute path. In addition, in the Symbian system, the default location of the installed application is "! :/System/apps ".
After editing the PKG file, save it to the corresponding directory.

3. 4. Package
In the command line, go to the directory where the PKG file is located and run the makesis helloworld. PKG command.

3.5. Upload Program
Upload the packaged program to your mobile phone with Bluetooth, and install it. OK. The whole process is successful!

Below is a summary of the key points:
==========================================
1. The commands to be remembered are processed in the Engineering Order:

Bldmake bldfiles-in DOS mode, run the command in the group directory of the project to generate abld. BAT for subsequent project compilation.
Abld makefile vc6 -- generate DSW and DSP engineering files of visusl C ++ 6.0
Abld build wins udeb -- generate the Unicode debug debugging version on the simulator
Abld build armi urel -- generate the Unicode release version running on the mobile phone
2. Related directories:

Directory for generating DSW and DSP engineering files of visusl C ++ 6.0:
/Symbian/6.1/series60/epoc32/build/[path name of the project +/group +/project name]/wins
Path Name of the project: If your project is under C:/symbian_work/helloworld/src (the project files under this directory are organized by directory such as Inc, SRC, and group ), the Directory of DSW and DSP engineering files that generate visusl C ++ 6.0 is: /Symbian/6.1/series60/epoc32/build/symbian_work/helloworld/src/group/helloworld/wins, ah, it's really deep enough, I really don't know why Symbian has such a deep directory!

The program file directory generated by the Unicode debug debugging version of the simulator:
/Symbian/6.1/series60/epoc32/release/wins/udeb/z/system/apps/Project Name
Directory of the simulation epoc.exe file:
/Symbian/6.1/series60/epoc32/release/wins/udeb
Generate the program file directory of the Unicode release version running on the mobile phone:
/Symbian/6.1/series60/epoc32/release/armi/urel

 

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.