* Task dependencies
@ 2017-04-13 7:34 Gary Thomas
2017-04-13 9:24 ` Gary Thomas
0 siblings, 1 reply; 3+ messages in thread
From: Gary Thomas @ 2017-04-13 7:34 UTC (permalink / raw)
To: yocto
I'm trying to understand why 'perl' is being built for my target
even though I don't mention it in any of the package recipes used
to build that target. When I used 'taskexp', I found that 'perl:do_build'
only has a single dependent task, namely 'my-image:do_build'
note: no perl packages end up in my image.
This is just one example where it seems bitbake is doing a lot of
unnecessary (certainly un-asked-for) work.
How can I unravel this mystery?
Thanks for any pointers
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Task dependencies
2017-04-13 7:34 Task dependencies Gary Thomas
@ 2017-04-13 9:24 ` Gary Thomas
2017-04-18 20:12 ` robert.berger@gmane
0 siblings, 1 reply; 3+ messages in thread
From: Gary Thomas @ 2017-04-13 9:24 UTC (permalink / raw)
To: yocto
On 2017-04-13 09:34, Gary Thomas wrote:
> I'm trying to understand why 'perl' is being built for my target
> even though I don't mention it in any of the package recipes used
> to build that target. When I used 'taskexp', I found that 'perl:do_build'
> only has a single dependent task, namely 'my-image:do_build'
> note: no perl packages end up in my image.
>
> This is just one example where it seems bitbake is doing a lot of
> unnecessary (certainly un-asked-for) work.
>
> How can I unravel this mystery?
>
> Thanks for any pointers
>
I think I've figured this out - my image includes a couple of
packages (i2c-tools, ntp) that each have some component that
needs perl although I don't install those components. So it
now makes sense that perl has to be built for my target even
though I'm not actually using it.
For example, in i2c-tools I see
RDEPENDS_${PN}-misc = "${PN} perl"
and since I don't actually install i2c-tools-misc, perl isn't
needed.
That said, I had to discover this by manually looking through the
task-depends.dot file as I did not see how to come up with this
answer using -u taskdep alone.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Task dependencies
2017-04-13 9:24 ` Gary Thomas
@ 2017-04-18 20:12 ` robert.berger@gmane
0 siblings, 0 replies; 3+ messages in thread
From: robert.berger@gmane @ 2017-04-18 20:12 UTC (permalink / raw)
To: yocto
Hi,
On 2017-04-13 11:24, Gary Thomas wrote:
> On 2017-04-13 09:34, Gary Thomas wrote:
>> I'm trying to understand why 'perl' is being built for my target
>> even though I don't mention it in any of the package recipes used
>> to build that target. When I used 'taskexp', I found that
>> 'perl:do_build'
>> only has a single dependent task, namely 'my-image:do_build'
>> note: no perl packages end up in my image.
>>
>> This is just one example where it seems bitbake is doing a lot of
>> unnecessary (certainly un-asked-for) work.
>>
>> How can I unravel this mystery?
>>
>> Thanks for any pointers
Did you have a look at the dependency explorer?
bitbake -g -u depexp core-image-sato-sdk
There you see also reverse dependencies (who depends e.g. on perl)
Regards,
Robert
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-04-18 20:28 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-04-13 7:34 Task dependencies Gary Thomas
2017-04-13 9:24 ` Gary Thomas
2017-04-18 20:12 ` robert.berger@gmane
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.