Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Philip Balister <philip@balister.org>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: Splitting meta-oe
Date: Wed, 25 Jan 2012 14:47:43 +0000	[thread overview]
Message-ID: <1908796.glHMrEiIxU@helios> (raw)
In-Reply-To: <4F20130D.2010208@balister.org>

On Wednesday 25 January 2012 09:34:53 Philip Balister wrote:
> On 01/25/2012 07:48 AM, Paul Eggleton wrote:
> > I think what most people want when they enable meta-oe in their layer
> > configuration is #1, and it's probably OK to get #2 along with it. They do
> > not however expect versions of toolchains, eglibc or other fairly
> > fundamental bits and pieces that might cause their build to fail when
> > everything worked fine just building with OE-Core (#4). Equally I expect
> > there will be some people who want just #3 and nothing else.
> 
> My understanding is the OE-Core toolchains lack the Linaro patches which
> a extremely useful for people using armv7. So dropping toolchains from
> meta-oe would be a really bad thing for a large portion of the user base.

I was suggesting moving these toolchains to a separate layer where those who 
don't need them aren't tripping over them. Adding such a layer to your 
configuration is more or less trivial, and once done you would not notice any 
difference.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2012-01-25 17:16 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-25 12:48 Splitting meta-oe Paul Eggleton
2012-01-25 14:01 ` Frans Meulenbroeks
2012-01-25 14:10 ` Martin Jansa
2012-01-25 15:09   ` Paul Eggleton
2012-01-25 17:01     ` Enrico
2012-01-25 14:34 ` Philip Balister
2012-01-25 14:47   ` Paul Eggleton [this message]
2012-01-25 16:00     ` Philip Balister
2012-01-25 17:33       ` Frans Meulenbroeks
2012-01-25 17:51         ` Khem Raj
2012-01-26  9:02         ` Martin Jansa
2012-01-26 14:45           ` Frans Meulenbroeks
2012-01-26 16:11             ` Martin Jansa
2012-01-26 18:36               ` Andreas Oberritter
2012-01-26 20:04           ` Khem Raj
2012-01-25 17:41       ` Paul Eggleton
2012-01-25 17:57         ` Phil Blundell
     [not found]           ` <4F2069CC.7060409@balister.org>
2012-01-25 21:03             ` Phil Blundell
2012-01-25 22:12               ` Philip Balister
2012-01-25 17:49 ` Khem Raj
2012-01-25 18:39   ` Paul Eggleton
2012-01-25 23:28     ` Khem Raj
2012-02-01 10:07 ` Paul Eggleton
2012-02-01 10:33   ` Koen Kooi
2012-02-01 11:11     ` Otavio Salvador
2012-02-01 15:39       ` Koen Kooi
2012-02-05 14:58       ` Koen Kooi

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=1908796.glHMrEiIxU@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=philip@balister.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