[oe] site/* - using common files for site information

Jamie Lenehan lenehan at twibble.org
Fri Aug 25 08:22:11 UTC 2006


On Fri, Aug 25, 2006 at 09:08:09AM +0100, Richard Purdie wrote:
> On Fri, 2006-08-25 at 15:33 +1000, Jamie Lenehan wrote:
[...]
> > If no one has any comments on this then I guess I'll push it in.
> > First the info.bbclass, then clean up the few recipes that directly
> > mess with CONFIG_SITE,

I missed out the need to update autotools.bbclass once none of the
recipes directly mess with the CONFIG_SITE files.

> >then clean up the x86 files and the the few
> > recipes that I've been maintaining. 
> 
> For what its worth, I like the idea of this but haven't had time to

I changed my mind about a dozen times on this, so seeing what someone
else thinks would be good. 

> review the patches. The name info.bbclass is perhaps too generic though
> - could you call it something like autotools-info.bbclass?

The reason I called it info.bbclass is because it's not actually
related to autotools. What it does is provide information about a
target - endianess, 32/64 bit, which libc it's using, what alias
exists for it in a general sort of way.

The autotools.bbclass then makes use of this to decided which site
files to use.

I also made use of the info.bbclass to provide the endiness
information to recipes that were currently manaully looking in the
site file to determine this (since the way they currently work breaks
with the site file.)

-- 
 Jamie Lenehan <lenehan at twibble.org>




More information about the Openembedded-devel mailing list