On Mon, 7 Feb 2011, Miretti, Gabriel wrote:
Hi, I just begin to work with Meego and particularly with Meego Compliance.
In 3.2.2, the specification says:
"They shall import external interfaces only from the
following sources:
* shared libraries supplied as a part of the application
package"
My question: There is a preferred/recommended/mandatory
method to load this libraries in order to avoid clashes
shared libraries of different applications? For example,
two 3rd party applications supplied "libgsoap.so", one
"libgsoap.so.1" and the other "libgsoap.so.0", if both
exposes its shared libraries one of them probably will
crash.
A MeeGo compliant app is not supposed to install anything
into /usr/lib (sec. 3.3.4). Therefore, if multiple apps
supply the same 3rd party lib, there's no conflict.
Suppose that your app needs 3rd party libs and you install
them in the folder /opt/foo/lib. Before you start your app,
you can manipulate the LD_LIBRARY_PATH to pull in your lib
folder.
### BEGIN STARTUP SCRIPT ###
#!/bin/sh
LD_LIBRARY_PATH="/opt/foo/lib${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}"
export LD_LIBRARY_PATH
exec /opt/foo/foo.bin "$@"
### END ###
-gabriel
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
