[oe] bitbake dependency question

[Khem Raj]

On Tue, Dec 13, 2016 at 3:39 PM, Robert Cagle
<rcagle at omnitron-systems.com> wrote:
> Hi Paul,
> Thanks for the response.
>
>> Another way to handle this kind of situation with plugins is to simply build
>> them all with all dependencies, and have the runtime design such that it's
>> fully flexible as to which plugins are installed - then you just make the
>> choice in the image. (Perhaps what you're building is already that way and
>> you're just trying to save on build time?)
>
> Unfortunately in this particular case it is more of a "compile-time plugin". RecipeD
> generates and compiles a C file based on artifacts left in /usr/share by its
> dependencies (Recipes A, B, and/or C), so runtime configuration isn't an option.
> In this case including unused plugins would cause incorrect results.

you can insert the DEPENDS from distribution layer via a bbappend into recipe
of packageD and ensure that plugin packages install the needed spec files during
do_install so they get staged into staging sysroot before packageD
starts to configure
itself. you might even use PACKAGECONFIG to control it.

>
> It appears this form of dependency isn't supported in OE, so I'll either use a
> variable defined in local.conf or more likely restructure the app so the plugins
> and their host are all built within a single recipe/build.
>
> Thanks for the info though, it is all very interesting.
>
>> Cheers,
>> Paul
>>
>> --
>>
>> Paul Eggleton
>> Intel Open Source Technology Centre
>
> -Bob
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel