From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 6/6] image.bbclass: Add support to build the SDK in parallel with the image
Date: Mon, 02 Jul 2012 21:12:33 +0100 [thread overview]
Message-ID: <1341259953.2886.29.camel@x121e.pbcl.net> (raw)
In-Reply-To: <28adf5fdb58c3409ec2dcc1a8dfffaaf2a8eab2b.1341032578.git.mark.hatle@windriver.com>
On Sat, 2012-06-30 at 00:07 -0500, Mark Hatle wrote:
> diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
> index 4f50376..7e41982 100644
> --- a/meta/classes/image.bbclass
> +++ b/meta/classes/image.bbclass
> @@ -3,6 +3,11 @@ inherit rootfs_${IMAGE_PKGTYPE}
> IMAGETEST ?= "dummy"
> inherit imagetest-${IMAGETEST}
>
> +inherit populate_sdk_base
This seems to haul a vast amount of stuff into image.bbclass. Is it
really necessary to have all that in there by default?
p.
next prev parent reply other threads:[~2012-07-02 20:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-30 5:07 [PATCH 0/6] Enable the ability to create an image matching SDK Mark Hatle
2012-06-30 5:07 ` [PATCH 1/6] Fix manual log file paths Mark Hatle
2012-06-30 5:07 ` [PATCH 2/6] populate_sdk.bbclass: Split into two parts Mark Hatle
2012-06-30 5:07 ` [PATCH 3/6] populate_sdk: Allow for attempt only packages in the SDK Mark Hatle
2012-06-30 5:07 ` [PATCH 4/6] populate_sdk_base.bbclass: Change to using task specific depends Mark Hatle
2012-06-30 5:07 ` [PATCH 5/6] populate_sdk: enable basic multilib support Mark Hatle
2012-06-30 5:07 ` [PATCH 6/6] image.bbclass: Add support to build the SDK in parallel with the image Mark Hatle
2012-07-02 19:44 ` Saul Wold
2012-07-02 19:49 ` Mark Hatle
2012-07-02 20:05 ` Saul Wold
2012-07-02 20:12 ` Phil Blundell [this message]
2012-07-02 20:32 ` Mark Hatle
2012-07-02 21:05 ` Phil Blundell
2012-07-02 21:37 ` Mark Hatle
2012-07-03 23:47 ` Saul Wold
2012-07-02 15:20 ` [PATCH 0/6 v2] Enable the ability to create an image matching SDK McClintock Matthew-B29882
2012-07-02 16:27 ` Mark Hatle
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=1341259953.2886.29.camel@x121e.pbcl.net \
--to=philb@gnu.org \
--cc=openembedded-core@lists.openembedded.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