On Tue, Nov 1, 2011 at 7:56 PM, Saul Wold <[email protected]> wrote: > Right I understood that part from before I think. But why can't you have > > IMAGE_CLASSES ?= "image_types" > > and then in the local.conf override that with > > IMAGE_CLASSES = "image_types_uboot" > > since image_types_uboot inherits image_types. > >> IMAGE_CLASSES += "image_types_uboot" and leave the other bit as is... > > I have to admit I like this a little better with the possible thought of > breaking up image_types a little more, keep more used ones in image_types, > but move lesser used ones to their on .bbclass > > Them IMAGE_CLASSES truly is a list of image_type classes.
I think this is best, let the user override IMAGE_CLASSES to (eventually) be able to add individual image_types_XYZ. Will send new patch. -M _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
