Embedded Application Programming Interface - picmg

13.2 Linux/Unix Shared Library Naming Convention
Problem
Due to the nature of ELF Shared Libraries in Linux/UNIX/... it may not be possible to distinguish one
manufacturer's DLL from another. Although it would possible to do this using a tool that uses the API,
It may not be possible to load the shared library, due to missing dependencies.
Solution
Filename Convention
libEApiYYY.so.W.Z
Part Example Description
YYY PMG Vendor PNPID
W 1 EAPI Specification Version number
X 0 EAPI Specification Revision number
Soname Convention
libEApi.so.W
Part Example Description
W 1 EAPI Specification Version number
Example
Shared Library
Filename = libEapiPMG.so.1.0
soname = libEApi.so.1
in file system.
/usr/lib/libEApi.so.1 → /usr/lib/libEapiPMG.so.1.0
/usr/lib/libEApiPMG.so.1.0
see EApiDK for sample implementation.
13.3 ELF/a.out Format Shared Libraries
13.3.1 Library Output Format
Problem
Due to the nature of ELF Dynamic Link Libraries in Linux/UNIX/... it may not be possible to distinguish
one manufacturer's DLL from another. Although it would possible to do this using a tool that uses the
API, It may not be possible to load the DLL, due to missing dependencies.
Solution
The solution is to require the shared libraries be executable. Upon Execution the library should then
print out the following information.
The Output format is
=Value
and should be matched by this regular expression. m/^\s*(\w+)\s*=\s*(.+)\s*$/
where
$1=Variable name
$2=Value/Data.
PICMG® EAPI R1.0, August 8, 2010 page 80 of 83