All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OEDEM next weekend
Date: Wed, 04 Nov 2009 23:31:43 -0500	[thread overview]
Message-ID: <20091105043143.GA30116@denix.org> (raw)
In-Reply-To: <19c1b8a90911041641w4b7397d3o8a96853600d0cb4e@mail.gmail.com>

On Wed, Nov 04, 2009 at 04:41:29PM -0800, Khem Raj wrote:
> On Mon, Nov 2, 2009 at 2:58 PM, Richard Purdie <rpurdie@rpsys.net> wrote:
> > On Sun, 2009-11-01 at 11:24 -0500, Philip Balister wrote:
> >> This has been mentioned here before, but I want to remind people that
> >> OEDEM (Openembedded Developers European Meeting) is next weekend in
> >> Cambridge, UK. There is a information and an agenda at:
> >>
> >> http://wiki.openembedded.net/index.php/Oedem/2009
> >>
> >> Note that registration is closed, but you can talk to Phil in case there
> >> are last minute dropouts.
> >>
> >> If you can't make it, but have any ideas or comments, please talk to one
> >> of the attendees or send us in email so we can collect everyones ideas.
> >
> > I'd like to second this. If you can't be there but want a viewpoint
> > represented, please do talk to the attendees.
> >
> > I just added "BitBake Future Roadmap" and "OE Core Changes" to the
> > agenda and will happily takes ideas on those topics if anyone has any
> > proposals.
> >
> > Are there any topics anyone feels are missing from the agenda?
> 
> Support for plugging external toolchains

I started a somewhat generic framework for plugging different external 
toolchains - it uses some pieces and ideas from Poky, at this point is 
Angstrom specific and been tested mostly with CodeSourcery and very little 
with MontaVista Pro5. This framework comes from Arago, where the use of 
external toolchain is a default setup. And most of it was merged few weeks 
ago into Angstrom. I would be glad to work on taking it even further...

> Using SDK for building OE instead of internal toolchains.

AFAIK, the generic external-toolchain.bb recipe is specifically for this 
purpose and seems to work fine. What is missing - is a standard official 
pre-built SDK (per distro?) available for download. A la Poky SDK...

-- 
Denys



  reply	other threads:[~2009-11-05  4:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-01 16:24 OEDEM next weekend Philip Balister
2009-11-02 22:58 ` Richard Purdie
2009-11-05  0:41   ` Khem Raj
2009-11-05  4:31     ` Denys Dmytriyenko [this message]
2009-11-02 23:32 ` Phil Blundell
  -- strict thread matches above, loose matches on Subject: below --
2009-11-02  0:10 Graeme Gregory

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=20091105043143.GA30116@denix.org \
    --to=denis@denix.org \
    --cc=openembedded-devel@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 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.