From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: how many ways can a recipe place content in its own ${STAGING_BINDIR_CROSS}?
Date: Tue, 07 Feb 2017 12:46:08 +0000 [thread overview]
Message-ID: <1486471568.24931.0.camel@linuxfoundation.org> (raw)
In-Reply-To: <alpine.LFD.2.20.1702070704440.10245@uk63952.mitel.com>
On Tue, 2017-02-07 at 07:21 -0500, Robert P. J. Day wrote:
> ok, that's easy enough, but let's look at "apr" now. if i look at
> what
> apr installs under its sysroot and specifically under the same
> usr/bin
> directory, i see:
>
> $ tree usr/bin
> usr/bin
> └── crossscripts
> └── apr-1-config
>
> so how did *that* script come to be under there? if i look at the
> apr_1.5.2.bb recipe, there's no manual installation of that script as
> there was with apache2. rather, there's all this:
Look at binconfig.bbclass which I'd bet apr inherits (although I didn't
actually look).
Cheers,
Richard
next prev parent reply other threads:[~2017-02-07 12:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 12:21 how many ways can a recipe place content in its own ${STAGING_BINDIR_CROSS}? Robert P. J. Day
2017-02-07 12:46 ` Richard Purdie [this message]
2017-02-07 12:47 ` Robert P. J. Day
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=1486471568.24931.0.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/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.