On Mon 2016-08-01 @ 03:08:36 PM, Burton, Ross wrote: > On 1 August 2016 at 15:07, Bruce Ashfield <bruce.ashfi...@gmail.com> wrote: > > > Not a large dependency, but it does bring to mind the question if this > > could be conditional on the type of image being built ? via distro > > feature, some other mechanism ? > > > > Exactly this: image building adds dependencies automatically based on what > is actually being used, so can the kernel do this too?
The way the build knows which image was built is to build the kernel then look in the output directory to see what extension was given to the artifact. iow, it only discovers the dependency partway through the build; it doesn't know the dependency when the build starts. Either bitbake will have to put together the kernel's config at the start of the build, then parse through it to try to determine which kernel will be built, or we need some sort of mechanism that allows us to add dependencies partway through a build, or we can add (yet another) build variable and hope people are able to keep it in sync. ...or we could just add lzop-native as a static dependency in the off-chance that it's needed. -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core