summaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual/closer-look.xml
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/ref-manual/closer-look.xml')
-rw-r--r--documentation/ref-manual/closer-look.xml10
1 files changed, 5 insertions, 5 deletions
diff --git a/documentation/ref-manual/closer-look.xml b/documentation/ref-manual/closer-look.xml
index c0f1747961..e4a2a022a7 100644
--- a/documentation/ref-manual/closer-look.xml
+++ b/documentation/ref-manual/closer-look.xml
@@ -114,7 +114,7 @@
114 114
115 <para> 115 <para>
116 Sourcing the build environment script creates a 116 Sourcing the build environment script creates a
117 <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink> 117 <link linkend='build-directory'>Build Directory</link>
118 if one does not already exist. 118 if one does not already exist.
119 BitBake uses the Build Directory for all its work during builds. 119 BitBake uses the Build Directory for all its work during builds.
120 The Build Directory has a <filename>conf</filename> directory that 120 The Build Directory has a <filename>conf</filename> directory that
@@ -641,7 +641,7 @@
641 <para> 641 <para>
642 When the OpenEmbedded build system generates an image or an SDK, 642 When the OpenEmbedded build system generates an image or an SDK,
643 it gets the packages from a package feed area located in the 643 it gets the packages from a package feed area located in the
644 <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>. 644 <link linkend='build-directory'>Build Directory</link>.
645 The 645 The
646 <link linkend='general-yocto-environment-figure'>general Yocto Project Development Environment figure</link> 646 <link linkend='general-yocto-environment-figure'>general Yocto Project Development Environment figure</link>
647 shows this package feeds area in the upper-right corner. 647 shows this package feeds area in the upper-right corner.
@@ -770,7 +770,7 @@
770 depend on it are re-executed. 770 depend on it are re-executed.
771 </note> 771 </note>
772 By default, everything is accomplished in the 772 By default, everything is accomplished in the
773 <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>, 773 <link linkend='build-directory'>Build Directory</link>,
774 which has a defined structure. 774 which has a defined structure.
775 For additional general information on the Build Directory, 775 For additional general information on the Build Directory,
776 see the 776 see the
@@ -1430,7 +1430,7 @@
1430 1430
1431 <para> 1431 <para>
1432 Images are written out to the 1432 Images are written out to the
1433 <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink> 1433 <link linkend='build-directory'>Build Directory</link>
1434 inside the <filename>tmp/deploy/images/<replaceable>machine</replaceable>/</filename> 1434 inside the <filename>tmp/deploy/images/<replaceable>machine</replaceable>/</filename>
1435 folder as shown in the figure. 1435 folder as shown in the figure.
1436 This folder contains any files expected to be loaded on the 1436 This folder contains any files expected to be loaded on the
@@ -1545,7 +1545,7 @@
1545 <para> 1545 <para>
1546 Once built, the SDK installers are written out to the 1546 Once built, the SDK installers are written out to the
1547 <filename>deploy/sdk</filename> folder inside the 1547 <filename>deploy/sdk</filename> folder inside the
1548 <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink> 1548 <link linkend='build-directory'>Build Directory</link>
1549 as shown in the figure at the beginning of this section. 1549 as shown in the figure at the beginning of this section.
1550 Depending on the type of SDK, several variables exist that help 1550 Depending on the type of SDK, several variables exist that help
1551 configure these files. 1551 configure these files.