Difference between revisions of "Inspect DEPENDS"

From Openembedded.org
Jump to: navigation, search
m (follow rename)
 
(11 intermediate revisions by 5 users 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 dot viewers will struggle with it. The "taskexp" UI also provides a graphical way to view dependencies:
  
   bitbake -g $packagename && less *.dot
+
   bitbake -g <packagename> -u taskexp
 
 
Then, installing for example debian package graphviz we can convet .dot file in .ps
 
 
 
dot -Tps task-depends.dot  -o task-depends.ps
 
 
 
And then you can open it with gimp.
 
 
 
!Be careful that big package give a .dot and .os result that require too much RAM, for example mplayer.
 
 
 
 
  
 
[[Category:FAQ]]
 
[[Category:FAQ]]
 
[[Category:Debug build]]
 
[[Category:Debug build]]

Latest revision as of 20:01, 17 April 2018

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 dot viewers will struggle with it. The "taskexp" UI also provides a graphical way to view dependencies:

 bitbake -g <packagename> -u taskexp