A Symbian OS UID is a 32-bit, globally unique identifier value used to identify a file type, both for running executable code and for associating data files with the appropriate application. Symbian OS uses a combination of up to three UIDs to uniquely identify a binary executable.
UID1: UID1 is a system-level identifier which distinguishes between EXEs and DLLs. This value is never stated explicitly but is determined by the Symbian build tools from the targettype specified in the MMP file.
UID2: distinguishes between shared library DLLs (KSharedLibrary-and polymorphic interface DLLs (in case of UID1 is DLL).
UID3: identifies a component uniquely. In order to ensure that each binary that needs a distinguishing UID is assigned a genuinely unique value, Symbian manages UID allocation through a central database and developers must be registered with Symbian Signed to request
UIDs
UID1: UID1 is a system-level identifier which distinguishes between EXEs and DLLs. This value is never stated explicitly but is determined by the Symbian build tools from the targettype specified in the MMP file.
UID2: distinguishes between shared library DLLs (KSharedLibrary-and polymorphic interface DLLs (in case of UID1 is DLL).
UID3: identifies a component uniquely. In order to ensure that each binary that needs a distinguishing UID is assigned a genuinely unique value, Symbian manages UID allocation through a central database and developers must be registered with Symbian Signed to request
UIDs
Note:
UID2 is not relevant for an EXE and can be left unspecified or set explicitly to KNullUid (= 0). UID3 can be left unspecified too but, on Symbian OS v9 and beyond, it should usually be set to a unique value to act as the secure identifier for the binary.
0 comments:
Post a Comment