Archived:Creating dependencies to Open C components
Article Metadata
Compatibility
S60 3rd Edition, FP1
Article
Overview
Creating dependencies to Open C components
Description
To ensure that an Open C application will work, it is worthwhile to create dependencies to any Open C plug-in components that are required to run the application. This way, the user will be warned during installation if Open C libraries are not present in the device.
To create dependencies to other components by declaring the required components in the PKG file:
(componentUID), version-range, {"Component name for lang 1","Component name for lang n",...}
For Open C plug-in components, the dependencies can be declared as follows:
(0x20009a80), 1, 0, 0, {"Symbian OS PIPS"}
(0x20009aa2), 1, 0, 0, {"Symbian OS STDIOSERVER"}
(0x10281f34), 1, 0, 0, {"Open C LIBSSL"}
(0x10281f2c), 1, 0, 0, {"Open C GLIBRARY"}
In the above example, the dependencies are created to the four OpenC components:
’Symbian OS STDIOSERVER’ (installed from stdioserver.sis),
’Symbian OS PIPS’ (pips_s60_wp.sis),
’Open C LIBSSL’ (openc_ssl.sis),
’Open C GLIBRARY’ (openc_glib.sis),
Dependencies may also be targeted to specific component versions:
(0x0123BABE), 1, 2, 0 ~ *, *, *, {"ComponentName"} ; Version greater than or equal to 1.2.0 is required
(0x0123BABE), 1, 2, 0 ~ 2, 0, 0, {"ComponentName"} ; Version from 1.2.0 to 2.00 required
(0x0123BABE), *, *, * ~ 2, 0, 0, {"ComponentName"} ; Any older version up to (and including) 2.0.0 is required

