From ae1f0e7a768020d36b8304713367174305b1a91f Mon Sep 17 00:00:00 2001 From: Bill Traynor Date: Mon, 15 Apr 2013 14:15:40 -0400 Subject: user-manual-metadata: Fixing missing closing tags. Added missing section closing tags. Signed-off-by: Bill Traynor --- doc/user-manual/user-manual-metadata.xml | 133 +++++++++++++++++-------------- 1 file changed, 75 insertions(+), 58 deletions(-) diff --git a/doc/user-manual/user-manual-metadata.xml b/doc/user-manual/user-manual-metadata.xml index 3d8ee126e..27c4edc2f 100644 --- a/doc/user-manual/user-manual-metadata.xml +++ b/doc/user-manual/user-manual-metadata.xml @@ -70,6 +70,7 @@ B containing preavalpost. +
Setting a default value (?=) @@ -85,6 +86,7 @@ immediate, so if there are multiple ?= assignments to a single variable, the first of those will be used.
+
Setting a weak default value (??=) @@ -108,6 +110,7 @@ value set with ??=.
+
Immediate variable expansion (:=) := results in a variable's contents being expanded immediately, @@ -135,6 +138,7 @@ cvalappend.
+
Appending (+=) and prepending (=+) @@ -253,8 +257,9 @@ yourself. is set to glibc ncurses libmad. -
-
+
+ +
Inclusion Next, there is the include directive, that causes BitBake to @@ -266,8 +271,9 @@ yourself. can find within BBPATH. -
-
+
+ +
Requiring inclusion In contrast to the include @@ -279,8 +285,9 @@ yourself. include directive. -
-
+
+ +
Inline Python variable expansion @@ -292,8 +299,9 @@ yourself. DATE variable containing today's date. -
-
+
+ +
Defining executable metadata NOTE: @@ -314,8 +322,9 @@ yourself. This is the similar to the previous, but flags it as Python so that BitBake knows it is Python code. -
-
+
+ +
Defining Python functions into the global Python namespace @@ -341,8 +350,9 @@ yourself. containing dependencywithcond. -
-
+
+ +
Variable flags Variables can have associated flags which provide a way of tagging extra information onto a variable. @@ -365,8 +375,9 @@ yourself. that is set to value. -
-
+
+ +
Inheritance NOTE: This is only supported in .bb @@ -383,8 +394,9 @@ yourself. BBPATH, where filename is what you inherited. -
-
+
+ +
Tasks NOTE: @@ -408,8 +420,9 @@ yourself. If anyone executes the do_build task, that will result in do_printdate being run first. -
-
+
+ +
Task Flags Tasks support a number of flags which control various functionality of the task. @@ -438,8 +451,9 @@ yourself. For the 'deptask', 'rdeptask', 'depends', 'rdepends'and 'recrdeptask' flags please see the dependencies section. -
-
+
+ +
Events NOTE: @@ -474,9 +488,9 @@ yourself. FILE variable. -
- -
+
+ +
Variants Two BitBake features exist to facilitate the creation of multiple buildable incarnations from a single recipe file. @@ -521,8 +535,9 @@ yourself. variable, for use in file:// search paths (FILESPATH). -
-
+
+ +
Variable interaction: Worked Examples Despite the documentation of the different forms of variable definition above, it can be hard to work out what happens when @@ -530,7 +545,9 @@ yourself. This section documents some common questions people have regarding the way variables interact. -
+
+ +
Override and append ordering There is often confusion about which order overrides and the various append operators take effect. @@ -596,8 +613,9 @@ yourself. taking the value "1 4523" since the _append operator executes at the same time as the expansion of other overrides. -
-
+
+ +
Key Expansion Key expansion happens at the data store finalisation time just before overrides are expanded. @@ -616,25 +634,26 @@ yourself. A2 would take the value of "X". -
-
+
+ +
Dependency handling BitBake handles dependencies at the task level since to allow for efficient operation with multiple processes executing in parallel, a robust method of specifying task dependencies is 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. -
- -
+
+ +
Build Dependencies DEPENDS lists build time dependencies. The 'deptask' flag for tasks is used to signify the task of @@ -650,9 +669,9 @@ yourself. means the do_populate_staging task of each item in DEPENDS must have completed before do_configure can execute. -
- -
+
+ +
Runtime Dependencies The PACKAGES variable lists runtime packages and each of these can have RDEPENDS and RRECOMMENDS runtime dependencies. @@ -668,9 +687,9 @@ yourself. means the do_package task of each item in RDEPENDS must have completed before do_package_write can execute. -
- -
+
+ +
Recursive Dependencies These are specified with the 'recrdeptask' flag which is used to signify the task(s) of dependencies which must have @@ -687,9 +706,9 @@ yourself. If that is the case, the taskname itself should be referenced in the task list, e.g. do_a[recrdeptask] = "do_a do_b". -
- -
+
+ +
Inter task The 'depends' flag for tasks is a more generic form which allows an interdependency on specific tasks rather than specifying @@ -708,11 +727,9 @@ yourself. the runtime namespace instead of the build time dependency namespace. -
- -
- -
+
+ +
Parsing
Configuration files @@ -746,9 +763,9 @@ yourself. Only variable definitions and include directives are allowed in .conf files. -
- -
+
+ +
Classes BitBake classes are our rudimentary inheritance mechanism. As briefly mentioned in the metadata introduction, they're @@ -758,9 +775,9 @@ yourself. relative to the directories in BBPATH. -
- -
+
+ +
.bb files A BitBake (.bb) file is a logical unit of tasks to be executed. Normally this is a package to be built. @@ -770,8 +787,8 @@ yourself. variable, which is set to a space separated list of .bb files, and does handle wildcards. -
+
- + -- cgit 1.2.3-korg