Difference between revisions of "Inspect DEPENDS"
From Openembedded.org
Line 15: | Line 15: | ||
And then we can open the .ps file with gimp. | And then we can open the .ps file with gimp. | ||
− | ''Be careful that a big package | + | ''Be careful that a big package gives .dot and .ps files that requires too much RAM, for example mplayer.'' |
[[Category:FAQ]] | [[Category:FAQ]] | ||
[[Category:Debug build]] | [[Category:Debug build]] |
Revision as of 12:14, 14 February 2010
How do do I inspect compile-time dependencies for packages?
You want a "visual" output of the dependency tree for a particular package?
bitbake --dry-run --verbose $packagename | grep "current path" | less
should give you that information. Another way is the more recent
bitbake -g $packagename && less *.dot
Then, installing for example debian package graphviz we can convert .dot file in .ps
dot -Tps task-depends.dot -o task-depends.ps
And then we can open the .ps file with gimp.
Be careful that a big package gives .dot and .ps files that requires too much RAM, for example mplayer.