The practice of setting up Symbian development environment on Vista system

Source: Internet
Author: User
Tags config root directory

We all know that Symbian is not a very easy to install development environment, and recently I changed the OS to Vista, and encountered unprecedented trouble. Toss a night finally ran through, the following process summed up, I hope that the next time to reload the system without too much effort.

The first step, according to the information on the Internet to install the required software, pay attention to two aspects:

The first version is not mistaken, as follows:

JDK 1.6.0_04 (Jdk-6u4-windows-i586-p.exe)

Perl 5.6.1 (Activeperl-5.6.1.638-mswin32-x86.msi)

Then, is the normal installation of carbide C + + v1.2, the online has cracked version of the LIC can be OEM version of the function.

Symbian SDK is casual, choose a few commonly used mainstream installation can be.

The second is the installation of the directory must be placed in C, or later very troublesome, including the establishment of the project documents should also be placed in the C:\Symbian\workspace, easy, although this makes people very uncomfortable.

The second step is to modify a place, or the emulator does not recognize the Java 1.6 environment (take S60 3rd for example).

Open the C:\Symbian\9.1\S60_3rd\Epoc32\tools\ecmt\config\config.properties file and modify one of the rows:

epdt.java.version.start=1.4.1,1.4.2,1.5,5.0,1.6,6.0

Just add 1.6,6.0 to the back and let it know more than 1.6 jdk.

The third step, because Vista ACL is more stringent, it is recommended that the Carbideide and emulator with administrator privileges to run.

Where the simulator position is in C:\Symbian\9.1\S60_3rd\Epoc32\release\winscw\udeb\epoc.exe and carbide is located in C:\nokia\carbide.c++ v1.2\ Carbide.c++.exe, this carbide also has to be run with the compatibility mode of XP SP2.

At this point, you should be able to successfully run the carbide environment on Vista and generate the HelloWorld program.

But it's not over yet, although you can compile an application that runs in an emulator environment, but if we want to generate the SIS file on the final device, that is, build target is set to GCCE mode, it doesn't compile.

The main reason is that the 3rd after the arm toolchain caused. So we need to revise a few more places:

First modify the environment variable and add a reference to it in the path of the user variable, as follows:

Path=C:\Java\jdk1.6.0_04\bin;C:\CSLArmToolchain\bin;C:\CSLArmToolchain\arm-none-symbianelf\bin;C:\CSLArmToolchain\libexec\gcc\arm-none-symbianelf\3.4.3;C:\Perl\bin;C:\ADSv1_2\bin;%PATH%;

Note that a few more directories, in addition to Jdk,perl is mainly the C:\CSLArmToolchain related subdirectories (I put cslarmtoolchain installed in the C root directory, in fact, can also be placed in the program files, do not affect). In addition, I put the system%path% to the last, save trouble.

Then modify two files, one of which is the Gcce.mk file located in the C:\Symbian\9.1\S60_3rd\tools\compilation_config directory. The code to modify line 14th is as follows:

Cc_install_path= "C:\CSLArmToolchain"

Forces the installation directory of the CC to be specified.

There is also line No. 333, which reads:

#add by sharetop
LINK_EXT_SHARETOP=-L"$(CC_INSTALL_PATH)\arm-none-symbianelf\lib" -L"$(CC_INSTALL_PATH)\lib\gcc\arm-none-symbianelf\3.4.3"
# Linker option common to all link commands for UREL build
SYMBIAN_UREL_LINK_FLAGS=$(SYMBIAN_LD_MESSAGE_OPTION) $(BPABI_OPTION) $(RELOCATABLE_IMAGE_OPTION) $(TARGET_RELOCATION_OPTION) $(UNRESOLVED_SYMBOL_REF_OPTION) $(STDLIB_OPTION) $(EXTRA_LD_OPTION) $(LINK_EXT_SHARETOP)
# Linker option common to all link commands for UDEB build
SYMBIAN_UDEB_LINK_FLAGS=$(SYMBIAN_LD_MESSAGE_OPTION) $(BPABI_OPTION) $(RELOCATABLE_IMAGE_OPTION) $(TARGET_RELOCATION_OPTION) $(UNRESOLVED_SYMBOL_REF_OPTION) $(STDLIB_OPTION) $(EXTRA_LD_OPTION) $(LINK_EXT_SHARETOP)

Mainly after symbian_udeb_link_flags to add two libraries, otherwise compiled O file can not be linked to EXE file, both libraries are under the Cslarmtoolchain.

You will then modify the cl_bpabi.pm of another file located in the C:\Symbian\9.1\S60_3rd\Epoc32\tools directory. This is a good change, just a word, find the function sub Gccinstallpath, simple, let it directly return to a fixed directory, in line 1649th, write:

Sub Gccinstallpath {

return "C:\\cslarmtoolchain\\bin";

...

The following code regardless of, you can stay indifferent, let it directly back to this directory.

Now, it is really the environment configuration completed, and then try to compile the HelloWorld version of Gcce, it will automatically sign and generate SISX files, can be copied to the phone to run.

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.