[yocto] How can I set a recipe that its binaries become available at cross-compile time?

Jussi Kukkonen jussi.kukkonen at intel.com
Mon May 23 07:23:53 PDT 2016


On 23 May 2016 at 16:37,  <S.Jaritz at esa-grimma.de> wrote:
> Hej
>
> I a cmake based application, some code generation via dbusxx-xml2cpp. It is
> provided by the dbuss-c++ lib. A recipe can be found under:
>
> http://git.yoctoproject.org/cgit/cgit.cgi/meta-ivi/tree/meta-ivi-demo/recipes-extended/dbus-c++?id=b90c2a20744e1e82b2169a88e68d7677bec907b6

You shouldn't need a separate native recipe: 'BBCLASSEXTEND =
"native"' in the main recipe should work.

> It working and it's compiling & linking, "dbusxx-xml2cpp" is included at the
> native build.
>
> How can I set a recipe that its binaries become available at cross-compile
> time?

If dbus-c++ installs the binaries properly and another recipe depends
on dbus-c++-native then the binaries should be in the native sysroot
during the other recipes build. As an example see dbus-glib and
connman-gnome in oe-core: dbus-glib-native provides dbus-binding-tool
which connman-gnome uses during build.

HTH,
  Jussi



More information about the yocto mailing list