From 306b7c7a9757ead077363074e7bbac2e5c03e7c5 Mon Sep 17 00:00:00 2001 From: Richard Purdie Date: Thu, 16 Nov 2006 15:02:15 +0000 Subject: bitbake: Upgrade from 1.4 -> 1.7.4ish git-svn-id: https://svn.o-hand.com/repos/poky/trunk@863 311d38ba-8fff-0310-9ca6-ca027cbcb966 --- bitbake/doc/manual/usermanual.xml | 29 ++++++++++++++++++++++++----- 1 file changed, 24 insertions(+), 5 deletions(-) (limited to 'bitbake/doc') diff --git a/bitbake/doc/manual/usermanual.xml b/bitbake/doc/manual/usermanual.xml index c314236c6f..7eb12035ad 100644 --- a/bitbake/doc/manual/usermanual.xml +++ b/bitbake/doc/manual/usermanual.xml @@ -17,7 +17,7 @@ Phil Blundell - This work is licensed under the Creative Commons Attribution License. To view a copy of this license, visit http://creativecommons.org/licenses/by/2.0/ or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA. + This work is licensed under the Creative Commons Attribution License. To view a copy of this license, visit http://creativecommons.org/licenses/by/2.5/ or send a letter to Creative Commons, 559 Nathan Abbott Way, Stanford, California 94305, USA. @@ -195,7 +195,7 @@ addtask printdate before do_build
Events NOTE: This is only supported in .bb and .bbclass files. - BitBake also implements a means of registering event handlers. Events are triggered at certain points during operation, such as, the beginning of operation against a given .bb, the start of a given task, task failure, task success, et cetera. The intent was to make it easy to do things like email notifications on build failure. + BitBake allows to install event handlers. Events are triggered at certain points during operation, such as, the beginning of operation against a given .bb, the start of a given task, task failure, task success, et cetera. The intent was to make it easy to do things like email notifications on build failure. addhandler myclass_eventhandler python myclass_eventhandler() { from bb.event import NotHandled, getName @@ -205,6 +205,7 @@ python myclass_eventhandler() { print "The file we run for is %s" % data.getVar('FILE', e.data, True) return NotHandled +} This event handler gets called every time an event is triggered. A global variable e is defined. e.data contains an instance of bb.data. With the getName(e) method one can get the name of the triggered event.The above event handler prints the name @@ -344,15 +345,19 @@ options: cannot be remade, the other dependencies of these targets can be processed all the same. -f, --force force run of specified cmd, regardless of stamp status - -i, --interactive drop into the interactive mode. + -i, --interactive drop into the interactive mode also called the BitBake + shell. -c CMD, --cmd=CMD Specify task to execute. Note that this only executes the specified task for the providee and the packages it depends on, i.e. 'compile' does not implicitly call stage for the dependencies (IOW: use only if you know - what you are doing) + what you are doing). Depending on the base.bbclass a + listtaks tasks is defined and will show available + tasks -r FILE, --read=FILE read the specified file before bitbake.conf -v, --verbose output more chit-chat to the terminal - -D, --debug Increase the debug level + -D, --debug Increase the debug level. You can specify this more + than once. -n, --dry-run don't execute, just go through the motions -p, --parse-only quit after parsing the BB files (developers only) -d, --disable-psyco disable using the psyco just-in-time compiler (not @@ -360,6 +365,12 @@ options: -s, --show-versions show current and preferred versions of all packages -e, --environment show the global or per-package environment (this is what used to be bbread) + -g, --graphviz emit the dependency trees of the specified packages in + the dot syntax + -I IGNORED_DOT_DEPS, --ignore-deps=IGNORED_DOT_DEPS + Stop processing at the given list of dependencies when + generating dependency graphs. This can help to make + the graph more appealing @@ -386,6 +397,14 @@ options: $ bitbake virtual/whatever $ bitbake -c clean virtual/whatever + + Generating dependency graphs + BitBake is able to generate dependency graphs using the dot syntax. These graphs can be converted +to images using the dot application from graphviz. +Three files will be written into the current working directory, depends.dot containing DEPENDS variables, rdepends.dot and alldepends.dot containing both DEPENDS and RDEPENDS. To stop depending on common depends one can use the -I depend to omit these from the graph. This can lead to more readable graphs. E.g. this way DEPENDS from inherited classes, e.g. base.bbclass, can be removed from the graph. + $ bitbake -g blah + $ bitbake -g -I virtual/whatever -I bloom blah +
-- cgit v1.2.3-54-g00ecf