Re: Poky SDK as an external toolchain

[Richard Purdie <richard.purdie@linuxfoundation.org>]

On Fri, 2011-10-14 at 08:44 -0600, 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 used to have code for doing exactly what you describe. It was error
prone, buggy and a world of pain. I was very relived when we removed it.

We do have external toolchain support. You could use that as you would
for a toolchain shipped by CSL or similar.

> 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

sstate is the answer and we need to actually make it work for your use
cases. We need to look at the problems you're having and find ways to
address them. I know it has issues but there isn't anything
fundamentally wrong with what its doing, we just need to get the issues
addressed. I'll happily do what I can to help that (and have been trying
to already) if the issues are known about. This is the first time anyone
has mentioed the 1GB size problem of the toolchain for example...

Cheers,

Richard