[yocto] Build toolchain only (crosstools substitute?)

[Paul Eggleton]

I'm pretty sure you can do that, yes.

Cheers,
Paul

On Tue, 03 May 2016 08:58:12 Michael Habibi wrote:
> If I needed to modify glibc or gcc build options (hypothetically speaking,
> to turn on profiling or debug), I assume I can do that with bbappends and
> the like?
> 
> Thanks Paul
> 
> On Mon, May 2, 2016 at 11:51 PM, Paul Eggleton <
> 
> paul.eggleton at linux.intel.com> wrote:
> > Hi Michael,
> > 
> > On Mon, 02 May 2016 16:38:16 Michael Habibi wrote:
> > > I have been a few months out of researching Yocto, so I'm having trouble
> > > caching it all back in (a lot to absorb!). Excuse me if this is answered
> > > clearly in the documentation (I glanced around and I know you can build
> > > relocatable toolchains, etc, but I suppose I'm asking more of a
> > > philosophical question).
> > > 
> > > I have long-term plans to change our distribution at work over from a
> > > custom distribution to one built by Yocto - but this is a few months to
> > > a
> > > year out.
> > > 
> > > In the mean time, we need a new toolchain simply to update our glibc and
> > > gcc packages. I understand that yocto 2.1 can build gcc 5.3 w/ glibc
> > > 2.23
> > > support. I was wondering if this would be considered an appropriate
> > > exercise to use the yocto framework to build solely a toolchain to be
> > 
> > used
> > 
> > > with a custom distribution (understanding that the custom distribution
> > > would have to be modified to source and use the new toolchain).
> > > 
> > > We typically use crosstools to generate the toolchain, but it is a bit
> > > outdated and only builds gcc 5.2 (which has some bugs that were fixed in
> > > 5.3). Essentially I want to use Yocto recipes as a substitute for
> > > crosstools-ng.
> > 
> > If you build (or download) our SDK that should give you what you need:
> > 
> > 
> > http://www.yoctoproject.org/docs/2.1/sdk-manual/sdk-manual.html#sdk-buildi
> > ng-an-sdk-installer
> > 
> > If it's just the toolchain you need you can ignore the bits about
> > the extensible SDK - the standard SDK is what you want. There's
> > some more explanatory stuff towards the top of that manual as well.
> > 
> > Cheers,
> > Paul
> > 
> > --
> > 
> > Paul Eggleton
> > Intel Open Source Technology Centre

-- 

Paul Eggleton
Intel Open Source Technology Centre