From: Gary Thomas <gary@mlbassoc.com>
To: "Ke, Liping" <liping.ke@intel.com>
Cc: Poky <poky@lists.pokylinux.org>
Subject: Re: Using prebuilt toolchains
Date: Thu, 28 Oct 2010 05:34:05 -0600 [thread overview]
Message-ID: <4CC95FAD.9050801@mlbassoc.com> (raw)
In-Reply-To: <789F9655DD1B8F43B48D77C5D30659732FC45129@shsmsx501.ccr.corp.intel.com>
On 10/27/2010 08:35 PM, Ke, Liping wrote:
> Hi, Gary
>
> Seems I misunderstand something. Seems what you want is about how to
> create a recipe which could reuse you pre-build images and save build
> time.
>
> But anyway, for normal application developers, providing an easy-to-use
> sdk-toolchain tarball is helpful. In theory, they have no needs to build
> the whole poky system by themselves.
Sadly, that's what they insist on :-(
Mostly my customers want to be able to [re]build exactly what's in their
embedded environment, typically from scratch. Poky does this great, but
the overhead of rebuilding the toolchain is a huge portion of the effort.
As for Kevin's comment:
>
> On the other hand, I think the new checksum and task based prebuilt can serve similar
> purpose for you... or even more since your users should be happier if you could provide more
> prebuilt stuff to them besides just toolchain. This is the merit of this project, to have end
> user really focusing on their own customization and value-added bits. :-)
>
This would be great and I've been working with Richard on it for a long time.
Sadly, it still doesn't work correctly and provides no benefit in its current
state.
... I keep using Poky (at the very bleeding edge) and hoping :-)
>>>> -----Original Message-----
>>>> From: poky-bounces@pokylinux.org [mailto:poky-bounces@pokylinux.org]
>>> On Behalf Of Gary Thomas
>>>> Sent: Wednesday, October 27, 2010 2:33 PM
>>>> To: Poky
>>>> Subject: [poky] Using prebuilt toolchains
>>>>
>>>> Congratulations on Laverne (4.0) and Yocto - I hope they are
>>>> prosperous for all :-)
>>>>
>>>> Is there any way to configure Poky (laverne) with a prebuilt
>>>> toolchain, e.g. a meta-toolchain setup? I no longer see any
>>>> mention of this in the manual (although I've never succeeded
>>>> to use such, no matter how hard I've tried)
>>>>
>>>
>>> --
>>> ------------------------------------------------------------
>>> Gary Thomas | Consulting for the
>>> MLB Associates | Embedded world
>>> ------------------------------------------------------------
>>> _______________________________________________
>>> poky mailing list
>>> poky@pokylinux.org
>>> https://lists.pokylinux.org/listinfo/poky
>> _______________________________________________
>> poky mailing list
>> poky@pokylinux.org
>> https://lists.pokylinux.org/listinfo/poky
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2010-10-28 11:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 21:33 Using prebuilt toolchains Gary Thomas
2010-10-27 21:58 ` Kamble, Nitin A
2010-10-27 23:06 ` Gary Thomas
2010-10-28 1:07 ` Tian, Kevin
2010-10-28 2:16 ` Ke, Liping
2010-10-28 2:35 ` Ke, Liping
2010-10-28 11:34 ` Gary Thomas [this message]
2010-10-28 12:54 ` Tian, Kevin
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=4CC95FAD.9050801@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=liping.ke@intel.com \
--cc=poky@lists.pokylinux.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.