From: Martin Jansa <martin.jansa@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] qemu.inc: depend on qemu-native only with runqemu DISTRO_FEATURE
Date: Fri, 12 Apr 2013 22:11:40 +0200 [thread overview]
Message-ID: <20130412201140.GV2477@jama> (raw)
In-Reply-To: <20130303005928.GA3285@jama>
[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]
On Sun, Mar 03, 2013 at 01:59:28AM +0100, Martin Jansa wrote:
> On Mon, Feb 04, 2013 at 12:18:24PM +0000, Richard Purdie wrote:
> > On Mon, 2013-02-04 at 10:57 +0100, Martin Jansa wrote:
> > > * qemu images are usefull even without qemu installed on build machine.
> > > Some people are building on one machine, but then downloading images
> > > somewhere else to test them.
> > > * use new "runqemu" DISTRO_FEATURE and BACKFILL it so the behavior stays
> > > the same, unless disabled by DISTRO_FEATURES_BACKFILL_CONSIDERED
> >
> > Using DISTRO_FEATURES for this is nasty since if you change this item,
> > the sstate cache is invalidated. Its really a build configuration level
> > thing, not a distro feature...
> >
> > So whilst I appreciate the reasoning for it, I don't think its the right
> > approach and we'll need to find another one.
>
> What about removing this completely and adding check in runqemu script
> to say that qemu-native wasn't built?
Or using IMAGETEST variable?
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2013-04-12 20:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 9:57 [PATCH] qemu.inc: depend on qemu-native only with runqemu DISTRO_FEATURE Martin Jansa
2013-02-04 12:18 ` Richard Purdie
2013-03-03 0:59 ` Martin Jansa
2013-04-12 20:11 ` Martin Jansa [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=20130412201140.GV2477@jama \
--to=martin.jansa@gmail.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.