diff options
25 files changed, 108 insertions, 108 deletions
diff --git a/documentation/brief-yoctoprojectqs/index.rst b/documentation/brief-yoctoprojectqs/index.rst index 51f684af01..5dc0bc7924 100644 --- a/documentation/brief-yoctoprojectqs/index.rst +++ b/documentation/brief-yoctoprojectqs/index.rst | |||
@@ -244,7 +244,7 @@ an entire Linux distribution, including the toolchain, from source. | |||
244 | $ bitbake core-image-sato | 244 | $ bitbake core-image-sato |
245 | 245 | ||
246 | For information on using the ``bitbake`` command, see the | 246 | For information on using the ``bitbake`` command, see the |
247 | :ref:`overview-manual/overview-manual-concepts:bitbake` section in the Yocto Project Overview and | 247 | :ref:`overview-manual/concepts:bitbake` section in the Yocto Project Overview and |
248 | Concepts Manual, or see the ":ref:`BitBake Command | 248 | Concepts Manual, or see the ":ref:`BitBake Command |
249 | <bitbake:bitbake-user-manual/bitbake-user-manual-intro:the bitbake command>`" section in the BitBake User Manual. | 249 | <bitbake:bitbake-user-manual/bitbake-user-manual-intro:the bitbake command>`" section in the BitBake User Manual. |
250 | 250 | ||
diff --git a/documentation/bsp-guide/bsp.rst b/documentation/bsp-guide/bsp.rst index e20df3f6b0..48bff35fa3 100644 --- a/documentation/bsp-guide/bsp.rst +++ b/documentation/bsp-guide/bsp.rst | |||
@@ -44,7 +44,7 @@ machine or platform name, which is "bsp_root_name" in the above form. | |||
44 | To help understand the BSP layer concept, consider the BSPs that the | 44 | To help understand the BSP layer concept, consider the BSPs that the |
45 | Yocto Project supports and provides with each release. You can see the | 45 | Yocto Project supports and provides with each release. You can see the |
46 | layers in the | 46 | layers in the |
47 | :ref:`overview-manual/overview-manual-development-environment:yocto project source repositories` | 47 | :ref:`overview-manual/development-environment:yocto project source repositories` |
48 | through | 48 | through |
49 | a web interface at :yocto_git:`/`. If you go to that interface, | 49 | a web interface at :yocto_git:`/`. If you go to that interface, |
50 | you will find a list of repositories under "Yocto Metadata Layers". | 50 | you will find a list of repositories under "Yocto Metadata Layers". |
@@ -253,7 +253,7 @@ developers can use this structure with other build systems besides the | |||
253 | OpenEmbedded build system. It is also intended that it will be be simple | 253 | OpenEmbedded build system. It is also intended that it will be be simple |
254 | to extract information and convert it to other formats if required. The | 254 | to extract information and convert it to other formats if required. The |
255 | OpenEmbedded build system, through its standard :ref:`layers mechanism | 255 | OpenEmbedded build system, through its standard :ref:`layers mechanism |
256 | <overview-manual/overview-manual-yp-intro:the yocto project layer model>`, can | 256 | <overview-manual/yp-intro:the yocto project layer model>`, can |
257 | directly accept the format described as a layer. The BSP layer captures | 257 | directly accept the format described as a layer. The BSP layer captures |
258 | all the hardware-specific details in one place using a standard format, | 258 | all the hardware-specific details in one place using a standard format, |
259 | which is useful for any person wishing to use the hardware platform | 259 | which is useful for any person wishing to use the hardware platform |
@@ -754,7 +754,7 @@ workflow. | |||
754 | are kept. The key point for a layer is that it is an isolated area | 754 | are kept. The key point for a layer is that it is an isolated area |
755 | that contains all the relevant information for the project that the | 755 | that contains all the relevant information for the project that the |
756 | OpenEmbedded build system knows about. For more information on | 756 | OpenEmbedded build system knows about. For more information on |
757 | layers, see the ":ref:`overview-manual/overview-manual-yp-intro:the yocto project layer model`" | 757 | layers, see the ":ref:`overview-manual/yp-intro:the yocto project layer model`" |
758 | section in the Yocto Project Overview and Concepts Manual. You can also | 758 | section in the Yocto Project Overview and Concepts Manual. You can also |
759 | reference the ":ref:`dev-manual/common-tasks:understanding and creating layers`" | 759 | reference the ":ref:`dev-manual/common-tasks:understanding and creating layers`" |
760 | section in the Yocto Project Development Tasks Manual. For more | 760 | section in the Yocto Project Development Tasks Manual. For more |
diff --git a/documentation/dev-manual/common-tasks.rst b/documentation/dev-manual/common-tasks.rst index fe3667bfb9..abeb1ed9c3 100644 --- a/documentation/dev-manual/common-tasks.rst +++ b/documentation/dev-manual/common-tasks.rst | |||
@@ -18,7 +18,7 @@ The OpenEmbedded build system supports organizing | |||
18 | Layers allow you to isolate different types of customizations from each | 18 | Layers allow you to isolate different types of customizations from each |
19 | other. For introductory information on the Yocto Project Layer Model, | 19 | other. For introductory information on the Yocto Project Layer Model, |
20 | see the | 20 | see the |
21 | ":ref:`overview-manual/overview-manual-yp-intro:the yocto project layer model`" | 21 | ":ref:`overview-manual/yp-intro:the yocto project layer model`" |
22 | section in the Yocto Project Overview and Concepts Manual. | 22 | section in the Yocto Project Overview and Concepts Manual. |
23 | 23 | ||
24 | Creating Your Own Layer | 24 | Creating Your Own Layer |
@@ -1319,7 +1319,7 @@ to determine how well the build went. | |||
1319 | ``log.do_fetch``, and ``log.do_compile``). | 1319 | ``log.do_fetch``, and ``log.do_compile``). |
1320 | 1320 | ||
1321 | You can find more information about the build process in | 1321 | You can find more information about the build process in |
1322 | ":doc:`/overview-manual/overview-manual-development-environment`" | 1322 | ":doc:`/overview-manual/development-environment`" |
1323 | chapter of the Yocto Project Overview and Concepts Manual. | 1323 | chapter of the Yocto Project Overview and Concepts Manual. |
1324 | 1324 | ||
1325 | Fetching Code | 1325 | Fetching Code |
@@ -1330,7 +1330,7 @@ files. Fetching is controlled mainly through the | |||
1330 | :term:`SRC_URI` variable. Your recipe | 1330 | :term:`SRC_URI` variable. Your recipe |
1331 | must have a ``SRC_URI`` variable that points to where the source is | 1331 | must have a ``SRC_URI`` variable that points to where the source is |
1332 | located. For a graphical representation of source locations, see the | 1332 | located. For a graphical representation of source locations, see the |
1333 | ":ref:`overview-manual/overview-manual-concepts:sources`" section in | 1333 | ":ref:`overview-manual/concepts:sources`" section in |
1334 | the Yocto Project Overview and Concepts Manual. | 1334 | the Yocto Project Overview and Concepts Manual. |
1335 | 1335 | ||
1336 | The :ref:`ref-tasks-fetch` task uses | 1336 | The :ref:`ref-tasks-fetch` task uses |
@@ -1599,7 +1599,7 @@ package "example" contains "libexample" and another package "mypackage" | |||
1599 | contains a binary that links to "libexample" then the OpenEmbedded build | 1599 | contains a binary that links to "libexample" then the OpenEmbedded build |
1600 | system will automatically add a runtime dependency to "mypackage" on | 1600 | system will automatically add a runtime dependency to "mypackage" on |
1601 | "example"). See the | 1601 | "example"). See the |
1602 | ":ref:`overview-manual/overview-manual-concepts:automatically added runtime dependencies`" | 1602 | ":ref:`overview-manual/concepts:automatically added runtime dependencies`" |
1603 | section in the Yocto Project Overview and Concepts Manual for further | 1603 | section in the Yocto Project Overview and Concepts Manual for further |
1604 | details. | 1604 | details. |
1605 | 1605 | ||
@@ -2486,7 +2486,7 @@ Reference Manual's variable glossary. | |||
2486 | 2486 | ||
2487 | - Using ``DEPENDS`` also allows runtime dependencies between | 2487 | - Using ``DEPENDS`` also allows runtime dependencies between |
2488 | packages to be added automatically. See the | 2488 | packages to be added automatically. See the |
2489 | ":ref:`overview-manual/overview-manual-concepts:automatically added runtime dependencies`" | 2489 | ":ref:`overview-manual/concepts:automatically added runtime dependencies`" |
2490 | section in the Yocto Project Overview and Concepts Manual for more | 2490 | section in the Yocto Project Overview and Concepts Manual for more |
2491 | information. | 2491 | information. |
2492 | 2492 | ||
@@ -3658,7 +3658,7 @@ build host running Linux. | |||
3658 | The build process creates an entire Linux distribution from source and | 3658 | The build process creates an entire Linux distribution from source and |
3659 | places it in your :term:`Build Directory` under | 3659 | places it in your :term:`Build Directory` under |
3660 | ``tmp/deploy/images``. For detailed information on the build process | 3660 | ``tmp/deploy/images``. For detailed information on the build process |
3661 | using BitBake, see the ":ref:`overview-manual/overview-manual-concepts:images`" section in the | 3661 | using BitBake, see the ":ref:`overview-manual/concepts:images`" section in the |
3662 | Yocto Project Overview and Concepts Manual. | 3662 | Yocto Project Overview and Concepts Manual. |
3663 | 3663 | ||
3664 | The following figure and list overviews the build process: | 3664 | The following figure and list overviews the build process: |
@@ -5490,7 +5490,7 @@ Using an Existing Kickstart File | |||
5490 | 5490 | ||
5491 | If you do not want to create your own kickstart file, you can use an | 5491 | If you do not want to create your own kickstart file, you can use an |
5492 | existing file provided by the Wic installation. As shipped, kickstart | 5492 | existing file provided by the Wic installation. As shipped, kickstart |
5493 | files can be found in the :ref:`overview-manual/overview-manual-development-environment:yocto project source repositories` in the | 5493 | files can be found in the :ref:`overview-manual/development-environment:yocto project source repositories` in the |
5494 | following two locations: | 5494 | following two locations: |
5495 | :: | 5495 | :: |
5496 | 5496 | ||
@@ -6526,7 +6526,7 @@ revision, respectively). The values are highly dependent on the policies | |||
6526 | and procedures of a given distribution and package feed. | 6526 | and procedures of a given distribution and package feed. |
6527 | 6527 | ||
6528 | Because the OpenEmbedded build system uses | 6528 | Because the OpenEmbedded build system uses |
6529 | ":ref:`signatures <overview-manual/overview-manual-concepts:checksums (signatures)>`", which are | 6529 | ":ref:`signatures <overview-manual/concepts:checksums (signatures)>`", which are |
6530 | unique to a given build, the build system knows when to rebuild | 6530 | unique to a given build, the build system knows when to rebuild |
6531 | packages. All the inputs into a given task are represented by a | 6531 | packages. All the inputs into a given task are represented by a |
6532 | signature, which can trigger a rebuild when different. Thus, the build | 6532 | signature, which can trigger a rebuild when different. Thus, the build |
@@ -6600,7 +6600,7 @@ Quality <#maintaining-build-output-quality>`__" section. | |||
6600 | use a PR Service while others do not leads to obvious problems. | 6600 | use a PR Service while others do not leads to obvious problems. |
6601 | 6601 | ||
6602 | For more information on shared state, see the | 6602 | For more information on shared state, see the |
6603 | ":ref:`overview-manual/overview-manual-concepts:shared state cache`" | 6603 | ":ref:`overview-manual/concepts:shared state cache`" |
6604 | section in the Yocto Project Overview and Concepts Manual. | 6604 | section in the Yocto Project Overview and Concepts Manual. |
6605 | 6605 | ||
6606 | Manually Bumping PR | 6606 | Manually Bumping PR |
@@ -6767,7 +6767,7 @@ multiple times if you have more than one set of modules to package. | |||
6767 | 6767 | ||
6768 | For more examples that show how to use ``do_split_packages``, see the | 6768 | For more examples that show how to use ``do_split_packages``, see the |
6769 | ``connman.inc`` file in the ``meta/recipes-connectivity/connman/`` | 6769 | ``connman.inc`` file in the ``meta/recipes-connectivity/connman/`` |
6770 | directory of the ``poky`` :ref:`source repository <overview-manual/overview-manual-development-environment:yocto project source repositories>`. You can | 6770 | directory of the ``poky`` :ref:`source repository <overview-manual/development-environment:yocto project source repositories>`. You can |
6771 | also find examples in ``meta/classes/kernel.bbclass``. | 6771 | also find examples in ``meta/classes/kernel.bbclass``. |
6772 | 6772 | ||
6773 | Following is a reference that shows ``do_split_packages`` mandatory and | 6773 | Following is a reference that shows ``do_split_packages`` mandatory and |
@@ -8080,7 +8080,7 @@ variable to "1" at the end of your ``conf/local.conf`` file found in the | |||
8080 | Enabling build history as | 8080 | Enabling build history as |
8081 | previously described causes the OpenEmbedded build system to collect | 8081 | previously described causes the OpenEmbedded build system to collect |
8082 | build output information and commit it as a single commit to a local | 8082 | build output information and commit it as a single commit to a local |
8083 | :ref:`overview-manual/overview-manual-development-environment:git` repository. | 8083 | :ref:`overview-manual/development-environment:git` repository. |
8084 | 8084 | ||
8085 | .. note:: | 8085 | .. note:: |
8086 | 8086 | ||
@@ -9394,7 +9394,7 @@ BitBake has determined by doing the following: | |||
9394 | ${BUILDDIR}/tmp/stamps/i586-poky-linux/db/6.0.30-r1.do_fetch.sigdata.7c048c18222b16ff0bcee2000ef648b1 | 9394 | ${BUILDDIR}/tmp/stamps/i586-poky-linux/db/6.0.30-r1.do_fetch.sigdata.7c048c18222b16ff0bcee2000ef648b1 |
9395 | 9395 | ||
9396 | For tasks that are accelerated through the shared state | 9396 | For tasks that are accelerated through the shared state |
9397 | (:ref:`sstate <overview-manual/overview-manual-concepts:shared state cache>`) cache, an | 9397 | (:ref:`sstate <overview-manual/concepts:shared state cache>`) cache, an |
9398 | additional ``siginfo`` file is written into | 9398 | additional ``siginfo`` file is written into |
9399 | :term:`SSTATE_DIR` along with | 9399 | :term:`SSTATE_DIR` along with |
9400 | the cached task output. The ``siginfo`` files contain exactly the | 9400 | the cached task output. The ``siginfo`` files contain exactly the |
@@ -9461,15 +9461,15 @@ files, see the "`Viewing Task Variable | |||
9461 | Dependencies <#dev-viewing-task-variable-dependencies>`__" section. | 9461 | Dependencies <#dev-viewing-task-variable-dependencies>`__" section. |
9462 | 9462 | ||
9463 | For conceptual information on shared state, see the | 9463 | For conceptual information on shared state, see the |
9464 | ":ref:`overview-manual/overview-manual-concepts:shared state`" | 9464 | ":ref:`overview-manual/concepts:shared state`" |
9465 | section in the Yocto Project Overview and Concepts Manual. | 9465 | section in the Yocto Project Overview and Concepts Manual. |
9466 | 9466 | ||
9467 | Invalidating Shared State to Force a Task to Run | 9467 | Invalidating Shared State to Force a Task to Run |
9468 | ------------------------------------------------ | 9468 | ------------------------------------------------ |
9469 | 9469 | ||
9470 | The OpenEmbedded build system uses | 9470 | The OpenEmbedded build system uses |
9471 | :ref:`checksums <overview-manual/overview-manual-concepts:checksums (signatures)>` and | 9471 | :ref:`checksums <overview-manual/concepts:checksums (signatures)>` and |
9472 | :ref:`overview-manual/overview-manual-concepts:shared state` cache to avoid unnecessarily | 9472 | :ref:`overview-manual/concepts:shared state` cache to avoid unnecessarily |
9473 | rebuilding tasks. Collectively, this scheme is known as "shared state | 9473 | rebuilding tasks. Collectively, this scheme is known as "shared state |
9474 | code". | 9474 | code". |
9475 | 9475 | ||
@@ -9530,7 +9530,7 @@ tasks (including tasks from other recipes) that the specified task | |||
9530 | depends on will be run before the task. Even when you manually specify a | 9530 | depends on will be run before the task. Even when you manually specify a |
9531 | task to run with ``-c``, BitBake will only run the task if it considers | 9531 | task to run with ``-c``, BitBake will only run the task if it considers |
9532 | it "out of date". See the | 9532 | it "out of date". See the |
9533 | ":ref:`overview-manual/overview-manual-concepts:stamp files and the rerunning of tasks`" | 9533 | ":ref:`overview-manual/concepts:stamp files and the rerunning of tasks`" |
9534 | section in the Yocto Project Overview and Concepts Manual for how | 9534 | section in the Yocto Project Overview and Concepts Manual for how |
9535 | BitBake determines whether a task is "out of date". | 9535 | BitBake determines whether a task is "out of date". |
9536 | 9536 | ||
@@ -10458,7 +10458,7 @@ Yocto general mailing list or on the openembedded-devel mailing list. | |||
10458 | You can also push a change upstream and request a maintainer to pull the | 10458 | You can also push a change upstream and request a maintainer to pull the |
10459 | change into the component's upstream repository. You do this by pushing | 10459 | change into the component's upstream repository. You do this by pushing |
10460 | to a contribution repository that is upstream. See the | 10460 | to a contribution repository that is upstream. See the |
10461 | ":ref:`overview-manual/overview-manual-development-environment:git workflows and the yocto project`" | 10461 | ":ref:`overview-manual/development-environment:git workflows and the yocto project`" |
10462 | section in the Yocto Project Overview and Concepts Manual for additional | 10462 | section in the Yocto Project Overview and Concepts Manual for additional |
10463 | concepts on working in the Yocto Project development environment. | 10463 | concepts on working in the Yocto Project development environment. |
10464 | 10464 | ||
@@ -10707,7 +10707,7 @@ been followed: | |||
10707 | located in the :term:`Source Directory` at | 10707 | located in the :term:`Source Directory` at |
10708 | ``meta/conf/distro/include``, to see who is responsible for code. | 10708 | ``meta/conf/distro/include``, to see who is responsible for code. |
10709 | 10709 | ||
10710 | - *Search by File:* Using :ref:`overview-manual/overview-manual-development-environment:git`, you can | 10710 | - *Search by File:* Using :ref:`overview-manual/development-environment:git`, you can |
10711 | enter the following command to bring up a short list of all | 10711 | enter the following command to bring up a short list of all |
10712 | commits against a specific file: | 10712 | commits against a specific file: |
10713 | :: | 10713 | :: |
@@ -10856,7 +10856,7 @@ follows: | |||
10856 | Working With Licenses | 10856 | Working With Licenses |
10857 | ===================== | 10857 | ===================== |
10858 | 10858 | ||
10859 | As mentioned in the ":ref:`overview-manual/overview-manual-development-environment:licensing`" | 10859 | As mentioned in the ":ref:`overview-manual/development-environment:licensing`" |
10860 | section in the Yocto Project Overview and Concepts Manual, open source | 10860 | section in the Yocto Project Overview and Concepts Manual, open source |
10861 | projects are open to the public and they consequently have different | 10861 | projects are open to the public and they consequently have different |
10862 | licensing structures in place. This section describes the mechanism by | 10862 | licensing structures in place. This section describes the mechanism by |
@@ -11299,7 +11299,7 @@ By releasing the version of the OpenEmbedded build system and the layers | |||
11299 | used during the build, you will be providing both compilation scripts | 11299 | used during the build, you will be providing both compilation scripts |
11300 | and the source code modifications in one step. | 11300 | and the source code modifications in one step. |
11301 | 11301 | ||
11302 | If the deployment team has a :ref:`overview-manual/overview-manual-concepts:bsp layer` | 11302 | If the deployment team has a :ref:`overview-manual/concepts:bsp layer` |
11303 | and a distro layer, and those | 11303 | and a distro layer, and those |
11304 | those layers are used to patch, compile, package, or modify (in any way) | 11304 | those layers are used to patch, compile, package, or modify (in any way) |
11305 | any open source software included in your released images, you might be | 11305 | any open source software included in your released images, you might be |
diff --git a/documentation/dev-manual/start.rst b/documentation/dev-manual/start.rst index 8244d68ed0..a26d2a3ead 100644 --- a/documentation/dev-manual/start.rst +++ b/documentation/dev-manual/start.rst | |||
@@ -78,7 +78,7 @@ particular working environment and set of practices. | |||
78 | developing under the control of an SCM system that is compatible | 78 | developing under the control of an SCM system that is compatible |
79 | with the OpenEmbedded build system is advisable. Of all of the SCMs | 79 | with the OpenEmbedded build system is advisable. Of all of the SCMs |
80 | supported by BitBake, the Yocto Project team strongly recommends using | 80 | supported by BitBake, the Yocto Project team strongly recommends using |
81 | :ref:`overview-manual/overview-manual-development-environment:git`. | 81 | :ref:`overview-manual/development-environment:git`. |
82 | Git is a distributed system | 82 | Git is a distributed system |
83 | that is easy to back up, allows you to work remotely, and then | 83 | that is easy to back up, allows you to work remotely, and then |
84 | connects back to the infrastructure. | 84 | connects back to the infrastructure. |
@@ -165,7 +165,7 @@ particular working environment and set of practices. | |||
165 | - Highlights when commits break the build. | 165 | - Highlights when commits break the build. |
166 | 166 | ||
167 | - Populates an :ref:`sstate | 167 | - Populates an :ref:`sstate |
168 | cache <overview-manual/overview-manual-concepts:shared state cache>` from which | 168 | cache <overview-manual/concepts:shared state cache>` from which |
169 | developers can pull rather than requiring local builds. | 169 | developers can pull rather than requiring local builds. |
170 | 170 | ||
171 | - Allows commit hook triggers, which trigger builds when commits | 171 | - Allows commit hook triggers, which trigger builds when commits |
@@ -218,17 +218,17 @@ particular working environment and set of practices. | |||
218 | some best practices exist within the Yocto Project development | 218 | some best practices exist within the Yocto Project development |
219 | environment. Consider the following: | 219 | environment. Consider the following: |
220 | 220 | ||
221 | - Use :ref:`overview-manual/overview-manual-development-environment:git` as the source control | 221 | - Use :ref:`overview-manual/development-environment:git` as the source control |
222 | system. | 222 | system. |
223 | 223 | ||
224 | - Maintain your Metadata in layers that make sense for your | 224 | - Maintain your Metadata in layers that make sense for your |
225 | situation. See the ":ref:`overview-manual/overview-manual-yp-intro:the yocto project layer model`" | 225 | situation. See the ":ref:`overview-manual/yp-intro:the yocto project layer model`" |
226 | section in the Yocto Project Overview and Concepts Manual and the | 226 | section in the Yocto Project Overview and Concepts Manual and the |
227 | ":ref:`dev-manual/common-tasks:understanding and creating layers`" | 227 | ":ref:`dev-manual/common-tasks:understanding and creating layers`" |
228 | section for more information on layers. | 228 | section for more information on layers. |
229 | 229 | ||
230 | - Separate the project's Metadata and code by using separate Git | 230 | - Separate the project's Metadata and code by using separate Git |
231 | repositories. See the ":ref:`overview-manual/overview-manual-development-environment:yocto project source repositories`" | 231 | repositories. See the ":ref:`overview-manual/development-environment:yocto project source repositories`" |
232 | section in the Yocto Project Overview and Concepts Manual for | 232 | section in the Yocto Project Overview and Concepts Manual for |
233 | information on these repositories. See the "`Locating Yocto | 233 | information on these repositories. See the "`Locating Yocto |
234 | Project Source Files <#locating-yocto-project-source-files>`__" | 234 | Project Source Files <#locating-yocto-project-source-files>`__" |
@@ -572,11 +572,11 @@ files you'll need to work with the Yocto Project. | |||
572 | .. note:: | 572 | .. note:: |
573 | 573 | ||
574 | - For concepts and introductory information about Git as it is used | 574 | - For concepts and introductory information about Git as it is used |
575 | in the Yocto Project, see the ":ref:`overview-manual/overview-manual-development-environment:git`" | 575 | in the Yocto Project, see the ":ref:`overview-manual/development-environment:git`" |
576 | section in the Yocto Project Overview and Concepts Manual. | 576 | section in the Yocto Project Overview and Concepts Manual. |
577 | 577 | ||
578 | - For concepts on Yocto Project source repositories, see the | 578 | - For concepts on Yocto Project source repositories, see the |
579 | ":ref:`overview-manual/overview-manual-development-environment:yocto project source repositories`" | 579 | ":ref:`overview-manual/development-environment:yocto project source repositories`" |
580 | section in the Yocto Project Overview and Concepts Manual." | 580 | section in the Yocto Project Overview and Concepts Manual." |
581 | 581 | ||
582 | Accessing Source Repositories | 582 | Accessing Source Repositories |
@@ -722,7 +722,7 @@ files is referred to as the :term:`Source Directory` | |||
722 | in the Yocto Project documentation. | 722 | in the Yocto Project documentation. |
723 | 723 | ||
724 | The preferred method of creating your Source Directory is by using | 724 | The preferred method of creating your Source Directory is by using |
725 | :ref:`overview-manual/overview-manual-development-environment:git` to clone a local copy of the upstream | 725 | :ref:`overview-manual/development-environment:git` to clone a local copy of the upstream |
726 | ``poky`` repository. Working from a cloned copy of the upstream | 726 | ``poky`` repository. Working from a cloned copy of the upstream |
727 | repository allows you to contribute back into the Yocto Project or to | 727 | repository allows you to contribute back into the Yocto Project or to |
728 | simply work with the latest software on a development branch. Because | 728 | simply work with the latest software on a development branch. Because |
diff --git a/documentation/kernel-dev/advanced.rst b/documentation/kernel-dev/advanced.rst index 163560b691..dd0b76bc31 100644 --- a/documentation/kernel-dev/advanced.rst +++ b/documentation/kernel-dev/advanced.rst | |||
@@ -16,7 +16,7 @@ complexity of the configuration and sources used to support multiple | |||
16 | BSPs and Linux kernel types. | 16 | BSPs and Linux kernel types. |
17 | 17 | ||
18 | Kernel Metadata exists in many places. One area in the | 18 | Kernel Metadata exists in many places. One area in the |
19 | :ref:`overview-manual/overview-manual-development-environment:yocto project source repositories` | 19 | :ref:`overview-manual/development-environment:yocto project source repositories` |
20 | is the ``yocto-kernel-cache`` Git repository. You can find this repository | 20 | is the ``yocto-kernel-cache`` Git repository. You can find this repository |
21 | grouped under the "Yocto Linux Kernel" heading in the | 21 | grouped under the "Yocto Linux Kernel" heading in the |
22 | :yocto_git:`Yocto Project Source Repositories <>`. | 22 | :yocto_git:`Yocto Project Source Repositories <>`. |
@@ -386,7 +386,7 @@ type as follows: | |||
386 | .. note:: | 386 | .. note:: |
387 | 387 | ||
388 | You can find kernel recipes in the ``meta/recipes-kernel/linux`` directory | 388 | You can find kernel recipes in the ``meta/recipes-kernel/linux`` directory |
389 | of the :ref:`overview-manual/overview-manual-development-environment:yocto project source repositories` | 389 | of the :ref:`overview-manual/development-environment:yocto project source repositories` |
390 | (e.g. ``poky/meta/recipes-kernel/linux/linux-yocto_4.12.bb``). See the | 390 | (e.g. ``poky/meta/recipes-kernel/linux/linux-yocto_4.12.bb``). See the |
391 | ":ref:`kernel-dev/advanced:using kernel metadata in a recipe`" | 391 | ":ref:`kernel-dev/advanced:using kernel metadata in a recipe`" |
392 | section for more information. | 392 | section for more information. |
diff --git a/documentation/kernel-dev/common.rst b/documentation/kernel-dev/common.rst index 403a63d584..67f8777c4f 100644 --- a/documentation/kernel-dev/common.rst +++ b/documentation/kernel-dev/common.rst | |||
@@ -63,7 +63,7 @@ section: | |||
63 | .. note:: | 63 | .. note:: |
64 | 64 | ||
65 | The previous commands assume the | 65 | The previous commands assume the |
66 | :ref:`overview-manual/overview-manual-development-environment:yocto project source repositories` | 66 | :ref:`overview-manual/development-environment:yocto project source repositories` |
67 | (i.e. ``poky``) have been cloned using Git and the local repository is named | 67 | (i.e. ``poky``) have been cloned using Git and the local repository is named |
68 | "poky". | 68 | "poky". |
69 | 69 | ||
@@ -249,7 +249,7 @@ section: | |||
249 | .. note:: | 249 | .. note:: |
250 | 250 | ||
251 | The previous commands assume the | 251 | The previous commands assume the |
252 | :ref:`overview-manual/overview-manual-development-environment:yocto project source repositories` | 252 | :ref:`overview-manual/development-environment:yocto project source repositories` |
253 | (i.e. ``poky``) have been cloned using Git and the local repository is named | 253 | (i.e. ``poky``) have been cloned using Git and the local repository is named |
254 | "poky". | 254 | "poky". |
255 | 255 | ||
diff --git a/documentation/kernel-dev/concepts-appx.rst b/documentation/kernel-dev/concepts-appx.rst index 865f6d8bef..4b6dbe5ef9 100644 --- a/documentation/kernel-dev/concepts-appx.rst +++ b/documentation/kernel-dev/concepts-appx.rst | |||
@@ -35,7 +35,7 @@ Yocto Project Linux kernel that caters to specific embedded designer | |||
35 | needs for targeted hardware. | 35 | needs for targeted hardware. |
36 | 36 | ||
37 | You can find a web interface to the Yocto Linux kernels in the | 37 | You can find a web interface to the Yocto Linux kernels in the |
38 | :ref:`overview-manual/overview-manual-development-environment:yocto project source repositories` | 38 | :ref:`overview-manual/development-environment:yocto project source repositories` |
39 | at :yocto_git:`/`. If you look at the interface, you will see to | 39 | at :yocto_git:`/`. If you look at the interface, you will see to |
40 | the left a grouping of Git repositories titled "Yocto Linux Kernel". | 40 | the left a grouping of Git repositories titled "Yocto Linux Kernel". |
41 | Within this group, you will find several Linux Yocto kernels developed | 41 | Within this group, you will find several Linux Yocto kernels developed |
@@ -160,7 +160,7 @@ implemented by the Yocto Project team using the Source Code Manager | |||
160 | 160 | ||
161 | - You can find documentation on Git at https://git-scm.com/doc. You can | 161 | - You can find documentation on Git at https://git-scm.com/doc. You can |
162 | also get an introduction to Git as it applies to the Yocto Project in the | 162 | also get an introduction to Git as it applies to the Yocto Project in the |
163 | ":ref:`overview-manual/overview-manual-development-environment:git`" section in the Yocto Project | 163 | ":ref:`overview-manual/development-environment:git`" section in the Yocto Project |
164 | Overview and Concepts Manual. The latter reference provides an | 164 | Overview and Concepts Manual. The latter reference provides an |
165 | overview of Git and presents a minimal set of Git commands that | 165 | overview of Git and presents a minimal set of Git commands that |
166 | allows you to be functional using Git. You can use as much, or as | 166 | allows you to be functional using Git. You can use as much, or as |
@@ -258,7 +258,7 @@ Yocto Linux kernel needed for any given set of requirements. | |||
258 | Yocto Linux kernels, but rather shows a single generic kernel just | 258 | Yocto Linux kernels, but rather shows a single generic kernel just |
259 | for conceptual purposes. Also keep in mind that this structure | 259 | for conceptual purposes. Also keep in mind that this structure |
260 | represents the | 260 | represents the |
261 | :ref:`overview-manual/overview-manual-development-environment:yocto project source repositories` | 261 | :ref:`overview-manual/development-environment:yocto project source repositories` |
262 | that are either pulled from during the build or established on the | 262 | that are either pulled from during the build or established on the |
263 | host development system prior to the build by either cloning a | 263 | host development system prior to the build by either cloning a |
264 | particular kernel's Git repository or by downloading and unpacking a | 264 | particular kernel's Git repository or by downloading and unpacking a |
diff --git a/documentation/overview-manual/overview-manual-concepts.rst b/documentation/overview-manual/concepts.rst index a10670fc58..8aa86c06e9 100644 --- a/documentation/overview-manual/overview-manual-concepts.rst +++ b/documentation/overview-manual/concepts.rst | |||
@@ -40,7 +40,7 @@ section of the Yocto Project Development Tasks Manual. | |||
40 | Following are some brief details on these core components. For | 40 | Following are some brief details on these core components. For |
41 | additional information on how these components interact during a build, | 41 | additional information on how these components interact during a build, |
42 | see the | 42 | see the |
43 | ":ref:`overview-manual/overview-manual-concepts:openembedded build system concepts`" | 43 | ":ref:`overview-manual/concepts:openembedded build system concepts`" |
44 | section. | 44 | section. |
45 | 45 | ||
46 | BitBake | 46 | BitBake |
@@ -1109,7 +1109,7 @@ the extensible SDK (eSDK): | |||
1109 | .. note:: | 1109 | .. note:: |
1110 | 1110 | ||
1111 | For more information on the cross-development toolchain generation, | 1111 | For more information on the cross-development toolchain generation, |
1112 | see the ":ref:`overview-manual/overview-manual-concepts:cross-development toolchain generation`" | 1112 | see the ":ref:`overview-manual/concepts:cross-development toolchain generation`" |
1113 | section. For information on advantages gained when building a | 1113 | section. For information on advantages gained when building a |
1114 | cross-development toolchain using the do_populate_sdk task, see the | 1114 | cross-development toolchain using the do_populate_sdk task, see the |
1115 | ":ref:`sdk-manual/sdk-appendix-obtain:building an sdk installer`" section in | 1115 | ":ref:`sdk-manual/sdk-appendix-obtain:building an sdk installer`" section in |
diff --git a/documentation/overview-manual/overview-manual-development-environment.rst b/documentation/overview-manual/development-environment.rst index 9a2997d9fc..9a2997d9fc 100644 --- a/documentation/overview-manual/overview-manual-development-environment.rst +++ b/documentation/overview-manual/development-environment.rst | |||
diff --git a/documentation/overview-manual/index.rst b/documentation/overview-manual/index.rst index f20b20e328..123aed9b8b 100644 --- a/documentation/overview-manual/index.rst +++ b/documentation/overview-manual/index.rst | |||
@@ -10,10 +10,10 @@ Yocto Project Overview and Concepts Manual | |||
10 | :caption: Table of Contents | 10 | :caption: Table of Contents |
11 | :numbered: | 11 | :numbered: |
12 | 12 | ||
13 | overview-manual-intro | 13 | intro |
14 | overview-manual-yp-intro | 14 | yp-intro |
15 | overview-manual-development-environment | 15 | development-environment |
16 | overview-manual-concepts | 16 | concepts |
17 | history | 17 | history |
18 | 18 | ||
19 | .. include:: /boilerplate.rst | 19 | .. include:: /boilerplate.rst |
diff --git a/documentation/overview-manual/overview-manual-intro.rst b/documentation/overview-manual/intro.rst index 50c623c3b9..bd247dd45c 100644 --- a/documentation/overview-manual/overview-manual-intro.rst +++ b/documentation/overview-manual/intro.rst | |||
@@ -28,7 +28,7 @@ The following list describes what you can get from this manual: | |||
28 | Yocto Project source repositories, workflows using Git and the Yocto | 28 | Yocto Project source repositories, workflows using Git and the Yocto |
29 | Project, a Git primer, and information about licensing. | 29 | Project, a Git primer, and information about licensing. |
30 | 30 | ||
31 | - :doc:`overview-manual-concepts` *:* This | 31 | - :doc:`/overview-manual/concepts` *:* This |
32 | chapter presents various concepts regarding the Yocto Project. You | 32 | chapter presents various concepts regarding the Yocto Project. You |
33 | can find conceptual information about components, development, | 33 | can find conceptual information about components, development, |
34 | cross-toolchains, and so forth. | 34 | cross-toolchains, and so forth. |
diff --git a/documentation/overview-manual/overview-manual-yp-intro.rst b/documentation/overview-manual/yp-intro.rst index a6568d1c8e..3afbb9378f 100644 --- a/documentation/overview-manual/overview-manual-yp-intro.rst +++ b/documentation/overview-manual/yp-intro.rst | |||
@@ -589,7 +589,7 @@ Project. | |||
589 | .. note:: | 589 | .. note:: |
590 | 590 | ||
591 | For additional detail about the Yocto Project development | 591 | For additional detail about the Yocto Project development |
592 | environment, see the ":doc:`overview-manual-development-environment`" | 592 | environment, see the ":doc:`/overview-manual/development-environment`" |
593 | chapter. | 593 | chapter. |
594 | 594 | ||
595 | - *Native Linux Host:* By far the best option for a Build Host. A | 595 | - *Native Linux Host:* By far the best option for a Build Host. A |
diff --git a/documentation/ref-manual/faq.rst b/documentation/ref-manual/faq.rst index 5b9fcc1912..cc6b3aee1b 100644 --- a/documentation/ref-manual/faq.rst +++ b/documentation/ref-manual/faq.rst | |||
@@ -198,7 +198,7 @@ and also any configuration information about how that package was | |||
198 | configured and built. | 198 | configured and built. |
199 | 199 | ||
200 | You can find more information on licensing in the | 200 | You can find more information on licensing in the |
201 | ":ref:`overview-manual/overview-manual-development-environment:licensing`" | 201 | ":ref:`overview-manual/development-environment:licensing`" |
202 | section in the Yocto | 202 | section in the Yocto |
203 | Project Overview and Concepts Manual and also in the | 203 | Project Overview and Concepts Manual and also in the |
204 | ":ref:`dev-manual/common-tasks:maintaining open source license compliance during your product's lifecycle`" | 204 | ":ref:`dev-manual/common-tasks:maintaining open source license compliance during your product's lifecycle`" |
diff --git a/documentation/ref-manual/migration-1.7.rst b/documentation/ref-manual/migration-1.7.rst index 85894d9df7..177d40900f 100644 --- a/documentation/ref-manual/migration-1.7.rst +++ b/documentation/ref-manual/migration-1.7.rst | |||
@@ -26,7 +26,7 @@ QEMU, you should now have these lines in ``local.conf``: | |||
26 | Minimum Git version | 26 | Minimum Git version |
27 | ------------------- | 27 | ------------------- |
28 | 28 | ||
29 | The minimum :ref:`overview-manual/overview-manual-development-environment:git` | 29 | The minimum :ref:`overview-manual/development-environment:git` |
30 | version required on the | 30 | version required on the |
31 | build host is now 1.7.8 because the ``--list`` option is now required by | 31 | build host is now 1.7.8 because the ``--list`` option is now required by |
32 | BitBake's Git fetcher. As always, if your host distribution does not | 32 | BitBake's Git fetcher. As always, if your host distribution does not |
diff --git a/documentation/ref-manual/migration-2.3.rst b/documentation/ref-manual/migration-2.3.rst index 9e95f45e1f..6984ff91e8 100644 --- a/documentation/ref-manual/migration-2.3.rst +++ b/documentation/ref-manual/migration-2.3.rst | |||
@@ -51,7 +51,7 @@ Consider the following: | |||
51 | :term:`SYSROOT_PREPROCESS_FUNCS`. | 51 | :term:`SYSROOT_PREPROCESS_FUNCS`. |
52 | 52 | ||
53 | For an example, see the ``pixbufcache`` class in ``meta/classes/`` in | 53 | For an example, see the ``pixbufcache`` class in ``meta/classes/`` in |
54 | the :ref:`overview-manual/overview-manual-development-environment:yocto project source repositories`. | 54 | the :ref:`overview-manual/development-environment:yocto project source repositories`. |
55 | 55 | ||
56 | .. note:: | 56 | .. note:: |
57 | 57 | ||
diff --git a/documentation/ref-manual/ref-classes.rst b/documentation/ref-manual/ref-classes.rst index 914ca42324..900341e5ac 100644 --- a/documentation/ref-manual/ref-classes.rst +++ b/documentation/ref-manual/ref-classes.rst | |||
@@ -406,7 +406,7 @@ cross-compilation tools. | |||
406 | 406 | ||
407 | The ``cross-canadian`` class provides support for the recipes that build | 407 | The ``cross-canadian`` class provides support for the recipes that build |
408 | the Canadian Cross-compilation tools for SDKs. See the | 408 | the Canadian Cross-compilation tools for SDKs. See the |
409 | ":ref:`overview-manual/overview-manual-concepts:cross-development toolchain generation`" | 409 | ":ref:`overview-manual/concepts:cross-development toolchain generation`" |
410 | section in the Yocto Project Overview and Concepts Manual for more | 410 | section in the Yocto Project Overview and Concepts Manual for more |
411 | discussion on these cross-compilation tools. | 411 | discussion on these cross-compilation tools. |
412 | 412 | ||
@@ -417,7 +417,7 @@ discussion on these cross-compilation tools. | |||
417 | 417 | ||
418 | The ``crosssdk`` class provides support for the recipes that build the | 418 | The ``crosssdk`` class provides support for the recipes that build the |
419 | cross-compilation tools used for building SDKs. See the | 419 | cross-compilation tools used for building SDKs. See the |
420 | ":ref:`overview-manual/overview-manual-concepts:cross-development toolchain generation`" | 420 | ":ref:`overview-manual/concepts:cross-development toolchain generation`" |
421 | section in the Yocto Project Overview and Concepts Manual for more | 421 | section in the Yocto Project Overview and Concepts Manual for more |
422 | discussion on these cross-compilation tools. | 422 | discussion on these cross-compilation tools. |
423 | 423 | ||
@@ -930,7 +930,7 @@ For information on customizing images, see the | |||
930 | ":ref:`dev-manual/common-tasks:customizing images`" section | 930 | ":ref:`dev-manual/common-tasks:customizing images`" section |
931 | in the Yocto Project Development Tasks Manual. For information on how | 931 | in the Yocto Project Development Tasks Manual. For information on how |
932 | images are created, see the | 932 | images are created, see the |
933 | ":ref:`overview-manual/overview-manual-concepts:images`" section in the | 933 | ":ref:`overview-manual/concepts:images`" section in the |
934 | Yocto Project Overview and Concpets Manual. | 934 | Yocto Project Overview and Concpets Manual. |
935 | 935 | ||
936 | .. _ref-classes-image-buildinfo: | 936 | .. _ref-classes-image-buildinfo: |
@@ -2039,7 +2039,7 @@ These classes are inherited by and used with the ``populate_sdk_base`` | |||
2039 | class. | 2039 | class. |
2040 | 2040 | ||
2041 | For more information on the cross-development toolchain generation, see | 2041 | For more information on the cross-development toolchain generation, see |
2042 | the ":ref:`overview-manual/overview-manual-concepts:cross-development toolchain generation`" | 2042 | the ":ref:`overview-manual/concepts:cross-development toolchain generation`" |
2043 | section in the Yocto Project Overview and Concepts Manual. For | 2043 | section in the Yocto Project Overview and Concepts Manual. For |
2044 | information on advantages gained when building a cross-development | 2044 | information on advantages gained when building a cross-development |
2045 | toolchain using the :ref:`ref-tasks-populate_sdk` | 2045 | toolchain using the :ref:`ref-tasks-populate_sdk` |
@@ -2268,7 +2268,7 @@ The root filesystem is created from packages using one of the | |||
2268 | :term:`PACKAGE_CLASSES` variable. | 2268 | :term:`PACKAGE_CLASSES` variable. |
2269 | 2269 | ||
2270 | For information on how root filesystem images are created, see the | 2270 | For information on how root filesystem images are created, see the |
2271 | ":ref:`overview-manual/overview-manual-concepts:image generation`" | 2271 | ":ref:`overview-manual/concepts:image generation`" |
2272 | section in the Yocto Project Overview and Concepts Manual. | 2272 | section in the Yocto Project Overview and Concepts Manual. |
2273 | 2273 | ||
2274 | .. _ref-classes-sanity: | 2274 | .. _ref-classes-sanity: |
@@ -2375,7 +2375,7 @@ default, the class is enabled through the | |||
2375 | :term:`INHERIT_DISTRO` variable's default value. | 2375 | :term:`INHERIT_DISTRO` variable's default value. |
2376 | 2376 | ||
2377 | For more information on sstate, see the | 2377 | For more information on sstate, see the |
2378 | ":ref:`overview-manual/overview-manual-concepts:shared state cache`" | 2378 | ":ref:`overview-manual/concepts:shared state cache`" |
2379 | section in the Yocto Project Overview and Concepts Manual. | 2379 | section in the Yocto Project Overview and Concepts Manual. |
2380 | 2380 | ||
2381 | .. _ref-classes-staging: | 2381 | .. _ref-classes-staging: |
diff --git a/documentation/ref-manual/ref-release-process.rst b/documentation/ref-manual/ref-release-process.rst index 54cd9510f6..20be09a4ff 100644 --- a/documentation/ref-manual/ref-release-process.rst +++ b/documentation/ref-manual/ref-release-process.rst | |||
@@ -50,7 +50,7 @@ Major Release Codenames | |||
50 | ======================= | 50 | ======================= |
51 | 51 | ||
52 | Each major release receives a codename that identifies the release in | 52 | Each major release receives a codename that identifies the release in |
53 | the :ref:`overview-manual/overview-manual-development-environment:yocto project source repositories`. | 53 | the :ref:`overview-manual/development-environment:yocto project source repositories`. |
54 | The concept is that branches of :term:`Metadata` with the same | 54 | The concept is that branches of :term:`Metadata` with the same |
55 | codename are likely to be compatible and thus work together. | 55 | codename are likely to be compatible and thus work together. |
56 | 56 | ||
diff --git a/documentation/ref-manual/ref-structure.rst b/documentation/ref-manual/ref-structure.rst index b681e8233f..606a77c7fa 100644 --- a/documentation/ref-manual/ref-structure.rst +++ b/documentation/ref-manual/ref-structure.rst | |||
@@ -399,8 +399,8 @@ This directory contains any "end result" output from the OpenEmbedded | |||
399 | build process. The :term:`DEPLOY_DIR` variable points | 399 | build process. The :term:`DEPLOY_DIR` variable points |
400 | to this directory. For more detail on the contents of the ``deploy`` | 400 | to this directory. For more detail on the contents of the ``deploy`` |
401 | directory, see the | 401 | directory, see the |
402 | ":ref:`overview-manual/overview-manual-concepts:images`" and | 402 | ":ref:`overview-manual/concepts:images`" and |
403 | ":ref:`overview-manual/overview-manual-concepts:application development sdk`" sections in the Yocto | 403 | ":ref:`overview-manual/concepts:application development sdk`" sections in the Yocto |
404 | Project Overview and Concepts Manual. | 404 | Project Overview and Concepts Manual. |
405 | 405 | ||
406 | .. _structure-build-tmp-deploy-deb: | 406 | .. _structure-build-tmp-deploy-deb: |
@@ -545,7 +545,7 @@ and timestamps for tracking purposes. | |||
545 | 545 | ||
546 | For information on how BitBake uses stamp files to determine if a task | 546 | For information on how BitBake uses stamp files to determine if a task |
547 | should be rerun, see the | 547 | should be rerun, see the |
548 | ":ref:`overview-manual/overview-manual-concepts:stamp files and the rerunning of tasks`" | 548 | ":ref:`overview-manual/concepts:stamp files and the rerunning of tasks`" |
549 | section in the Yocto Project Overview and Concepts Manual. | 549 | section in the Yocto Project Overview and Concepts Manual. |
550 | 550 | ||
551 | .. _structure-build-tmp-log: | 551 | .. _structure-build-tmp-log: |
diff --git a/documentation/ref-manual/ref-system-requirements.rst b/documentation/ref-manual/ref-system-requirements.rst index d162c9bad2..66afb08102 100644 --- a/documentation/ref-manual/ref-system-requirements.rst +++ b/documentation/ref-manual/ref-system-requirements.rst | |||
@@ -15,7 +15,7 @@ Yocto Project. | |||
15 | 15 | ||
16 | For introductory information on the Yocto Project, see the | 16 | For introductory information on the Yocto Project, see the |
17 | :yocto_home:`Yocto Project Website <>` and the | 17 | :yocto_home:`Yocto Project Website <>` and the |
18 | ":ref:`overview-manual/overview-manual-development-environment:the yocto project development environment`" | 18 | ":ref:`overview-manual/development-environment:the yocto project development environment`" |
19 | chapter in the Yocto Project Overview and Concepts Manual. | 19 | chapter in the Yocto Project Overview and Concepts Manual. |
20 | 20 | ||
21 | If you want to use the Yocto Project to quickly build an image without | 21 | If you want to use the Yocto Project to quickly build an image without |
diff --git a/documentation/ref-manual/ref-tasks.rst b/documentation/ref-manual/ref-tasks.rst index 768c10eebd..8b9e0c2d89 100644 --- a/documentation/ref-manual/ref-tasks.rst +++ b/documentation/ref-manual/ref-tasks.rst | |||
@@ -140,7 +140,7 @@ The ``do_image`` task performs pre-processing on the image through the | |||
140 | :term:`IMAGE_PREPROCESS_COMMAND` and | 140 | :term:`IMAGE_PREPROCESS_COMMAND` and |
141 | dynamically generates supporting ``do_image_*`` tasks as needed. | 141 | dynamically generates supporting ``do_image_*`` tasks as needed. |
142 | 142 | ||
143 | For more information on image creation, see the ":ref:`overview-manual/overview-manual-concepts:image generation`" | 143 | For more information on image creation, see the ":ref:`overview-manual/concepts:image generation`" |
144 | section in the Yocto Project Overview and Concepts Manual. | 144 | section in the Yocto Project Overview and Concepts Manual. |
145 | 145 | ||
146 | .. _ref-tasks-image-complete: | 146 | .. _ref-tasks-image-complete: |
@@ -159,7 +159,7 @@ through the | |||
159 | :term:`IMAGE_POSTPROCESS_COMMAND`. | 159 | :term:`IMAGE_POSTPROCESS_COMMAND`. |
160 | 160 | ||
161 | For more information on image creation, see the | 161 | For more information on image creation, see the |
162 | ":ref:`overview-manual/overview-manual-concepts:image generation`" | 162 | ":ref:`overview-manual/concepts:image generation`" |
163 | section in the Yocto Project Overview and Concepts Manual. | 163 | section in the Yocto Project Overview and Concepts Manual. |
164 | 164 | ||
165 | .. _ref-tasks-install: | 165 | .. _ref-tasks-install: |
@@ -174,7 +174,7 @@ compilation directory. The ``do_install`` task, as well as other tasks | |||
174 | that either directly or indirectly depend on the installed files (e.g. | 174 | that either directly or indirectly depend on the installed files (e.g. |
175 | :ref:`ref-tasks-package`, ``do_package_write_*``, and | 175 | :ref:`ref-tasks-package`, ``do_package_write_*``, and |
176 | :ref:`ref-tasks-rootfs`), run under | 176 | :ref:`ref-tasks-rootfs`), run under |
177 | :ref:`fakeroot <overview-manual/overview-manual-concepts:fakeroot and pseudo>`. | 177 | :ref:`fakeroot <overview-manual/concepts:fakeroot and pseudo>`. |
178 | 178 | ||
179 | .. note:: | 179 | .. note:: |
180 | 180 | ||
@@ -218,7 +218,7 @@ The ``do_package`` task, in conjunction with the | |||
218 | :ref:`ref-tasks-packagedata` task, also saves some | 218 | :ref:`ref-tasks-packagedata` task, also saves some |
219 | important package metadata. For additional information, see the | 219 | important package metadata. For additional information, see the |
220 | :term:`PKGDESTWORK` variable and the | 220 | :term:`PKGDESTWORK` variable and the |
221 | ":ref:`overview-manual/overview-manual-concepts:automatically added runtime dependencies`" | 221 | ":ref:`overview-manual/concepts:automatically added runtime dependencies`" |
222 | section in the Yocto Project Overview and Concepts Manual. | 222 | section in the Yocto Project Overview and Concepts Manual. |
223 | 223 | ||
224 | .. _ref-tasks-package_qa: | 224 | .. _ref-tasks-package_qa: |
@@ -237,7 +237,7 @@ see the :ref:`insane <ref-classes-insane>` class. | |||
237 | Creates Debian packages (i.e. ``*.deb`` files) and places them in the | 237 | Creates Debian packages (i.e. ``*.deb`` files) and places them in the |
238 | ``${``\ :term:`DEPLOY_DIR_DEB`\ ``}`` directory in | 238 | ``${``\ :term:`DEPLOY_DIR_DEB`\ ``}`` directory in |
239 | the package feeds area. For more information, see the | 239 | the package feeds area. For more information, see the |
240 | ":ref:`overview-manual/overview-manual-concepts:package feeds`" section in | 240 | ":ref:`overview-manual/concepts:package feeds`" section in |
241 | the Yocto Project Overview and Concepts Manual. | 241 | the Yocto Project Overview and Concepts Manual. |
242 | 242 | ||
243 | .. _ref-tasks-package_write_ipk: | 243 | .. _ref-tasks-package_write_ipk: |
@@ -248,7 +248,7 @@ the Yocto Project Overview and Concepts Manual. | |||
248 | Creates IPK packages (i.e. ``*.ipk`` files) and places them in the | 248 | Creates IPK packages (i.e. ``*.ipk`` files) and places them in the |
249 | ``${``\ :term:`DEPLOY_DIR_IPK`\ ``}`` directory in | 249 | ``${``\ :term:`DEPLOY_DIR_IPK`\ ``}`` directory in |
250 | the package feeds area. For more information, see the | 250 | the package feeds area. For more information, see the |
251 | ":ref:`overview-manual/overview-manual-concepts:package feeds`" section in | 251 | ":ref:`overview-manual/concepts:package feeds`" section in |
252 | the Yocto Project Overview and Concepts Manual. | 252 | the Yocto Project Overview and Concepts Manual. |
253 | 253 | ||
254 | .. _ref-tasks-package_write_rpm: | 254 | .. _ref-tasks-package_write_rpm: |
@@ -259,7 +259,7 @@ the Yocto Project Overview and Concepts Manual. | |||
259 | Creates RPM packages (i.e. ``*.rpm`` files) and places them in the | 259 | Creates RPM packages (i.e. ``*.rpm`` files) and places them in the |
260 | ``${``\ :term:`DEPLOY_DIR_RPM`\ ``}`` directory in | 260 | ``${``\ :term:`DEPLOY_DIR_RPM`\ ``}`` directory in |
261 | the package feeds area. For more information, see the | 261 | the package feeds area. For more information, see the |
262 | ":ref:`overview-manual/overview-manual-concepts:package feeds`" section in | 262 | ":ref:`overview-manual/concepts:package feeds`" section in |
263 | the Yocto Project Overview and Concepts Manual. | 263 | the Yocto Project Overview and Concepts Manual. |
264 | 264 | ||
265 | .. _ref-tasks-package_write_tar: | 265 | .. _ref-tasks-package_write_tar: |
@@ -270,7 +270,7 @@ the Yocto Project Overview and Concepts Manual. | |||
270 | Creates tarballs and places them in the | 270 | Creates tarballs and places them in the |
271 | ``${``\ :term:`DEPLOY_DIR_TAR`\ ``}`` directory in | 271 | ``${``\ :term:`DEPLOY_DIR_TAR`\ ``}`` directory in |
272 | the package feeds area. For more information, see the | 272 | the package feeds area. For more information, see the |
273 | ":ref:`overview-manual/overview-manual-concepts:package feeds`" section in | 273 | ":ref:`overview-manual/concepts:package feeds`" section in |
274 | the Yocto Project Overview and Concepts Manual. | 274 | the Yocto Project Overview and Concepts Manual. |
275 | 275 | ||
276 | .. _ref-tasks-packagedata: | 276 | .. _ref-tasks-packagedata: |
@@ -349,7 +349,7 @@ patch files end with either ``.patch`` or ``.diff``, every file would be | |||
349 | applied as a patch by default except for the ``patch_file5`` patch. | 349 | applied as a patch by default except for the ``patch_file5`` patch. |
350 | 350 | ||
351 | You can find out more about the patching process in the | 351 | You can find out more about the patching process in the |
352 | ":ref:`overview-manual/overview-manual-concepts:patching`" section in | 352 | ":ref:`overview-manual/concepts:patching`" section in |
353 | the Yocto Project Overview and Concepts Manual and the | 353 | the Yocto Project Overview and Concepts Manual and the |
354 | ":ref:`dev-manual/common-tasks:patching code`" section in the | 354 | ":ref:`dev-manual/common-tasks:patching code`" section in the |
355 | Yocto Project Development Tasks Manual. | 355 | Yocto Project Development Tasks Manual. |
@@ -368,7 +368,7 @@ the image is constructed. | |||
368 | ------------------- | 368 | ------------------- |
369 | 369 | ||
370 | Creates the file and directory structure for an installable SDK. See the | 370 | Creates the file and directory structure for an installable SDK. See the |
371 | ":ref:`overview-manual/overview-manual-concepts:sdk generation`" | 371 | ":ref:`overview-manual/concepts:sdk generation`" |
372 | section in the Yocto Project Overview and Concepts Manual for more | 372 | section in the Yocto Project Overview and Concepts Manual for more |
373 | information. | 373 | information. |
374 | 374 | ||
@@ -378,7 +378,7 @@ information. | |||
378 | ----------------------- | 378 | ----------------------- |
379 | 379 | ||
380 | Creates the file and directory structure for an installable extensible | 380 | Creates the file and directory structure for an installable extensible |
381 | SDK (eSDK). See the ":ref:`overview-manual/overview-manual-concepts:sdk generation`" | 381 | SDK (eSDK). See the ":ref:`overview-manual/concepts:sdk generation`" |
382 | section in the Yocto Project Overview and Concepts Manual for more | 382 | section in the Yocto Project Overview and Concepts Manual for more |
383 | information. | 383 | information. |
384 | 384 | ||
@@ -434,7 +434,7 @@ Unpacks the source code into a working directory pointed to by | |||
434 | ``${``\ :term:`WORKDIR`\ ``}``. The :term:`S` | 434 | ``${``\ :term:`WORKDIR`\ ``}``. The :term:`S` |
435 | variable also plays a role in where unpacked source files ultimately | 435 | variable also plays a role in where unpacked source files ultimately |
436 | reside. For more information on how source files are unpacked, see the | 436 | reside. For more information on how source files are unpacked, see the |
437 | ":ref:`overview-manual/overview-manual-concepts:source fetching`" | 437 | ":ref:`overview-manual/concepts:source fetching`" |
438 | section in the Yocto Project Overview and Concepts Manual and also see | 438 | section in the Yocto Project Overview and Concepts Manual and also see |
439 | the ``WORKDIR`` and ``S`` variable descriptions. | 439 | the ``WORKDIR`` and ``S`` variable descriptions. |
440 | 440 | ||
@@ -500,7 +500,7 @@ You can run this task using BitBake as follows: | |||
500 | $ bitbake -c clean recipe | 500 | $ bitbake -c clean recipe |
501 | 501 | ||
502 | Running this task does not remove the | 502 | Running this task does not remove the |
503 | :ref:`sstate <overview-manual/overview-manual-concepts:shared state cache>` cache files. | 503 | :ref:`sstate <overview-manual/concepts:shared state cache>` cache files. |
504 | Consequently, if no changes have been made and the recipe is rebuilt | 504 | Consequently, if no changes have been made and the recipe is rebuilt |
505 | after cleaning, output files are simply restored from the sstate cache. | 505 | after cleaning, output files are simply restored from the sstate cache. |
506 | If you want to remove the sstate cache files for the recipe, you need to | 506 | If you want to remove the sstate cache files for the recipe, you need to |
@@ -513,7 +513,7 @@ use the :ref:`ref-tasks-cleansstate` task instead | |||
513 | --------------- | 513 | --------------- |
514 | 514 | ||
515 | Removes all output files, shared state | 515 | Removes all output files, shared state |
516 | (:ref:`sstate <overview-manual/overview-manual-concepts:shared state cache>`) cache, and | 516 | (:ref:`sstate <overview-manual/concepts:shared state cache>`) cache, and |
517 | downloaded source files for a target (i.e. the contents of | 517 | downloaded source files for a target (i.e. the contents of |
518 | :term:`DL_DIR`). Essentially, the ``do_cleanall`` task is | 518 | :term:`DL_DIR`). Essentially, the ``do_cleanall`` task is |
519 | identical to the :ref:`ref-tasks-cleansstate` task | 519 | identical to the :ref:`ref-tasks-cleansstate` task |
@@ -534,10 +534,10 @@ task. | |||
534 | ------------------ | 534 | ------------------ |
535 | 535 | ||
536 | Removes all output files and shared state | 536 | Removes all output files and shared state |
537 | (:ref:`sstate <overview-manual/overview-manual-concepts:shared state cache>`) cache for a | 537 | (:ref:`sstate <overview-manual/concepts:shared state cache>`) cache for a |
538 | target. Essentially, the ``do_cleansstate`` task is identical to the | 538 | target. Essentially, the ``do_cleansstate`` task is identical to the |
539 | :ref:`ref-tasks-clean` task with the added removal of | 539 | :ref:`ref-tasks-clean` task with the added removal of |
540 | shared state (:ref:`sstate <overview-manual/overview-manual-concepts:shared state cache>`) | 540 | shared state (:ref:`sstate <overview-manual/concepts:shared state cache>`) |
541 | cache. | 541 | cache. |
542 | 542 | ||
543 | You can run this task using BitBake as follows: | 543 | You can run this task using BitBake as follows: |
@@ -593,7 +593,7 @@ Lists all defined tasks for a target. | |||
593 | ``do_package_index`` | 593 | ``do_package_index`` |
594 | -------------------- | 594 | -------------------- |
595 | 595 | ||
596 | Creates or updates the index in the :ref:`overview-manual/overview-manual-concepts:package feeds` area. | 596 | Creates or updates the index in the :ref:`overview-manual/concepts:package feeds` area. |
597 | 597 | ||
598 | .. note:: | 598 | .. note:: |
599 | 599 | ||
@@ -631,7 +631,7 @@ has some more information about these types of images. | |||
631 | ------------- | 631 | ------------- |
632 | 632 | ||
633 | Creates the root filesystem (file and directory structure) for an image. | 633 | Creates the root filesystem (file and directory structure) for an image. |
634 | See the ":ref:`overview-manual/overview-manual-concepts:image generation`" | 634 | See the ":ref:`overview-manual/concepts:image generation`" |
635 | section in the Yocto Project Overview and Concepts Manual for more | 635 | section in the Yocto Project Overview and Concepts Manual for more |
636 | information on how the root filesystem is created. | 636 | information on how the root filesystem is created. |
637 | 637 | ||
diff --git a/documentation/ref-manual/ref-terms.rst b/documentation/ref-manual/ref-terms.rst index ba1930ebda..f41073602d 100644 --- a/documentation/ref-manual/ref-terms.rst +++ b/documentation/ref-manual/ref-terms.rst | |||
@@ -160,7 +160,7 @@ universal, the list includes them just in case: | |||
160 | 160 | ||
161 | Creation of these toolchains is simple and automated. For information on | 161 | Creation of these toolchains is simple and automated. For information on |
162 | toolchain concepts as they apply to the Yocto Project, see the | 162 | toolchain concepts as they apply to the Yocto Project, see the |
163 | ":ref:`overview-manual/overview-manual-concepts:Cross-Development | 163 | ":ref:`overview-manual/concepts:Cross-Development |
164 | Toolchain Generation`" section in the Yocto Project Overview and Concepts | 164 | Toolchain Generation`" section in the Yocto Project Overview and Concepts |
165 | Manual. You can also find more information on using the relocatable | 165 | Manual. You can also find more information on using the relocatable |
166 | toolchain in the :doc:`/sdk-manual/index` manual. | 166 | toolchain in the :doc:`/sdk-manual/index` manual. |
@@ -189,7 +189,7 @@ universal, the list includes them just in case: | |||
189 | layers used within Yocto Project. | 189 | layers used within Yocto Project. |
190 | 190 | ||
191 | For introductory information on layers, see the | 191 | For introductory information on layers, see the |
192 | ":ref:`overview-manual/overview-manual-yp-intro:The Yocto Project Layer | 192 | ":ref:`overview-manual/yp-intro:The Yocto Project Layer |
193 | Model`" section in the Yocto Project Overview and Concepts Manual. For | 193 | Model`" section in the Yocto Project Overview and Concepts Manual. For |
194 | more detailed information on layers, see the | 194 | more detailed information on layers, see the |
195 | ":ref:`dev-manual/common-tasks:Understanding and Creating | 195 | ":ref:`dev-manual/common-tasks:Understanding and Creating |
@@ -366,7 +366,7 @@ universal, the list includes them just in case: | |||
366 | 366 | ||
367 | For more information on concepts related to Git repositories, | 367 | For more information on concepts related to Git repositories, |
368 | branches, and tags, see the | 368 | branches, and tags, see the |
369 | ":ref:`overview-manual/overview-manual-development-environment:repositories, tags, and branches`" | 369 | ":ref:`overview-manual/development-environment:repositories, tags, and branches`" |
370 | section in the Yocto Project Overview and Concepts Manual. | 370 | section in the Yocto Project Overview and Concepts Manual. |
371 | 371 | ||
372 | :term:`Task` | 372 | :term:`Task` |
diff --git a/documentation/ref-manual/ref-variables.rst b/documentation/ref-manual/ref-variables.rst index d98e358173..a8a949b92a 100644 --- a/documentation/ref-manual/ref-variables.rst +++ b/documentation/ref-manual/ref-variables.rst | |||
@@ -1016,7 +1016,7 @@ system and gives an overview of their function and contents. | |||
1016 | (SDK). | 1016 | (SDK). |
1017 | 1017 | ||
1018 | - *task:* Save output file signatures for | 1018 | - *task:* Save output file signatures for |
1019 | :ref:`shared state <overview-manual/overview-manual-concepts:shared state cache>` | 1019 | :ref:`shared state <overview-manual/concepts:shared state cache>` |
1020 | (sstate) tasks. | 1020 | (sstate) tasks. |
1021 | This saves one file per task and lists the SHA-256 checksums for | 1021 | This saves one file per task and lists the SHA-256 checksums for |
1022 | each file staged (i.e. the output of the task). | 1022 | each file staged (i.e. the output of the task). |
@@ -1522,7 +1522,7 @@ system and gives an overview of their function and contents. | |||
1522 | .. note:: | 1522 | .. note:: |
1523 | 1523 | ||
1524 | Tasks that read from or write to this directory should run under | 1524 | Tasks that read from or write to this directory should run under |
1525 | :ref:`fakeroot <overview-manual/overview-manual-concepts:fakeroot and pseudo>`. | 1525 | :ref:`fakeroot <overview-manual/concepts:fakeroot and pseudo>`. |
1526 | 1526 | ||
1527 | :term:`DATE` | 1527 | :term:`DATE` |
1528 | The date the build was started. Dates appear using the year, month, | 1528 | The date the build was started. Dates appear using the year, month, |
@@ -1641,7 +1641,7 @@ system and gives an overview of their function and contents. | |||
1641 | - One recipe having another recipe in ``DEPENDS`` does not by | 1641 | - One recipe having another recipe in ``DEPENDS`` does not by |
1642 | itself add any runtime dependencies between the packages | 1642 | itself add any runtime dependencies between the packages |
1643 | produced by the two recipes. However, as explained in the | 1643 | produced by the two recipes. However, as explained in the |
1644 | ":ref:`overview-manual/overview-manual-concepts:automatically added runtime dependencies`" | 1644 | ":ref:`overview-manual/concepts:automatically added runtime dependencies`" |
1645 | section in the Yocto Project Overview and Concepts Manual, | 1645 | section in the Yocto Project Overview and Concepts Manual, |
1646 | runtime dependencies will often be added automatically, meaning | 1646 | runtime dependencies will often be added automatically, meaning |
1647 | ``DEPENDS`` alone is sufficient for most recipes. | 1647 | ``DEPENDS`` alone is sufficient for most recipes. |
@@ -1672,9 +1672,9 @@ system and gives an overview of their function and contents. | |||
1672 | For more information on the structure of the Build Directory, see | 1672 | For more information on the structure of the Build Directory, see |
1673 | ":ref:`ref-manual/ref-structure:the build directory - \`\`build/\`\``" section. | 1673 | ":ref:`ref-manual/ref-structure:the build directory - \`\`build/\`\``" section. |
1674 | For more detail on the contents of the ``deploy`` directory, see the | 1674 | For more detail on the contents of the ``deploy`` directory, see the |
1675 | ":ref:`overview-manual/overview-manual-concepts:images`", | 1675 | ":ref:`overview-manual/concepts:images`", |
1676 | ":ref:`overview-manual/overview-manual-concepts:package feeds`", and | 1676 | ":ref:`overview-manual/concepts:package feeds`", and |
1677 | ":ref:`overview-manual/overview-manual-concepts:application development sdk`" sections all in the | 1677 | ":ref:`overview-manual/concepts:application development sdk`" sections all in the |
1678 | Yocto Project Overview and Concepts Manual. | 1678 | Yocto Project Overview and Concepts Manual. |
1679 | 1679 | ||
1680 | :term:`DEPLOY_DIR_DEB` | 1680 | :term:`DEPLOY_DIR_DEB` |
@@ -1696,7 +1696,7 @@ system and gives an overview of their function and contents. | |||
1696 | :ref:`ref-tasks-package_write_deb` task | 1696 | :ref:`ref-tasks-package_write_deb` task |
1697 | writes Debian packages into the appropriate folder. For more | 1697 | writes Debian packages into the appropriate folder. For more |
1698 | information on how packaging works, see the | 1698 | information on how packaging works, see the |
1699 | ":ref:`overview-manual/overview-manual-concepts:package feeds`" section | 1699 | ":ref:`overview-manual/concepts:package feeds`" section |
1700 | in the Yocto Project Overview and Concepts Manual. | 1700 | in the Yocto Project Overview and Concepts Manual. |
1701 | 1701 | ||
1702 | :term:`DEPLOY_DIR_IMAGE` | 1702 | :term:`DEPLOY_DIR_IMAGE` |
@@ -1710,8 +1710,8 @@ system and gives an overview of their function and contents. | |||
1710 | For more information on the structure of the Build Directory, see | 1710 | For more information on the structure of the Build Directory, see |
1711 | ":ref:`ref-manual/ref-structure:the build directory - \`\`build/\`\``" section. | 1711 | ":ref:`ref-manual/ref-structure:the build directory - \`\`build/\`\``" section. |
1712 | For more detail on the contents of the ``deploy`` directory, see the | 1712 | For more detail on the contents of the ``deploy`` directory, see the |
1713 | ":ref:`overview-manual/overview-manual-concepts:images`" and | 1713 | ":ref:`overview-manual/concepts:images`" and |
1714 | ":ref:`overview-manual/overview-manual-concepts:application development sdk`" sections both in | 1714 | ":ref:`overview-manual/concepts:application development sdk`" sections both in |
1715 | the Yocto Project Overview and Concepts Manual. | 1715 | the Yocto Project Overview and Concepts Manual. |
1716 | 1716 | ||
1717 | :term:`DEPLOY_DIR_IPK` | 1717 | :term:`DEPLOY_DIR_IPK` |
@@ -1732,7 +1732,7 @@ system and gives an overview of their function and contents. | |||
1732 | :ref:`ref-tasks-package_write_ipk` task | 1732 | :ref:`ref-tasks-package_write_ipk` task |
1733 | writes IPK packages into the appropriate folder. For more information | 1733 | writes IPK packages into the appropriate folder. For more information |
1734 | on how packaging works, see the | 1734 | on how packaging works, see the |
1735 | ":ref:`overview-manual/overview-manual-concepts:package feeds`" section | 1735 | ":ref:`overview-manual/concepts:package feeds`" section |
1736 | in the Yocto Project Overview and Concepts Manual. | 1736 | in the Yocto Project Overview and Concepts Manual. |
1737 | 1737 | ||
1738 | :term:`DEPLOY_DIR_RPM` | 1738 | :term:`DEPLOY_DIR_RPM` |
@@ -1753,7 +1753,7 @@ system and gives an overview of their function and contents. | |||
1753 | :ref:`ref-tasks-package_write_rpm` task | 1753 | :ref:`ref-tasks-package_write_rpm` task |
1754 | writes RPM packages into the appropriate folder. For more information | 1754 | writes RPM packages into the appropriate folder. For more information |
1755 | on how packaging works, see the | 1755 | on how packaging works, see the |
1756 | ":ref:`overview-manual/overview-manual-concepts:package feeds`" section | 1756 | ":ref:`overview-manual/concepts:package feeds`" section |
1757 | in the Yocto Project Overview and Concepts Manual. | 1757 | in the Yocto Project Overview and Concepts Manual. |
1758 | 1758 | ||
1759 | :term:`DEPLOY_DIR_TAR` | 1759 | :term:`DEPLOY_DIR_TAR` |
@@ -1774,7 +1774,7 @@ system and gives an overview of their function and contents. | |||
1774 | :ref:`ref-tasks-package_write_tar` task | 1774 | :ref:`ref-tasks-package_write_tar` task |
1775 | writes TAR packages into the appropriate folder. For more information | 1775 | writes TAR packages into the appropriate folder. For more information |
1776 | on how packaging works, see the | 1776 | on how packaging works, see the |
1777 | ":ref:`overview-manual/overview-manual-concepts:package feeds`" section | 1777 | ":ref:`overview-manual/concepts:package feeds`" section |
1778 | in the Yocto Project Overview and Concepts Manual. | 1778 | in the Yocto Project Overview and Concepts Manual. |
1779 | 1779 | ||
1780 | :term:`DEPLOYDIR` | 1780 | :term:`DEPLOYDIR` |
@@ -2419,7 +2419,7 @@ system and gives an overview of their function and contents. | |||
2419 | 2419 | ||
2420 | The previous statement appears in the | 2420 | The previous statement appears in the |
2421 | ``linux-yocto-dev.bbappend`` file, which is found in the | 2421 | ``linux-yocto-dev.bbappend`` file, which is found in the |
2422 | :ref:`overview-manual/overview-manual-development-environment:yocto project source repositories` in | 2422 | :ref:`overview-manual/development-environment:yocto project source repositories` in |
2423 | ``meta-intel/common/recipes-kernel/linux``. Here, the machine | 2423 | ``meta-intel/common/recipes-kernel/linux``. Here, the machine |
2424 | override is a special :term:`PACKAGE_ARCH` | 2424 | override is a special :term:`PACKAGE_ARCH` |
2425 | definition for multiple ``meta-intel`` machines. | 2425 | definition for multiple ``meta-intel`` machines. |
@@ -2509,7 +2509,7 @@ system and gives an overview of their function and contents. | |||
2509 | build system uses files from ``files/defconfig``. | 2509 | build system uses files from ``files/defconfig``. |
2510 | 2510 | ||
2511 | You can find out more about the patching process in the | 2511 | You can find out more about the patching process in the |
2512 | ":ref:`overview-manual/overview-manual-concepts:patching`" section | 2512 | ":ref:`overview-manual/concepts:patching`" section |
2513 | in the Yocto Project Overview and Concepts Manual and the | 2513 | in the Yocto Project Overview and Concepts Manual and the |
2514 | ":ref:`dev-manual/common-tasks:patching code`" section in | 2514 | ":ref:`dev-manual/common-tasks:patching code`" section in |
2515 | the Yocto Project Development Tasks Manual. See the | 2515 | the Yocto Project Development Tasks Manual. See the |
@@ -3126,7 +3126,7 @@ system and gives an overview of their function and contents. | |||
3126 | The location is | 3126 | The location is |
3127 | derived using the :term:`DEPLOY_DIR_IMAGE` | 3127 | derived using the :term:`DEPLOY_DIR_IMAGE` |
3128 | and :term:`IMAGE_NAME` variables. You can find | 3128 | and :term:`IMAGE_NAME` variables. You can find |
3129 | information on how the image is created in the ":ref:`overview-manual/overview-manual-concepts:image generation`" | 3129 | information on how the image is created in the ":ref:`overview-manual/concepts:image generation`" |
3130 | section in the Yocto Project Overview and Concepts Manual. | 3130 | section in the Yocto Project Overview and Concepts Manual. |
3131 | 3131 | ||
3132 | :term:`IMAGE_NAME` | 3132 | :term:`IMAGE_NAME` |
@@ -5578,7 +5578,7 @@ system and gives an overview of their function and contents. | |||
5578 | ${STAGING_DIR_HOST}/pkgdata | 5578 | ${STAGING_DIR_HOST}/pkgdata |
5579 | 5579 | ||
5580 | For examples of how this data is used, see the | 5580 | For examples of how this data is used, see the |
5581 | ":ref:`overview-manual/overview-manual-concepts:automatically added runtime dependencies`" | 5581 | ":ref:`overview-manual/concepts:automatically added runtime dependencies`" |
5582 | section in the Yocto Project Overview and Concepts Manual and the | 5582 | section in the Yocto Project Overview and Concepts Manual and the |
5583 | ":ref:`dev-manual/common-tasks:viewing package information with \`\`oe-pkgdata-util\`\``" | 5583 | ":ref:`dev-manual/common-tasks:viewing package information with \`\`oe-pkgdata-util\`\``" |
5584 | section in the Yocto Project Development Tasks Manual. For more | 5584 | section in the Yocto Project Development Tasks Manual. For more |
@@ -5691,9 +5691,9 @@ system and gives an overview of their function and contents. | |||
5691 | 5691 | ||
5692 | The OpenEmbedded build system does not need the aid of ``PR`` | 5692 | The OpenEmbedded build system does not need the aid of ``PR`` |
5693 | to know when to rebuild a recipe. The build system uses the task | 5693 | to know when to rebuild a recipe. The build system uses the task |
5694 | :ref:`input checksums <overview-manual/overview-manual-concepts:checksums (signatures)>` along with the | 5694 | :ref:`input checksums <overview-manual/concepts:checksums (signatures)>` along with the |
5695 | :ref:`stamp <structure-build-tmp-stamps>` and | 5695 | :ref:`stamp <structure-build-tmp-stamps>` and |
5696 | :ref:`overview-manual/overview-manual-concepts:shared state cache` | 5696 | :ref:`overview-manual/concepts:shared state cache` |
5697 | mechanisms. | 5697 | mechanisms. |
5698 | 5698 | ||
5699 | The ``PR`` variable primarily becomes significant when a package | 5699 | The ``PR`` variable primarily becomes significant when a package |
@@ -5875,7 +5875,7 @@ system and gives an overview of their function and contents. | |||
5875 | libplds4.so" | 5875 | libplds4.so" |
5876 | 5876 | ||
5877 | For more information, see the | 5877 | For more information, see the |
5878 | ":ref:`overview-manual/overview-manual-concepts:automatically added runtime dependencies`" | 5878 | ":ref:`overview-manual/concepts:automatically added runtime dependencies`" |
5879 | section in the Yocto Project Overview and Concepts Manual. | 5879 | section in the Yocto Project Overview and Concepts Manual. |
5880 | 5880 | ||
5881 | :term:`PROVIDES` | 5881 | :term:`PROVIDES` |
@@ -6068,7 +6068,7 @@ system and gives an overview of their function and contents. | |||
6068 | runtime dependencies are automatically detected and added. Therefore, | 6068 | runtime dependencies are automatically detected and added. Therefore, |
6069 | most recipes do not need to set ``RDEPENDS``. For more information, | 6069 | most recipes do not need to set ``RDEPENDS``. For more information, |
6070 | see the | 6070 | see the |
6071 | ":ref:`overview-manual/overview-manual-concepts:automatically added runtime dependencies`" | 6071 | ":ref:`overview-manual/concepts:automatically added runtime dependencies`" |
6072 | section in the Yocto Project Overview and Concepts Manual. | 6072 | section in the Yocto Project Overview and Concepts Manual. |
6073 | 6073 | ||
6074 | The practical effect of the above ``RDEPENDS`` assignment is that | 6074 | The practical effect of the above ``RDEPENDS`` assignment is that |
@@ -7023,7 +7023,7 @@ system and gives an overview of their function and contents. | |||
7023 | 7023 | ||
7024 | - ``file://`` - Fetches files, which are usually files shipped | 7024 | - ``file://`` - Fetches files, which are usually files shipped |
7025 | with the :term:`Metadata`, from the local machine (e.g. | 7025 | with the :term:`Metadata`, from the local machine (e.g. |
7026 | :ref:`patch <overview-manual/overview-manual-concepts:patching>` files). | 7026 | :ref:`patch <overview-manual/concepts:patching>` files). |
7027 | The path is relative to the :term:`FILESPATH` | 7027 | The path is relative to the :term:`FILESPATH` |
7028 | variable. Thus, the build system searches, in order, from the | 7028 | variable. Thus, the build system searches, in order, from the |
7029 | following directories, which are assumed to be a subdirectories of | 7029 | following directories, which are assumed to be a subdirectories of |
@@ -7316,7 +7316,7 @@ system and gives an overview of their function and contents. | |||
7316 | see the :ref:`ref-tasks-populate_sysroot` | 7316 | see the :ref:`ref-tasks-populate_sysroot` |
7317 | task, the ":ref:`sdk-manual/sdk-extensible:sharing files between recipes`" | 7317 | task, the ":ref:`sdk-manual/sdk-extensible:sharing files between recipes`" |
7318 | section in the Yocto Project Development Tasks Manual, the | 7318 | section in the Yocto Project Development Tasks Manual, the |
7319 | ":ref:`overview-manual/overview-manual-concepts:configuration, compilation, and staging`" | 7319 | ":ref:`overview-manual/concepts:configuration, compilation, and staging`" |
7320 | section in the Yocto Project Overview and Concepts Manual, and the | 7320 | section in the Yocto Project Overview and Concepts Manual, and the |
7321 | :term:`SYSROOT_DIRS` variable. | 7321 | :term:`SYSROOT_DIRS` variable. |
7322 | 7322 | ||
@@ -7437,7 +7437,7 @@ system and gives an overview of their function and contents. | |||
7437 | 7437 | ||
7438 | For information on how BitBake uses stamp files to determine if a | 7438 | For information on how BitBake uses stamp files to determine if a |
7439 | task should be rerun, see the | 7439 | task should be rerun, see the |
7440 | ":ref:`overview-manual/overview-manual-concepts:stamp files and the rerunning of tasks`" | 7440 | ":ref:`overview-manual/concepts:stamp files and the rerunning of tasks`" |
7441 | section in the Yocto Project Overview and Concepts Manual. | 7441 | section in the Yocto Project Overview and Concepts Manual. |
7442 | 7442 | ||
7443 | See :term:`STAMPS_DIR`, | 7443 | See :term:`STAMPS_DIR`, |
diff --git a/documentation/sdk-manual/sdk-appendix-customizing.rst b/documentation/sdk-manual/sdk-appendix-customizing.rst index 5a33f6385e..97ade0801d 100644 --- a/documentation/sdk-manual/sdk-appendix-customizing.rst +++ b/documentation/sdk-manual/sdk-appendix-customizing.rst | |||
@@ -87,7 +87,7 @@ adjustments: | |||
87 | following: | 87 | following: |
88 | 88 | ||
89 | - After ensuring the tasks are :ref:`shared | 89 | - After ensuring the tasks are :ref:`shared |
90 | state <overview-manual/overview-manual-concepts:shared state cache>` tasks (i.e. the | 90 | state <overview-manual/concepts:shared state cache>` tasks (i.e. the |
91 | output of the task is saved to and can be restored from the shared | 91 | output of the task is saved to and can be restored from the shared |
92 | state cache) or ensuring the tasks are able to be produced quickly | 92 | state cache) or ensuring the tasks are able to be produced quickly |
93 | from a task that is a shared state task, add the task name to the | 93 | from a task that is a shared state task, add the task name to the |
diff --git a/documentation/sdk-manual/sdk-extensible.rst b/documentation/sdk-manual/sdk-extensible.rst index 14ad23ba8f..c94213d6ca 100644 --- a/documentation/sdk-manual/sdk-extensible.rst +++ b/documentation/sdk-manual/sdk-extensible.rst | |||
@@ -183,7 +183,7 @@ system. | |||
183 | part of an image built using the build system. | 183 | part of an image built using the build system. |
184 | 184 | ||
185 | The ``devtool`` command line is organized similarly to | 185 | The ``devtool`` command line is organized similarly to |
186 | :ref:`overview-manual/overview-manual-development-environment:git` in that it has a number of | 186 | :ref:`overview-manual/development-environment:git` in that it has a number of |
187 | sub-commands for each function. You can run ``devtool --help`` to see | 187 | sub-commands for each function. You can run ``devtool --help`` to see |
188 | all the commands. | 188 | all the commands. |
189 | 189 | ||
diff --git a/documentation/toaster-manual/reference.rst b/documentation/toaster-manual/reference.rst index 4da415d860..dfe51889e8 100644 --- a/documentation/toaster-manual/reference.rst +++ b/documentation/toaster-manual/reference.rst | |||
@@ -65,7 +65,7 @@ set up the code for the web application that "hooks" into your set of | |||
65 | layers. | 65 | layers. |
66 | 66 | ||
67 | For general information on layers, see the | 67 | For general information on layers, see the |
68 | ":ref:`overview-manual/overview-manual-yp-intro:the yocto project layer model`" | 68 | ":ref:`overview-manual/yp-intro:the yocto project layer model`" |
69 | section in the Yocto Project Overview and Concepts Manual. For information on how | 69 | section in the Yocto Project Overview and Concepts Manual. For information on how |
70 | to create layers, see the ":ref:`dev-manual/common-tasks:understanding and creating layers`" | 70 | to create layers, see the ":ref:`dev-manual/common-tasks:understanding and creating layers`" |
71 | section in the Yocto Project Development Tasks Manual. | 71 | section in the Yocto Project Development Tasks Manual. |