diff options
author | Michael Opdenacker <michael.opdenacker@bootlin.com> | 2021-09-03 10:46:25 +0200 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2021-10-08 22:01:24 +0100 |
commit | f7a8e145e96b7056237e8911d799afa4430edbe3 (patch) | |
tree | 914530e1e2ffc71fff3fa88a669849a416e157b0 | |
parent | 2e78ec95bee9c5d776a68bfd926ba9f0a501eb40 (diff) | |
download | poky-f7a8e145e96b7056237e8911d799afa4430edbe3.tar.gz |
manuals: font fixes
This fixes font inconsistencies, mixing a ``text`` string
with another string with the regular font, where the whole string
makes more sense with a single font.
The result is also much simpler and will make future
searches easier.
(From yocto-docs rev: e6d1c166a97a1b6bb42ca49dfcbd3d39f8eadc16)
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r-- | documentation/dev-manual/common-tasks.rst | 4 | ||||
-rw-r--r-- | documentation/migration-guides/migration-2.7.rst | 4 | ||||
-rw-r--r-- | documentation/overview-manual/concepts.rst | 2 | ||||
-rw-r--r-- | documentation/ref-manual/classes.rst | 4 | ||||
-rw-r--r-- | documentation/ref-manual/faq.rst | 2 | ||||
-rw-r--r-- | documentation/ref-manual/terms.rst | 2 | ||||
-rw-r--r-- | documentation/ref-manual/variables.rst | 6 |
7 files changed, 12 insertions, 12 deletions
diff --git a/documentation/dev-manual/common-tasks.rst b/documentation/dev-manual/common-tasks.rst index b81f51bf83..71e5d6ef57 100644 --- a/documentation/dev-manual/common-tasks.rst +++ b/documentation/dev-manual/common-tasks.rst | |||
@@ -9453,8 +9453,8 @@ log to ``${T}/log.do_``\ `task`, and can also log to standard output | |||
9453 | 9453 | ||
9454 | Calling this function does not cause the task to fail. | 9454 | Calling this function does not cause the task to fail. |
9455 | 9455 | ||
9456 | - ``bb.fatal(``\ msg\ ``)``: This logging function is similar to | 9456 | - ``bb.fatal(msg)``: This logging function is similar to |
9457 | ``bb.error(``\ msg\ ``)`` but also causes the calling task to fail. | 9457 | ``bb.error(msg)`` but also causes the calling task to fail. |
9458 | 9458 | ||
9459 | .. note:: | 9459 | .. note:: |
9460 | 9460 | ||
diff --git a/documentation/migration-guides/migration-2.7.rst b/documentation/migration-guides/migration-2.7.rst index 69bd390603..ae70353bf7 100644 --- a/documentation/migration-guides/migration-2.7.rst +++ b/documentation/migration-guides/migration-2.7.rst | |||
@@ -87,8 +87,8 @@ This section provides information about packaging changes. | |||
87 | ``bind-utils`` package. | 87 | ``bind-utils`` package. |
88 | 88 | ||
89 | - Debug split: The default debug split has been changed to create | 89 | - Debug split: The default debug split has been changed to create |
90 | separate source packages (i.e. package_name\ ``-dbg`` and | 90 | separate source packages (i.e. ``package_name-dbg`` and |
91 | package_name\ ``-src``). If you are currently using ``dbg-pkgs`` in | 91 | ``package_name-src``). If you are currently using ``dbg-pkgs`` in |
92 | :term:`IMAGE_FEATURES` to bring in debug | 92 | :term:`IMAGE_FEATURES` to bring in debug |
93 | symbols and you still need the sources, you must now also add | 93 | symbols and you still need the sources, you must now also add |
94 | ``src-pkgs`` to :term:`IMAGE_FEATURES`. Source packages remain in the | 94 | ``src-pkgs`` to :term:`IMAGE_FEATURES`. Source packages remain in the |
diff --git a/documentation/overview-manual/concepts.rst b/documentation/overview-manual/concepts.rst index 3017637529..1ac6abe22b 100644 --- a/documentation/overview-manual/concepts.rst +++ b/documentation/overview-manual/concepts.rst | |||
@@ -1200,7 +1200,7 @@ usually made available in the form of a shared state (sstate) cache. | |||
1200 | :term:`SSTATE_MIRRORS` | 1200 | :term:`SSTATE_MIRRORS` |
1201 | variables. | 1201 | variables. |
1202 | 1202 | ||
1203 | The idea of a setscene task (i.e ``do_``\ taskname\ ``_setscene``) is a | 1203 | The idea of a setscene task (i.e ``do_taskname_setscene``) is a |
1204 | version of the task where instead of building something, BitBake can | 1204 | version of the task where instead of building something, BitBake can |
1205 | skip to the end result and simply place a set of files into specific | 1205 | skip to the end result and simply place a set of files into specific |
1206 | locations as needed. In some cases, it makes sense to have a setscene | 1206 | locations as needed. In some cases, it makes sense to have a setscene |
diff --git a/documentation/ref-manual/classes.rst b/documentation/ref-manual/classes.rst index 5c60fd8c82..ffaad9bfc9 100644 --- a/documentation/ref-manual/classes.rst +++ b/documentation/ref-manual/classes.rst | |||
@@ -1600,7 +1600,7 @@ or other tools from the build host). | |||
1600 | You can create a recipe that builds tools that run natively on the host | 1600 | You can create a recipe that builds tools that run natively on the host |
1601 | a couple different ways: | 1601 | a couple different ways: |
1602 | 1602 | ||
1603 | - Create a myrecipe\ ``-native.bb`` recipe that inherits the ``native`` | 1603 | - Create a ``myrecipe-native.bb`` recipe that inherits the ``native`` |
1604 | class. If you use this method, you must order the inherit statement | 1604 | class. If you use this method, you must order the inherit statement |
1605 | in the recipe after all other inherit statements so that the | 1605 | in the recipe after all other inherit statements so that the |
1606 | ``native`` class is inherited last. | 1606 | ``native`` class is inherited last. |
@@ -1642,7 +1642,7 @@ wish to build tools to run as part of an SDK (i.e. tools that run on | |||
1642 | You can create a recipe that builds tools that run on the SDK machine a | 1642 | You can create a recipe that builds tools that run on the SDK machine a |
1643 | couple different ways: | 1643 | couple different ways: |
1644 | 1644 | ||
1645 | - Create a ``nativesdk-``\ myrecipe\ ``.bb`` recipe that inherits the | 1645 | - Create a ``nativesdk-myrecipe.bb`` recipe that inherits the |
1646 | ``nativesdk`` class. If you use this method, you must order the | 1646 | ``nativesdk`` class. If you use this method, you must order the |
1647 | inherit statement in the recipe after all other inherit statements so | 1647 | inherit statement in the recipe after all other inherit statements so |
1648 | that the ``nativesdk`` class is inherited last. | 1648 | that the ``nativesdk`` class is inherited last. |
diff --git a/documentation/ref-manual/faq.rst b/documentation/ref-manual/faq.rst index d3a603d4a4..f40367bd58 100644 --- a/documentation/ref-manual/faq.rst +++ b/documentation/ref-manual/faq.rst | |||
@@ -143,7 +143,7 @@ various proxy types and configuring proxy servers, see the | |||
143 | ":yocto_wiki:`Working Behind a Network Proxy </Working_Behind_a_Network_Proxy>`" | 143 | ":yocto_wiki:`Working Behind a Network Proxy </Working_Behind_a_Network_Proxy>`" |
144 | Wiki page. | 144 | Wiki page. |
145 | 145 | ||
146 | **Q:** What's the difference between target and target\ ``-native``? | 146 | **Q:** What's the difference between ``target`` and ``target-native``? |
147 | 147 | ||
148 | **A:** The ``*-native`` targets are designed to run on the system being | 148 | **A:** The ``*-native`` targets are designed to run on the system being |
149 | used for the build. These are usually tools that are needed to assist | 149 | used for the build. These are usually tools that are needed to assist |
diff --git a/documentation/ref-manual/terms.rst b/documentation/ref-manual/terms.rst index e5a7565df5..eccae91a1c 100644 --- a/documentation/ref-manual/terms.rst +++ b/documentation/ref-manual/terms.rst | |||
@@ -31,7 +31,7 @@ universal, the list includes them just in case: | |||
31 | busybox_1.21.%.bbappend | 31 | busybox_1.21.%.bbappend |
32 | 32 | ||
33 | That append file | 33 | That append file |
34 | would match any ``busybox_1.21.``\ x\ ``.bb`` version of the recipe. So, | 34 | would match any ``busybox_1.21.x.bb`` version of the recipe. So, |
35 | the append file would match any of the following recipe names: | 35 | the append file would match any of the following recipe names: |
36 | 36 | ||
37 | .. code-block:: shell | 37 | .. code-block:: shell |
diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst index 5f6f91146b..6638ece539 100644 --- a/documentation/ref-manual/variables.rst +++ b/documentation/ref-manual/variables.rst | |||
@@ -730,7 +730,7 @@ system and gives an overview of their function and contents. | |||
730 | Each configuration file you | 730 | Each configuration file you |
731 | use must reside in the :term:`Build Directory` | 731 | use must reside in the :term:`Build Directory` |
732 | ``conf/multiconfig`` directory (e.g. | 732 | ``conf/multiconfig`` directory (e.g. |
733 | build_directory\ ``/conf/multiconfig/configA.conf``). | 733 | ``build_directory/conf/multiconfig/configA.conf``). |
734 | 734 | ||
735 | For information on how to use :term:`BBMULTICONFIG` in an environment | 735 | For information on how to use :term:`BBMULTICONFIG` in an environment |
736 | that supports building targets with multiple configurations, see the | 736 | that supports building targets with multiple configurations, see the |
@@ -5364,7 +5364,7 @@ system and gives an overview of their function and contents. | |||
5364 | so one of two ways: | 5364 | so one of two ways: |
5365 | 5365 | ||
5366 | - *Append file:* Create an append file named | 5366 | - *Append file:* Create an append file named |
5367 | recipename\ ``.bbappend`` in your layer and override the value of | 5367 | ``recipename.bbappend`` in your layer and override the value of |
5368 | :term:`PACKAGECONFIG`. You can either completely override the | 5368 | :term:`PACKAGECONFIG`. You can either completely override the |
5369 | variable:: | 5369 | variable:: |
5370 | 5370 | ||
@@ -8745,7 +8745,7 @@ system and gives an overview of their function and contents. | |||
8745 | :term:`WKS_FILE` | 8745 | :term:`WKS_FILE` |
8746 | Specifies the location of the Wic kickstart file that is used by the | 8746 | Specifies the location of the Wic kickstart file that is used by the |
8747 | OpenEmbedded build system to create a partitioned image | 8747 | OpenEmbedded build system to create a partitioned image |
8748 | (image\ ``.wic``). For information on how to create a partitioned | 8748 | (``image.wic``). For information on how to create a partitioned |
8749 | image, see the | 8749 | image, see the |
8750 | ":ref:`dev-manual/common-tasks:creating partitioned images using wic`" | 8750 | ":ref:`dev-manual/common-tasks:creating partitioned images using wic`" |
8751 | section in the Yocto Project Development Tasks Manual. For details on | 8751 | section in the Yocto Project Development Tasks Manual. For details on |