Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Getting started on creating a layer for OE-Core
Date: Thu, 24 Nov 2011 11:59:37 -0500	[thread overview]
Message-ID: <4ECE77F9.5090703@balister.org> (raw)
In-Reply-To: <4ECBE307.1080600@linaro.org>

On 11/22/2011 12:59 PM, Ken Werner wrote:
> Hi,
> 
> I'm currently reading the OpenEmbedded User Manual and wondering what's
> the best way to add a layer for the Linaro toolchain components (Linaro
> GCC, Linaro GDB). This is my first time with OE. I just setup the
> environment and started to build an image that targets qemuarm (bitbake
> is still building). Any suggestions or general help is much appreciated.

Can you comment on what you expect to get out of the Linaro toolchain layer?

As had been noted here, OE already has some of the Linaro work in the
toolchains. However, we have had issues with some patches so we can't
run a "complete Linaro toolchain". (Toolchain guys, correct me if I am
wrong)

From my perspective, the Linaro work is great (I primarily use Cortex-A8
devices), but my understanding is that due to Linaro's focus on advanced
ARM processors, regressions for other architectures and older arms can
occur.

So I see the point of a dedicated Linaro tool layer being an excellent
vehicle for testing Linaro's work on a diverse set of machines to make
life easier for people using Linaro's work on other architectures.

Philip



  parent reply	other threads:[~2011-11-24 17:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-22 17:59 Getting started on creating a layer for OE-Core Ken Werner
2011-11-22 18:02 ` Koen Kooi
2011-11-22 18:08   ` Paul Eggleton
2011-11-22 18:17     ` Koen Kooi
2011-11-22 18:21       ` Ken Werner
2011-11-22 18:15   ` Ken Werner
2011-11-24 16:59 ` Philip Balister [this message]
2011-11-24 17:18   ` Koen Kooi
2011-11-24 18:00   ` Khem Raj
2011-11-28 20:55   ` Ken Werner

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=4ECE77F9.5090703@balister.org \
    --to=philip@balister.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