diff options
Diffstat (limited to 'documentation/ref-manual/faq.rst')
-rw-r--r-- | documentation/ref-manual/faq.rst | 11 |
1 files changed, 5 insertions, 6 deletions
diff --git a/documentation/ref-manual/faq.rst b/documentation/ref-manual/faq.rst index 07244a0311..3e8127b927 100644 --- a/documentation/ref-manual/faq.rst +++ b/documentation/ref-manual/faq.rst | |||
@@ -256,8 +256,7 @@ situation changes, the team will not support spaces in pathnames. | |||
256 | **A:** The toolchain configuration is very flexible and customizable. It | 256 | **A:** The toolchain configuration is very flexible and customizable. It |
257 | is primarily controlled with the ``TCMODE`` variable. This variable | 257 | is primarily controlled with the ``TCMODE`` variable. This variable |
258 | controls which ``tcmode-*.inc`` file to include from the | 258 | controls which ``tcmode-*.inc`` file to include from the |
259 | ``meta/conf/distro/include`` directory within the `Source | 259 | ``meta/conf/distro/include`` directory within the :term:`Source Directory`. |
260 | Directory <#source-directory>`__. | ||
261 | 260 | ||
262 | The default value of ``TCMODE`` is "default", which tells the | 261 | The default value of ``TCMODE`` is "default", which tells the |
263 | OpenEmbedded build system to use its internally built toolchain (i.e. | 262 | OpenEmbedded build system to use its internally built toolchain (i.e. |
@@ -342,8 +341,8 @@ redirect requests through proxy servers. | |||
342 | **A:** Yes - you can easily do this. When you use BitBake to build an | 341 | **A:** Yes - you can easily do this. When you use BitBake to build an |
343 | image, all the build output goes into the directory created when you run | 342 | image, all the build output goes into the directory created when you run |
344 | the build environment setup script (i.e. | 343 | the build environment setup script (i.e. |
345 | ````` <#structure-core-script>`__). By default, this `Build | 344 | ````` <#structure-core-script>`__). By default, this :term:`Build Directory` |
346 | Directory <#build-directory>`__ is named ``build`` but can be named | 345 | is named ``build`` but can be named |
347 | anything you want. | 346 | anything you want. |
348 | 347 | ||
349 | Within the Build Directory, is the ``tmp`` directory. To remove all the | 348 | Within the Build Directory, is the ``tmp`` directory. To remove all the |
@@ -379,8 +378,8 @@ system of that image. Thus, the build system provides a value of | |||
379 | "/usr/bin" for ``bindir``, a value of "/usr/lib" for ``libdir``, and so | 378 | "/usr/bin" for ``bindir``, a value of "/usr/lib" for ``libdir``, and so |
380 | forth. | 379 | forth. |
381 | 380 | ||
382 | Meanwhile, ``DESTDIR`` is a path within the `Build | 381 | Meanwhile, ``DESTDIR`` is a path within the :term:`Build Directory`. |
383 | Directory <#build-directory>`__. However, when the recipe builds a | 382 | However, when the recipe builds a |
384 | native program (i.e. one that is intended to run on the build machine), | 383 | native program (i.e. one that is intended to run on the build machine), |
385 | that program is never installed directly to the build machine's root | 384 | that program is never installed directly to the build machine's root |
386 | file system. Consequently, the build system uses paths within the Build | 385 | file system. Consequently, the build system uses paths within the Build |