Inspect DEPENDS - Revision history

Florian: follow rename

2018-04-17T20:01:24Z

follow rename

← Older revision		Revision as of 20:01, 17 April 2018
Line 5:		Line 5:
	bitbake -g <packagename> && less task-depends.dot		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:		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 ~~depexp~~		bitbake -g <packagename> -u taskexp

	[[Category:FAQ]]		[[Category:FAQ]]
	[[Category:Debug build]]		[[Category:Debug build]]

2012-11-07T14:16:40Z

← Older revision		Revision as of 14:16, 7 November 2012
Line 1:		Line 1:
	~~{{Outdated}}~~		'''How do do I inspect dependencies for recipes?'''

	~~'''How do do I inspect compile-time dependencies for packages?'''~~		You can get the dependency graph information using:

	~~You want a "visual" output of the dependency tree for a particular package?~~		bitbake -g <packagename> && less task-depends.dot

	~~bitbake --dry-run --verbose $packagename \| grep~~ "~~current path~~" ~~\| less~~		unfortunately the graph is large and many fot viewers will struggle with it. The "depexp" UI also provides a graphical way to view dependencies:

	~~should give you that information. Another way is the more recent~~		bitbake -g <packagename> -u depexp

	bitbake -g $packagename ~~&& less *.dot~~

	~~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]]

2012-11-03T16:39:52Z

← Older revision		Revision as of 16:39, 3 November 2012
Line 1:		Line 1:
			{{Outdated}}

	'''How do do I inspect compile-time dependencies for packages?'''		'''How do do I inspect compile-time dependencies for packages?'''

2010-02-18T13:24:52Z

← Older revision		Revision as of 13:24, 18 February 2010
Line 9:		Line 9:
	bitbake -g $packagename && less *.dot		bitbake -g $packagename && less *.dot

	~~Then~~, ~~installing for example debian package graphviz we~~ can convert .dot file in .ps		If you have graphviz installed, you can convert the .dot file to PostScript (.ps).

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

	And then we can open the .ps file with gimp.		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 ~~big~~ package gives .dot and .ps files that ~~requires~~ too much RAM, ~~for example mplayer.~~''		''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]]

2010-02-14T12:14:41Z

← Older revision		Revision as of 12:14, 14 February 2010
Line 15:		Line 15:
	And then we 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 gives .dot and .ps files that requires too much RAM, for example mplayer.''

	[[Category:FAQ]]		[[Category:FAQ]]
	[[Category:Debug build]]		[[Category:Debug build]]

2010-02-14T12:13:51Z

← Older revision		Revision as of 12:13, 14 February 2010
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.''

2010-02-13T04:05:23Z

← Older revision		Revision as of 04:05, 13 February 2010
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]]

2010-02-13T04:04:38Z

Undo revision 2183 by 93.144.17.199 (Talk)

← Older revision		Revision as of 04:04, 13 February 2010
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]]

2010-02-13T04:04:22Z

Undo revision 2184 by 93.144.17.199 (Talk)

← Older revision		Revision as of 04:04, 13 February 2010
Line 13:		Line 13:
	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 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.		!Be careful that big package give a .dot and .os result that require too much RAM, for example mplayer.

2010-02-13T04:03:45Z

Undo revision 2185 by 93.144.17.199 (Talk)

← Older revision		Revision as of 04:03, 13 February 2010
Line 15:		Line 15:
	And then you can open the .ps file with gimp.		And then you can open the .ps file with gimp.

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