Re: "all" architecture packages

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

On Tue, 2011-05-31 at 14:26 +0200, Koen Kooi wrote:
> Op 31 mei 2011, om 14:15 heeft Richard Purdie het volgende geschreven:
> 
> > Hi,
> > 
> > There have been various comments on the list and in the bugzilla about
> > issues with "all" architecture recipes.
> > 
> > To start cleaning this up I've merged:
> > 
> > http://git.openembedded.net/cgit.cgi/openembedded-core/commit/?id=26e5e5feb695864b11e47e24017e254c28f14494
> > 
> > which creates an "allarch" class and starts to convert some recipes over
> > to using it. There is further information in the commit message. Use of
> > the class ensures the packages really are suitable for all architectures
> > and that the sstate packages are reusable.
> > 
> > The list of packages which still need attention are:
> > 
> > meta/recipes-connectivity/resolvconf/resolvconf_1.48.bb                 
> > meta/recipes-devtools/update-alternatives/update-alternatives-dpkg.inc  
> > meta/recipes-gnome/gnome/gnome-common_2.28.0.bb                         
> > meta/recipes-gnome/gnome/gnome-icon-theme_2.31.0.bb                     
> > meta/recipes-gnome/hicolor-icon-theme/hicolor-icon-theme_0.12.bb        
> > meta/recipes-graphics/ttf-fonts/liberation-fonts_1.04.bb                
> > meta/recipes-graphics/ttf-fonts/liberation-fonts_1.06.bb                
> > meta/recipes-graphics/ttf-fonts/ttf-bitstream-vera_1.10.bb              
> > meta/recipes-graphics/xcursor-transparent-theme/xcursor-transparent-theme_0.1.1.bb
> > meta/recipes-graphics/xorg-font/encodings_1.0.4.bb                      
> > meta/recipes-graphics/xorg-font/font-alias_1.0.3.bb                     
> > meta/recipes-graphics/xorg-font/font-util_1.2.0.bb                      
> > meta/recipes-graphics/xorg-font/xorg-font-common.inc                    
> > meta/recipes-graphics/xorg-font/xorg-minimal-fonts.bb                   
> > meta/recipes-kernel/linux-firmware/linux-firmware_git.bb                
> > meta/recipes-sato/sato-icon-theme/sato-icon-theme.inc                   
> > meta/recipes-sato/sato-icon-theme/sato-icon-theme_0.4.1.bb              
> > meta/recipes-support/hal/hal-info.inc                                   
> > 
> > Some of these are easy, some trigger configure tests for the cross
> > compiler and are harder to fix.
> > 
> > If a package can't use allarch.bbclass, its a strong indicator it
> > shouldn't be PACKAGE_ARCH = "all"...
> 
> What about recipes that have an arch component and noarch config files
> split out? A made-up example would be udev and udev-rules. Is it still
> possible to do PACKAGE_ARCH_udev-rules = "all" in the udev recipe?

Those continue to work as before, the recipe is built as target/machine
specific with "all" shared components that overwrite each other.

I'm not 100% sure what value marking them as "all" has mind...

Cheers,

Richard