All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Summary of Toolchain/SDK session
Date: Wed, 11 Nov 2009 10:57:06 -0500	[thread overview]
Message-ID: <4AFADED2.8010708@balister.org> (raw)

Toolchain generation is currently a fragile process. Richard's staging 
changes should help resolve these issues.

There are several classes of developers:

1) Create recipes for existing software.
2) Modifying kernel config within OE.
3) People creating new software to run on machine that can not be tested 
on desktop.

Marco and Ken briefly presented their Eclipse based projects to help 
developers. Marco's is targeted at hiding OE from developers, Ken's 
provides help for people writing recipes. Ken has promised to write more 
on the eclipse plugin issues.

http://community.buglabs.net/kgilmer/posts/110-BitBake-Commander-6-8-Installers-

For SW developers (3) there is an Anjuta plugin:

http://labs.o-hand.com/anjuta-poky-sdk-plugin/

and you can do remote development on a Beagle with Netbeans:

http://mechomaniac.com/BeagleboardDevelopmentWithNetbeans

There was also discussion on making it easier to install OE/bitbake.

Conclusions:

1) Toolchain generation should improve after staging layout changes.
2) People are working on Eclipse plugins, this should be encouraged.
3) Need better documentation to setup Eclipse and CDT with OE toolchains.
4) Need to add a page linking to projects that are useful for people 
using OE.

Philip




                 reply	other threads:[~2009-11-11 15:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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