Archived:Specifying a platform or product dependency in S60 3rd Edition SIS files (Known Issue)

Comments

(no comments yet)

Log in or Join to leave comments.

Archived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.

The article is believed to be still valid for the original topic scope.

Article Metadata

---

Compatibility

Platform(s): S60 3rd Edition

---

Article

Created: User:Technical writer 1 (January 26, 2006, updated May 21, 2007)

Last edited: hamishwillee (21 Jun 2012)

Overview

The format of the platform dependency line required in .pkg files has changed between S60 2nd and 3rd Editions.

Description

On S60 2nd Edition, the mandatory .pkg line is defined the same way as any dependency on a software component:
; Supports S60 2nd Edition
(0x101F7960), 0, 0, 0, {"Series60ProductID"}(0x101F7960), 0, 0, 0,
On S60 3rd Edition, the platform dependency is considered a hardware dependency, and the line must be defined with square brackets enclosing the platform UID:
; Supports S60 3rd Edition
[0x101F7961], 0, 0, 0, {"Series60ProductID"}
This format is also used with device (model) specific product IDs.
Note that the old definition is still a valid .pkg line in S60 3rd Edition, and the makesis utility parses it without errors. However, an attempt to install such a SIS file to a S60 3rd Edition device will fail with an "Application not compatible" error, as the platform UID is not recognized by the installer.
Some tools or IDEs that are capable of automatically creating .pkg files for S60 3rd Edition projects may still incorrectly use the old format for the dependency line.

Solution

Check that the .pkg files used for generating SIS files for S60 3rd Edition use a correctly formatted line for the platform dependency.