mirror of
https://git.yoctoproject.org/poky
synced 2026-04-30 12:32:12 +02:00
documentation: Fixed links for "build-directory" term.
Fixes [YOCTO #11630] Moving the "Yocto Project Terms" section from the dev-manual to the ref-manual broke several links to the id "build-directory". I fixed these to reference into the ref-manual now. (From yocto-docs rev: debe2ae8ce203ebe0f1cee0de54124c15df8bb7e) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
committed by
Richard Purdie
Richard Purdie
parent
b8b87dd690
commit
74bf586c94
@@ -536,7 +536,7 @@
|
||||
<para role="glossdeffirst">
|
||||
<!-- <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> -->
|
||||
The directory within the
|
||||
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>
|
||||
<link linkend='build-directory'>Build Directory</link>
|
||||
in which the OpenEmbedded build system places generated
|
||||
objects during a recipe's build process.
|
||||
By default, this directory is the same as the <link linkend='var-S'><filename>S</filename></link>
|
||||
@@ -734,7 +734,7 @@
|
||||
variable to "1", "yes", or "true"
|
||||
in your <filename>local.conf</filename> file, which is
|
||||
located in the
|
||||
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>:
|
||||
<link linkend='build-directory'>Build Directory</link>:
|
||||
Here is an example:
|
||||
<literallayout class='monospaced'>
|
||||
BB_DANGLINGAPPENDS_WARNONLY = "1"
|
||||
@@ -759,7 +759,7 @@
|
||||
Disk space monitoring is disabled by default.
|
||||
To enable monitoring, add the <filename>BB_DISKMON_DIRS</filename>
|
||||
variable to your <filename>conf/local.conf</filename> file found in the
|
||||
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>.
|
||||
<link linkend='build-directory'>Build Directory</link>.
|
||||
Use the following form:
|
||||
<literallayout class='monospaced'>
|
||||
BB_DISKMON_DIRS = "<replaceable>action</replaceable>,<replaceable>dir</replaceable>,<replaceable>threshold</replaceable> [...]"
|
||||
@@ -852,7 +852,7 @@
|
||||
Defines the disk space and free inode warning intervals.
|
||||
To set these intervals, define the variable in your
|
||||
<filename>conf/local.conf</filename> file in the
|
||||
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>.
|
||||
<link linkend='build-directory'>Build Directory</link>.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
@@ -936,7 +936,7 @@
|
||||
</literallayout>
|
||||
Set this variable in your <filename>local.conf</filename>
|
||||
file in the
|
||||
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>.
|
||||
<link linkend='build-directory'>Build Directory</link>.
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
@@ -1154,7 +1154,8 @@
|
||||
<!-- <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> -->
|
||||
Lists the layers to enable during the build.
|
||||
This variable is defined in the <filename>bblayers.conf</filename> configuration
|
||||
file in the <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>.
|
||||
file in the
|
||||
<link linkend='build-directory'>Build Directory</link>.
|
||||
Here is an example:
|
||||
<literallayout class='monospaced'>
|
||||
BBLAYERS = " \
|
||||
@@ -1250,7 +1251,7 @@
|
||||
BBMULTIFONFIG = "configA configB configC"
|
||||
</literallayout>
|
||||
Each configuration file you use must reside in the
|
||||
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory's</ulink>
|
||||
<link linkend='build-directory'>Build Directory</link>
|
||||
<filename>conf/multiconfig</filename> directory
|
||||
(e.g.
|
||||
<replaceable>build_directory</replaceable><filename>/conf/multiconfig/configA.conf</filename>).
|
||||
@@ -1280,7 +1281,7 @@
|
||||
<filename>PATH</filename> variable.
|
||||
<note>
|
||||
If you run BitBake from a directory outside of the
|
||||
<ulink url='&YOCTO_DOCS_DEV_URL;build-directory'>Build Directory</ulink>,
|
||||
<link linkend='build-directory'>Build Directory</link>,
|
||||
you must be sure to set
|
||||
<filename>BBPATH</filename> to point to the
|
||||
Build Directory.
|
||||
@@ -1626,7 +1627,7 @@
|
||||
<para role="glossdeffirst">
|
||||
<!-- <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> -->
|
||||
Points to the location of the
|
||||
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>.
|
||||
<link linkend='build-directory'>Build Directory</link>.
|
||||
You can define this directory indirectly through the
|
||||
<link linkend='structure-core-script'><filename>&OE_INIT_FILE;</filename></link>
|
||||
and
|
||||
@@ -2595,7 +2596,7 @@
|
||||
You should only set this variable in the
|
||||
<filename>local.conf</filename> configuration file found
|
||||
in the
|
||||
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>.
|
||||
<link linkend='build-directory'>Build Directory</link>.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
@@ -2805,7 +2806,8 @@
|
||||
<para role="glossdeffirst">
|
||||
<!-- <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> -->
|
||||
The destination directory.
|
||||
The location in the <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>
|
||||
The location in the
|
||||
<link linkend='build-directory'>Build Directory</link>
|
||||
where components are installed by the
|
||||
<link linkend='ref-tasks-install'><filename>do_install</filename></link>
|
||||
task.
|
||||
@@ -3116,7 +3118,7 @@
|
||||
system uses to place images, packages, SDKs and other output
|
||||
files that are ready to be used outside of the build system.
|
||||
By default, this directory resides within the
|
||||
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>
|
||||
<link linkend='build-directory'>Build Directory</link>
|
||||
as <filename>${TMPDIR}/deploy</filename>.
|
||||
</para>
|
||||
|
||||
@@ -3189,7 +3191,7 @@
|
||||
The directory is machine-specific as it contains the
|
||||
<filename>${MACHINE}</filename> name.
|
||||
By default, this directory resides within the
|
||||
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>
|
||||
<link linkend='build-directory'>Build Directory</link>
|
||||
as <filename>${DEPLOY_DIR}/images/${MACHINE}/</filename>.
|
||||
</para>
|
||||
|
||||
@@ -3794,7 +3796,7 @@
|
||||
to touch it.
|
||||
By default, the directory is <filename>downloads</filename>
|
||||
in the
|
||||
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>.
|
||||
<link linkend='build-directory'>Build Directory</link>.
|
||||
<literallayout class='monospaced'>
|
||||
#DL_DIR ?= "${TOPDIR}/downloads"
|
||||
</literallayout>
|
||||
@@ -4191,7 +4193,7 @@
|
||||
<para>
|
||||
Typically, you configure this variable in your
|
||||
<filename>local.conf</filename> file, which is found in the
|
||||
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>.
|
||||
<link linkend='build-directory'>Build Directory</link>.
|
||||
Although you can use this variable from within a recipe,
|
||||
best practices dictate that you do not.
|
||||
<note>
|
||||
@@ -4761,7 +4763,7 @@
|
||||
<para>
|
||||
You define the <filename>FILESYSTEM_PERMS_TABLES</filename> variable in the
|
||||
<filename>conf/local.conf</filename> file, which is found in the
|
||||
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>, to
|
||||
<link linkend='build-directory'>Build Directory</link>, to
|
||||
point to your custom <filename>fs-perms.txt</filename>.
|
||||
You can specify more than a single file permissions setting table.
|
||||
The paths you specify to these files must be defined within the
|
||||
@@ -5613,7 +5615,7 @@
|
||||
Typically, you configure this variable in an image recipe.
|
||||
Although you can use this variable from your
|
||||
<filename>local.conf</filename> file, which is found in the
|
||||
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>,
|
||||
<link linkend='build-directory'>Build Directory</link>,
|
||||
best practices dictate that you do not.
|
||||
<note>
|
||||
To enable extra features from outside the image recipe,
|
||||
@@ -6562,7 +6564,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
|
||||
The combined binary is deposited into the
|
||||
<filename>tmp/deploy</filename> directory, which is part
|
||||
of the
|
||||
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>.
|
||||
<link linkend='build-directory'>Build Directory</link>.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
@@ -7941,7 +7943,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
|
||||
Specifies the target device for which the image is built.
|
||||
You define <filename>MACHINE</filename> in the
|
||||
<filename>local.conf</filename> file found in the
|
||||
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>.
|
||||
<link linkend='build-directory'>Build Directory</link>.
|
||||
By default, <filename>MACHINE</filename> is set to
|
||||
"qemux86", which is an x86-based architecture machine to
|
||||
be emulated using QEMU:
|
||||
@@ -9085,7 +9087,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
|
||||
This variable, which is set in the
|
||||
<filename>local.conf</filename> configuration file found in
|
||||
the <filename>conf</filename> folder of the
|
||||
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>,
|
||||
<link linkend='build-directory'>Build Directory</link>,
|
||||
specifies the package manager the OpenEmbedded build system
|
||||
uses when packaging data.
|
||||
</para>
|
||||
@@ -10531,7 +10533,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
|
||||
build system to attempt before any others by adding
|
||||
something like the following to the
|
||||
<filename>local.conf</filename> configuration file in the
|
||||
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>:
|
||||
<link linkend='build-directory'>Build Directory</link>:
|
||||
<literallayout class='monospaced'>
|
||||
PREMIRRORS_prepend = "\
|
||||
git://.*/.* http://www.yoctoproject.org/sources/ \n \
|
||||
@@ -11493,7 +11495,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
|
||||
<para role="glossdeffirst">
|
||||
<!-- <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> -->
|
||||
The location in the
|
||||
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>
|
||||
<link linkend='build-directory'>Build Directory</link>
|
||||
where unpacked recipe source code resides.
|
||||
By default, this directory is
|
||||
<filename>${</filename><link linkend='var-WORKDIR'><filename>WORKDIR</filename></link><filename>}/${</filename><link linkend='var-BPN'><filename>BPN</filename></link><filename>}-${</filename><link linkend='var-PV'><filename>PV</filename></link><filename>}</filename>,
|
||||
@@ -12411,7 +12413,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
|
||||
To enable file removal, set the variable to "1" in your
|
||||
<filename>conf/local.conf</filename> configuration file
|
||||
in your:
|
||||
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>.
|
||||
<link linkend='build-directory'>Build Directory</link>.
|
||||
<literallayout class='monospaced'>
|
||||
SKIP_FILEDEPS = "1"
|
||||
</literallayout>
|
||||
@@ -14263,7 +14265,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
|
||||
The suffix identifies the <filename>libc</filename> variant
|
||||
for building.
|
||||
When you are building for multiple variants with the same
|
||||
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>,
|
||||
<link linkend='build-directory'>Build Directory</link>,
|
||||
this mechanism ensures that output for different
|
||||
<filename>libc</filename> variants is kept separate to
|
||||
avoid potential conflicts.
|
||||
@@ -14421,7 +14423,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
|
||||
<filename>ssh</filename>.
|
||||
You can set this variable to "1" in your
|
||||
<filename>local.conf</filename> file in the
|
||||
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>
|
||||
<link linkend='build-directory'>Build Directory</link>
|
||||
to have the OpenEmbedded build system automatically run
|
||||
these tests after an image successfully builds:
|
||||
<literallayout class='monospaced'>
|
||||
@@ -14789,7 +14791,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
|
||||
files (other than the shared state cache).
|
||||
By default, the <filename>TMPDIR</filename> variable points
|
||||
to <filename>tmp</filename> within the
|
||||
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>.
|
||||
<link linkend='build-directory'>Build Directory</link>.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
@@ -14924,7 +14926,7 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
|
||||
<para role="glossdeffirst">
|
||||
<!-- <para role="glossdeffirst"><imagedata fileref="figures/define-generic.png" /> -->
|
||||
The top-level
|
||||
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>.
|
||||
<link linkend='build-directory'>Build Directory</link>.
|
||||
BitBake automatically sets this variable when you
|
||||
initialize your build environment using either
|
||||
<link linkend='structure-core-script'><filename>&OE_INIT_FILE;</filename></link>
|
||||
|
||||
Reference in New Issue
Block a user