diff options
Diffstat (limited to 'documentation/overview-manual/overview-manual-concepts.rst')
-rw-r--r-- | documentation/overview-manual/overview-manual-concepts.rst | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/documentation/overview-manual/overview-manual-concepts.rst b/documentation/overview-manual/overview-manual-concepts.rst index bbf2d0494e..d2e335e802 100644 --- a/documentation/overview-manual/overview-manual-concepts.rst +++ b/documentation/overview-manual/overview-manual-concepts.rst | |||
@@ -34,7 +34,7 @@ itself is of various types: | |||
34 | 34 | ||
35 | BitBake knows how to combine multiple data sources together and refers | 35 | BitBake knows how to combine multiple data sources together and refers |
36 | to each data source as a layer. For information on layers, see the | 36 | to each data source as a layer. For information on layers, see the |
37 | ":ref:`dev-manual/dev-manual-common-tasks:understanding and creating layers`" | 37 | ":ref:`dev-manual/common-tasks:understanding and creating layers`" |
38 | section of the Yocto Project Development Tasks Manual. | 38 | section of the Yocto Project Development Tasks Manual. |
39 | 39 | ||
40 | Following are some brief details on these core components. For | 40 | Following are some brief details on these core components. For |
@@ -153,7 +153,7 @@ Conforming to a known structure allows BitBake to make assumptions | |||
153 | during builds on where to find types of metadata. You can find | 153 | during builds on where to find types of metadata. You can find |
154 | procedures and learn about tools (i.e. ``bitbake-layers``) for creating | 154 | procedures and learn about tools (i.e. ``bitbake-layers``) for creating |
155 | layers suitable for the Yocto Project in the | 155 | layers suitable for the Yocto Project in the |
156 | ":ref:`dev-manual/dev-manual-common-tasks:understanding and creating layers`" | 156 | ":ref:`dev-manual/common-tasks:understanding and creating layers`" |
157 | section of the Yocto Project Development Tasks Manual. | 157 | section of the Yocto Project Development Tasks Manual. |
158 | 158 | ||
159 | OpenEmbedded Build System Concepts | 159 | OpenEmbedded Build System Concepts |
@@ -317,7 +317,7 @@ during the build. By default, the layers listed in this file include | |||
317 | layers minimally needed by the build system. However, you must manually | 317 | layers minimally needed by the build system. However, you must manually |
318 | add any custom layers you have created. You can find more information on | 318 | add any custom layers you have created. You can find more information on |
319 | working with the ``bblayers.conf`` file in the | 319 | working with the ``bblayers.conf`` file in the |
320 | ":ref:`dev-manual/dev-manual-common-tasks:enabling your layer`" | 320 | ":ref:`dev-manual/common-tasks:enabling your layer`" |
321 | section in the Yocto Project Development Tasks Manual. | 321 | section in the Yocto Project Development Tasks Manual. |
322 | 322 | ||
323 | The files ``site.conf`` and ``auto.conf`` are not created by the | 323 | The files ``site.conf`` and ``auto.conf`` are not created by the |
@@ -418,7 +418,7 @@ a ``README`` file as good practice and especially if the layer is to be | |||
418 | distributed, a configuration directory, and recipe directories. You can | 418 | distributed, a configuration directory, and recipe directories. You can |
419 | learn about the general structure for layers used with the Yocto Project | 419 | learn about the general structure for layers used with the Yocto Project |
420 | in the | 420 | in the |
421 | ":ref:`dev-manual/dev-manual-common-tasks:creating your own layer`" | 421 | ":ref:`dev-manual/common-tasks:creating your own layer`" |
422 | section in the | 422 | section in the |
423 | Yocto Project Development Tasks Manual. For a general discussion on | 423 | Yocto Project Development Tasks Manual. For a general discussion on |
424 | layers and the many layers from which you can draw, see the | 424 | layers and the many layers from which you can draw, see the |
@@ -827,7 +827,7 @@ For more information on how the source directories are created, see the | |||
827 | "`Source Fetching <#source-fetching-dev-environment>`__" section. For | 827 | "`Source Fetching <#source-fetching-dev-environment>`__" section. For |
828 | more information on how to create patches and how the build system | 828 | more information on how to create patches and how the build system |
829 | processes patches, see the | 829 | processes patches, see the |
830 | ":ref:`dev-manual/dev-manual-common-tasks:patching code`" | 830 | ":ref:`dev-manual/common-tasks:patching code`" |
831 | section in the | 831 | section in the |
832 | Yocto Project Development Tasks Manual. You can also see the | 832 | Yocto Project Development Tasks Manual. You can also see the |
833 | ":ref:`sdk-manual/sdk-extensible:use \`\`devtool modify\`\` to modify the source of an existing component`" | 833 | ":ref:`sdk-manual/sdk-extensible:use \`\`devtool modify\`\` to modify the source of an existing component`" |
@@ -1029,7 +1029,7 @@ stage of package installation, post installation scripts that are part | |||
1029 | of the packages are run. Any scripts that fail to run on the build host | 1029 | of the packages are run. Any scripts that fail to run on the build host |
1030 | are run on the target when the target system is first booted. If you are | 1030 | are run on the target when the target system is first booted. If you are |
1031 | using a | 1031 | using a |
1032 | :ref:`read-only root filesystem <dev-manual/dev-manual-common-tasks:creating a read-only root filesystem>`, | 1032 | :ref:`read-only root filesystem <dev-manual/common-tasks:creating a read-only root filesystem>`, |
1033 | all the post installation scripts must succeed on the build host during | 1033 | all the post installation scripts must succeed on the build host during |
1034 | the package installation phase since the root filesystem on the target | 1034 | the package installation phase since the root filesystem on the target |
1035 | is read-only. | 1035 | is read-only. |
@@ -1192,7 +1192,7 @@ varflag. If some other task depends on such a task, then that task will | |||
1192 | also always be considered out of date, which might not be what you want. | 1192 | also always be considered out of date, which might not be what you want. |
1193 | 1193 | ||
1194 | For details on how to view information about a task's signature, see the | 1194 | For details on how to view information about a task's signature, see the |
1195 | ":ref:`dev-manual/dev-manual-common-tasks:viewing task variable dependencies`" | 1195 | ":ref:`dev-manual/common-tasks:viewing task variable dependencies`" |
1196 | section in the Yocto Project Development Tasks Manual. | 1196 | section in the Yocto Project Development Tasks Manual. |
1197 | 1197 | ||
1198 | Setscene Tasks and Shared State | 1198 | Setscene Tasks and Shared State |
@@ -1626,15 +1626,15 @@ them if they are deemed to be valid. | |||
1626 | the shared state packages. Consequently, considerations exist that | 1626 | the shared state packages. Consequently, considerations exist that |
1627 | affect maintaining shared state feeds. For information on how the | 1627 | affect maintaining shared state feeds. For information on how the |
1628 | build system works with packages and can track incrementing ``PR`` | 1628 | build system works with packages and can track incrementing ``PR`` |
1629 | information, see the ":ref:`dev-manual/dev-manual-common-tasks:automatically incrementing a package version number`" | 1629 | information, see the ":ref:`dev-manual/common-tasks:automatically incrementing a package version number`" |
1630 | section in the Yocto Project Development Tasks Manual. | 1630 | section in the Yocto Project Development Tasks Manual. |
1631 | 1631 | ||
1632 | - The code in the build system that supports incremental builds is | 1632 | - The code in the build system that supports incremental builds is |
1633 | not simple code. For techniques that help you work around issues | 1633 | not simple code. For techniques that help you work around issues |
1634 | related to shared state code, see the | 1634 | related to shared state code, see the |
1635 | ":ref:`dev-manual/dev-manual-common-tasks:viewing metadata used to create the input signature of a shared state task`" | 1635 | ":ref:`dev-manual/common-tasks:viewing metadata used to create the input signature of a shared state task`" |
1636 | and | 1636 | and |
1637 | ":ref:`dev-manual/dev-manual-common-tasks:invalidating shared state to force a task to run`" | 1637 | ":ref:`dev-manual/common-tasks:invalidating shared state to force a task to run`" |
1638 | sections both in the Yocto Project Development Tasks Manual. | 1638 | sections both in the Yocto Project Development Tasks Manual. |
1639 | 1639 | ||
1640 | The rest of this section goes into detail about the overall incremental | 1640 | The rest of this section goes into detail about the overall incremental |