Difference between revisions of "Inspect DEPENDS"

From Openembedded.org
Jump to: navigation, search
(Undo revision 2183 by 93.144.17.199 (Talk))
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 the .ps file with gimp.
 +
 +
''Be careful that a big package give a .dot and .os result that requires too much RAM, for example mplayer.''
  
 
[[Category:FAQ]]
 
[[Category:FAQ]]
 
[[Category:Debug build]]
 
[[Category:Debug build]]

Revision as of 04:05, 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 the .ps file with gimp.

Be careful that a big package give a .dot and .os result that requires too much RAM, for example mplayer.

Personal tools
Namespaces

Variants
Actions
Navigation
Categories
OE services
Toolbox