[Buildroot] [PATCH next v4 6/6] core: implement per-package SDK and target
thomas.petazzoni at bootlin.com
Mon Nov 19 10:48:06 UTC 2018
On Sun, 18 Nov 2018 22:55:26 +0100, Arnout Vandecappelle wrote:
> > Yes, we got bitten pretty hard when preparing the kconfig infra. But
> > what can we remember from an almost-5-year old work initiated after
> > FOSDEM? ;-)
> >> The goal is that one can run 'make foo-menuconfig' from a clean tree,
> >> without first processing (downloading, building, ...) the dependencies
> >> of foo first.
> >> If you put this stuff in the configure step of foo, you are bound byi
> >> its dependencies. There may be other reasons too, not sure.
> > I am all in favour of simplifying it if it can be made simpler by adding
> > an official extra 'prepare' step, that exists for all types of package
> > infras. This we'd have 4 levels of dependencies:
> > 1- download dependencies
> > 2- extract dependencies
> > 3- prepare dependencies
> > 4- configure dependencies
> I think your mixing two things here. The "prepare" that ThomasP is talking
> about is really the PPD creation. The additional step for autoreconf or kconfig
> is something else - it's a step with commands that are defined by the package
I don't think Yann is mixing things here. Indeed we are using the word
"prepare" for two different things: preparing the PPD folder, and
"doing some stuff before the configure step".
For the PPD folder, some preparation currently occurs at the download
step (for download dependencies), some preparation occurs at the
extract step (for the extract dependencies) and some preparation occurs
at the configuration step (for the normal dependencies).
The issue with the kconfig infrastructure is that it creates a new type
of dependency called "kconfig dependency", which should be ready to do
all the kconfig-related activities, but that we want separate from the
normal "configure dependencies" because we want to be able to do "make
linux-menuconfig" or "make busybox-menuconfig" without having to wait
for their dependencies to build.
So what Yann is proposing is that instead of having this "kconfig
dependency" stuff be shoe-horned into the dependency chain by
pkg-kconfig.mk, we should promote it to a new step in the build steps.
By the lack of better naming, Yann named that step "prepare", but it
has nothing to do with "preparing PPD".
Indeed, what we would do is:
1. Download step
Prepare PPD with download dependencies
Do the normal download stuff
2. Extract step
Prepare PPD with extract dependencies
Do the normal extract stuff
3. Patch step
Prepare PPD with patch dependencies
Do the normal patch stuff
4. Prepare step
Prepare PPD with the prepare dependencies
Do the prepare stuff (i.e only the kconfig stuff for now)
5. Configure step
Prepare PPD with the normal dependencies
Do the normal configure stuff
Does that clarify Yann's proposal ?
I personally find it OK, even though it's a bit annoying to introduce
yet another step just for the sake of pkg-kconfig.
Also: I would not move autoreconf into this prepare step, but keep it
as it is today, within the configure step. I don't (today at least) see
the point/usefulness of moving the autoreconf into this prepare step.
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
More information about the buildroot