Please note that User Registration has been temporarily disabled due to a recent increase in automated registrations. If anyone needs an account, please request one here: RequestAccount. Thanks for your patience!

Difference between revisions of "Inspect DEPENDS"

From Openembedded.org
Jump to: navigation, search
Line 9: Line 9:
 
   bitbake -g $packagename && less *.dot
 
   bitbake -g $packagename && less *.dot
  
Then, installing for example debian package graphviz we can convet .dot file in .ps
+
Then, installing for example debian package graphviz we can convert .dot file in .ps
  
 
   dot -Tps task-depends.dot  -o task-depends.ps
 
   dot -Tps task-depends.dot  -o task-depends.ps
  
And then you can open the .ps file with gimp.
+
And then we 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.''  
 
''Be careful that a big package give a .dot and .os result that requires too much RAM, for example mplayer.''  

Revision as of 12:13, 14 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 convert .dot file in .ps

 dot -Tps task-depends.dot  -o task-depends.ps

And then we 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