[yocto] CommonAPI *.so bindings

Suchy, Pawel pawel.suchy at delphi.com
Wed Nov 30 07:32:53 PST 2016


Yocto in none dev image does not allow to have symbolic links to versioned shared libraries.
That is causing a problem with binding CommonAPI dynamic libraries via commonapi.ini.
The commonapi.ini file contains sections where dependencies to proxy objects could be defined:
[proxy] local:commonapi.examples.Test:commonapi.examples.Test=libTest-DBus.so

But it cannot take link to versioned library because of that code:

 Runtime::loadLibrary<http://docs.projects.genivi.org/ipc.common-api-runtime/3.1.5/classCommonAPI_1_1Runtime.html#a3e51dbc5c5b72e879442c4ff579799ed>(const std::string &_library) {
321  std::string itsLibrary(_library);
323  // TODO: decide whether this really is a good idea...
324  #ifdef WIN32
325  if (itsLibrary.rfind(".dll") != itsLibrary.length() - 4) {
326  itsLibrary += ".dll";
327  }
328  #else
329  if (itsLibrary.rfind(".so") != itsLibrary.length() - 3) {
330  itsLibrary += ".so";
331  }
332  #endif

1. How to solve best this?
2. Is it a good Yocto practice to not allow to have symbolic links in none-dev images?
3. Is there a way to have symbolic links to libs in /usr/lib directory in none-dev images?

Kind Regards,

**************************************************************************************** Note: If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. ****************************************************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20161130/3ee8f1e8/attachment.html>

More information about the yocto mailing list