From: Saul Wold <sgw@linux.intel.com>
To: Martin Ertsaas <mertsas@cisco.com>
Cc: Thomas Kristensen <thkriste@cisco.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] populate_sdk_base.bbclass: Make it possible to overrise the create_shar method of populate_sdk_base.
Date: Wed, 24 Oct 2012 08:51:50 -0700 [thread overview]
Message-ID: <50880E96.30307@linux.intel.com> (raw)
In-Reply-To: <1350627387-20385-1-git-send-email-mertsas@cisco.com>
On 10/18/2012 11:16 PM, Martin Ertsaas wrote:
> From: Thomas Kristensen <thkriste@cisco.com>
>
> If you wish to change the install/unpack method of the sdk, this can now be done by making
> your own create_shar method, and setting a SDK_PACKAGAING_FUNC variable to your
> new create_shar function.
>
> Signed-off-by: Thomas Kristensen <thkriste@cisco.com>
> ---
> meta/classes/populate_sdk_base.bbclass | 4 +++-
> 1 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/meta/classes/populate_sdk_base.bbclass b/meta/classes/populate_sdk_base.bbclass
> index 6eb6726..a914a2c 100644
> --- a/meta/classes/populate_sdk_base.bbclass
> +++ b/meta/classes/populate_sdk_base.bbclass
> @@ -24,6 +24,8 @@ PID = "${@os.getpid()}"
>
> EXCLUDE_FROM_WORLD = "1"
>
> +SDK_PACKAGING_FUNC ?= "create_shar"
> +
> python () {
> # If we don't do this we try and run the mapping hooks while parsing which is slow
> # bitbake should really provide something to let us know this...
> @@ -56,7 +58,7 @@ fakeroot python do_populate_sdk() {
>
> bb.build.exec_func("tar_sdk", d)
>
> - bb.build.exec_func("create_shar", d)
> + bb.build.exec_func(d.getVar("SDK_PACKAGING_FUNC", True), d)
> }
>
> fakeroot populate_sdk_image() {
>
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2012-10-24 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 6:16 [PATCH v2] populate_sdk_base.bbclass: Make it possible to overrise the create_shar method of populate_sdk_base Martin Ertsaas
2012-10-24 15:51 ` Saul Wold [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=50880E96.30307@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=mertsas@cisco.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=thkriste@cisco.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox