On Sun, Aug 10, 2014 at 08:22:35PM -0600, Simon Glass wrote:
Hi Tom,
On 8 August 2014 07:04, Tom Rini trini@ti.com wrote:
On Fri, Aug 01, 2014 at 12:48:44PM +0100, Simon Glass wrote:
Hi,
At present, as a work-around, we generate boards.cfg if needed. This is quite a slow process since each board config must be fully processed.
What can we do to improve this? We only need a small number of options in order to start buildman - things like CONFIG_SYS_ARCH, CONFIG_SYS_CPU, etc.
I wonder if we could run a script which adds these to the defconfigs for each board and then apply a patch to mainline? Would that require removing the options from the config.h files? Or could we do that later as a separate step?
I wonder (and I haven't had my coffee nor dug into this much more yet) about using say https://github.com/ulfalizer/Kconfiglib to have buildman parse all configs/ and then use that information to build what's been asked (depending on how long the reading+parsing takes). If it's relatively quick, that would be a big argument in favour of dropping MAKEALL.
Well I've had my wine but it seems to parse the Kconfig files rather than the #includes that are part of U-Boot's system. Unless I'm missing something, we would still need to find out things like the CPU type, even with that tool.
Well, my thought was: foreach Kconfig file, read to build state machine foreach defconfig, evaluate config, spl/config, tpl/config, store object
Now we can poke those objects for everything with CONFIG_SYS_CPU whatever, and so forth. Or maybe that all takes longer than what we do today.