On Friday, January 15, 2016 at 12:42:18 AM, Otavio Salvador wrote: > On Thu, Jan 14, 2016 at 7:41 PM, Marek Vasut <ma...@denx.de> wrote: > > On Thursday, January 14, 2016 at 10:37:16 PM, Otavio Salvador wrote: > >> On Thu, Jan 14, 2016 at 7:15 PM, Marek Vasut <ma...@denx.de> wrote: > >> ... > >> > >> > Taking a look at u-boot.inc and uboot-config.bbclass makes me wonder > >> > how all that could work at all. It's either a stackpile of legacy > >> > cruft or just poor design. > >> > >> I think it is a mix of both. > >> > >> How would you address this in a clean way? > > > > I would have one U-Boot build per package. Debian doesn't do it that way > > tho, so their rationale might be something to consider here too. > > This is what we do in uboot-config class, isn't it?
The class lacks documentation and is written in rather obscure way, so I am not sure about how the result is packaged, sorry. > Without going deep on the minor details, could you describe how you > think it should be done? Can you be more specific about this "it" ? What do you refer to ? Best regards, Marek Vasut -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
