diff options
| author | Michael Opdenacker <michael.opdenacker@bootlin.com> | 2022-12-08 10:25:59 +0100 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2022-12-18 10:41:21 +0000 |
| commit | 01e5d22507e57c66452f14610ee8eb3d66ac9d71 (patch) | |
| tree | 7241fa93a3a0d11db32d042e5d70a750132ab0a1 /documentation/dev-manual/new-recipe.rst | |
| parent | 8b812b29c4b13ba028c0d66f73a6599a988486d5 (diff) | |
| download | poky-01e5d22507e57c66452f14610ee8eb3d66ac9d71.tar.gz | |
manuals: fix double colons
Fixing double colons appearing alone on a line, while
they could be put at the end of the previous line.
Sometimes placing a note after the quoted text
to avoid such a situation. It's more natural too
not to have a note between the introduction text
and the quoted section.
(From yocto-docs rev: fb054622f5119444eb947fe580253f37e0d872c6)
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/dev-manual/new-recipe.rst')
| -rw-r--r-- | documentation/dev-manual/new-recipe.rst | 16 |
1 files changed, 5 insertions, 11 deletions
diff --git a/documentation/dev-manual/new-recipe.rst b/documentation/dev-manual/new-recipe.rst index 2e9c2089f7..3adebf2746 100644 --- a/documentation/dev-manual/new-recipe.rst +++ b/documentation/dev-manual/new-recipe.rst | |||
| @@ -109,8 +109,7 @@ Following are some syntax examples: | |||
| 109 | 109 | ||
| 110 | - Use this syntax to generate a recipe using code that | 110 | - Use this syntax to generate a recipe using code that |
| 111 | you extract from source. The extracted code is placed in its own layer | 111 | you extract from source. The extracted code is placed in its own layer |
| 112 | defined by :term:`EXTERNALSRC`. | 112 | defined by :term:`EXTERNALSRC`:: |
| 113 | :: | ||
| 114 | 113 | ||
| 115 | recipetool create -o OUTFILE -x EXTERNALSRC source | 114 | recipetool create -o OUTFILE -x EXTERNALSRC source |
| 116 | 115 | ||
| @@ -147,8 +146,7 @@ get started. Here are some points on both methods: | |||
| 147 | - *Use and modify the following skeleton recipe:* If for some reason | 146 | - *Use and modify the following skeleton recipe:* If for some reason |
| 148 | you do not want to use ``recipetool`` and you cannot find an existing | 147 | you do not want to use ``recipetool`` and you cannot find an existing |
| 149 | recipe that is close to meeting your needs, you can use the following | 148 | recipe that is close to meeting your needs, you can use the following |
| 150 | structure to provide the fundamental areas of a new recipe. | 149 | structure to provide the fundamental areas of a new recipe:: |
| 151 | :: | ||
| 152 | 150 | ||
| 153 | DESCRIPTION = "" | 151 | DESCRIPTION = "" |
| 154 | HOMEPAGE = "" | 152 | HOMEPAGE = "" |
| @@ -347,9 +345,7 @@ paste them into your recipe and then run the build again to continue. | |||
| 347 | This final example is a bit more complicated and is from the | 345 | This final example is a bit more complicated and is from the |
| 348 | ``meta/recipes-sato/rxvt-unicode/rxvt-unicode_9.20.bb`` recipe. The | 346 | ``meta/recipes-sato/rxvt-unicode/rxvt-unicode_9.20.bb`` recipe. The |
| 349 | example's :term:`SRC_URI` statement identifies multiple files as the source | 347 | example's :term:`SRC_URI` statement identifies multiple files as the source |
| 350 | files for the recipe: a tarball, a patch file, a desktop file, and an | 348 | files for the recipe: a tarball, a patch file, a desktop file, and an icon:: |
| 351 | icon. | ||
| 352 | :: | ||
| 353 | 349 | ||
| 354 | SRC_URI = "http://dist.schmorp.de/rxvt-unicode/Attic/rxvt-unicode-${PV}.tar.bz2 \ | 350 | SRC_URI = "http://dist.schmorp.de/rxvt-unicode/Attic/rxvt-unicode-${PV}.tar.bz2 \ |
| 355 | file://xwc.patch \ | 351 | file://xwc.patch \ |
| @@ -1196,8 +1192,7 @@ under ``files``) requires a recipe that has the file listed in the | |||
| 1196 | :ref:`ref-tasks-compile` and :ref:`ref-tasks-install` tasks. The :term:`S` variable defines the | 1192 | :ref:`ref-tasks-compile` and :ref:`ref-tasks-install` tasks. The :term:`S` variable defines the |
| 1197 | directory containing the source code, which is set to | 1193 | directory containing the source code, which is set to |
| 1198 | :term:`WORKDIR` in this case --- the | 1194 | :term:`WORKDIR` in this case --- the |
| 1199 | directory BitBake uses for the build. | 1195 | directory BitBake uses for the build:: |
| 1200 | :: | ||
| 1201 | 1196 | ||
| 1202 | SUMMARY = "Simple helloworld application" | 1197 | SUMMARY = "Simple helloworld application" |
| 1203 | SECTION = "examples" | 1198 | SECTION = "examples" |
| @@ -1233,8 +1228,7 @@ which contains the definitions of all the steps needed to build an | |||
| 1233 | Autotool-based application. The result of the build is automatically | 1228 | Autotool-based application. The result of the build is automatically |
| 1234 | packaged. And, if the application uses NLS for localization, packages | 1229 | packaged. And, if the application uses NLS for localization, packages |
| 1235 | with local information are generated (one package per language). | 1230 | with local information are generated (one package per language). |
| 1236 | Following is one example: (``hello_2.3.bb``) | 1231 | Following is one example: (``hello_2.3.bb``):: |
| 1237 | :: | ||
| 1238 | 1232 | ||
| 1239 | SUMMARY = "GNU Helloworld application" | 1233 | SUMMARY = "GNU Helloworld application" |
| 1240 | SECTION = "examples" | 1234 | SECTION = "examples" |
