<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 3, 2016 at 8:53 AM, Trevor Woerner <span dir="ltr"><<a href="mailto:twoerner@gmail.com" target="_blank">twoerner@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Mon 2016-08-01 @ 03:08:36 PM, Burton, Ross wrote:<br>
</span><span class="">> On 1 August 2016 at 15:07, Bruce Ashfield <<a href="mailto:bruce.ashfield@gmail.com">bruce.ashfield@gmail.com</a>> wrote:<br>
><br>
> > Not a large dependency, but it does bring to mind the question if this<br>
> > could be conditional on the type of image being built ? via distro<br>
> > feature, some other mechanism ?<br>
> ><br>
><br>
> Exactly this: image building adds dependencies automatically based on what<br>
> is actually being used, so can the kernel do this too?<br>
<br>
</span>The way the build knows which image was built is to build the kernel then look<br>
in the output directory to see what extension was given to the artifact. iow,<br>
it only discovers the dependency partway through the build; it doesn't know<br>
the dependency when the build starts.<br>
<br>
Either bitbake will have to put together the kernel's config at the start of<br>
the build, then parse through it to try to determine which kernel will be<br>
built, or we need some sort of mechanism that allows us to add dependencies<br>
partway through a build, or we can add (yet another) build variable and hope<br>
people are able to keep it in sync.<br><br></blockquote><div><br></div><div>I'm on vacation for the next two weeks, so sorry for the slow reply. <br><br></div><div>Wouldn't something like PACKAGECONFIG work here ? Something automatic<br></div><div>is going to be complex (like you describe), but something like this would be an<br></div><div>easy way for a BSP (or other) layer to bbappend the kernel and add this as<br></div><div>a dependency.<br><br></div><div>... but then again, I suppose they could currently just bbappend the kernel recipe<br></div><div>and add it directly to the DEPENDS.<br></div><div><br></div><div>Bruce<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
...or we could just add lzop-native as a static dependency in the off-chance that<br>
it's needed.<br>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"</div>
</div></div>