From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: tweaking insane.bbclass to handle MIPS SEAD-3?
Date: Fri, 19 Apr 2013 12:09:07 +0100 [thread overview]
Message-ID: <2375821.Mtker55D4M@helios> (raw)
In-Reply-To: <alpine.DEB.2.02.1304190647010.5423@oneiric>
On Friday 19 April 2013 06:53:59 Robert P. J. Day wrote:
> On Fri, 19 Apr 2013, Paul Eggleton wrote:
> > On Thursday 18 April 2013 13:14:51 Robert P. J. Day wrote:
> > > if one created a BSP for the MIPS SEAD-3, where would it go? i
> > >
> > > notice there's no current MIPS-related OE layer anywhere. i'm
> > > assuming http://layers.openembedded.org/layerindex/ is the
> > > canonical source these days for layer locations, yes? the only
> > > MIPS match one gets there is for the qemumips machine.
> >
> > I guess there isn't one yet, so if you'd like to create and publish
> > one, go for it. There's some info on how that should be done in the
> > OE layers FAQ:
> > http://www.openembedded.org/Layers_FAQ
>
> short note -- the wiki page "Creating a new Layer":
>
> http://www.openembedded.org/wiki/Creating_a_new_Layer
>
> seems out of date, in that the "Best practices" section refers to
> qt4.inc and the QT_SQL_DRIVER_FLAGS variable:
>
> "An example here would be the way Qt 4 database support plugins are
> configured - OE-core doesn't have MySQL or PostgreSQL, however meta-oe
> does, so meta-oe uses .bbappends to modify a variable
> QT_SQL_DRIVER_FLAGS to enable the appropriate plugins. This variable
> was added to qt4.inc in OE-core specifically to allow meta-oe to be
> able to control which plugins are built."
>
> i don't think so:
>
> $ git show 64c6887ca19d2ce52e538186c93163dddf68438f
> commit 64c6887ca19d2ce52e538186c93163dddf68438f
> Author: Paul Eggleton <paul.eggleton@linux.intel.com>
> Date: Wed Apr 10 15:57:59 2013 +0000
>
> qt4: remove bbappend content
>
> These changes to Qt's configuration need to be applied in distro layers,
> not in meta-oe.
>
> (We have to preserve the PRINC value to avoid PR going backwards.)
>
> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
>
> might want to pick a different example.
Ah yes, I looked at that recently and made a mental note to change it which I
then promptly forgot. It's fixed now (using the same example, but mentioning
where the appends should go), thanks for pointing this out.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2013-04-19 11:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 12:38 tweaking insane.bbclass to handle MIPS SEAD-3? Robert P. J. Day
2013-04-18 14:08 ` Mark Hatle
2013-04-18 14:25 ` Robert P. J. Day
2013-04-18 15:08 ` Mark Hatle
2013-04-18 15:44 ` Robert P. J. Day
2013-04-18 16:02 ` Mark Hatle
2013-04-18 16:07 ` Robert P. J. Day
2013-04-18 17:14 ` Robert P. J. Day
2013-04-19 9:36 ` Paul Eggleton
2013-04-19 10:53 ` Robert P. J. Day
2013-04-19 11:09 ` Paul Eggleton [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=2375821.Mtker55D4M@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rpjday@crashcourse.ca \
/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.