summaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual/ref-structure.rst
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/ref-manual/ref-structure.rst')
-rw-r--r--documentation/ref-manual/ref-structure.rst15
1 files changed, 7 insertions, 8 deletions
diff --git a/documentation/ref-manual/ref-structure.rst b/documentation/ref-manual/ref-structure.rst
index c63900e604..a21c0bdd52 100644
--- a/documentation/ref-manual/ref-structure.rst
+++ b/documentation/ref-manual/ref-structure.rst
@@ -26,8 +26,7 @@ section in the Yocto Project Development Tasks Manual.
26Top-Level Core Components 26Top-Level Core Components
27========================= 27=========================
28 28
29This section describes the top-level components of the `Source 29This section describes the top-level components of the :term:`Source Directory`.
30Directory <#source-directory>`__.
31 30
32.. _structure-core-bitbake: 31.. _structure-core-bitbake:
33 32
@@ -57,8 +56,8 @@ Manual <&YOCTO_DOCS_BB_URL;>`__.
57 56
58This directory contains user configuration files and the output 57This directory contains user configuration files and the output
59generated by the OpenEmbedded build system in its standard configuration 58generated by the OpenEmbedded build system in its standard configuration
60where the source tree is combined with the output. The `Build 59where the source tree is combined with the output. The :term:`Build Directory`
61Directory <#build-directory>`__ is created initially when you ``source`` 60is created initially when you ``source``
62the OpenEmbedded build environment setup script (i.e. 61the OpenEmbedded build environment setup script (i.e.
63````` <#structure-core-script>`__). 62````` <#structure-core-script>`__).
64 63
@@ -175,8 +174,8 @@ creates the ``build/`` directory in your current working directory. If
175you provide a Build Directory argument when you ``source`` the script, 174you provide a Build Directory argument when you ``source`` the script,
176you direct the OpenEmbedded build system to create a Build Directory of 175you direct the OpenEmbedded build system to create a Build Directory of
177your choice. For example, the following command creates a Build 176your choice. For example, the following command creates a Build
178Directory named ``mybuilds/`` that is outside of the `Source 177Directory named ``mybuilds/`` that is outside of the :term:`Source Directory`:
179Directory <#source-directory>`__: $ source OE_INIT_FILE ~/mybuilds The 178$ source OE_INIT_FILE ~/mybuilds The
180OpenEmbedded build system uses the template configuration files, which 179OpenEmbedded build system uses the template configuration files, which
181are found by default in the ``meta-poky/conf/`` directory in the Source 180are found by default in the ``meta-poky/conf/`` directory in the Source
182Directory. See the "`Creating a Custom Template Configuration 181Directory. See the "`Creating a Custom Template Configuration
@@ -206,8 +205,8 @@ These files are standard top-level files.
206The Build Directory - ``build/`` 205The Build Directory - ``build/``
207================================ 206================================
208 207
209The OpenEmbedded build system creates the `Build 208The OpenEmbedded build system creates the :term:`Build Directory`
210Directory <#build-directory>`__ when you run the build environment setup 209when you run the build environment setup
211script ````` <#structure-core-script>`__. If you do not give the Build 210script ````` <#structure-core-script>`__. If you do not give the Build
212Directory a specific name when you run the setup script, the name 211Directory a specific name when you run the setup script, the name
213defaults to ``build/``. 212defaults to ``build/``.