diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml
index 02416b3cda..df9d5b0f76 100644
--- a/documentation/adt-manual/adt-prepare.xml
+++ b/documentation/adt-manual/adt-prepare.xml
@@ -106,7 +106,7 @@
build environment while also creating the default
Build Directory, and run the BitBake command that
results in the tarball
- ~/yocto-project/build/tmp/deploy/sdk/adt_installer.tar.bz2:
+ poky/build/tmp/deploy/sdk/adt_installer.tar.bz2:
Before using BitBake to build the ADT tarball, be
sure to make sure your
@@ -136,7 +136,7 @@
a top-level directory named adt-installer:
$ cd ~
- $ cp ~/poky/build/tmp/deploy/sdk/adt_installer.tar.bz2 $HOME
+ $ cp poky/build/tmp/deploy/sdk/adt_installer.tar.bz2 $HOME
$ tar -xjf adt_installer.tar.bz2
Unpacking it creates the directory adt-installer,
@@ -206,7 +206,7 @@
When you run the installer, the environment must use a
host gcc:
- $ cd ~/adt-installer
+ $ cd adt-installer
$ ./adt_installer
Once the installer begins to run, you are asked to enter the
@@ -303,7 +303,7 @@
The first thing the installer prompts you for is the
directory into which you want to install the toolchain.
The default directory used is
- opt/poky/&DISTRO;.
+ /opt/poky/&DISTRO;.
If you do not have write permissions for the directory
into which you are installing the toolchain, the
toolchain installer notifies you and exits.
@@ -545,7 +545,7 @@
the toolchain environment script in the
tmp directory.
If you installed the toolchain by hand, the environment setup
- script is located in opt/poky/&DISTRO;.
+ script is located in /opt/poky/&DISTRO;.
@@ -563,16 +563,16 @@
built filesystem that is located in the
~/Downloads directory.
Furthermore, this command extracts the root filesystem into the
- $HOME/qemux86-sato directory:
+ qemux86-sato directory:
$ cd ~
$ source /opt/poky/&DISTRO;/environment-setup-i586-poky-linux
$ runqemu-extract-sdk \
- ~Downloads/core-image-sato-sdk-qemux86-2011091411831.rootfs.tar.bz2 \
+ ~/Downloads/core-image-sato-sdk-qemux86-2011091411831.rootfs.tar.bz2 \
$HOME/qemux86-sato
You could now point to the target sysroot at
- $HOME/qemux86-sato.
+ qemux86-sato.
@@ -625,13 +625,13 @@
By default, this toolchain does not build static binaries.
If you want to use the toolchain to build these types of libraries,
- you need to be sure your image has the appropriate static
+ you need to be sure your image has the appropriate static
development libraries.
- Use the
+ Use the
IMAGE_INSTALL
variable inside your local.conf file to
install the appropriate library packages.
- Following is an example using eglibc static
+ Following is an example using eglibc static
development libraries:
IMAGE_INSTALL_append = " eglibc-staticdev"
diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml
index c85e7e0883..9a8f3af573 100644
--- a/documentation/bsp-guide/bsp.xml
+++ b/documentation/bsp-guide/bsp.xml
@@ -562,7 +562,7 @@
For example, suppose you had some configuration options in a file called
network_configs.cfg.
- You can place that file inside a directory named /linux-yocto and then add
+ You can place that file inside a directory named linux-yocto and then add
a SRC_URI statement such as the following to the append file.
When the OpenEmbedded build system builds the kernel, the configuration options are
picked up and applied.
@@ -748,7 +748,7 @@
Instructions on how to boot the BSP build from
the BSP layer.Instructions on how to boot the binary images
- contained in the /binary directory,
+ contained in the binary directory,
if present.Information on any known bugs or issues that users
should know about when either building or booting the BSP
@@ -759,7 +759,7 @@
meta-<bsp_name> directory.
This file specifies exactly where you can find the sources used to
generate the binary images contained in the
- /binary directory, if present.
+ binary directory, if present.
See the
README.sources
file for the Fish River Island 2 BSP in the meta-fri2 BSP layer
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 4aecb449f3..7d5063b79b 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -357,7 +357,7 @@
to cause the build to use your own version of
the file.
For example, an append file in your layer at
- /meta-one/recipes-core/base-files/base-files.bbappend
+ meta-one/recipes-core/base-files/base-files.bbappend
could extend
FILESPATH
using
@@ -369,7 +369,7 @@
The build for machine "one" will pick up your
machine-specific file as long as you have the
file in
- /meta-one/recipes-core/base-files/base-files/.
+ meta-one/recipes-core/base-files/base-files/.
However, if you are building for a different
machine and the
bblayers.conf file includes
@@ -384,9 +384,9 @@
the file in a subdirectory specific to the
machine.
For example, rather than placing the file in
- /meta-one/recipes-core/base-files/base-files/
+ meta-one/recipes-core/base-files/base-files/
as shown above, put it in
- /meta-one/recipes-core/base-files/base-files/one/.
+ meta-one/recipes-core/base-files/base-files/one/.
Not only does this make sure the file is used
only when building for machine "one" but the
build process locates the file more quickly.
@@ -1957,7 +1957,7 @@
Source Directory
top-level folder is ~/poky:
- $ cd ~/poky
+ $ cd poky
$ source oe-init-build-env
$ bitbake linux-yocto -c menuconfig
@@ -2006,7 +2006,7 @@
x86 architecture, the
.config file would be located here:
- ~/poky/build/tmp/work/qemux86-poky-linux/linux-yocto-3.4.11+git1+84f...
+ poky/build/tmp/work/qemux86-poky-linux/linux-yocto-3.4.11+git1+84f...
...656ed30-r1/linux-qemux86-standard-build
@@ -2079,7 +2079,7 @@
kernel's configuration.
For example, suppose you had a set of configuration options in a file called
myconfig.cfg.
- If you put that file inside a directory named /linux-yocto
+ If you put that file inside a directory named linux-yocto
that resides in the same directory as the kernel's append file and then add
a SRC_URI statement such as the following to the kernel's append file,
those configuration options will be picked up and applied when the kernel is built.
@@ -5271,7 +5271,7 @@
You have checked out the
dora-toaster branch:
- $ cd ~/poky
+ $ cd poky
$ git checkout -b dora-toaster origin/dora-toaster
Be sure your build machine has
@@ -5629,7 +5629,7 @@
Downloaded archives reside in the
Build Directory in
- /tmp and are cleared up when they are no longer in use.
+ tmp and are cleared up when they are no longer in use.
diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml
index 46cd5b30a1..8b0bfc6fa8 100644
--- a/documentation/dev-manual/dev-manual-model.xml
+++ b/documentation/dev-manual/dev-manual-model.xml
@@ -1675,7 +1675,7 @@
the following is the work directory for the acl recipe that
creates the acl package:
- ~/poky/build/tmp/work/i586-poky-linux/acl/2.2.51-r3/
+ poky/build/tmp/work/i586-poky-linux/acl/2.2.51-r3/
@@ -1691,8 +1691,8 @@
for the acl package that is being
built for a MIPS-based device:
- ~/poky/build/tmp/work/mips-poky-linux/acl/2.2.51-r2
- ~/poky/build/tmp/work/mips-poky-linux/acl/2.2.51-r2/acl-2.2.51
+ poky/build/tmp/work/mips-poky-linux/acl/2.2.51-r2
+ poky/build/tmp/work/mips-poky-linux/acl/2.2.51-r2/acl-2.2.51
diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml
index 0dc4bd58bb..600c789a6d 100644
--- a/documentation/dev-manual/dev-manual-newbie.xml
+++ b/documentation/dev-manual/dev-manual-newbie.xml
@@ -1462,8 +1462,8 @@
For help on using these scripts, simply provide the
-h argument as follows:
- $ ~/poky/scripts/create-pull-request -h
- $ ~/poky/scripts/send-pull-request -h
+ $ poky/scripts/create-pull-request -h
+ $ poky/scripts/send-pull-request -h
diff --git a/documentation/kernel-dev/kernel-dev-maint-appx.xml b/documentation/kernel-dev/kernel-dev-maint-appx.xml
index 5f9788aa31..a7c144ff75 100644
--- a/documentation/kernel-dev/kernel-dev-maint-appx.xml
+++ b/documentation/kernel-dev/kernel-dev-maint-appx.xml
@@ -45,7 +45,7 @@
Here is an example that assumes the local Git repository for the kernel is in
a top-level directory named linux-yocto-3.4:
- $ cd ~/linux-yocto-3.4
+ $ cd linux-yocto-3.4
$ git checkout -b meta origin/meta
Once you have checked out and switched to the meta branch,
@@ -208,7 +208,7 @@
the build tree directory.
The files include the final .config file, all the .o
files, the .a files, and so forth.
- Since each machine or BSP has its own separate
+ Since each machine or BSP has its own separate
Build Directory
in its own separate branch
of the Git repository, you can easily switch between different builds.
diff --git a/documentation/ref-manual/migration.xml b/documentation/ref-manual/migration.xml
index a3a3e88a07..dc24628e3c 100644
--- a/documentation/ref-manual/migration.xml
+++ b/documentation/ref-manual/migration.xml
@@ -829,10 +829,10 @@
- /run
+ run
- The /run directory from the Filesystem
+ The run directory from the Filesystem
Hierarchy Standard 3.0 has been introduced.
You can find some of the implications for this change
here.
@@ -1033,7 +1033,7 @@
base-files: Remove the unnecessary
- /media/xxx directories.
+ media/xxx directories.
alsa-state: Provide an empty
diff --git a/documentation/ref-manual/ref-bitbake.xml b/documentation/ref-manual/ref-bitbake.xml
index b587d46caa..e24ea45281 100644
--- a/documentation/ref-manual/ref-bitbake.xml
+++ b/documentation/ref-manual/ref-bitbake.xml
@@ -222,7 +222,7 @@
As each task completes, a timestamp is written to the directory specified by the
STAMP variable.
- On subsequent runs, BitBake looks within the /build/tmp/stamps
+ On subsequent runs, BitBake looks within the build/tmp/stamps
directory and does not rerun
tasks that are already completed unless a timestamp is found to be invalid.
Currently, invalid timestamps are only considered on a per
diff --git a/documentation/ref-manual/ref-features.xml b/documentation/ref-manual/ref-features.xml
index 3f216e3a64..dedcf67e33 100644
--- a/documentation/ref-manual/ref-features.xml
+++ b/documentation/ref-manual/ref-features.xml
@@ -38,7 +38,7 @@
Here is an example that discovers the recipes whose build is potentially
changed based on a given feature:
- $ cd $HOME/poky
+ $ cd poky
$ git grep 'contains.*MACHINE_FEATURES.*<feature>'
diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml
index 84deee8899..2b0e8909fe 100644
--- a/documentation/ref-manual/ref-variables.xml
+++ b/documentation/ref-manual/ref-variables.xml
@@ -701,10 +701,10 @@
The following example uses a complete regular expression
to tell BitBake to ignore all recipe and recipe append
- files in the /meta-ti/recipes-misc/
+ files in the meta-ti/recipes-misc/
directory:
- BBMASK = "/meta-ti/recipes-misc/"
+ BBMASK = "meta-ti/recipes-misc/"
If you want to mask out multiple directories or recipes,
use the vertical bar to separate the regular expression
@@ -999,7 +999,7 @@
/etc or ${bindir} rather
than /usr/bin.
You can find a list of these variables at the top of the
- /meta/conf/bitbake.conf file in the
+ meta/conf/bitbake.conf file in the
Source Directory.
@@ -1036,7 +1036,7 @@
Specifies the parent directory of the OpenEmbedded
- Core Metadata layer (i.e. /meta).
+ Core Metadata layer (i.e. meta).
@@ -1362,7 +1362,7 @@
You can set this directory by defining the
DL_DIR variable in the
- /conf/local.conf file.
+ conf/local.conf file.
This directory is self-maintaining and you should not have
to touch it.
By default, the directory is downloads
@@ -1712,7 +1712,7 @@
/etc, or ${bindir} rather
than /usr/bin.
You can find a list of these variables at the top of the
- /meta/conf/bitbake.conf file in the
+ meta/conf/bitbake.conf file in the
Source Directory.
@@ -2068,7 +2068,7 @@
to a default value using the ?= operator, using a
+= operation against IMAGE_INSTALL
will result in unexpected behavior when used in
- /conf/local.conf.
+ conf/local.conf.
Furthermore, the same operation from within an image recipe may or may not
succeed depending on the specific situation.
In both these cases, the behavior is contrary to how most users expect
@@ -4770,7 +4770,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
to keep the unpacked recipe for db
is the following:
- ~/poky/build/tmp/work/qemux86-poky-linux/db/5.1.19-r3/db-5.1.19
+ poky/build/tmp/work/qemux86-poky-linux/db/5.1.19-r3/db-5.1.19
@@ -5888,7 +5888,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
In this case, the working directory the build system uses to build
the v86d package is the following:
- ~/poky/build/tmp/work/qemux86-poky-linux/v86d/01.9-r0
+ poky/build/tmp/work/qemux86-poky-linux/v86d/01.9-r0
@@ -5905,7 +5905,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
the acl recipe, which is being built for a
MIPS-based device, is the following:
- ~/poky/build/tmp/work/mips-poky-linux/acl/2.2.51-r2
+ poky/build/tmp/work/mips-poky-linux/acl/2.2.51-r2
diff --git a/documentation/ref-manual/technical-details.xml b/documentation/ref-manual/technical-details.xml
index 4d1c2e3f4e..6d4c6b712c 100644
--- a/documentation/ref-manual/technical-details.xml
+++ b/documentation/ref-manual/technical-details.xml
@@ -1149,7 +1149,7 @@
recipe-by-recipe basis through the LICENSE_FLAGS variable
definition in the affected recipe.
For instance, the
- $HOME/poky/meta/recipes-multimedia/gstreamer/gst-plugins-ugly
+ poky/meta/recipes-multimedia/gstreamer/gst-plugins-ugly
recipe contains the following statement:
LICENSE_FLAGS = "commercial"
@@ -1165,7 +1165,7 @@
LICENSE_FLAGS_WHITELIST variable, which is a variable
typically defined in your local.conf file.
For example, to enable
- the $HOME/poky/meta/recipes-multimedia/gstreamer/gst-plugins-ugly
+ the poky/meta/recipes-multimedia/gstreamer/gst-plugins-ugly
package, you could add either the string
"commercial_gst-plugins-ugly" or the more general string
"commercial" to LICENSE_FLAGS_WHITELIST.
@@ -1312,7 +1312,7 @@
Other helpful variables related to commercial
license handling exist and are defined in the
- $HOME/poky/meta/conf/distro/include/default-distrovars.inc file:
+ poky/meta/conf/distro/include/default-distrovars.inc file:
COMMERCIAL_AUDIO_PLUGINS ?= ""
COMMERCIAL_VIDEO_PLUGINS ?= ""
diff --git a/documentation/ref-manual/usingpoky.xml b/documentation/ref-manual/usingpoky.xml
index 49166e15bf..b9df733f3f 100644
--- a/documentation/ref-manual/usingpoky.xml
+++ b/documentation/ref-manual/usingpoky.xml
@@ -62,7 +62,7 @@
The target is the name of the recipe you want to build.
Common targets are the images in meta/recipes-core/images,
- /meta/recipes-sato/images, etc. all found in the
+ meta/recipes-sato/images, etc. all found in the
Source Directory.
Or, the target can be the name of a recipe for a specific piece of software such as
BusyBox.