diff options
Diffstat (limited to 'documentation/ref-manual/faq.rst')
-rw-r--r-- | documentation/ref-manual/faq.rst | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/documentation/ref-manual/faq.rst b/documentation/ref-manual/faq.rst index d3dac28b0f..07244a0311 100644 --- a/documentation/ref-manual/faq.rst +++ b/documentation/ref-manual/faq.rst | |||
@@ -8,7 +8,7 @@ FAQ | |||
8 | 8 | ||
9 | **A:** The term "`Poky <#>`__" refers to the specific reference build | 9 | **A:** The term "`Poky <#>`__" refers to the specific reference build |
10 | system that the Yocto Project provides. Poky is based on | 10 | system that the Yocto Project provides. Poky is based on |
11 | `OE-Core <#oe-core>`__ and `BitBake <#bitbake-term>`__. Thus, the | 11 | :term:`OpenEmbedded-Core (OE-Core)` and :term:`BitBake`. Thus, the |
12 | generic term used here for the build system is the "OpenEmbedded build | 12 | generic term used here for the build system is the "OpenEmbedded build |
13 | system." Development in the Yocto Project using Poky is closely tied to | 13 | system." Development in the Yocto Project using Poky is closely tied to |
14 | OpenEmbedded, with changes always being merged to OE-Core or BitBake | 14 | OpenEmbedded, with changes always being merged to OE-Core or BitBake |
@@ -29,7 +29,7 @@ steps on how to update your build tools. | |||
29 | 29 | ||
30 | **A:** There are three areas that help with stability; | 30 | **A:** There are three areas that help with stability; |
31 | 31 | ||
32 | - The Yocto Project team keeps `OE-Core <#oe-core>`__ small and | 32 | - The Yocto Project team keeps :term:`OpenEmbedded-Core (OE-Core)` small and |
33 | focused, containing around 830 recipes as opposed to the thousands | 33 | focused, containing around 830 recipes as opposed to the thousands |
34 | available in other OpenEmbedded community layers. Keeping it small | 34 | available in other OpenEmbedded community layers. Keeping it small |
35 | makes it easy to test and maintain. | 35 | makes it easy to test and maintain. |
@@ -227,19 +227,19 @@ meta-MACHINE/recipes-bsp/netbase/netbase_5.0.bbappend | |||
227 | size, you need to set various configurations: | 227 | size, you need to set various configurations: |
228 | 228 | ||
229 | - *Image Size:* The OpenEmbedded build system uses the | 229 | - *Image Size:* The OpenEmbedded build system uses the |
230 | ```IMAGE_ROOTFS_SIZE`` <#var-IMAGE_ROOTFS_SIZE>`__ variable to define | 230 | :term:`IMAGE_ROOTFS_SIZE` variable to define |
231 | the size of the image in Kbytes. The build system determines the size | 231 | the size of the image in Kbytes. The build system determines the size |
232 | by taking into account the initial root filesystem size before any | 232 | by taking into account the initial root filesystem size before any |
233 | modifications such as requested size for the image and any requested | 233 | modifications such as requested size for the image and any requested |
234 | additional free disk space to be added to the image. | 234 | additional free disk space to be added to the image. |
235 | 235 | ||
236 | - *Overhead:* Use the | 236 | - *Overhead:* Use the |
237 | ```IMAGE_OVERHEAD_FACTOR`` <#var-IMAGE_OVERHEAD_FACTOR>`__ variable | 237 | :term:`IMAGE_OVERHEAD_FACTOR` variable |
238 | to define the multiplier that the build system applies to the initial | 238 | to define the multiplier that the build system applies to the initial |
239 | image size, which is 1.3 by default. | 239 | image size, which is 1.3 by default. |
240 | 240 | ||
241 | - *Additional Free Space:* Use the | 241 | - *Additional Free Space:* Use the |
242 | ```IMAGE_ROOTFS_EXTRA_SPACE`` <#var-IMAGE_ROOTFS_EXTRA_SPACE>`__ | 242 | :term:`IMAGE_ROOTFS_EXTRA_SPACE` |
243 | variable to add additional free space to the image. The build system | 243 | variable to add additional free space to the image. The build system |
244 | adds this space to the image after it determines its | 244 | adds this space to the image after it determines its |
245 | ``IMAGE_ROOTFS_SIZE``. | 245 | ``IMAGE_ROOTFS_SIZE``. |
@@ -281,8 +281,8 @@ environments if HTTP transport is available. | |||
281 | 281 | ||
282 | When the build system searches for source code, it first tries the local | 282 | When the build system searches for source code, it first tries the local |
283 | download directory. If that location fails, Poky tries | 283 | download directory. If that location fails, Poky tries |
284 | ```PREMIRRORS`` <#var-PREMIRRORS>`__, the upstream source, and then | 284 | :term:`PREMIRRORS`, the upstream source, and then |
285 | ```MIRRORS`` <#var-MIRRORS>`__ in that order. | 285 | :term:`MIRRORS` in that order. |
286 | 286 | ||
287 | Assuming your distribution is "poky", the OpenEmbedded build system uses | 287 | Assuming your distribution is "poky", the OpenEmbedded build system uses |
288 | the Yocto Project source ``PREMIRRORS`` by default for SCM-based | 288 | the Yocto Project source ``PREMIRRORS`` by default for SCM-based |
@@ -409,7 +409,7 @@ my recipe is installing to the wrong place, or I am getting permissions | |||
409 | errors during the do_install task in my recipe! What is wrong? | 409 | errors during the do_install task in my recipe! What is wrong? |
410 | 410 | ||
411 | **A:** This situation results when a build system does not recognize the | 411 | **A:** This situation results when a build system does not recognize the |
412 | environment variables supplied to it by `BitBake <#bitbake-term>`__. The | 412 | environment variables supplied to it by :term:`BitBake`. The |
413 | incident that prompted this FAQ entry involved a Makefile that used an | 413 | incident that prompted this FAQ entry involved a Makefile that used an |
414 | environment variable named ``BINDIR`` instead of the more standard | 414 | environment variable named ``BINDIR`` instead of the more standard |
415 | variable ``bindir``. The makefile's hardcoded default value of | 415 | variable ``bindir``. The makefile's hardcoded default value of |