[OE-core] packageA rdepends on packageB but it isn't a build dependency warnings

[Andreas Oberritter]

Hi André,

On Wed, 27 Nov 2019 12:56:43 +0000
André Draszik <git at andred.net> wrote:

> I am getting above QA warnings for some packages. Simple example - a recipe
> packageA with a shell script that calls out to certain other command line
> utilities from packageB.
> 
> Given packageA is only a shell script, it ought to be enough to simply add
> an RDEPENDS on packageB in that recipe. But when I do that, most of the time
> (not always it appears, though!) I get the warning from the subject of this
> email.
> I have even seen the generated IPK package to not have an entry for the runtime
> dependency. Again, sometimes, not always.
> 
> Is it really necessary in this case to add a DEPENDS, or is there some flag
> that can be set or something? I didn't find anything after a quick search...

in general, it should work with just RDEPENDS_${package}, if package is listed
in PACKAGES statically. If you build the list of PACKAGES dynamically, e.g.
with do_split_packages or anonymous python, then you'll need to add explicit
entries in DEPENDS.

Best regards,
Andreas