Bitbaking a recipe often triggers a do_package_write_rpm of a dependant recipe... why?

Bitbaking a recipe often triggers a do_package_write_rpm of a dependant recipe... why?

[Torsten Sievers]

[-- Attachment #1: Type: text/plain, Size: 1163 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 1589 bytes --]

Re: Bitbaking a recipe often triggers a do_package_write_rpm of a dependant recipe... why?

[Khem Raj]

On Thu, Oct 5, 2017 at 3:09 AM, Torsten Sievers
<torstensievers@googlemail.com> wrote:
> 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...

hard to know without seeing the code but you can try to dump the task
signatures for do_package_write_rpm task from sdk recipe or use
bitbake-diffsigs tool to compute the differencs between two runs of
this task which
can give some insights into the task variable dependencies which might be
in play

> BR
>   Torsten
>
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>