[Buildroot] [PATCH next v4 6/6] core: implement per-package SDK and target

[Thomas Petazzoni <thomas.petazzoni@bootlin.com>]

Hello,

On Tue, 20 Nov 2018 11:29:00 +0100, Thomas Petazzoni wrote:

> >  Perhaps, though, we should have a more general strategy of a per-infra
> > definition of what the steps are, instead of having a fixed sequence of steps.
> > I.e., have a pattern that should be followed by an infra-specific step to make
> > sure things are done correctly. So, for the kconfig case we would have an extra
> > kconfig_fixup step (we already have the stamp file, but it's not a real step
> > with hooks and the KCONFIG_DEPENDENCIES were strapped on as an afterthought),
> > and for the autoreconf case we would have an extra autoreconf step (instead of a
> > hook).  
> 
> And so those "injected" steps should take care of preparing the
> per-package folder with whatever dependencies they need ?
> 
> This is probably something that can be done to fix the pkg-kconfig
> stuff without having to create a new "prepare" step in the generic
> infrastructure.

Just tried that and it works. It will be part of my v5, which I hope
to send either later today, worst case tomorrow. With this, I can run
"make linux-menuconfig" from a clean tree, and the KCONFIG_DEPENDENCIES
are properly copied to the linux per-package folder.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com