[Openembedded-architecture] Yocto Compatible 2.0 + signature changes

Joshua Watt jpewhacker at gmail.com
Fri May 12 13:20:21 UTC 2017


> That would lead to a combinatorial explosion of potential paths that
> would need to be checked when deciding whether to reparse, because the
> actual file path most likely uses one or a few of the many overrides in
> OVERRIDES. It's probably doable, just something to be aware of.

Ya, come to think of it, something like (where "foo" is in OVERRIDES):

 BBAPPENDPATHS_foo += "${LAYERDIR}/foo/recipes-*/*/*.bbappend"

might be better for that reason. It would move the exponential search
into bitbakes variable cache in memory instead of having to search the
disk

>
> The same caveat as for the conditional include applies: only overrides
> set in the base configuration can be used, and they must be the same for
> all configurations in a multiconfig build.

I'm not too familiar with mutliconfig, but that does seems like it
would need to be solved... does this stem from all of them sharing a
bblayer.conf, and hence everyone currently gets the same BBPATH?. It
seems like allowing config specific BBPATHS (or BBAPPENDPATHS) might
be able solve that problem? That might even be a more targeted
solution to the problem that trying to solve it for conditional
includes.

Joshua Watt



More information about the Openembedded-architecture mailing list