[yocto] Bitbaking a recipe often triggers a do_package_write_rpm of a dependant recipe... why?

[Torsten Sievers]

Hi guys,

Here is the situation:

I have two custom made recipes, one is a SDK , the other one is a set of
examples that use the sdk.

The examples recipe has DEPENDS and RDEPENDS set that point to artifacts
that are produced by the SDK recipe.

So far, so normal

Now the strange thing happens:

when I do

bitbake sdk

everything is fine, it configures,compiles,installs and eventually create a
rpm (by do_package_write_rpm)

when I run

bitbake examples

immediately after the finish of the bitbake sdk

it is compiling,installing etc the example rpm. However it is also very
often (but not always) re-triggering the do_package_write_rpm from the
SDK.  but why?

I double checked, the SDK code/recipe was not touched, and the SDK rpm was
sitting right there before I bitbaked the examples.


i am digging deep inside bitbake / yocto recipes for days but i cannot find
the rootcause...

Any hint what could cause this? I would not bother too much, but the
building of the SDK rpms takes roughly 10 minutes, thus significantly
slowing down my development iterations.

Any hints are highly appreciated...
BR
  Torsten
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20171005/08af1b67/attachment.html>