All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patrick Ohly <patrick.ohly@intel.com>, Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] native.bbclass: populate native recipe with it's files
Date: Sun, 19 Feb 2017 10:47:01 -0800	[thread overview]
Message-ID: <1487530021.30548.22.camel@linuxfoundation.org> (raw)
In-Reply-To: <1487316357.13854.504.camel@intel.com>

On Fri, 2017-02-17 at 08:25 +0100, Patrick Ohly wrote:
> On Thu, 2017-02-16 at 15:46 -0800, Saul Wold wrote:
> > 
> > This allows a native package's recipe-sysroot-native to be
> > populated with
> > that packages native image files.  This in turns allows it to be
> > used by
> > scripts or other tools without creating un-necessary DEPENDS.
> > 
> > An example of this is systemtap-native and the crosstap script.
> The intended usage wasn't clear to me at first. I think it is
> something
> like "bitbake foobar-native" and then calling foobar's tools directly
> from tmp/work/*/foobar-native/*/recipe-sysroot-native (?).
> 
> If true, then any recipe intending to be used like that also needs to
> exclude itself from do_rm_work:
> RM_WORK_EXCLUDE += "${PN}"
> 
> Or perhaps more selectively exclude the RSS:
> RM_WORK_EXCLUDE_ITEMS += "recipe-sysroot-native" (is there a variable
> for this name?)

I've been idly wondering whether just excluding recipe-sysroot* from
rm_work might be useful since its mostly hardlinked files anyway and
likely doesn't cause too much of a space issue...

Cheers,

Richard


  reply	other threads:[~2017-02-19 18:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-16 23:46 [PATCH] native.bbclass: populate native recipe with it's files Saul Wold
2017-02-16 23:53 ` Richard Purdie
2017-02-17  0:15 ` Khem Raj
2017-02-17  7:25 ` Patrick Ohly
2017-02-19 18:47   ` Richard Purdie [this message]
2017-02-20 12:36     ` Patrick Ohly
  -- strict thread matches above, loose matches on Subject: below --
2017-02-20  5:40 Saul Wold

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=1487530021.30548.22.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=patrick.ohly@intel.com \
    --cc=sgw@linux.intel.com \
    /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.