Inspect DEPENDS: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
PaulEggleton (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
{{Outdated}} | |||
'''How do do I inspect compile-time dependencies for packages?''' | '''How do do I inspect compile-time dependencies for packages?''' | ||
Revision as of 16:39, 3 November 2012
| NOTE: This page has been identified as having content that is significantly out-of-date, usually because it refers to OpenEmbedded-Classic - for new projects, you should use OpenEmbedded-Core.
See OpenEmbedded Wiki Update Project for more details. |
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
If you have graphviz installed, you can convert the .dot file to PostScript (.ps).
dot -Tps task-depends.dot -o task-depends.ps
And then we can open the .ps file with gimp or evince, send it to the printer or whatever you usually do with these files.
Be careful that a complex package such as mplayer gives .dot and .ps files that will require too much RAM, so they can't actually be opened