Difference between revisions of "Inspect DEPENDS"

From Openembedded.org
Jump to: navigation, search
 
(One intermediate revision by one user not shown)
Line 1: Line 1:
'''How do do I inspect compile-time dependencies for packages?'''
+
'''How do do I inspect dependencies for recipes?'''
  
You want a "visual" output of the dependency tree for a particular package?
+
You can get the dependency graph information using:
  
   bitbake --dry-run --verbose $packagename | grep "current path" | less
+
   bitbake -g <packagename> && less task-depends.dot
  
should give you that information. Another way is the more recent
+
unfortunately the graph is large and many fot viewers will struggle with it. The "depexp" UI also provides a graphical way to view dependencies:
  
   bitbake -g $packagename && less *.dot
+
   bitbake -g <packagename> -u depexp
 
+
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''
+
  
 
[[Category:FAQ]]
 
[[Category:FAQ]]
 
[[Category:Debug build]]
 
[[Category:Debug build]]

Latest revision as of 14:16, 7 November 2012

How do do I inspect dependencies for recipes?

You can get the dependency graph information using:

 bitbake -g <packagename> && less task-depends.dot

unfortunately the graph is large and many fot viewers will struggle with it. The "depexp" UI also provides a graphical way to view dependencies:

 bitbake -g <packagename> -u depexp
Personal tools
Namespaces

Variants
Actions
Navigation
Categories
OE services
Toolbox