From 70b11ba5824b9b713ab35dd7b677c102d59af915 Mon Sep 17 00:00:00 2001 From: Richard Purdie Date: Tue, 12 Jun 2007 10:06:56 +0000 Subject: bitbake: Sync manual updates and version info with bitbake svn git-svn-id: https://svn.o-hand.com/repos/poky/trunk@1920 311d38ba-8fff-0310-9ca6-ca027cbcb966 --- bitbake/doc/manual/usermanual.xml | 54 ++++++++++++++++++++++++++++++++++++++- 1 file changed, 53 insertions(+), 1 deletion(-) (limited to 'bitbake/doc') diff --git a/bitbake/doc/manual/usermanual.xml b/bitbake/doc/manual/usermanual.xml index 4db452747d..a79716a0aa 100644 --- a/bitbake/doc/manual/usermanual.xml +++ b/bitbake/doc/manual/usermanual.xml @@ -175,6 +175,12 @@ include directive. DEPENDS = "${@get_depends(bb, d)}" This would result in DEPENDS containing dependencywithcond. +
+ Variable Flags + Variables can have associated flags which provide a way of tagging extra information onto a variable. Several flags are used internally by bitbake but they can be used externally too if needed. The standard operations mentioned above also work on flags. + VARIABLE[SOMEFLAG] = "value" + In this example, VARIABLE has a flag, SOMEFLAG which is set to value. +
Inheritance NOTE: This is only supported in .bb and .bbclass files. @@ -212,6 +218,42 @@ method one can get the name of the triggered event.The above event of the event and the content of the FILE variable.
+
+ Dependency Handling + Bitbake 1.7.x onwards works with the metadata at the task level since this is optimal when dealing with multiple threads of execution. A robust method of specifing task dependencies is therefore needed. +
+ Dependencies internal to the .bb file + Where the dependencies are internal to a given .bb file, the dependencies are handled by the previously detailed addtask directive. +
+ +
+ DEPENDS + DEPENDS is taken to specify build time dependencies. The 'deptask' flag for tasks is used to signify the task of each DEPENDS which must have completed before that task can be executed. + do_configure[deptask] = "do_populate_staging" + means the do_populate_staging task of each item in DEPENDS must have completed before do_configure can execute. +
+
+ RDEPENDS + RDEPENDS is taken to specify runtime dependencies. The 'rdeptask' flag for tasks is used to signify the task of each RDEPENDS which must have completed before that task can be executed. + do_package_write[rdeptask] = "do_package" + means the do_package task of each item in RDEPENDS must have completed before do_package_write can execute. +
+
+ Recursive DEPENDS + These are specified with the 'recdeptask' flag and is used signify the task(s) of each DEPENDS which must have completed before that task can be executed. It applies recursively so also, the DEPENDS of each item in the original DEPENDS must be met and so on. +
+
+ Recursive RDEPENDS + These are specified with the 'recrdeptask' flag and is used signify the task(s) of each RDEPENDS which must have completed before that task can be executed. It applies recursively so also, the RDEPENDS of each item in the original RDEPENDS must be met and so on. It also runs all DEPENDS first too. +
+
+ Inter Task + The 'depends' flag for tasks is a more generic form of which allows an interdependency on specific tasks rather than specifying the data in DEPENDS or RDEPENDS. + do_patch[depends] = "quilt-native:do_populate_staging" + means the do_populate_staging task of the target quilt-native must have completed before the do_patch can execute. +
+
+
Parsing
@@ -371,6 +413,8 @@ options: Stop processing at the given list of dependencies when generating dependency graphs. This can help to make the graph more appealing + -l DEBUG_DOMAINS, --log-domains=DEBUG_DOMAINS + Show debug logging for the specified logging domains @@ -401,12 +445,20 @@ options: 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. +Two files will be written into the current working directory, depends.dot containing dependency information at the package level and task-depends.dot containing a breakdown of the dependencies at the task level. 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
+
+ Special variables + Certain variables affect bitbake operation: +
+ <varname>BB_NUMBER_THREADS</varname> + The number of threads bitbake should run at once (default: 1). +
+
Metadata As you may have seen in the usage information, or in the information about .bb files, the BBFILES variable is how the bitbake tool locates its files. This variable is a space seperated list of files that are available, and supports wildcards. -- cgit v1.2.3