On Monday, October 27, 2014 at 07:59:42 AM, Koen Kooi wrote: Hi!
sorry for the very late reply. > > So uh, what exactly would you propose then? Ask the BSPs to cater for the > > change ? I don't quite like that option, since it's like breaking an API > > (or similar interface, I'm not sure what the local equivalent of that > > would be). > > Personally, I'd try to keep the kernel_foo() methods the same since those > are very popular, a lot of BSPs append the configure one. So maybe > something like: > > kernel.bbclass: > do_configure > do_install > addtask > etc > inherit kernel-${KERNEL_IMAGETYPE.bbclass} > > kernel-${KERNEL_IMAGETYPE.bbclass} > do_install (overrides the one in kernel.bbclass) > > Someone more familiar with bbclass method (re)naming and scoping should > weigh in on the method override above, but I think it should work. I wonder, is it possible to inherit bbclass if it exists as a file and inherit nothing otherwise ? In case I do: inherit kernel-${@d.getVar("KERNEL_IMAGETYPE", True).lower()} I get a nasty spit from bitbake in case I'm building with zImage KERNEL_IMAGETYPE . The reason is obvious, the file kernel-zimage.bbclass doesn't exist. So I wonder if there's some easy way to check if the class actually exists. Best regards, Marek Vasut -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core