Re: ugly OE issue with RDEPENDS

[Koen Kooi <k.kooi@student.utwente.nl>]

On 31-03-09 14:48, Robert Schuster wrote:
> Hi,
> I have this specific issue with with RDEPENDS and no idea how to solve
> it. It affects my Java recipes but in theory it can happen to any other
> recipes too. It is nothing Java specific. The unwanted effect is that OE
> builds to much and as such slows down the time to build a specific
> package considerably.
>
> Ok here is how it goes:
>
> I want to build recipe jamvm (application). This in turn needs recipe
> classpath. classpath puts a lot of useful things into staging which is
> needed by the jamvm build. So far so good.
>
> The problem is. classpath's tar.gz also contains some Java applications
> (the well known jar, javah and so). Via PACKAGE variable I place those
> into the binary package classpath-tools. To make everything as smooth as
> possible for the user I furthermore declare:
>
> RDEPENDS_classpath-tools = "java2-runtime". This means: For this package
> to work correctly a Java runtime needs to be installed. OE in turn
> demands that this java2-runtime dependency is also satisfied during the
> build.
>
> The odd thing that happens here is: jamvm (which I want to build) is a
> provider for java2-runtime but this does not interest OE and it builds
> another provider for java2-runtime instead. In my case this is
> openjdk-6, a recipe takes a very long time to built.

The real issue is that you RDEPEND on a virtual package, but you're not 
giving OE enough info to resolve the virtual to a real provider. I 
suppose you want bitbake to (reverse) check the build target for any 
virtuals it might provide, right?

regards,

Koen