diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index f55e99122b..793b4c78c6 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -599,71 +599,47 @@
what you require.
-
- Adding Packages
-
-
- The simplest way to add extra packages to all images is by using the
- IMAGE_INSTALL
- variable with the _append operator:
-
+
+ The simplest way to add extra packages to all images is by using the
+ IMAGE_INSTALL
+ variable with the _append operator:
+
IMAGE_INSTALL_append = " strace"
-
- Use of the syntax is important.
- Specifically, the space between the quote and the package name, which is
- strace in this example.
- This space is required since the _append
- operator does not add the space.
-
+
+ Use of the syntax is important.
+ Specifically, the space between the quote and the package name, which is
+ strace in this example.
+ This space is required since the _append
+ operator does not add the space.
+
-
- Furthermore, you must use _append instead of the +=
- operator if you want to avoid ordering issues.
- The reason for this is because doing so unconditionally appends to the variable and
- avoids ordering problems due to the variable being set in image recipes and
- .bbclass files with operators like ?=.
- Using _append ensures the operation takes affect.
-
+
+ Furthermore, you must use _append instead of the +=
+ operator if you want to avoid ordering issues.
+ The reason for this is because doing so unconditionally appends to the variable and
+ avoids ordering problems due to the variable being set in image recipes and
+ .bbclass files with operators like ?=.
+ Using _append ensures the operation takes affect.
+
-
- As shown in its simplest use, IMAGE_INSTALL_append affects
- all images.
- It is possible to extend the syntax so that the variable applies to a specific image only.
- Here is an example:
-
+
+ As shown in its simplest use, IMAGE_INSTALL_append affects
+ all images.
+ It is possible to extend the syntax so that the variable applies to a specific image only.
+ Here is an example:
+
IMAGE_INSTALL_append_pn-core-image-minimal = " strace"
-
- This example adds strace to core-image-minimal
- only.
-
+
+ This example adds strace to core-image-minimal
+ only.
+
-
- You can add packages using a similar approach through the
- CORE_IMAGE_EXTRA_INSTALL
- variable.
- If you use this variable, only core-image-* images are affected.
-
-
-
-
- Excluding Packages
-
-
- It is possible to filter or mask out .bb and
- .bbappend files such that BitBake ignores them during
- the build.
- You can do this by providing an expression with the
- BBMASK
- variable.
- Here is an example:
-
- BBMASK = ".*/meta-mymachine/recipes-maybe/"
-
- Here, all .bb and .bbappend files
- in the directory that matches the expression are ignored during the build
- process.
-
-
+
+ You can add packages using a similar approach through the
+ CORE_IMAGE_EXTRA_INSTALL
+ variable.
+ If you use this variable, only core-image-* images are affected.
+
@@ -2013,6 +1989,26 @@ so that there are some definite steps on how to do this. I need more detail her
build directory that is different than the source directory.
+
+
+ Excluding Packages From the Build
+
+
+ It is possible to filter or mask out .bb and
+ .bbappend files such that BitBake ignores them during
+ the build.
+ You can do this by providing an expression with the
+ BBMASK
+ variable.
+ Here is an example:
+
+ BBMASK = ".*/meta-mymachine/recipes-maybe/"
+
+ Here, all .bb and .bbappend files
+ in the directory that match the expression are ignored during the build
+ process - BitBake does not even parse them.
+
+