Hi Jean-Michel,
On 06/30/2015 05:56 PM, Jean-Michel Hautbois wrote:
Hi all,
2015-06-30 16:40 GMT+02:00 Nikolay Dimitrov <[email protected]>:
Hi Jean-Michel,
Are you sure that core-image-base is actually adding the unneeded
dependency? I don't see gpu-viv-bin-mx6q being built as part of this
image.
Well, no, I am not sure, but I must say it is a bit difficult to know
exactly who is adding what...
Well, there's a way to tell precisely who's pulling which dependency.
This command generates a dependency graph (I think Daiane/Gary already
mentioned this):
bitbake -g your-custom-image
This will create several text files, and one of them is pn-depends.dot,
where you can search for dependencies ("->" means "depends on"). Hope
this info makes your experience a little bit more scientific and less
empirical :D.
Also, Daiane mentioned blacklisting the package. I think this could be
useful, because when some package pulls-in the blacklisted dependency,
bitbake will print the exact dependency route across the graph and will
stop with error.
In my machine, I have conf/machine/include/imx-base.inc included,
which could lead to this behaviour... maybe...
Can you please check whether some of your added components doesn't
actually pull-in the gpu-viv-bin-mx6q?
Regards,
Nikolay
--
_______________________________________________
meta-freescale mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-freescale
