[poky] Poky SDK as an external toolchain

[Mark Hatle]

On 10/14/11 9:44 AM, Gary Thomas wrote:
> Premise: I'm happy with the toolchain that builds with Poky/Yocto
> Problem: I'm not happy rebuilding said toolchain all the time, nor
> having my customers have to rebuild it.
> 
> Solution? I'd like to build the meta-toolchain and then be able to
> use that as an external toolchain for subsequent builds.  That way,
> I can create the tools and reuse them internally as well as pass
> them to my customers.
> 
> How can I make this happen?  The last time I tried anything like
> this, I spent many days in the attempt only to find out that it
> was never going to work...

We have a similar need for our commercial products.  We allow/enable our
customers to rebuild the toolchains (and use the results), but we only provide
official support for our binary versions.  There are simply too many variations
possible to try to support the toolchains in source format.  (Toolchains =
bintuils, gcc, stock eglibc and a stock uclibc configurations...)

Our intention is simply to create custom recipes that extract our binaries and
use them instead of doing a by-source build.  If there is an easier way that
would be nice.  (And I agree, using the results of the meta-toolchain build is
the right approach for anything standard.)

I'd suggest this get added as an enhancement request to the bugzilla.  We're
currently working on feature planning for 1.2 so this would be a good time to
add it into the bucket of possible work items.

--Mark

> Note: sstate is *not* the answer.  Not only is it HUGE (well over
> 1GB for a typical setup), but it doesn't work reliably - see
> bug #1536
> 
> Ideas/hints?
> 
> Thanks
>