From: Martin Jansa <martin.jansa@gmail.com>
To: Paul Barker <paul@paulbarker.me.uk>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-devel@lists.openembedded.org,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [RFC] Layers, PRINC and bbappends
Date: Wed, 22 May 2013 11:17:38 +0200 [thread overview]
Message-ID: <20130522091738.GH32431@jama> (raw)
In-Reply-To: <CANyK_8cbVGMQkD7_KEd5KYTBxP+ZT5jY6VVVpdSAv_uY7JPY1w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1586 bytes --]
On Wed, May 22, 2013 at 09:47:39AM +0100, Paul Barker wrote:
> On 16 May 2013 00:02, Paul Barker <paul@paulbarker.me.uk> wrote:
> > On 15 May 2013 21:33, Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> >
> >>
> >> (e.g. when I include
> >> meta-raspberrypi, it changes the psplash logo, regardless of whether I'm
> >> building for the pi).
> >>
> >> In many ways the bbappend is too easy and encourages anti-social
> >> behaviour. I would recommend bouncing meta-rpi as being non yocto
> >> project compatible due to the psplash issue if it were to apply which it
> >> has not.
> >>
> >
> > I noticed the psplash logo when building a qemu image with
> > meta-raspberrypi included, will look into fixing it so it only goes
> > into MACHINE="raspberrypi" builds. Copying in yocto@ and Andrei as
> > this is raspberrypi related.
> >
>
> I've just sent a patch to the yocto@ list to fix this but it's brought
> up two things:
>
> 1) In openembedded-core/meta/classes/image.bbclass SPLASH is set with
> '?='. I'm overriding this with '=' in
> meta-raspberrypi/conf/machine/raspberrypi.conf which means it can't be
> overridden further in local.conf. Is this worth changing to '??=' in
> image.bbclass, '?=' in the machine conf so that it can be overridden
> with '=' in local.conf? Is my understanding of the overrides correct
> here?
You can still use:
SPLASH_forcevariable = "foo"
SPLASH_your-distro = "foo"
SPLASH_your-machine = "foo"
or any other OVERRIDE in local.conf.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-05-22 9:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 7:36 [RFC] Layers, PRINC and bbappends Koen Kooi
2013-05-15 14:44 ` Paul Eggleton
2013-05-16 6:31 ` Koen Kooi
2013-05-16 8:29 ` Paul Eggleton
2013-05-16 8:59 ` [OE-core] " Martin Jansa
2013-05-16 9:10 ` Paul Eggleton
2013-05-16 9:29 ` Martin Jansa
2013-05-16 20:15 ` Richard Purdie
2013-05-15 20:33 ` Richard Purdie
2013-05-15 23:02 ` Paul Barker
2013-05-22 8:47 ` Paul Barker
2013-05-22 9:17 ` Martin Jansa [this message]
2013-05-22 10:08 ` [OE-core] " Paul Eggleton
[not found] ` <1369217654.6695.62.camel@phil-desktop.brightsign>
2013-05-23 2:50 ` Chris Larson
2013-05-27 12:07 ` Paul Barker
2013-05-16 6:23 ` Koen Kooi
2013-05-16 8:37 ` Paul Eggleton
2013-05-16 9:27 ` Martin Jansa
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=20130522091738.GH32431@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paul@paulbarker.me.uk \
--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