On Tue, 2019-09-17 at 12:33 +0300, Dmitry Eremin-Solenikov wrote: > вт, 17 сент. 2019 г. в 01:17, Richard Purdie > <[email protected]>: > > On Fri, 2019-09-13 at 18:44 +0300, [email protected] wrote: > > > From: Dmitry Eremin-Solenikov <[email protected] > > > > > > > > > > Create new bbclass defining common variables for all UEFI-related > > > packages (bootloaders, test applications, etc). > > > > > > Signed-off-by: Dmitry Eremin-Solenikov < > > > [email protected]> > > > --- > > > meta/classes/uefi.bbclass | 26 ++++++++++++++++++++++++++ > > > 1 file changed, 26 insertions(+) > > > create mode 100644 meta/classes/uefi.bbclass > > > > I really want to get away from the proliferation of bbclass files > > we > > have. Wouldn't this make more sense as a .conf file? > > Moving configuration to .conf file might make sense. I even can > implement anonymous function as per-arch override. However there are > still functions like efi_populate_common() and > efi_iso_populate_common(), which can not be moved to .conf file. > > Would you prefer separate uefi.conf file and uefi-bootloader.bbclass > files
Would functions like this not be better suited to a lib/oe/efi.py ? Its really easy to just put everything in a bbclass but I'm not convinced its scaling well... Cheers, Richard -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
