All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Eric Bénard" <eric@eukrea.com>
To: Michael Fainstein <Michael.Fainstein@ecitele.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: how to use native executable from one recipe during install in another recipe
Date: Thu, 11 Apr 2013 14:53:30 +0200	[thread overview]
Message-ID: <20130411145330.1dbee1c2@e6520eb> (raw)
In-Reply-To: <62673661A504604B856269DAADA8BC281DE35E00@ILPTWPVEXMB02.ecitele.com>

Hi Michael,

Le Thu, 11 Apr 2013 11:58:50 +0000,
Michael Fainstein <Michael.Fainstein@ecitele.com> a écrit :
> I have one recipe that inherits "native", builds native executable and installs it in tmp/work/x86_64-linux/foo-native-1.00-r0/image/sbin/foo
>
do you have BBCLASSEXTEND = "native" in this recipe ?

In the end, isn't the native binary installed in :
sysroots/x86_64-linux/usr/sbin/ ?

> Another recipe depends on first one and needs to execute foo in its do_install in order to install files in tmp/work/ppce500v2-fsl-linux-gnuspe/foo-1.00-r0/image/etc/
> 
> I can't find a way to do it. Any suggestions? How can I install foo in first recipe to some common location that 2nd recipe can use? Is there such standard location?
> 
You should then be able to call it in the other recipe as IIRC this path
is in $PATH (and your recipe should depend on foo-native)

Eric


  reply	other threads:[~2013-04-11 12:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-11 11:58 how to use native executable from one recipe during install in another recipe Michael Fainstein
2013-04-11 12:53 ` Eric Bénard [this message]
2013-04-11 14:54   ` Michael Fainstein
2013-04-11 20:37     ` Khem Raj

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=20130411145330.1dbee1c2@e6520eb \
    --to=eric@eukrea.com \
    --cc=Michael.Fainstein@ecitele.com \
    --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.