All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Looijmans <mike.looijmans@topic.nl>
To: <S.Jaritz@esa-grimma.de>, <yocto@yoctoproject.org>
Subject: Re: How can I set a recipe that its binaries become available at cross-compile time?
Date: Mon, 23 May 2016 15:56:39 +0200	[thread overview]
Message-ID: <57430C17.3040409@topic.nl> (raw)
In-Reply-To: <OFD3CFEA30.52570675-ONC1257FBC.0049688D-C1257FBC.004AD217@esa-grimma.de>

On 23-05-16 15:37, S.Jaritz@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
>
>
> 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?

Simply adding the following to a recipe should make the command available in 
the PATH:

DEPENDS += "dbus-c++-native"

(though your moving of the binary into a "dbg" package might disturb that. I'd 
create a "utils" package for it)


Kind regards,

Mike Looijmans
System Expert

TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: mike.looijmans@topicproducts.com
Website: www.topicproducts.com

Please consider the environment before printing this e-mail







  reply	other threads:[~2016-05-24  2:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-23 13:37 How can I set a recipe that its binaries become available at cross-compile time? S.Jaritz
2016-05-23 13:56 ` Mike Looijmans [this message]
2016-05-23 14:23 ` Jussi Kukkonen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=57430C17.3040409@topic.nl \
    --to=mike.looijmans@topic.nl \
    --cc=S.Jaritz@esa-grimma.de \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.