diff options
Diffstat (limited to 'documentation/overview-manual/overview-manual-yp-intro.rst')
-rw-r--r-- | documentation/overview-manual/overview-manual-yp-intro.rst | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/documentation/overview-manual/overview-manual-yp-intro.rst b/documentation/overview-manual/overview-manual-yp-intro.rst index f01d9f7125..823c96d88c 100644 --- a/documentation/overview-manual/overview-manual-yp-intro.rst +++ b/documentation/overview-manual/overview-manual-yp-intro.rst | |||
@@ -319,14 +319,14 @@ applications using the Yocto Project: | |||
319 | 319 | ||
320 | The ``devtool`` command employs a number of sub-commands that allow | 320 | The ``devtool`` command employs a number of sub-commands that allow |
321 | you to add, modify, and upgrade recipes. As with the OpenEmbedded | 321 | you to add, modify, and upgrade recipes. As with the OpenEmbedded |
322 | build system, “recipes” represent software packages within | 322 | build system, "recipes" represent software packages within |
323 | ``devtool``. When you use ``devtool add``, a recipe is automatically | 323 | ``devtool``. When you use ``devtool add``, a recipe is automatically |
324 | created. When you use ``devtool modify``, the specified existing | 324 | created. When you use ``devtool modify``, the specified existing |
325 | recipe is used in order to determine where to get the source code and | 325 | recipe is used in order to determine where to get the source code and |
326 | how to patch it. In both cases, an environment is set up so that when | 326 | how to patch it. In both cases, an environment is set up so that when |
327 | you build the recipe a source tree that is under your control is used | 327 | you build the recipe a source tree that is under your control is used |
328 | in order to allow you to make changes to the source as desired. By | 328 | in order to allow you to make changes to the source as desired. By |
329 | default, both new recipes and the source go into a “workspace” | 329 | default, both new recipes and the source go into a "workspace" |
330 | directory under the eSDK. The ``devtool upgrade`` command updates an | 330 | directory under the eSDK. The ``devtool upgrade`` command updates an |
331 | existing recipe so that you can build it for an updated set of source | 331 | existing recipe so that you can build it for an updated set of source |
332 | files. | 332 | files. |
@@ -417,7 +417,7 @@ activities using the Yocto Project: | |||
417 | years ago. Both prelink and cross-prelink are maintained in the same | 417 | years ago. Both prelink and cross-prelink are maintained in the same |
418 | repository albeit on separate branches. By providing an emulated | 418 | repository albeit on separate branches. By providing an emulated |
419 | runtime dynamic linker (i.e. ``glibc``-derived ``ld.so`` emulation), | 419 | runtime dynamic linker (i.e. ``glibc``-derived ``ld.so`` emulation), |
420 | the cross-prelink project extends the prelink software’s ability to | 420 | the cross-prelink project extends the prelink software's ability to |
421 | prelink a sysroot environment. Additionally, the cross-prelink | 421 | prelink a sysroot environment. Additionally, the cross-prelink |
422 | software enables the ability to work in sysroot style environments. | 422 | software enables the ability to work in sysroot style environments. |
423 | 423 | ||
@@ -432,7 +432,7 @@ activities using the Yocto Project: | |||
432 | library code can be re-used from shared Copy-On-Write (COW) pages. | 432 | library code can be re-used from shared Copy-On-Write (COW) pages. |
433 | 433 | ||
434 | The original upstream prelink project only supports running prelink | 434 | The original upstream prelink project only supports running prelink |
435 | on the end target device due to the reliance on the target device’s | 435 | on the end target device due to the reliance on the target device's |
436 | dynamic linker. This restriction causes issues when developing a | 436 | dynamic linker. This restriction causes issues when developing a |
437 | cross-compiled system. The cross-prelink adds a synthesized dynamic | 437 | cross-compiled system. The cross-prelink adds a synthesized dynamic |
438 | loader that runs on the host, thus permitting cross-prelinking | 438 | loader that runs on the host, thus permitting cross-prelinking |
@@ -495,7 +495,7 @@ The following list consists of components associated with the | |||
495 | Sharing a core set of metadata results in Poky as an integration | 495 | Sharing a core set of metadata results in Poky as an integration |
496 | layer on top of OE-Core. You can see that in this | 496 | layer on top of OE-Core. You can see that in this |
497 | `figure <#yp-key-dev-elements>`__. The Yocto Project combines various | 497 | `figure <#yp-key-dev-elements>`__. The Yocto Project combines various |
498 | components such as BitBake, OE-Core, script “glue”, and documentation | 498 | components such as BitBake, OE-Core, script "glue", and documentation |
499 | for its build system. | 499 | for its build system. |
500 | 500 | ||
501 | .. _gs-reference-distribution-poky: | 501 | .. _gs-reference-distribution-poky: |
@@ -556,7 +556,7 @@ targets: | |||
556 | .. note:: | 556 | .. note:: |
557 | 557 | ||
558 | As best it can, opkg maintains backwards compatibility with ipkg | 558 | As best it can, opkg maintains backwards compatibility with ipkg |
559 | and conforms to a subset of Debian’s policy manual regarding | 559 | and conforms to a subset of Debian's policy manual regarding |
560 | control files. | 560 | control files. |
561 | 561 | ||
562 | .. _gs-archived-components: | 562 | .. _gs-archived-components: |