From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: Task-base is big :(
Date: Thu, 13 Sep 2007 00:21:37 +0100 [thread overview]
Message-ID: <1189639297.6480.142.camel@localhost.localdomain> (raw)
In-Reply-To: <HOECLKEKOHLAMMGDLLBHGENPMDAA.skoroneos@digital-opsis.com>
On Wed, 2007-09-12 at 08:56 +0300, Stelios Koroneos wrote:
> As more people start to use OE and as these people would be mostly
> interested in "vertical" solutions (develop an app or add apps to an
> existing distro without having to rebuild everything) i think we need to
> have a closer look at the OE SDK vs build everything from scratch.
> Having a "standard" toolchain availiable (and the way to use it) for people
> that are not interested in developing distro's would IMHO provide additional
> "user friendliness" and make OE an even more attractive solution.
Poky has some partially developed ideas here. Have a look at:
http://pokylinux.org/autobuild/toolchain/2732/poky-0.0-snapshot-20070912-arm-toolchain.tar.bz2
and
http://pokylinux.org/autobuild/toolchain/2732/poky-0.0-snapshot-20070912-i586-toolchain.tar.bz2
These are two toolchains that can be used in two ways:
1. As an external SDK style standalone toolchain
2. When combined with a poky build it becomes a poor mans "packaged
staging" which removes the toolchain build time from the equation by
using this prebuilt toolchain + glibc package.
OE has half the needed functionality since meta-toolchain works the same
in OE as it does in Poky now and will generate tarballs like the above.
The missing link is a distro configuration to actually use such a
generated tarball in OE.
Whilst Poky doesn't package much in the way of libraries, they would be
straight forward to add just by adding the package names to the
appropriate tasks.
Cheers,
Richard
next prev parent reply other threads:[~2007-09-12 23:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-11 11:18 Task-base is big :( Marcin Juszkiewicz
2007-09-11 17:37 ` Leon Woestenberg
2007-09-11 19:27 ` Koen Kooi
2007-09-11 21:10 ` USE flags - why they won't work for OE Richard Purdie
2007-09-11 23:14 ` Leon Woestenberg
2007-09-12 5:55 ` Stelios Koroneos
2007-09-12 11:06 ` José Bernardo Bandos Rodrigues
2007-09-12 16:38 ` Darcy Watkins
2007-09-12 11:46 ` Leon Woestenberg
2007-09-12 21:35 ` Richard Purdie
2007-09-11 21:17 ` Task-base is big :( Richard Purdie
2007-09-11 22:22 ` Detlef Vollmann
2007-09-11 22:55 ` Leon Woestenberg
2007-09-12 5:56 ` Stelios Koroneos
2007-09-12 7:53 ` Graeme Gregory
2007-09-12 8:43 ` Koen Kooi
2007-09-12 12:02 ` Binary packages (was: Task-base is big :( ) Detlef Vollmann
2007-09-12 12:45 ` Task-base is big :( Detlef Vollmann
2007-09-12 23:21 ` Richard Purdie [this message]
2007-09-11 23:43 ` Dr. Michael Lauer
2007-09-12 6:04 ` Koen Kooi
2007-09-14 7:21 ` Splitting up bluez in a sane way, was " Koen Kooi
2007-09-14 9:22 ` Marcin Juszkiewicz
2007-09-14 9:44 ` Koen Kooi
2007-09-15 8:29 ` Koen Kooi
2007-09-15 12:31 ` Marcin Juszkiewicz
2007-09-15 12:59 ` Koen Kooi
2007-09-18 17:54 ` 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=1189639297.6480.142.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.