All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: "Kamble, Nitin A" <nitin.a.kamble@intel.com>
Cc: Poky <poky@lists.pokylinux.org>
Subject: Re: Using prebuilt toolchains
Date: Wed, 27 Oct 2010 17:06:53 -0600	[thread overview]
Message-ID: <4CC8B08D.10402@mlbassoc.com> (raw)
In-Reply-To: <8EA2C2C4116BF44AB370468FBF85A77701969CD2DE@orsmsx504.amr.corp.intel.com>

On 10/27/2010 03:58 PM, Kamble, Nitin A wrote:
> Hi Gary,
>   The tool chain is customized to work well for all the recipes. If you are going to build just one package a separate tool chain may work, but it's unlikely that a separate toolchain will work well for all the recipes.
>

That's not really what I'm looking for.  What I want is to build
the tools *once* and then reuse them, without having to rebuild
them every time I start a Poky build from scratch.  I'm happy using
the Poky "customized" tools, but I really dislike having to rebuild
them over and over again...  I also am really keen to deliver a Poky
setup to my customers which they can use to build their target systems.
They shouldn't have to be bothered with building the tools themselves.

> -----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
------------------------------------------------------------


  reply	other threads:[~2010-10-27 23:06 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 [this message]
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
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=4CC8B08D.10402@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=nitin.a.kamble@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.