[oe] openembedded / dpkg-buildpackage hybrid
esbenhaabendal at gmail.com
Wed Nov 24 10:52:40 CET 2010
Chris Larson <clarson at kergoth.com> writes:
> ... Right now the OE sysroot (where files are shared
> between dependencies) is global, rather than per-recipe, and if
> multiple versions of something get yanked into a build, they'll step
> all over one another in that sysroot. We've discussed possibly moving
> to per-recipe sysroots in the past, constructing them on demand based
> upon what that recipe requires, but we're not there yet, ...
If I may be so bold, why is OE not going in that direction full speed?
We seem to (at best) to be on a very long detour...
It "just" requires rethinking that way DEPENDS is handled, which will
end up being much more like RDEPENDS is done now. A recipe depends on a
number of "items". Items are provided by packages, and packages can
(recursively) depend on other items. When constructing the runqueue,
the task that sets the stage depends on the task that packages stage
packages on all recipes that provides any of the (recursively) needed
Looking at build dependencies just makes so much more sense IMHO, and a
lot of issues that OE has/is fighting goes away. No more race
situations with a common stage dir, and no more problems with -initial,
-intermediate recipes. It even opens up for more flexible build
dependency handling, but that is another side of it.
For anyone interested, I have something like the above (based on OE) at
The entire runqueue code is rewritten from scratch, using an in-memory
sqlite database, but the concept could just as well be done based on a
truckload of Python dicts and lists, if this is more to ones liking ;-)
The interesting code with regards to this subject is in lib/oelite
It uses standard bitbake, but OE classes are heavily modified, and a
number of basic OE features are completely missing (but this is not
related to the per-receipe style staging).
So have a look if you like, or just skip it as it cannot easily be merged into
OpenEmbedded as it is now.
More information about the Openembedded-devel