Difference between revisions of "Inspect DEPENDS"

From Openembedded.org
Jump to: navigation, search
m (FAQ/Depends moved to Inspect DEPENDS: remove FAQ namespace)
Line 8: Line 8:
  
 
   bitbake -g $packagename && less *.dot
 
   bitbake -g $packagename && less *.dot
 +
 +
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]]

Revision as of 03:57, 13 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 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.

Personal tools
Namespaces

Variants
Actions
Navigation
Categories
OE services
Toolbox