diff options
author | Paul Barker <pbarker@konsulko.com> | 2020-11-27 15:19:09 +0000 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2020-12-03 12:04:21 +0000 |
commit | 48748377a41a697a2b280ddbecb1c39487d1b7b8 (patch) | |
tree | 256c470487c98c810fbb28ab4973d7180ac23baf | |
parent | 8faafa99cc9a45c1920ec3ea696a9ec7fb653194 (diff) | |
download | poky-48748377a41a697a2b280ddbecb1c39487d1b7b8.tar.gz |
documentation: Simplify yocto_git links
The yocto_git external link directive is modified to include the
`/cgit/cgit.cgi` element of the URL so that we can simplify the links in
the text.
Manual links to git.yoctoproject.org are converted to use the yocto_git
directive where possible. Note that this directive can't be used in some
places such as example code.
(From yocto-docs rev: 3a8ba5dcc783411c73fe49fb217cbc4d6528d9a7)
Signed-off-by: Paul Barker <pbarker@konsulko.com>
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
24 files changed, 80 insertions, 91 deletions
diff --git a/documentation/bsp-guide/bsp.rst b/documentation/bsp-guide/bsp.rst index d6a4f545cc..357e740a5c 100644 --- a/documentation/bsp-guide/bsp.rst +++ b/documentation/bsp-guide/bsp.rst | |||
@@ -172,8 +172,7 @@ section. | |||
172 | #. *Optionally Clone the meta-intel BSP Layer:* If your hardware is | 172 | #. *Optionally Clone the meta-intel BSP Layer:* If your hardware is |
173 | based on current Intel CPUs and devices, you can leverage this BSP | 173 | based on current Intel CPUs and devices, you can leverage this BSP |
174 | layer. For details on the ``meta-intel`` BSP layer, see the layer's | 174 | layer. For details on the ``meta-intel`` BSP layer, see the layer's |
175 | `README <http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/tree/README>`__ | 175 | :yocto_git:`README </meta-intel/tree/README>` file. |
176 | file. | ||
177 | 176 | ||
178 | #. *Navigate to Your Source Directory:* Typically, you set up the | 177 | #. *Navigate to Your Source Directory:* Typically, you set up the |
179 | ``meta-intel`` Git repository inside the :term:`Source Directory` (e.g. | 178 | ``meta-intel`` Git repository inside the :term:`Source Directory` (e.g. |
@@ -902,13 +901,13 @@ Yocto Project: | |||
902 | ``meta-bsp_root_name`` directory. This license covers the BSP | 901 | ``meta-bsp_root_name`` directory. This license covers the BSP |
903 | Metadata as a whole. You must specify which license to use since no | 902 | Metadata as a whole. You must specify which license to use since no |
904 | default license exists when one is not specified. See the | 903 | default license exists when one is not specified. See the |
905 | :yocto_git:`COPYING.MIT </cgit.cgi/meta-raspberrypi/tree/COPYING.MIT>` | 904 | :yocto_git:`COPYING.MIT </meta-raspberrypi/tree/COPYING.MIT>` |
906 | file for the Raspberry Pi BSP in the ``meta-raspberrypi`` BSP layer | 905 | file for the Raspberry Pi BSP in the ``meta-raspberrypi`` BSP layer |
907 | as an example. | 906 | as an example. |
908 | 907 | ||
909 | - *README File:* You must include a ``README`` file in the | 908 | - *README File:* You must include a ``README`` file in the |
910 | ``meta-bsp_root_name`` directory. See the | 909 | ``meta-bsp_root_name`` directory. See the |
911 | :yocto_git:`README.md </cgit.cgi/meta-raspberrypi/tree/README.md>` | 910 | :yocto_git:`README.md </meta-raspberrypi/tree/README.md>` |
912 | file for the Raspberry Pi BSP in the ``meta-raspberrypi`` BSP layer | 911 | file for the Raspberry Pi BSP in the ``meta-raspberrypi`` BSP layer |
913 | as an example. | 912 | as an example. |
914 | 913 | ||
@@ -1181,16 +1180,16 @@ Use these steps to create a BSP layer: | |||
1181 | :yocto_git:`Source Repositories <>`. To get examples of what you need | 1180 | :yocto_git:`Source Repositories <>`. To get examples of what you need |
1182 | in your configuration file, locate a layer (e.g. "meta-ti") and | 1181 | in your configuration file, locate a layer (e.g. "meta-ti") and |
1183 | examine the | 1182 | examine the |
1184 | :yocto_git:`local.conf </cgit/cgit.cgi/meta-ti/tree/conf/layer.conf>` | 1183 | :yocto_git:`local.conf </meta-ti/tree/conf/layer.conf>` |
1185 | file. | 1184 | file. |
1186 | 1185 | ||
1187 | - *Create a Machine Configuration File:* Create a | 1186 | - *Create a Machine Configuration File:* Create a |
1188 | ``conf/machine/bsp_root_name.conf`` file. See | 1187 | ``conf/machine/bsp_root_name.conf`` file. See |
1189 | :yocto_git:`meta-yocto-bsp/conf/machine </cgit/cgit.cgi/poky/tree/meta-yocto-bsp/conf/machine>` | 1188 | :yocto_git:`meta-yocto-bsp/conf/machine </poky/tree/meta-yocto-bsp/conf/machine>` |
1190 | for sample ``bsp_root_name.conf`` files. Other samples such as | 1189 | for sample ``bsp_root_name.conf`` files. Other samples such as |
1191 | :yocto_git:`meta-ti </cgit/cgit.cgi/meta-ti/tree/conf/machine>` | 1190 | :yocto_git:`meta-ti </meta-ti/tree/conf/machine>` |
1192 | and | 1191 | and |
1193 | :yocto_git:`meta-freescale </cgit/cgit.cgi/meta-freescale/tree/conf/machine>` | 1192 | :yocto_git:`meta-freescale </meta-freescale/tree/conf/machine>` |
1194 | exist from other vendors that have more specific machine and tuning | 1193 | exist from other vendors that have more specific machine and tuning |
1195 | examples. | 1194 | examples. |
1196 | 1195 | ||
@@ -1204,7 +1203,7 @@ Use these steps to create a BSP layer: | |||
1204 | 1203 | ||
1205 | The remainder of this section provides a description of the Yocto | 1204 | The remainder of this section provides a description of the Yocto |
1206 | Project reference BSP for Beaglebone, which resides in the | 1205 | Project reference BSP for Beaglebone, which resides in the |
1207 | :yocto_git:`meta-yocto-bsp </cgit/cgit.cgi/poky/tree/meta-yocto-bsp>` | 1206 | :yocto_git:`meta-yocto-bsp </poky/tree/meta-yocto-bsp>` |
1208 | layer. | 1207 | layer. |
1209 | 1208 | ||
1210 | BSP Layer Configuration Example | 1209 | BSP Layer Configuration Example |
@@ -1413,7 +1412,7 @@ Project Reference Manual. | |||
1413 | .. note:: | 1412 | .. note:: |
1414 | 1413 | ||
1415 | For more information on how the SPL variables are used, see the | 1414 | For more information on how the SPL variables are used, see the |
1416 | :yocto_git:`u-boot.inc </cgit/cgit.cgi/poky/tree/meta/recipes-bsp/u-boot/u-boot.inc>` | 1415 | :yocto_git:`u-boot.inc </poky/tree/meta/recipes-bsp/u-boot/u-boot.inc>` |
1417 | include file. | 1416 | include file. |
1418 | 1417 | ||
1419 | - :term:`UBOOT_* <UBOOT_ENTRYPOINT>`: Defines | 1418 | - :term:`UBOOT_* <UBOOT_ENTRYPOINT>`: Defines |
@@ -1457,7 +1456,7 @@ The ``meta-yocto-bsp/recipes-kernel/linux`` directory in the layer contains | |||
1457 | metadata used to build the kernel. In this case, a kernel append file | 1456 | metadata used to build the kernel. In this case, a kernel append file |
1458 | (i.e. ``linux-yocto_5.0.bbappend``) is used to override an established | 1457 | (i.e. ``linux-yocto_5.0.bbappend``) is used to override an established |
1459 | kernel recipe (i.e. ``linux-yocto_5.0.bb``), which is located in | 1458 | kernel recipe (i.e. ``linux-yocto_5.0.bb``), which is located in |
1460 | :yocto_git:`/cgit/cgit.cgi/poky/tree/meta/recipes-kernel/linux`. | 1459 | :yocto_git:`/poky/tree/meta/recipes-kernel/linux`. |
1461 | 1460 | ||
1462 | Following is the contents of the append file: :: | 1461 | Following is the contents of the append file: :: |
1463 | 1462 | ||
diff --git a/documentation/conf.py b/documentation/conf.py index c906d066a9..a626b1f14d 100644 --- a/documentation/conf.py +++ b/documentation/conf.py | |||
@@ -75,7 +75,7 @@ extlinks = { | |||
75 | 'yocto_bugs': ('https://bugzilla.yoctoproject.org%s', None), | 75 | 'yocto_bugs': ('https://bugzilla.yoctoproject.org%s', None), |
76 | 'yocto_ab': ('https://autobuilder.yoctoproject.org%s', None), | 76 | 'yocto_ab': ('https://autobuilder.yoctoproject.org%s', None), |
77 | 'yocto_docs': ('https://docs.yoctoproject.org%s', None), | 77 | 'yocto_docs': ('https://docs.yoctoproject.org%s', None), |
78 | 'yocto_git': ('https://git.yoctoproject.org%s', None), | 78 | 'yocto_git': ('https://git.yoctoproject.org/cgit/cgit.cgi%s', None), |
79 | 'oe_home': ('https://www.openembedded.org%s', None), | 79 | 'oe_home': ('https://www.openembedded.org%s', None), |
80 | 'oe_lists': ('https://lists.openembedded.org%s', None), | 80 | 'oe_lists': ('https://lists.openembedded.org%s', None), |
81 | 'oe_git': ('https://git.openembedded.org%s', None), | 81 | 'oe_git': ('https://git.openembedded.org%s', None), |
diff --git a/documentation/dev-manual/dev-manual-common-tasks.rst b/documentation/dev-manual/dev-manual-common-tasks.rst index 4257a4bb99..891fd9b001 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.rst +++ b/documentation/dev-manual/dev-manual-common-tasks.rst | |||
@@ -75,7 +75,7 @@ Follow these general steps to create your layer without using tools: | |||
75 | ``conf`` directory and then modify the file as needed. | 75 | ``conf`` directory and then modify the file as needed. |
76 | 76 | ||
77 | The ``meta-yocto-bsp/conf/layer.conf`` file in the Yocto Project | 77 | The ``meta-yocto-bsp/conf/layer.conf`` file in the Yocto Project |
78 | :yocto_git:`Source Repositories </cgit/cgit.cgi/poky/tree/meta-yocto-bsp/conf>` | 78 | :yocto_git:`Source Repositories </poky/tree/meta-yocto-bsp/conf>` |
79 | demonstrates the required syntax. For your layer, you need to replace | 79 | demonstrates the required syntax. For your layer, you need to replace |
80 | "yoctobsp" with a unique identifier for your layer (e.g. "machinexyz" | 80 | "yoctobsp" with a unique identifier for your layer (e.g. "machinexyz" |
81 | for a layer named "meta-machinexyz"): | 81 | for a layer named "meta-machinexyz"): |
@@ -2107,15 +2107,12 @@ being able to provide the ``virtual/kernel`` item. | |||
2107 | 2107 | ||
2108 | Now comes the time to actually build an image and you need a kernel | 2108 | Now comes the time to actually build an image and you need a kernel |
2109 | recipe, but which one? You can configure your build to call out the | 2109 | recipe, but which one? You can configure your build to call out the |
2110 | kernel recipe you want by using the | 2110 | kernel recipe you want by using the :term:`PREFERRED_PROVIDER` variable. As |
2111 | :term:`PREFERRED_PROVIDER` | 2111 | an example, consider the :yocto_git:`x86-base.inc |
2112 | variable. As an example, consider the | 2112 | </poky/tree/meta/conf/machine/include/x86-base.inc>` include file, which is a |
2113 | `x86-base.inc <https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/conf/machine/include/x86-base.inc>`_ | 2113 | machine (i.e. :term:`MACHINE`) configuration file. This include file is the |
2114 | include file, which is a machine (i.e. | 2114 | reason all x86-based machines use the ``linux-yocto`` kernel. Here are the |
2115 | :term:`MACHINE`) configuration file. | 2115 | relevant lines from the include file: |
2116 | This include file is the reason all x86-based machines use the | ||
2117 | ``linux-yocto`` kernel. Here are the relevant lines from the include | ||
2118 | file: | ||
2119 | :: | 2116 | :: |
2120 | 2117 | ||
2121 | PREFERRED_PROVIDER_virtual/kernel ??= "linux-yocto" | 2118 | PREFERRED_PROVIDER_virtual/kernel ??= "linux-yocto" |
@@ -3058,7 +3055,7 @@ The following steps describe how to set up the AUH utility: | |||
3058 | 7. *Create and Edit an AUH Configuration File:* You need to have the | 3055 | 7. *Create and Edit an AUH Configuration File:* You need to have the |
3059 | ``upgrade-helper/upgrade-helper.conf`` configuration file in your | 3056 | ``upgrade-helper/upgrade-helper.conf`` configuration file in your |
3060 | build directory. You can find a sample configuration file in the | 3057 | build directory. You can find a sample configuration file in the |
3061 | :yocto_git:`AUH source repository </cgit/cgit.cgi/auto-upgrade-helper/tree/>`. | 3058 | :yocto_git:`AUH source repository </auto-upgrade-helper/tree/>`. |
3062 | 3059 | ||
3063 | Read through the sample file and make configurations as needed. For | 3060 | Read through the sample file and make configurations as needed. For |
3064 | example, if you enabled build history in your ``local.conf`` as | 3061 | example, if you enabled build history in your ``local.conf`` as |
@@ -3122,7 +3119,7 @@ the layer tree. | |||
3122 | 3119 | ||
3123 | You can easily set up to run the AUH utility on a regular basis by using | 3120 | You can easily set up to run the AUH utility on a regular basis by using |
3124 | a cron job. See the | 3121 | a cron job. See the |
3125 | :yocto_git:`weeklyjob.sh </cgit/cgit.cgi/auto-upgrade-helper/tree/weeklyjob.sh>` | 3122 | :yocto_git:`weeklyjob.sh </auto-upgrade-helper/tree/weeklyjob.sh>` |
3126 | file distributed with the utility for an example. | 3123 | file distributed with the utility for an example. |
3127 | 3124 | ||
3128 | Using ``devtool upgrade`` | 3125 | Using ``devtool upgrade`` |
@@ -4362,9 +4359,9 @@ your tunings to best consider build times and package feed maintenance. | |||
4362 | higher levels noted earlier can be useful. For example, consider how | 4359 | higher levels noted earlier can be useful. For example, consider how |
4363 | NXP (formerly Freescale) allows for the easy reuse of binary packages | 4360 | NXP (formerly Freescale) allows for the easy reuse of binary packages |
4364 | in their layer | 4361 | in their layer |
4365 | :yocto_git:`meta-freescale </cgit/cgit.cgi/meta-freescale/>`. | 4362 | :yocto_git:`meta-freescale </meta-freescale/>`. |
4366 | In this example, the | 4363 | In this example, the |
4367 | :yocto_git:`fsl-dynamic-packagearch </cgit/cgit.cgi/meta-freescale/tree/classes/fsl-dynamic-packagearch.bbclass>` | 4364 | :yocto_git:`fsl-dynamic-packagearch </meta-freescale/tree/classes/fsl-dynamic-packagearch.bbclass>` |
4368 | class shares GPU packages for i.MX53 boards because all boards share | 4365 | class shares GPU packages for i.MX53 boards because all boards share |
4369 | the AMD GPU. The i.MX6-based boards can do the same because all | 4366 | the AMD GPU. The i.MX6-based boards can do the same because all |
4370 | boards share the Vivante GPU. This class inspects the BitBake | 4367 | boards share the Vivante GPU. This class inspects the BitBake |
@@ -5564,7 +5561,7 @@ partition. | |||
5564 | Source plugins are subclasses defined in plugin files. As shipped, the | 5561 | Source plugins are subclasses defined in plugin files. As shipped, the |
5565 | Yocto Project provides several plugin files. You can see the source | 5562 | Yocto Project provides several plugin files. You can see the source |
5566 | plugin files that ship with the Yocto Project | 5563 | plugin files that ship with the Yocto Project |
5567 | :yocto_git:`here </cgit/cgit.cgi/poky/tree/scripts/lib/wic/plugins/source>`. | 5564 | :yocto_git:`here </poky/tree/scripts/lib/wic/plugins/source>`. |
5568 | Each of these plugin files contains source plugins that are designed to | 5565 | Each of these plugin files contains source plugins that are designed to |
5569 | populate a specific Wic image partition. | 5566 | populate a specific Wic image partition. |
5570 | 5567 | ||
@@ -6175,7 +6172,7 @@ system to make your images more secure: | |||
6175 | - Consider enabling a Mandatory Access Control (MAC) framework such as | 6172 | - Consider enabling a Mandatory Access Control (MAC) framework such as |
6176 | SMACK or SELinux and tuning it appropriately for your device's usage. | 6173 | SMACK or SELinux and tuning it appropriately for your device's usage. |
6177 | You can find more information in the | 6174 | You can find more information in the |
6178 | :yocto_git:`meta-selinux </cgit/cgit.cgi/meta-selinux/>` layer. | 6175 | :yocto_git:`meta-selinux </meta-selinux/>` layer. |
6179 | 6176 | ||
6180 | Tools for Hardening Your Image | 6177 | Tools for Hardening Your Image |
6181 | ------------------------------ | 6178 | ------------------------------ |
@@ -8436,7 +8433,7 @@ might be significant in human-readable form. Here is an example: | |||
8436 | 8433 | ||
8437 | To see changes to the build history using a web interface, follow the | 8434 | To see changes to the build history using a web interface, follow the |
8438 | instruction in the ``README`` file | 8435 | instruction in the ``README`` file |
8439 | :yocto_git:`here </cgit/cgit.cgi/buildhistory-web/>`. | 8436 | :yocto_git:`here </buildhistory-web/>`. |
8440 | 8437 | ||
8441 | Here is a sample screenshot of the interface: | 8438 | Here is a sample screenshot of the interface: |
8442 | 8439 | ||
@@ -9511,7 +9508,7 @@ the build system to run the task again. | |||
9511 | 9508 | ||
9512 | For an example of a commit that makes a cosmetic change to invalidate | 9509 | For an example of a commit that makes a cosmetic change to invalidate |
9513 | shared state, see this | 9510 | shared state, see this |
9514 | :yocto_git:`commit </cgit.cgi/poky/commit/meta/classes/package.bbclass?id=737f8bbb4f27b4837047cb9b4fbfe01dfde36d54>`. | 9511 | :yocto_git:`commit </poky/commit/meta/classes/package.bbclass?id=737f8bbb4f27b4837047cb9b4fbfe01dfde36d54>`. |
9515 | 9512 | ||
9516 | Running Specific Tasks | 9513 | Running Specific Tasks |
9517 | ---------------------- | 9514 | ---------------------- |
@@ -10475,7 +10472,7 @@ used testing branches for OpenEmbedded-Core are as follows: | |||
10475 | proposed changes to the core metadata. | 10472 | proposed changes to the core metadata. |
10476 | 10473 | ||
10477 | - *poky "master-next" branch:* This branch is part of the | 10474 | - *poky "master-next" branch:* This branch is part of the |
10478 | :yocto_git:`poky </cgit/cgit.cgi/poky/>` repository and combines proposed | 10475 | :yocto_git:`poky </poky/>` repository and combines proposed |
10479 | changes to bitbake, the core metadata and the poky distro. | 10476 | changes to bitbake, the core metadata and the poky distro. |
10480 | 10477 | ||
10481 | Similarly, stable branches maintained by the project may have corresponding | 10478 | Similarly, stable branches maintained by the project may have corresponding |
@@ -11381,7 +11378,7 @@ this function, you have to follow the following steps: | |||
11381 | SPDX_DEPLOY_DIR = "${DEPLOY_DIR}" //Optional | 11378 | SPDX_DEPLOY_DIR = "${DEPLOY_DIR}" //Optional |
11382 | 11379 | ||
11383 | For more usage information refer to :yocto_git:`the meta-spdxscanner repository | 11380 | For more usage information refer to :yocto_git:`the meta-spdxscanner repository |
11384 | </cgit/cgit.cgi/meta-spdxscanner/>`. | 11381 | </meta-spdxscanner/>`. |
11385 | 11382 | ||
11386 | 11383 | ||
11387 | Copying Licenses that Do Not Exist | 11384 | Copying Licenses that Do Not Exist |
@@ -11487,7 +11484,7 @@ Setting Up Your Own Error Reporting Server | |||
11487 | ------------------------------------------ | 11484 | ------------------------------------------ |
11488 | 11485 | ||
11489 | If you want to set up your own error reporting server, you can obtain | 11486 | If you want to set up your own error reporting server, you can obtain |
11490 | the code from the Git repository at :yocto_git:`/cgit/cgit.cgi/error-report-web/`. | 11487 | the code from the Git repository at :yocto_git:`/error-report-web/`. |
11491 | Instructions on how to set it up are in the README document. | 11488 | Instructions on how to set it up are in the README document. |
11492 | 11489 | ||
11493 | Using Wayland and Weston | 11490 | Using Wayland and Weston |
diff --git a/documentation/dev-manual/dev-manual-start.rst b/documentation/dev-manual/dev-manual-start.rst index 07e822899a..1c2314c430 100644 --- a/documentation/dev-manual/dev-manual-start.rst +++ b/documentation/dev-manual/dev-manual-start.rst | |||
@@ -586,7 +586,7 @@ Working from a copy of the upstream :ref:`dev-manual/dev-manual-start:accessing | |||
586 | preferred method for obtaining and using a Yocto Project release. You | 586 | preferred method for obtaining and using a Yocto Project release. You |
587 | can view the Yocto Project Source Repositories at | 587 | can view the Yocto Project Source Repositories at |
588 | :yocto_git:`/`. In particular, you can find the ``poky`` | 588 | :yocto_git:`/`. In particular, you can find the ``poky`` |
589 | repository at :yocto_git:`/cgit.cgi/poky`. | 589 | repository at :yocto_git:`/poky`. |
590 | 590 | ||
591 | Use the following procedure to locate the latest upstream copy of the | 591 | Use the following procedure to locate the latest upstream copy of the |
592 | ``poky`` Git repository: | 592 | ``poky`` Git repository: |
@@ -600,7 +600,7 @@ Use the following procedure to locate the latest upstream copy of the | |||
600 | 600 | ||
601 | 3. *Find the URL Used to Clone the Repository:* At the bottom of the | 601 | 3. *Find the URL Used to Clone the Repository:* At the bottom of the |
602 | page, note the URL used to clone that repository | 602 | page, note the URL used to clone that repository |
603 | (e.g. :yocto_git:`/cgit.cgi/poky`). | 603 | (e.g. :yocto_git:`/poky`). |
604 | 604 | ||
605 | .. note:: | 605 | .. note:: |
606 | 606 | ||
diff --git a/documentation/kernel-dev/kernel-dev-advanced.rst b/documentation/kernel-dev/kernel-dev-advanced.rst index 6999057b8a..db0a1eb2e5 100644 --- a/documentation/kernel-dev/kernel-dev-advanced.rst +++ b/documentation/kernel-dev/kernel-dev-advanced.rst | |||
@@ -200,7 +200,7 @@ either | |||
200 | :term:`FILESEXTRAPATHS` if | 200 | :term:`FILESEXTRAPATHS` if |
201 | you are creating Metadata in `recipe-space <#recipe-space-metadata>`__, | 201 | you are creating Metadata in `recipe-space <#recipe-space-metadata>`__, |
202 | or the top level of | 202 | or the top level of |
203 | :yocto_git:`yocto-kernel-cache </cgit/cgit.cgi/yocto-kernel-cache/tree/>` | 203 | :yocto_git:`yocto-kernel-cache </yocto-kernel-cache/tree/>` |
204 | if you are creating `Metadata outside of the | 204 | if you are creating `Metadata outside of the |
205 | recipe-space <#metadata-outside-the-recipe-space>`__. | 205 | recipe-space <#metadata-outside-the-recipe-space>`__. |
206 | 206 | ||
@@ -469,7 +469,7 @@ supported kernel type. | |||
469 | For BSPs supported by the Yocto Project, the BSP description files | 469 | For BSPs supported by the Yocto Project, the BSP description files |
470 | are located in the ``bsp`` directory of the ``yocto-kernel-cache`` | 470 | are located in the ``bsp`` directory of the ``yocto-kernel-cache`` |
471 | repository organized under the "Yocto Linux Kernel" heading in the | 471 | repository organized under the "Yocto Linux Kernel" heading in the |
472 | :yocto_git:`Yocto Project Source Repositories </>`. | 472 | :yocto_git:`Yocto Project Source Repositories <>`. |
473 | 473 | ||
474 | This section overviews the BSP description structure, the aggregation | 474 | This section overviews the BSP description structure, the aggregation |
475 | concepts, and presents a detailed example using a BSP supported by the | 475 | concepts, and presents a detailed example using a BSP supported by the |
diff --git a/documentation/kernel-dev/kernel-dev-maint-appx.rst b/documentation/kernel-dev/kernel-dev-maint-appx.rst index 69f680688f..ec1c0ac03d 100644 --- a/documentation/kernel-dev/kernel-dev-maint-appx.rst +++ b/documentation/kernel-dev/kernel-dev-maint-appx.rst | |||
@@ -103,7 +103,7 @@ patch, or BSP: | |||
103 | located by searching these system directories: | 103 | located by searching these system directories: |
104 | 104 | ||
105 | - The in-tree kernel-cache directories, which are located in the | 105 | - The in-tree kernel-cache directories, which are located in the |
106 | :yocto_git:`yocto-kernel-cache </cgit/cgit.cgi/yocto-kernel-cache/tree/bsp>` | 106 | :yocto_git:`yocto-kernel-cache </yocto-kernel-cache/tree/bsp>` |
107 | repository organized under the "Yocto Linux Kernel" heading in the | 107 | repository organized under the "Yocto Linux Kernel" heading in the |
108 | :yocto_git:`Yocto Project Source Repositories <>`. | 108 | :yocto_git:`Yocto Project Source Repositories <>`. |
109 | 109 | ||
@@ -167,7 +167,7 @@ specific to some target hardware. | |||
167 | The end result is a branched, clean history tree that makes up the | 167 | The end result is a branched, clean history tree that makes up the |
168 | kernel for a given release. You can see the script (``kgit-scc``) | 168 | kernel for a given release. You can see the script (``kgit-scc``) |
169 | responsible for this in the | 169 | responsible for this in the |
170 | :yocto_git:`yocto-kernel-tools </cgit.cgi/yocto-kernel-tools/tree/tools>` | 170 | :yocto_git:`yocto-kernel-tools </yocto-kernel-tools/tree/tools>` |
171 | repository. | 171 | repository. |
172 | 172 | ||
173 | - The steps used to construct the full kernel tree are the same | 173 | - The steps used to construct the full kernel tree are the same |
diff --git a/documentation/overview-manual/overview-manual-concepts.rst b/documentation/overview-manual/overview-manual-concepts.rst index 353a2f99ff..1b522910d2 100644 --- a/documentation/overview-manual/overview-manual-concepts.rst +++ b/documentation/overview-manual/overview-manual-concepts.rst | |||
@@ -273,7 +273,7 @@ The ``local.conf`` file provides many basic variables that define a | |||
273 | build environment. Here is a list of a few. To see the default | 273 | build environment. Here is a list of a few. To see the default |
274 | configurations in a ``local.conf`` file created by the build environment | 274 | configurations in a ``local.conf`` file created by the build environment |
275 | script, see the | 275 | script, see the |
276 | :yocto_git:`local.conf.sample </cgit/cgit.cgi/poky/tree/meta-poky/conf/local.conf.sample>` | 276 | :yocto_git:`local.conf.sample </poky/tree/meta-poky/conf/local.conf.sample>` |
277 | in the ``meta-poky`` layer: | 277 | in the ``meta-poky`` layer: |
278 | 278 | ||
279 | - *Target Machine Selection:* Controlled by the | 279 | - *Target Machine Selection:* Controlled by the |
@@ -393,17 +393,17 @@ figure <#general-workflow-figure>`__: | |||
393 | configurations. This type of information is specific to a particular | 393 | configurations. This type of information is specific to a particular |
394 | target architecture. A good example of a BSP layer from the `Poky | 394 | target architecture. A good example of a BSP layer from the `Poky |
395 | Reference Distribution <#gs-reference-distribution-poky>`__ is the | 395 | Reference Distribution <#gs-reference-distribution-poky>`__ is the |
396 | :yocto_git:`meta-yocto-bsp </cgit/cgit.cgi/poky/tree/meta-yocto-bsp>` | 396 | :yocto_git:`meta-yocto-bsp </poky/tree/meta-yocto-bsp>` |
397 | layer. | 397 | layer. |
398 | 398 | ||
399 | - *Policy Configuration:* Distribution Layers (i.e. "Distro Layer" in | 399 | - *Policy Configuration:* Distribution Layers (i.e. "Distro Layer" in |
400 | the following figure) providing top-level or general policies for the | 400 | the following figure) providing top-level or general policies for the |
401 | images or SDKs being built for a particular distribution. For | 401 | images or SDKs being built for a particular distribution. For |
402 | example, in the Poky Reference Distribution the distro layer is the | 402 | example, in the Poky Reference Distribution the distro layer is the |
403 | :yocto_git:`meta-poky </cgit/cgit.cgi/poky/tree/meta-poky>` | 403 | :yocto_git:`meta-poky </poky/tree/meta-poky>` |
404 | layer. Within the distro layer is a ``conf/distro`` directory that | 404 | layer. Within the distro layer is a ``conf/distro`` directory that |
405 | contains distro configuration files (e.g. | 405 | contains distro configuration files (e.g. |
406 | :yocto_git:`poky.conf </cgit/cgit.cgi/poky/tree/meta-poky/conf/distro/poky.conf>` | 406 | :yocto_git:`poky.conf </poky/tree/meta-poky/conf/distro/poky.conf>` |
407 | that contain many policy configurations for the Poky distribution. | 407 | that contain many policy configurations for the Poky distribution. |
408 | 408 | ||
409 | The following figure shows an expanded representation of these three | 409 | The following figure shows an expanded representation of these three |
@@ -427,9 +427,8 @@ Model <#the-yocto-project-layer-model>`__" sections both earlier in this | |||
427 | manual. | 427 | manual. |
428 | 428 | ||
429 | If you explored the previous links, you discovered some areas where many | 429 | If you explored the previous links, you discovered some areas where many |
430 | layers that work with the Yocto Project exist. The `Source | 430 | layers that work with the Yocto Project exist. The :yocto_git:`Source |
431 | Repositories <http://git.yoctoproject.org/>`__ also shows layers | 431 | Repositories <>` also shows layers categorized under "Yocto Metadata Layers." |
432 | categorized under "Yocto Metadata Layers." | ||
433 | 432 | ||
434 | .. note:: | 433 | .. note:: |
435 | 434 | ||
@@ -879,7 +878,7 @@ This step in the build process consists of the following tasks: | |||
879 | variables. For information on how this variable works within that | 878 | variables. For information on how this variable works within that |
880 | class, see the | 879 | class, see the |
881 | :ref:`autotools <ref-classes-autotools>` class | 880 | :ref:`autotools <ref-classes-autotools>` class |
882 | :yocto_git:`here </cgit/cgit.cgi/poky/tree/meta/classes/autotools.bbclass>`. | 881 | :yocto_git:`here </poky/tree/meta/classes/autotools.bbclass>`. |
883 | 882 | ||
884 | - *do_compile*: Once a configuration task has been satisfied, | 883 | - *do_compile*: Once a configuration task has been satisfied, |
885 | BitBake compiles the source using the | 884 | BitBake compiles the source using the |
@@ -957,7 +956,7 @@ The :term:`FILES` variable defines the | |||
957 | files that go into each package in | 956 | files that go into each package in |
958 | :term:`PACKAGES`. If you want | 957 | :term:`PACKAGES`. If you want |
959 | details on how this is accomplished, you can look at | 958 | details on how this is accomplished, you can look at |
960 | :yocto_git:`package.bbclass </cgit/cgit.cgi/poky/tree/meta/classes/package.bbclass>`. | 959 | :yocto_git:`package.bbclass </poky/tree/meta/classes/package.bbclass>`. |
961 | 960 | ||
962 | Depending on the type of packages being created (RPM, DEB, or IPK), the | 961 | Depending on the type of packages being created (RPM, DEB, or IPK), the |
963 | :ref:`do_package_write_* <ref-tasks-package_write_deb>` | 962 | :ref:`do_package_write_* <ref-tasks-package_write_deb>` |
diff --git a/documentation/overview-manual/overview-manual-development-environment.rst b/documentation/overview-manual/overview-manual-development-environment.rst index 983e1919ef..5baf08946b 100644 --- a/documentation/overview-manual/overview-manual-development-environment.rst +++ b/documentation/overview-manual/overview-manual-development-environment.rst | |||
@@ -416,7 +416,7 @@ files. Git uses "branches" to organize different development efforts. | |||
416 | For example, the ``poky`` repository has several branches that include | 416 | For example, the ``poky`` repository has several branches that include |
417 | the current "&DISTRO_NAME_NO_CAP;" branch, the "master" branch, and many | 417 | the current "&DISTRO_NAME_NO_CAP;" branch, the "master" branch, and many |
418 | branches for past Yocto Project releases. You can see all the branches | 418 | branches for past Yocto Project releases. You can see all the branches |
419 | by going to https://git.yoctoproject.org/cgit.cgi/poky/ and clicking on the | 419 | by going to :yocto_git:`/poky/` and clicking on the |
420 | ``[...]`` link beneath the "Branch" heading. | 420 | ``[...]`` link beneath the "Branch" heading. |
421 | 421 | ||
422 | Each of these branches represents a specific area of development. The | 422 | Each of these branches represents a specific area of development. The |
@@ -461,9 +461,8 @@ Yocto Project Release. | |||
461 | Git uses "tags" to mark specific changes in a repository branch | 461 | Git uses "tags" to mark specific changes in a repository branch |
462 | structure. Typically, a tag is used to mark a special point such as the | 462 | structure. Typically, a tag is used to mark a special point such as the |
463 | final change (or commit) before a project is released. You can see the | 463 | final change (or commit) before a project is released. You can see the |
464 | tags used with the ``poky`` Git repository by going to | 464 | tags used with the ``poky`` Git repository by going to :yocto_git:`/poky/` |
465 | https://git.yoctoproject.org/cgit.cgi/poky/ and clicking on the ``[...]`` link | 465 | and clicking on the ``[...]`` link beneath the "Tag" heading. |
466 | beneath the "Tag" heading. | ||
467 | 466 | ||
468 | Some key tags for the ``poky`` repository are ``jethro-14.0.3``, | 467 | Some key tags for the ``poky`` repository are ``jethro-14.0.3``, |
469 | ``morty-16.0.1``, ``pyro-17.0.0``, and | 468 | ``morty-16.0.1``, ``pyro-17.0.0``, and |
diff --git a/documentation/overview-manual/overview-manual-yp-intro.rst b/documentation/overview-manual/overview-manual-yp-intro.rst index 83ed18a375..2b9ea91490 100644 --- a/documentation/overview-manual/overview-manual-yp-intro.rst +++ b/documentation/overview-manual/overview-manual-yp-intro.rst | |||
@@ -267,9 +267,8 @@ with the string ``meta-``. | |||
267 | , but it is a commonly accepted standard in the Yocto Project | 267 | , but it is a commonly accepted standard in the Yocto Project |
268 | community. | 268 | community. |
269 | 269 | ||
270 | For example, if you were to examine the `tree | 270 | For example, if you were to examine the :yocto_git:`tree view </poky/tree/>` |
271 | view <https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/>`__ of the | 271 | of the ``poky`` repository, you will see several layers: ``meta``, |
272 | ``poky`` repository, you will see several layers: ``meta``, | ||
273 | ``meta-skeleton``, ``meta-selftest``, ``meta-poky``, and | 272 | ``meta-skeleton``, ``meta-selftest``, ``meta-poky``, and |
274 | ``meta-yocto-bsp``. Each of these repositories represents a distinct | 273 | ``meta-yocto-bsp``. Each of these repositories represents a distinct |
275 | layer. | 274 | layer. |
@@ -467,7 +466,7 @@ The following list consists of components associated with the | |||
467 | OpenEmbedded-derived systems, which includes the Yocto Project. The | 466 | OpenEmbedded-derived systems, which includes the Yocto Project. The |
468 | Yocto Project and the OpenEmbedded Project both maintain the | 467 | Yocto Project and the OpenEmbedded Project both maintain the |
469 | OpenEmbedded-Core. You can find the OE-Core metadata in the Yocto | 468 | OpenEmbedded-Core. You can find the OE-Core metadata in the Yocto |
470 | Project :yocto_git:`Source Repositories </cgit/cgit.cgi/poky/tree/meta>`. | 469 | Project :yocto_git:`Source Repositories </poky/tree/meta>`. |
471 | 470 | ||
472 | Historically, the Yocto Project integrated the OE-Core metadata | 471 | Historically, the Yocto Project integrated the OE-Core metadata |
473 | throughout the Yocto Project source repository reference system | 472 | throughout the Yocto Project source repository reference system |
@@ -671,7 +670,7 @@ Poky is a combined repository of BitBake, OpenEmbedded-Core (which is | |||
671 | found in ``meta``), ``meta-poky``, ``meta-yocto-bsp``, and documentation | 670 | found in ``meta``), ``meta-poky``, ``meta-yocto-bsp``, and documentation |
672 | provided all together and known to work well together. You can view | 671 | provided all together and known to work well together. You can view |
673 | these items that make up the Poky repository in the | 672 | these items that make up the Poky repository in the |
674 | :yocto_git:`Source Repositories </cgit/cgit.cgi/poky/tree/>`. | 673 | :yocto_git:`Source Repositories </poky/tree/>`. |
675 | 674 | ||
676 | .. note:: | 675 | .. note:: |
677 | 676 | ||
@@ -870,8 +869,7 @@ helpful for getting started: | |||
870 | set of recipes. | 869 | set of recipes. |
871 | 870 | ||
872 | You can see the Metadata in the ``meta`` directory of the Yocto | 871 | You can see the Metadata in the ``meta`` directory of the Yocto |
873 | Project `Source | 872 | Project :yocto_git:`Source Repositories <>`. |
874 | Repositories <http://git.yoctoproject.org/cgit/cgit.cgi>`__. | ||
875 | 873 | ||
876 | - *Packages:* In the context of the Yocto Project, this term refers to | 874 | - *Packages:* In the context of the Yocto Project, this term refers to |
877 | a recipe's packaged output produced by BitBake (i.e. a "baked | 875 | a recipe's packaged output produced by BitBake (i.e. a "baked |
diff --git a/documentation/ref-manual/migration-1.3.rst b/documentation/ref-manual/migration-1.3.rst index 5f975850ba..12e225b149 100644 --- a/documentation/ref-manual/migration-1.3.rst +++ b/documentation/ref-manual/migration-1.3.rst | |||
@@ -173,7 +173,7 @@ the OpenEmbedded community layers such as ``meta-oe`` and | |||
173 | ``meta-gnome``. For the remainder, you can now find them in the | 173 | ``meta-gnome``. For the remainder, you can now find them in the |
174 | ``meta-extras`` repository, which is in the | 174 | ``meta-extras`` repository, which is in the |
175 | :yocto_git:`Source Repositories <>` at | 175 | :yocto_git:`Source Repositories <>` at |
176 | :yocto_git:`/cgit/cgit.cgi/meta-extras/`. | 176 | :yocto_git:`/meta-extras/`. |
177 | 177 | ||
178 | .. _1.3-linux-kernel-naming: | 178 | .. _1.3-linux-kernel-naming: |
179 | 179 | ||
diff --git a/documentation/ref-manual/migration-1.6.rst b/documentation/ref-manual/migration-1.6.rst index a6c4c8a93a..822d5cfa03 100644 --- a/documentation/ref-manual/migration-1.6.rst +++ b/documentation/ref-manual/migration-1.6.rst | |||
@@ -411,6 +411,6 @@ The previous reference BSPs for the ``beagleboard`` and | |||
411 | ``routerstationpro`` machines are still available in a new | 411 | ``routerstationpro`` machines are still available in a new |
412 | ``meta-yocto-bsp-old`` layer in the | 412 | ``meta-yocto-bsp-old`` layer in the |
413 | :yocto_git:`Source Repositories <>` at | 413 | :yocto_git:`Source Repositories <>` at |
414 | :yocto_git:`/cgit/cgit.cgi/meta-yocto-bsp-old/`. | 414 | :yocto_git:`/meta-yocto-bsp-old/`. |
415 | 415 | ||
416 | 416 | ||
diff --git a/documentation/ref-manual/migration-2.2.rst b/documentation/ref-manual/migration-2.2.rst index 8afa8ffdda..ac247dce46 100644 --- a/documentation/ref-manual/migration-2.2.rst +++ b/documentation/ref-manual/migration-2.2.rst | |||
@@ -292,9 +292,9 @@ The following changes took place for BitBake: | |||
292 | functionality. These changes will affect external tools that use | 292 | functionality. These changes will affect external tools that use |
293 | BitBake's tinfoil module. For information on these changes, see the | 293 | BitBake's tinfoil module. For information on these changes, see the |
294 | changes made to the scripts supplied with OpenEmbedded-Core: | 294 | changes made to the scripts supplied with OpenEmbedded-Core: |
295 | `1 <http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=189371f8393971d00bca0fceffd67cc07784f6ee>`__ | 295 | :yocto_git:`1 </poky/commit/?id=189371f8393971d00bca0fceffd67cc07784f6ee>` |
296 | and | 296 | and |
297 | `2 <http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=4a5aa7ea4d07c2c90a1654b174873abb018acc67>`__. | 297 | :yocto_git:`2 </poky/commit/?id=4a5aa7ea4d07c2c90a1654b174873abb018acc67>`. |
298 | 298 | ||
299 | - The task management code has been rewritten to avoid using ID | 299 | - The task management code has been rewritten to avoid using ID |
300 | indirection in order to improve performance. This change is unlikely | 300 | indirection in order to improve performance. This change is unlikely |
diff --git a/documentation/ref-manual/migration-2.3.rst b/documentation/ref-manual/migration-2.3.rst index 4041ad0556..c0a8f04195 100644 --- a/documentation/ref-manual/migration-2.3.rst +++ b/documentation/ref-manual/migration-2.3.rst | |||
@@ -323,7 +323,7 @@ The following package management changes took place: | |||
323 | .. note:: | 323 | .. note:: |
324 | 324 | ||
325 | For further details on this change, see the | 325 | For further details on this change, see the |
326 | :yocto_git:`commit message </cgit/cgit.cgi/poky/commit/?id=f4d4f99cfbc2396e49c1613a7d237b9e57f06f81>`. | 326 | :yocto_git:`commit message </poky/commit/?id=f4d4f99cfbc2396e49c1613a7d237b9e57f06f81>`. |
327 | 327 | ||
328 | .. _migration-2.3-removed-recipes: | 328 | .. _migration-2.3-removed-recipes: |
329 | 329 | ||
diff --git a/documentation/ref-manual/migration-2.5.rst b/documentation/ref-manual/migration-2.5.rst index 1aeddc81c3..7f1b80938f 100644 --- a/documentation/ref-manual/migration-2.5.rst +++ b/documentation/ref-manual/migration-2.5.rst | |||
@@ -180,7 +180,7 @@ or :: | |||
180 | The earlier build-time provides behavior was a quirk of the | 180 | The earlier build-time provides behavior was a quirk of the |
181 | way the Python manifest file was created. For more information on this | 181 | way the Python manifest file was created. For more information on this |
182 | change please see :yocto_git:`this commit | 182 | change please see :yocto_git:`this commit |
183 | </cgit/cgit.cgi/poky/commit/?id=8d94b9db221d1def42f091b991903faa2d1651ce>`. | 183 | </poky/commit/?id=8d94b9db221d1def42f091b991903faa2d1651ce>`. |
184 | 184 | ||
185 | .. _migration-2.5-miscellaneous-changes: | 185 | .. _migration-2.5-miscellaneous-changes: |
186 | 186 | ||
@@ -293,8 +293,8 @@ The following are additional changes: | |||
293 | 293 | ||
294 | - Patches whose context does not match exactly (i.e. where patch | 294 | - Patches whose context does not match exactly (i.e. where patch |
295 | reports "fuzz" when applying) will generate a warning. For an example | 295 | reports "fuzz" when applying) will generate a warning. For an example |
296 | of this see `this | 296 | of this see :yocto_git:`this commit |
297 | commit <http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=cc97bc08125b63821ce3f616771830f77c456f57>`__. | 297 | </poky/commit/?id=cc97bc08125b63821ce3f616771830f77c456f57>`. |
298 | 298 | ||
299 | - Layers are expected to set ``LAYERSERIES_COMPAT_layername`` to match | 299 | - Layers are expected to set ``LAYERSERIES_COMPAT_layername`` to match |
300 | the version(s) of OpenEmbedded-Core they are compatible with. This is | 300 | the version(s) of OpenEmbedded-Core they are compatible with. This is |
diff --git a/documentation/ref-manual/migration-3.0.rst b/documentation/ref-manual/migration-3.0.rst index 047b75526f..7ef2742f8b 100644 --- a/documentation/ref-manual/migration-3.0.rst +++ b/documentation/ref-manual/migration-3.0.rst | |||
@@ -197,7 +197,7 @@ The following BitBake changes have occurred. | |||
197 | - The arguments passed to functions used with | 197 | - The arguments passed to functions used with |
198 | :term:`bitbake:BB_HASHCHECK_FUNCTION` | 198 | :term:`bitbake:BB_HASHCHECK_FUNCTION` |
199 | have changed. If you are using your own custom hash check function, | 199 | have changed. If you are using your own custom hash check function, |
200 | see :yocto_git:`/cgit/cgit.cgi/poky/commit/?id=40a5e193c4ba45c928fccd899415ea56b5417725` | 200 | see :yocto_git:`/poky/commit/?id=40a5e193c4ba45c928fccd899415ea56b5417725` |
201 | for details. | 201 | for details. |
202 | 202 | ||
203 | - Task specifications in ``BB_TASKDEPDATA`` and class implementations | 203 | - Task specifications in ``BB_TASKDEPDATA`` and class implementations |
diff --git a/documentation/ref-manual/ref-classes.rst b/documentation/ref-manual/ref-classes.rst index 62876194d1..e0cdbe87fa 100644 --- a/documentation/ref-manual/ref-classes.rst +++ b/documentation/ref-manual/ref-classes.rst | |||
@@ -2774,7 +2774,7 @@ To use this class, you need to define a number of variables: | |||
2774 | These variables list alternative commands needed by a package, provide | 2774 | These variables list alternative commands needed by a package, provide |
2775 | pathnames for links, default links for targets, and so forth. For | 2775 | pathnames for links, default links for targets, and so forth. For |
2776 | details on how to use this class, see the comments in the | 2776 | details on how to use this class, see the comments in the |
2777 | :yocto_git:`update-alternatives.bbclass </cgit/cgit.cgi/poky/tree/meta/classes/update-alternatives.bbclass>` | 2777 | :yocto_git:`update-alternatives.bbclass </poky/tree/meta/classes/update-alternatives.bbclass>` |
2778 | file. | 2778 | file. |
2779 | 2779 | ||
2780 | .. note:: | 2780 | .. note:: |
diff --git a/documentation/ref-manual/ref-devtool-reference.rst b/documentation/ref-manual/ref-devtool-reference.rst index 93fd1465f9..a769b3bd40 100644 --- a/documentation/ref-manual/ref-devtool-reference.rst +++ b/documentation/ref-manual/ref-devtool-reference.rst | |||
@@ -349,7 +349,7 @@ particular recipe. | |||
349 | .. note:: | 349 | .. note:: |
350 | 350 | ||
351 | - For the ``oe-core`` layer, recipe maintainers come from the | 351 | - For the ``oe-core`` layer, recipe maintainers come from the |
352 | `maintainers.inc <http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/conf/distro/include/maintainers.inc>`_ | 352 | :yocto_git:`maintainers.inc </poky/tree/meta/conf/distro/include/maintainers.inc>` |
353 | file. | 353 | file. |
354 | 354 | ||
355 | - If the recipe is using the :ref:`bitbake:bitbake-user-manual/bitbake-user-manual-fetching:git fetcher (\`\`git://\`\`)` | 355 | - If the recipe is using the :ref:`bitbake:bitbake-user-manual/bitbake-user-manual-fetching:git fetcher (\`\`git://\`\`)` |
@@ -388,7 +388,7 @@ satisfied. | |||
388 | When a reason for not upgrading displays, the reason is usually | 388 | When a reason for not upgrading displays, the reason is usually |
389 | written into the recipe using the ``RECIPE_NO_UPDATE_REASON`` | 389 | written into the recipe using the ``RECIPE_NO_UPDATE_REASON`` |
390 | variable. See the | 390 | variable. See the |
391 | :yocto_git:`base-passwd.bb </cgit/cgit.cgi/poky/tree/meta/recipes-core/base-passwd/base-passwd_3.5.29.bb>` | 391 | :yocto_git:`base-passwd.bb </poky/tree/meta/recipes-core/base-passwd/base-passwd_3.5.29.bb>` |
392 | recipe for an example. | 392 | recipe for an example. |
393 | 393 | ||
394 | :: | 394 | :: |
diff --git a/documentation/ref-manual/ref-tasks.rst b/documentation/ref-manual/ref-tasks.rst index 299e8f7d66..9fde9a8378 100644 --- a/documentation/ref-manual/ref-tasks.rst +++ b/documentation/ref-manual/ref-tasks.rst | |||
@@ -301,7 +301,7 @@ to locate and apply patch files to the source code. | |||
301 | Patch files, by default, are ``*.patch`` and ``*.diff`` files created | 301 | Patch files, by default, are ``*.patch`` and ``*.diff`` files created |
302 | and kept in a subdirectory of the directory holding the recipe file. For | 302 | and kept in a subdirectory of the directory holding the recipe file. For |
303 | example, consider the | 303 | example, consider the |
304 | :yocto_git:`bluez5 </cgit/cgit.cgi/poky/tree/meta/recipes-connectivity/bluez5>` | 304 | :yocto_git:`bluez5 </poky/tree/meta/recipes-connectivity/bluez5>` |
305 | recipe from the OE-Core layer (i.e. ``poky/meta``): | 305 | recipe from the OE-Core layer (i.e. ``poky/meta``): |
306 | :: | 306 | :: |
307 | 307 | ||
diff --git a/documentation/ref-manual/ref-terms.rst b/documentation/ref-manual/ref-terms.rst index b4ceebc0bb..f59aaf2788 100644 --- a/documentation/ref-manual/ref-terms.rst +++ b/documentation/ref-manual/ref-terms.rst | |||
@@ -218,7 +218,7 @@ universal, the list includes them just in case: | |||
218 | 218 | ||
219 | In the context of the kernel ("kernel Metadata"), the term refers to | 219 | In the context of the kernel ("kernel Metadata"), the term refers to |
220 | the kernel config fragments and features contained in the | 220 | the kernel config fragments and features contained in the |
221 | :yocto_git:`yocto-kernel-cache </cgit/cgit.cgi/yocto-kernel-cache>` | 221 | :yocto_git:`yocto-kernel-cache </yocto-kernel-cache>` |
222 | Git repository. | 222 | Git repository. |
223 | 223 | ||
224 | :term:`OpenEmbedded-Core (OE-Core)` | 224 | :term:`OpenEmbedded-Core (OE-Core)` |
@@ -232,7 +232,7 @@ universal, the list includes them just in case: | |||
232 | core set of recipes. | 232 | core set of recipes. |
233 | 233 | ||
234 | You can see the Metadata in the ``meta`` directory of the Yocto | 234 | You can see the Metadata in the ``meta`` directory of the Yocto |
235 | Project :yocto_git:`Source Repositories </cgit/cgit.cgi/poky>`. | 235 | Project :yocto_git:`Source Repositories </poky>`. |
236 | 236 | ||
237 | :term:`OpenEmbedded Build System` | 237 | :term:`OpenEmbedded Build System` |
238 | The build system specific to the Yocto | 238 | The build system specific to the Yocto |
diff --git a/documentation/ref-manual/ref-variables.rst b/documentation/ref-manual/ref-variables.rst index 921d19e7f5..f8cd5416d9 100644 --- a/documentation/ref-manual/ref-variables.rst +++ b/documentation/ref-manual/ref-variables.rst | |||
@@ -3600,7 +3600,7 @@ system and gives an overview of their function and contents. | |||
3600 | configuration file. You cannot set the variable in a recipe file. | 3600 | configuration file. You cannot set the variable in a recipe file. |
3601 | 3601 | ||
3602 | See the | 3602 | See the |
3603 | :yocto_git:`local.conf.sample.extended </cgit/cgit.cgi/poky/tree/meta-poky/conf/local.conf.sample.extended>` | 3603 | :yocto_git:`local.conf.sample.extended </poky/tree/meta-poky/conf/local.conf.sample.extended>` |
3604 | file for additional information. Also, for information on creating an | 3604 | file for additional information. Also, for information on creating an |
3605 | initramfs, see the ":ref:`dev-manual/dev-manual-common-tasks:building an initial ram filesystem (initramfs) image`" section | 3605 | initramfs, see the ":ref:`dev-manual/dev-manual-common-tasks:building an initial ram filesystem (initramfs) image`" section |
3606 | in the Yocto Project Development Tasks Manual. | 3606 | in the Yocto Project Development Tasks Manual. |
diff --git a/documentation/test-manual/test-manual-intro.rst b/documentation/test-manual/test-manual-intro.rst index cf511e9256..b41972084b 100644 --- a/documentation/test-manual/test-manual-intro.rst +++ b/documentation/test-manual/test-manual-intro.rst | |||
@@ -25,14 +25,14 @@ loaded with information from the README files and notes from key | |||
25 | engineers: | 25 | engineers: |
26 | 26 | ||
27 | - *yocto-autobuilder2:* This | 27 | - *yocto-autobuilder2:* This |
28 | :yocto_git:`README.md </cgit.cgi/yocto-autobuilder2/tree/README.md>` | 28 | :yocto_git:`README.md </yocto-autobuilder2/tree/README.md>` |
29 | is the main README which detials how to set up the Yocto Project | 29 | is the main README which detials how to set up the Yocto Project |
30 | Autobuilder. The ``yocto-autobuilder2`` repository represents the | 30 | Autobuilder. The ``yocto-autobuilder2`` repository represents the |
31 | Yocto Project's console UI plugin to Buildbot and the configuration | 31 | Yocto Project's console UI plugin to Buildbot and the configuration |
32 | necessary to configure Buildbot to perform the testing the project | 32 | necessary to configure Buildbot to perform the testing the project |
33 | requires. | 33 | requires. |
34 | 34 | ||
35 | - *yocto-autobuilder-helper:* This :yocto_git:`README </cgit.cgi/yocto-autobuilder-helper/tree/README/>` | 35 | - *yocto-autobuilder-helper:* This :yocto_git:`README </yocto-autobuilder-helper/tree/README/>` |
36 | and repository contains Yocto Project Autobuilder Helper scripts and | 36 | and repository contains Yocto Project Autobuilder Helper scripts and |
37 | configuration. The ``yocto-autobuilder-helper`` repository contains | 37 | configuration. The ``yocto-autobuilder-helper`` repository contains |
38 | the "glue" logic that defines which tests to run and how to run them. | 38 | the "glue" logic that defines which tests to run and how to run them. |
diff --git a/documentation/test-manual/test-manual-test-process.rst b/documentation/test-manual/test-manual-test-process.rst index bbf0103803..8a5e29d922 100644 --- a/documentation/test-manual/test-manual-test-process.rst +++ b/documentation/test-manual/test-manual-test-process.rst | |||
@@ -35,9 +35,9 @@ which the result was required. | |||
35 | The Autobuilder does build the ``master`` branch once daily for several | 35 | The Autobuilder does build the ``master`` branch once daily for several |
36 | reasons, in particular, to ensure the current ``master`` branch does | 36 | reasons, in particular, to ensure the current ``master`` branch does |
37 | build, but also to keep ``yocto-testresults`` | 37 | build, but also to keep ``yocto-testresults`` |
38 | (:yocto_git:`/cgit.cgi/yocto-testresults/`), | 38 | (:yocto_git:`/yocto-testresults/`), |
39 | buildhistory | 39 | buildhistory |
40 | (:yocto_git:`/cgit.cgi/poky-buildhistory/`), and | 40 | (:yocto_git:`/poky-buildhistory/`), and |
41 | our sstate up to date. On the weekend, there is a master-next build | 41 | our sstate up to date. On the weekend, there is a master-next build |
42 | instead to ensure the test results are updated for the less frequently | 42 | instead to ensure the test results are updated for the less frequently |
43 | run targets. | 43 | run targets. |
@@ -45,7 +45,7 @@ run targets. | |||
45 | Performance builds (buildperf-\* targets in the console) are triggered | 45 | Performance builds (buildperf-\* targets in the console) are triggered |
46 | separately every six hours and automatically push their results to the | 46 | separately every six hours and automatically push their results to the |
47 | buildstats repository at: | 47 | buildstats repository at: |
48 | :yocto_git:`/cgit.cgi/yocto-buildstats/`. | 48 | :yocto_git:`/yocto-buildstats/`. |
49 | 49 | ||
50 | The 'quick' targets have been selected to be the ones which catch the | 50 | The 'quick' targets have been selected to be the ones which catch the |
51 | most failures or give the most valuable data. We run 'fast' ptests in | 51 | most failures or give the most valuable data. We run 'fast' ptests in |
diff --git a/documentation/toaster-manual/toaster-manual-reference.rst b/documentation/toaster-manual/toaster-manual-reference.rst index 2202d599f6..ed0bad11b7 100644 --- a/documentation/toaster-manual/toaster-manual-reference.rst +++ b/documentation/toaster-manual/toaster-manual-reference.rst | |||
@@ -25,8 +25,7 @@ A layer index is a web application that contains information about a set | |||
25 | of custom layers. A good example of an existing layer index is the | 25 | of custom layers. A good example of an existing layer index is the |
26 | OpenEmbedded Layer Index. A public instance of this layer index exists | 26 | OpenEmbedded Layer Index. A public instance of this layer index exists |
27 | at http://layers.openembedded.org. You can find the code for this | 27 | at http://layers.openembedded.org. You can find the code for this |
28 | layer index's web application at | 28 | layer index's web application at :yocto_git:`/layerindex-web/`. |
29 | http://git.yoctoproject.org/cgit/cgit.cgi/layerindex-web/. | ||
30 | 29 | ||
31 | When you tie a layer source into Toaster, it can query the layer source | 30 | When you tie a layer source into Toaster, it can query the layer source |
32 | through a | 31 | through a |
@@ -83,9 +82,8 @@ index. | |||
83 | 82 | ||
84 | In the previous section, the code for the OpenEmbedded Metadata Index | 83 | In the previous section, the code for the OpenEmbedded Metadata Index |
85 | (i.e. http://layers.openembedded.org) was referenced. You can use | 84 | (i.e. http://layers.openembedded.org) was referenced. You can use |
86 | this code, which is at | 85 | this code, which is at :yocto_git:`/layerindex-web/`, as a base to create |
87 | http://git.yoctoproject.org/cgit/cgit.cgi/layerindex-web/, as a | 86 | your own layer index. |
88 | base to create your own layer index. | ||
89 | 87 | ||
90 | Use the Administration Interface | 88 | Use the Administration Interface |
91 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | 89 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
@@ -165,14 +163,13 @@ As shipped, Toaster is configured to work with the following releases: | |||
165 | - *Yocto Project &DISTRO; "&DISTRO_NAME;" or OpenEmbedded "&DISTRO_NAME;":* | 163 | - *Yocto Project &DISTRO; "&DISTRO_NAME;" or OpenEmbedded "&DISTRO_NAME;":* |
166 | This release causes your Toaster projects to build against the head | 164 | This release causes your Toaster projects to build against the head |
167 | of the &DISTRO_NAME_NO_CAP; branch at | 165 | of the &DISTRO_NAME_NO_CAP; branch at |
168 | https://git.yoctoproject.org/cgit/cgit.cgi/poky/log/?h=&DISTRO_NAME_NO_CAP; or | 166 | :yocto_git:`/poky/log/?h=&DISTRO_NAME_NO_CAP;` or |
169 | http://git.openembedded.org/openembedded-core/commit/?h=&DISTRO_NAME_NO_CAP;. | 167 | :oe_git:`/openembedded-core/commit/?h=&DISTRO_NAME_NO_CAP;`. |
170 | 168 | ||
171 | - *Yocto Project "Master" or OpenEmbedded "Master":* This release | 169 | - *Yocto Project "Master" or OpenEmbedded "Master":* This release |
172 | causes your Toaster Projects to build against the head of the master | 170 | causes your Toaster Projects to build against the head of the master |
173 | branch, which is where active development takes place, at | 171 | branch, which is where active development takes place, at |
174 | https://git.yoctoproject.org/cgit/cgit.cgi/poky/log/ or | 172 | :yocto_git:`/poky/log/` or :oe_git:`/openembedded-core/log/`. |
175 | http://git.openembedded.org/openembedded-core/log/. | ||
176 | 173 | ||
177 | - *Local Yocto Project or Local OpenEmbedded:* This release causes your | 174 | - *Local Yocto Project or Local OpenEmbedded:* This release causes your |
178 | Toaster Projects to build against the head of the ``poky`` or | 175 | Toaster Projects to build against the head of the ``poky`` or |
diff --git a/documentation/toaster-manual/toaster-manual-setup-and-use.rst b/documentation/toaster-manual/toaster-manual-setup-and-use.rst index b73caac375..6e2ba02531 100644 --- a/documentation/toaster-manual/toaster-manual-setup-and-use.rst +++ b/documentation/toaster-manual/toaster-manual-setup-and-use.rst | |||
@@ -561,8 +561,8 @@ the same clone you are using to run Toaster. Unless you manually update | |||
561 | this clone, your builds will always use the same Git revision. | 561 | this clone, your builds will always use the same Git revision. |
562 | 562 | ||
563 | If you select any of the other release options, Toaster will fetch the | 563 | If you select any of the other release options, Toaster will fetch the |
564 | tip of your selected release from the upstream `Yocto Project | 564 | tip of your selected release from the upstream :yocto_git:`Yocto Project |
565 | repository <https://git.yoctoproject.org>`__ every time you run a build. | 565 | repository <>` every time you run a build. |
566 | Fetching this tip effectively means that if your selected release is | 566 | Fetching this tip effectively means that if your selected release is |
567 | updated upstream, the Git revision you are using for your builds will | 567 | updated upstream, the Git revision you are using for your builds will |
568 | change. If you are doing development locally, you might not want this | 568 | change. If you are doing development locally, you might not want this |