[oe] [PATCH][RFC] gcc: Restructure package creation.

Tom Rini tom_rini at mentor.com
Mon Feb 1 23:04:39 UTC 2010


On Mon, 2010-02-01 at 12:55 +0000, Phil Blundell wrote:
> On Sun, 2010-01-31 at 23:57 -0800, Khem Raj wrote:
> > Hi,
> > 
> > Inspired by a discussion with RP on IRC this patch does following.
> > 
> > * Package most of target libraries during gcc-cross recipes
> >   and not during gcc target recipe.
> > 
> > * Do not build and package libraries like libstdc++ and others
> >   twice (once during cross compile and then during target gcc compile)
> > 
> > More libraries that can be built in cross gcc recipe should be packaged
> > there. These changes can be done after this patch.
> > 
> > Comments ?
> 
> I think it might be better to unbundle the libraries from gcc{-cross}
> altogether, and put them in a new recipe called gcc-runtime or
> something.  Having them built as part of gcc-cross seems to cause a
> certain level of headache for people who are using external toolchains;
> this happens already with libgcc and libstdc++, and I suspect your patch
> will cause the same issues to start popping up with the other libraries.

Well, isn't that exposing problems that exist today, rather than adding
new ones (ie the problem is that an unexpected (OE-built) libfoo is
used) ?

> Or, even better, put the different language runtimes in separate recipes
> so that folks who want to use Fortran can build those libraries without
> everybody else needing to do so.

It would be a good idea, I think, to 'time' a few builds like this, to
see how much time we save not building libgfortran (and the java one
too) and how much time we do or don't save by building libstdc++ on its
own.

-- 
Tom Rini <tom_rini at mentor.com>
Mentor Graphics Corporation




More information about the Openembedded-devel mailing list