Notes for porting s60 3 Edition program to version 5

The original s60 3rd development environment remains unchanged. Install s60_5th_edition_sdk_v1_0_en. Please read releasenotes.txt carefully to learn about the new features of this version, which will save you a lot of detours.

 

Note the following points from releasenotes.txt:

1) supports Java and web runtime widget development. If Java development is not performed, skip the eclipse installation step.

2) supports arm rvct compiler 2.2 build 593 and later versions. However, it is verified that rvct 2.2 build 435 can be used normally.

3) The 5th SDK can be used in Windows Vista, but the rvct compiler cannot be used in Vista.

4) openc has been integrated into the 5th mobile phone, and the openc package does not need to be embedded in the program. Otherwise, an "Update error" occurs during installation"

 

Theoretically, the application architecture version 5 and Version 3 are no different, but you only need to add a touch screen event (such as handlepointereventl) to the interface. However, I believe that many problems will still occur during the transplantation process.

 

After the SDK is installed, "s60_5th_edition_sdk_v1.0" is displayed in the available SDK of carbide 1.3 SDK preferences.

 

The following are the key points of transplantation:

1. openc and MMF are used in my program. So we need to copy the openc and MMF plug-ins used in s60 3rd to the 5th SDK.

2. To test the real machine as soon as possible, install TRK and panic_code_enabler_3.0. These software requires a developer certificate.

Use the serial number 5530xm to apply for a developer certificate.

3. Install the correct version of TRK for online debugging. The SDK below compares with the TRK version. If the version is not correct, the phone will be restarted after a single-host debugging.

S60 3rd ed and Mr correspond to s60 3.0.0
S60 3rd ed FP1 corresponds to s60 3.1.0
S60 3rd ed fp2 corresponds to s60 3.2.0

S60 5th Ed corresponds to s60 5.0.0

4. Import the project, select the 5th SDK, and compile and run it. Make sure that a set of Code uses the macro definition _ s60_50 _ and _ series60_30 _ to distinguish between Version 3 and version 5. Note that such a macro definition can only be in. CPP ,. C ,. used in H, and used in MMP is invalid.