Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Wold, Saul" <saul.wold@intel.com>
To: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>,
	"richard.purdie@linuxfoundation.org"
	<richard.purdie@linuxfoundation.org>
Subject: Re: [PATCH v2] native.bbclass: populate native recipe with it's files
Date: Thu, 2 Mar 2017 23:37:44 +0000	[thread overview]
Message-ID: <1488497862.22952.145.camel@intel.com> (raw)
In-Reply-To: <1488497132-15876-1-git-send-email-sgw@linux.intel.com>


Drop this, apparently Richard already applied this and I was looking at
an older master branch when I sent this.

Sau!

On Thu, 2017-03-02 at 15:25 -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.
> 
> Signed-off-by: Saul Wold <sgw@linux.intel.com>
> ---
> v2: removed the "before do_build"
>  meta/classes/native.bbclass | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/meta/classes/native.bbclass
> b/meta/classes/native.bbclass
> index ec91fc3..6becf82 100644
> --- a/meta/classes/native.bbclass
> +++ b/meta/classes/native.bbclass
> @@ -174,6 +174,11 @@ python native_virtclass_handler () {
>  addhandler native_virtclass_handler
>  native_virtclass_handler[eventmask] = "bb.event.RecipePreFinalise"
>  
> +python do_addto_recipe_sysroot () {
> +    bb.build.exec_func("extend_recipe_sysroot", d)
> +}
> +addtask addto_recipe_sysroot after do_populate_sysroot
> +
>  inherit nopackages
>  
>  do_packagedata[stamp-extra-info] = ""
> -- 
> 2.7.4
> 

      reply	other threads:[~2017-03-02 23:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-02 23:25 [PATCH v2] native.bbclass: populate native recipe with it's files Saul Wold
2017-03-02 23:37 ` Wold, Saul [this message]

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=1488497862.22952.145.camel@intel.com \
    --to=saul.wold@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox