diff options
Diffstat (limited to 'documentation/ref-manual')
| -rw-r--r-- | documentation/ref-manual/migration.xml | 6 | ||||
| -rw-r--r-- | documentation/ref-manual/ref-bitbake.xml | 2 | ||||
| -rw-r--r-- | documentation/ref-manual/ref-features.xml | 2 | ||||
| -rw-r--r-- | documentation/ref-manual/ref-variables.xml | 20 | ||||
| -rw-r--r-- | documentation/ref-manual/technical-details.xml | 6 | ||||
| -rw-r--r-- | documentation/ref-manual/usingpoky.xml | 2 |
6 files changed, 19 insertions, 19 deletions
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 @@ </section> <section id='migration-1.5-run'> - <title><filename>/run</filename></title> + <title><filename>run</filename></title> <para> - The <filename>/run</filename> directory from the Filesystem + The <filename>run</filename> directory from the Filesystem Hierarchy Standard 3.0 has been introduced. You can find some of the implications for this change <ulink url='http://cgit.openembedded.org/openembedded-core/commit/?id=0e326280a15b0f2c4ef2ef4ec441f63f55b75873'>here</ulink>. @@ -1033,7 +1033,7 @@ </para></listitem> <listitem><para> <filename>base-files</filename>: Remove the unnecessary - <filename>/media/xxx</filename> directories. + <filename>media/xxx</filename> directories. </para></listitem> <listitem><para> <filename>alsa-state</filename>: 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 @@ <para> As each task completes, a timestamp is written to the directory specified by the <filename><link linkend='var-STAMP'>STAMP</link></filename> variable. - On subsequent runs, BitBake looks within the <filename>/build/tmp/stamps</filename> + On subsequent runs, BitBake looks within the <filename>build/tmp/stamps</filename> 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: <literallayout class='monospaced'> - $ cd $HOME/poky + $ cd poky $ git grep 'contains.*MACHINE_FEATURES.*<feature>' </literallayout> </para> 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 @@ <para> The following example uses a complete regular expression to tell BitBake to ignore all recipe and recipe append - files in the <filename>/meta-ti/recipes-misc/</filename> + files in the <filename>meta-ti/recipes-misc/</filename> directory: <literallayout class='monospaced'> - BBMASK = "/meta-ti/recipes-misc/" + BBMASK = "meta-ti/recipes-misc/" </literallayout> If you want to mask out multiple directories or recipes, use the vertical bar to separate the regular expression @@ -999,7 +999,7 @@ <filename>/etc</filename> or <filename>${bindir}</filename> rather than <filename>/usr/bin</filename>. You can find a list of these variables at the top of the - <filename>/meta/conf/bitbake.conf</filename> file in the + <filename>meta/conf/bitbake.conf</filename> file in the <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>. </note> </glossdef> @@ -1036,7 +1036,7 @@ <glossdef> <para> Specifies the parent directory of the OpenEmbedded - Core Metadata layer (i.e. <filename>/meta</filename>). + Core Metadata layer (i.e. <filename>meta</filename>). </para> <para> @@ -1362,7 +1362,7 @@ <para> You can set this directory by defining the <filename>DL_DIR</filename> variable in the - <filename>/conf/local.conf</filename> file. + <filename>conf/local.conf</filename> file. This directory is self-maintaining and you should not have to touch it. By default, the directory is <filename>downloads</filename> @@ -1712,7 +1712,7 @@ <filename>/etc</filename>, or <filename>${bindir}</filename> rather than <filename>/usr/bin</filename>. You can find a list of these variables at the top of the - <filename>/meta/conf/bitbake.conf</filename> file in the + <filename>meta/conf/bitbake.conf</filename> file in the <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>. </note> @@ -2068,7 +2068,7 @@ to a default value using the <filename>?=</filename> operator, using a <filename>+=</filename> operation against <filename>IMAGE_INSTALL</filename> will result in unexpected behavior when used in - <filename>/conf/local.conf</filename>. + <filename>conf/local.conf</filename>. 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 <filename>db</filename> is the following: <literallayout class='monospaced'> - ~/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 </literallayout> </para> </glossdef> @@ -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 <filename>v86d</filename> package is the following: <literallayout class='monospaced'> - ~/poky/build/tmp/work/qemux86-poky-linux/v86d/01.9-r0 + poky/build/tmp/work/qemux86-poky-linux/v86d/01.9-r0 </literallayout> </para> @@ -5905,7 +5905,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" the <filename>acl</filename> recipe, which is being built for a MIPS-based device, is the following: <literallayout class='monospaced'> - ~/poky/build/tmp/work/mips-poky-linux/acl/2.2.51-r2 + poky/build/tmp/work/mips-poky-linux/acl/2.2.51-r2 </literallayout> </para> </glossdef> 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 <filename>LICENSE_FLAGS</filename> variable definition in the affected recipe. For instance, the - <filename>$HOME/poky/meta/recipes-multimedia/gstreamer/gst-plugins-ugly</filename> + <filename>poky/meta/recipes-multimedia/gstreamer/gst-plugins-ugly</filename> recipe contains the following statement: <literallayout class='monospaced'> LICENSE_FLAGS = "commercial" @@ -1165,7 +1165,7 @@ <filename>LICENSE_FLAGS_WHITELIST</filename> variable, which is a variable typically defined in your <filename>local.conf</filename> file. For example, to enable - the <filename>$HOME/poky/meta/recipes-multimedia/gstreamer/gst-plugins-ugly</filename> + the <filename>poky/meta/recipes-multimedia/gstreamer/gst-plugins-ugly</filename> package, you could add either the string "commercial_gst-plugins-ugly" or the more general string "commercial" to <filename>LICENSE_FLAGS_WHITELIST</filename>. @@ -1312,7 +1312,7 @@ <para> Other helpful variables related to commercial license handling exist and are defined in the - <filename>$HOME/poky/meta/conf/distro/include/default-distrovars.inc</filename> file: + <filename>poky/meta/conf/distro/include/default-distrovars.inc</filename> file: <literallayout class='monospaced'> 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 @@ <para> The <filename>target</filename> is the name of the recipe you want to build. Common targets are the images in <filename>meta/recipes-core/images</filename>, - <filename>/meta/recipes-sato/images</filename>, etc. all found in the + <filename>meta/recipes-sato/images</filename>, etc. all found in the <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>. Or, the target can be the name of a recipe for a specific piece of software such as BusyBox. |