summaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual/structure.rst
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/ref-manual/structure.rst')
-rw-r--r--documentation/ref-manual/structure.rst8
1 files changed, 4 insertions, 4 deletions
diff --git a/documentation/ref-manual/structure.rst b/documentation/ref-manual/structure.rst
index 262b041ea6..12a085552f 100644
--- a/documentation/ref-manual/structure.rst
+++ b/documentation/ref-manual/structure.rst
@@ -261,7 +261,7 @@ OpenEmbedded build system creates it from ``local.conf.sample`` when you
261:ref:`structure-core-script`. 261:ref:`structure-core-script`.
262 262
263The source ``local.conf.sample`` file used depends on the 263The source ``local.conf.sample`` file used depends on the
264``$TEMPLATECONF`` script variable, which defaults to ``meta-poky/conf/`` 264:term:`TEMPLATECONF` script variable, which defaults to ``meta-poky/conf/``
265when you are building from the Yocto Project development environment, 265when you are building from the Yocto Project development environment,
266and to ``meta/conf/`` when you are building from the OpenEmbedded-Core 266and to ``meta/conf/`` when you are building from the OpenEmbedded-Core
267environment. Because the script variable points to the source of the 267environment. Because the script variable points to the source of the
@@ -278,7 +278,7 @@ file, it uses ``sed`` to substitute final
278 278
279.. note:: 279.. note::
280 280
281 You can see how the ``TEMPLATECONF`` variable is used by looking at the 281 You can see how the :term:`TEMPLATECONF` variable is used by looking at the
282 ``scripts/oe-setup-builddir`` script in the :term:`Source Directory`. 282 ``scripts/oe-setup-builddir`` script in the :term:`Source Directory`.
283 You can find the Yocto Project version of the ``local.conf.sample`` file in 283 You can find the Yocto Project version of the ``local.conf.sample`` file in
284 the ``meta-poky/conf`` directory. 284 the ``meta-poky/conf`` directory.
@@ -300,7 +300,7 @@ you ``source`` the top-level build environment setup script (i.e.
300:ref:`structure-core-script`). 300:ref:`structure-core-script`).
301 301
302As with the ``local.conf`` file, the source ``bblayers.conf.sample`` 302As with the ``local.conf`` file, the source ``bblayers.conf.sample``
303file used depends on the ``$TEMPLATECONF`` script variable, which 303file used depends on the :term:`TEMPLATECONF` script variable, which
304defaults to ``meta-poky/conf/`` when you are building from the Yocto 304defaults to ``meta-poky/conf/`` when you are building from the Yocto
305Project development environment, and to ``meta/conf/`` when you are 305Project development environment, and to ``meta/conf/`` when you are
306building from the OpenEmbedded-Core environment. Because the script 306building from the OpenEmbedded-Core environment. Because the script
@@ -315,7 +315,7 @@ Once the build process gets the sample file, it uses ``sed`` to substitute final
315 315
316.. note:: 316.. note::
317 317
318 You can see how the ``TEMPLATECONF`` variable ``scripts/oe-setup-builddir`` 318 You can see how the :term:`TEMPLATECONF` variable is defined by the ``scripts/oe-setup-builddir``
319 script in the :term:`Source Directory`. You can find the Yocto Project 319 script in the :term:`Source Directory`. You can find the Yocto Project
320 version of the ``bblayers.conf.sample`` file in the ``meta-poky/conf/`` 320 version of the ``bblayers.conf.sample`` file in the ``meta-poky/conf/``
321 directory. 321 directory.