diff --git a/documentation/ref-manual/ref-structure.xml b/documentation/ref-manual/ref-structure.xml
index d2d75932f8..66e58f262d 100644
--- a/documentation/ref-manual/ref-structure.xml
+++ b/documentation/ref-manual/ref-structure.xml
@@ -101,7 +101,7 @@
- documentation
+ documentation/
This directory holds the source for the Yocto Project documentation
@@ -109,7 +109,7 @@
versions of the manuals.
Each manual is contained in a sub-folder.
For example, the files for this manual reside in
- ref-manual.
+ the ref-manual/ directory.
@@ -179,9 +179,9 @@
- The scripts directory has useful scripts that assist contributing
- back to the Yocto Project, such as create_pull_request and
- send_pull_request.
+ The scripts directory has useful scripts that assist in contributing
+ back to the Yocto Project, such as create-pull-request and
+ send-pull-request.
@@ -209,7 +209,8 @@
By default, running this script without a
Build Directory
- argument creates the build directory.
+ argument creates the build directory
+ in your current working directory.
If you provide a Build Directory argument when you
source the script, you direct the OpenEmbedded
build system to create a Build Directory of your choice.
@@ -346,7 +347,7 @@
MACHINE
for which you want to build, which package types you wish to use
(PACKAGE_CLASSES),
- the location from which you want to downloaded files
+ the location from which you want to access downloaded files
(DL_DIR),
and how you want your host machine to use resources
(BB_NUMBER_THREADS
@@ -368,9 +369,9 @@
The source local.conf.sample file used
depends on the $TEMPLATECONF script variable,
- which defaults to /meta-yocto/conf
+ which defaults to meta-yocto/conf
when you are building from the Yocto Project development
- environment and defaults to /meta/conf when
+ environment and defaults to meta/conf when
you are building from the OpenEmbedded Core environment.
Because the script variable points to the source of the
local.conf.sample file, this implies that
@@ -387,11 +388,11 @@
You can see how the TEMPLATECONF variable
is used by looking at the
- /scripts/oe-setup-builddir script in the
+ scripts/oe-setup-builddir script in the
Source Directory.
You can find the Yocto Project version of the
local.conf.sample file in the
- /meta-yocto/conf directory.
+ meta-yocto/conf directory.
@@ -424,9 +425,9 @@
The source bblayers.conf.sample file used
depends on the $TEMPLATECONF script variable,
- which defaults to /meta-yocto/conf
+ which defaults to meta-yocto/conf
when you are building from the Yocto Project development
- environment and defaults to /meta/conf when
+ environment and defaults to meta/conf when
you are building from the OpenEmbedded Core environment.
Because the script variable points to the source of the
bblayers.conf.sample file, this implies that
@@ -441,11 +442,11 @@
values for all ##OEROOT## values.
You can see how the TEMPLATECONF variable
- /scripts/oe-setup-builddir script in the
+ scripts/oe-setup-builddir script in the
Source Directory.
You can find the Yocto Project version of the
bblayers.conf.sample file in the
- /meta-yocto/conf directory.
+ meta-yocto/conf directory.
@@ -487,7 +488,7 @@
build/tmp/
- This directory receives all the OpenEmbedded build system's output.
+ This directory receives all of the OpenEmbedded build system's output.
BitBake creates this directory if it does not exist.
As a last resort, to clean up a build and start it from scratch (other than the downloads),
you can remove everything in the tmp directory or get rid of the
@@ -551,6 +552,15 @@
+
+ build/tmp/deploy/ipk/
+
+
+ This directory receives .ipk packages produced by
+ the build process.
+
+
+
build/tmp/deploy/licenses/
@@ -597,14 +607,6 @@
-
- build/tmp/deploy/ipk/
-
-
- This directory receives .ipk packages produced by
- the build process.
-
-
build/tmp/sysroots/
@@ -646,15 +648,6 @@
-
- build/tmp/pkgdata/
-
-
- This directory contains intermediate packaging data that is used later in the packaging process.
- For more information, see the "Packaging - package*.bbclass" section.
-
-
-
build/tmp/work/