All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org,
	richard.purdie@linuxfoundation.org
Subject: [PATCH] native.bbclass: populate native recipe with it's files
Date: Thu, 16 Feb 2017 15:46:01 -0800	[thread overview]
Message-ID: <1487288761-22432-1-git-send-email-sgw@linux.intel.com> (raw)

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>
---
 meta/classes/native.bbclass | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/meta/classes/native.bbclass b/meta/classes/native.bbclass
index ec91fc3..d9dfea7 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 before do_build
+
 inherit nopackages
 
 do_packagedata[stamp-extra-info] = ""
-- 
2.7.4



             reply	other threads:[~2017-02-16 23:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-16 23:46 Saul Wold [this message]
2017-02-16 23:53 ` [PATCH] native.bbclass: populate native recipe with it's files Richard Purdie
2017-02-17  0:15 ` Khem Raj
2017-02-17  7:25 ` Patrick Ohly
2017-02-19 18:47   ` Richard Purdie
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=1487288761-22432-1-git-send-email-sgw@linux.intel.com \
    --to=sgw@linux.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 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.