mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-06-02 13:29:49 +00:00
Code Issues Projects Releases Wiki Activity

bitbake: docs: sphinx: replace special quotes with double quotes

Browse Source 
(Bitbake rev: c87cc35a5665afbf67f6dbb3458976c215fd5ee3)

Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Nicolas Dechesne
2020-10-05 13:59:29 +02:00
committed by Richard Purdie
parent b2c2b87953
commit 25fd9fddc3
5 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
bitbake/doc/bitbake-user-manual/bitbake-user-manual-execution.rst
+2 -2
View File
@@ -315,7 +315,7 @@ any ``DEFAULT_PREFERENCE`` setting. ``DEFAULT_PREFERENCE`` is often used
to mark newer and more experimental recipe versions until they have to mark newer and more experimental recipe versions until they have
undergone sufficient testing to be considered stable. undergone sufficient testing to be considered stable.
When there are multiple “versions” of a given recipe, BitBake defaults When there are multiple "versions" of a given recipe, BitBake defaults
to selecting the most recent version, unless otherwise specified. If the to selecting the most recent version, unless otherwise specified. If the
recipe in question has a recipe in question has a
:term:`DEFAULT_PREFERENCE` set lower than :term:`DEFAULT_PREFERENCE` set lower than
@@ -325,7 +325,7 @@ to specify their preference for the default selected version.
Additionally, the user can specify their preferred version. Additionally, the user can specify their preferred version.
If the first recipe is named ``a_1.1.bb``, then the If the first recipe is named ``a_1.1.bb``, then the
:term:`PN` variable will be set to “a”, and the :term:`PN` variable will be set to "a", and the
:term:`PV` variable will be set to 1.1. :term:`PV` variable will be set to 1.1.
Thus, if a recipe named ``a_1.2.bb`` exists, BitBake will choose 1.2 by Thus, if a recipe named ``a_1.2.bb`` exists, BitBake will choose 1.2 by
bitbake/doc/bitbake-user-manual/bitbake-user-manual-fetching.rst
+1 -1
View File
@@ -350,7 +350,7 @@ The supported parameters are as follows:
- *"rev":* The revision of the source code to checkout. - *"rev":* The revision of the source code to checkout.
- *"scmdata":* Causes the “.svn” directories to be available during - *"scmdata":* Causes the ".svn" directories to be available during
compile-time when set to "keep". By default, these directories are compile-time when set to "keep". By default, these directories are
removed. removed.
bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.rst
+1 -1
View File
@@ -465,7 +465,7 @@ Executing a Task Against a Single Recipe
Executing tasks for a single recipe file is relatively simple. You Executing tasks for a single recipe file is relatively simple. You
specify the file in question, and BitBake parses it and executes the specify the file in question, and BitBake parses it and executes the
specified task. If you do not specify a task, BitBake executes the specified task. If you do not specify a task, BitBake executes the
default task, which is "build”. BitBake obeys inter-task dependencies default task, which is "build". BitBake obeys inter-task dependencies
when doing so. when doing so.
The following command runs the build task, which is the default task, on The following command runs the build task, which is the default task, on
bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst
+4 -4
View File
@@ -516,8 +516,8 @@ variable.
- *Selecting a Variable:* The ``OVERRIDES`` variable is a - *Selecting a Variable:* The ``OVERRIDES`` variable is a
colon-character-separated list that contains items for which you want colon-character-separated list that contains items for which you want
to satisfy conditions. Thus, if you have a variable that is to satisfy conditions. Thus, if you have a variable that is
conditional on “arm”, and “arm” is in ``OVERRIDES``, then the conditional on "arm", and "arm" is in ``OVERRIDES``, then the
“arm”-specific version of the variable is used rather than the "arm"-specific version of the variable is used rather than the
non-conditional version. Here is an example: :: non-conditional version. Here is an example: ::
OVERRIDES = "architecture:os:machine" OVERRIDES = "architecture:os:machine"
@@ -1917,8 +1917,8 @@ This command returns the signature data in a readable
format that allows you to examine the inputs used when the OpenEmbedded format that allows you to examine the inputs used when the OpenEmbedded
build system generates signatures. For example, using build system generates signatures. For example, using
``bitbake-dumpsigs`` allows you to examine the ``do_compile`` task's ``bitbake-dumpsigs`` allows you to examine the ``do_compile`` task's
“sigdata” for a C application (e.g. ``bash``). Running the command also "sigdata" for a C application (e.g. ``bash``). Running the command also
reveals that the “CC” variable is part of the inputs that are hashed. reveals that the "CC" variable is part of the inputs that are hashed.
Any changes to this variable would invalidate the stamp and cause the Any changes to this variable would invalidate the stamp and cause the
``do_compile`` task to run. ``do_compile`` task to run.
bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
+1 -1
View File
@@ -553,7 +553,7 @@ overview of their function and contents.
device. To select the scheduler, use the following command form where device. To select the scheduler, use the following command form where
device is the device (e.g. sda, sdb, and so forth): :: device is the device (e.g. sda, sdb, and so forth): ::
$ sudo sh -c “echo cfq > /sys/block/device/queu/scheduler $ sudo sh -c "echo cfq > /sys/block/device/queu/scheduler"
:term:`BB_TASK_NICE_LEVEL` :term:`BB_TASK_NICE_LEVEL`
Allows specific tasks to change their priority (i.e. nice level). Allows specific tasks to change their priority (i.e. nice level).