android - Shared object and resource file with company name? -

android - Shared object and resource file with company name? -

i'm working on android phone issue. can't find mod htc evo 4g (kingdom). apparently, company called dxo labs used dmca forcefulness cyanogenmod remove htc mods.

i want list of shared objects built dxo labs on evo. have device can enumerate shared objects on device. don't know if elf dsos built (or built with) company info windows executables. don't ever recall coming across them, don't believe ever looked.

do linux executables , shared objects in elf format have mechanism similar windows resource files? sorry have ask. i'm having problem locating document on android's elf file format , abi other platforms have.

looking @ system v application binary interface, possible mark objects company information. page 81, notes section:

sometimes vendor or scheme builder needs mark object file special info other programs check conformance, compatibility, etc. sections of type sht_note , programme header elements of type pt_note can used purpose. note info in sections , programme header elements holds number of entries, each of array of 4-byte words in format of target processor. labels appear below help explain note info organization, not part of specification.

+----------------+ | namesz | +----------------+ | descz | +----------------+ | type | +----------------+ | name | +----------------+ | desc | +----------------+

namesz , name: first namesz bytes in name contain null-terminated character representation of entry’s owner or originator. there no formal mechanism avoiding name conflicts. convention, vendors utilize own name, such ‘‘xyz computer company,’’ identifier. if no name present, namesz contains 0. padding present, if necessary, ensure 4-byte alignment descriptor. such padding not included in namesz.

descsz , desc: first descsz bytes in desc hold note descriptor. abi places no constraints on descriptor’s contents. if no descriptor present, descsz contains 0. padding present, if necessary, ensure 4-byte alignment next note entry. such padding not included in descsz.

type: word gives interpretation of descriptor. each originator controls own types; multiple interpretations of single type value may exist. thus, programme must recognize both name , type ‘‘understand’’ descriptor. types must nonnegative. abi not define descriptors mean.

and page 115 on vendor extensions:

besides services listed above, libc may contain other symbols. abi-conforming scheme vendor may add together symbol c library provide vendor-specific services. abi not define these services, , programs using these services not abi-conforming. nonetheless, abi defines recommended extension mechanism, providing way avoid conflict among services multiple vendors.

a symbol of form _$vendor.company. company provides operating scheme entry vendor named company. c library not have unadorned alternatives these names. conventionally, vendor uses single name provide multiple services, letting first argument _$vendor.company select among alternatives. example, ‘‘xyz computer company’’ might add together _$vendor.xyz c library.

android linux embedded-resource elf shared-objects