summaryrefslogtreecommitdiffstats
path: root/bitbake/doc/bitbake-user-manual
diff options
context:
space:
mode:
Diffstat (limited to 'bitbake/doc/bitbake-user-manual')
-rw-r--r--bitbake/doc/bitbake-user-manual/bitbake-user-manual-execution.rst4
-rw-r--r--bitbake/doc/bitbake-user-manual/bitbake-user-manual-fetching.rst2
-rw-r--r--bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.rst2
-rw-r--r--bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst8
-rw-r--r--bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst2
5 files changed, 9 insertions, 9 deletions
diff --git a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-execution.rst b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-execution.rst
index 019afd22f6..d74e768f69 100644
--- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-execution.rst
+++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-execution.rst
@@ -315,7 +315,7 @@ any ``DEFAULT_PREFERENCE`` setting. ``DEFAULT_PREFERENCE`` is often used
315to mark newer and more experimental recipe versions until they have 315to mark newer and more experimental recipe versions until they have
316undergone sufficient testing to be considered stable. 316undergone sufficient testing to be considered stable.
317 317
318When there are multiple versions of a given recipe, BitBake defaults 318When there are multiple "versions" of a given recipe, BitBake defaults
319to selecting the most recent version, unless otherwise specified. If the 319to selecting the most recent version, unless otherwise specified. If the
320recipe in question has a 320recipe in question has a
321:term:`DEFAULT_PREFERENCE` set lower than 321:term:`DEFAULT_PREFERENCE` set lower than
@@ -325,7 +325,7 @@ to specify their preference for the default selected version.
325Additionally, the user can specify their preferred version. 325Additionally, the user can specify their preferred version.
326 326
327If the first recipe is named ``a_1.1.bb``, then the 327If the first recipe is named ``a_1.1.bb``, then the
328:term:`PN` variable will be set to a, and the 328:term:`PN` variable will be set to "a", and the
329:term:`PV` variable will be set to 1.1. 329:term:`PV` variable will be set to 1.1.
330 330
331Thus, if a recipe named ``a_1.2.bb`` exists, BitBake will choose 1.2 by 331Thus, if a recipe named ``a_1.2.bb`` exists, BitBake will choose 1.2 by
diff --git a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-fetching.rst b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-fetching.rst
index f62ddffe8e..6760b10828 100644
--- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-fetching.rst
+++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-fetching.rst
@@ -350,7 +350,7 @@ The supported parameters are as follows:
350 350
351- *"rev":* The revision of the source code to checkout. 351- *"rev":* The revision of the source code to checkout.
352 352
353- *"scmdata":* Causes the .svn directories to be available during 353- *"scmdata":* Causes the ".svn" directories to be available during
354 compile-time when set to "keep". By default, these directories are 354 compile-time when set to "keep". By default, these directories are
355 removed. 355 removed.
356 356
diff --git a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.rst b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.rst
index 77dc9668ab..6f9d392935 100644
--- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.rst
+++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.rst
@@ -465,7 +465,7 @@ Executing a Task Against a Single Recipe
465Executing tasks for a single recipe file is relatively simple. You 465Executing tasks for a single recipe file is relatively simple. You
466specify the file in question, and BitBake parses it and executes the 466specify the file in question, and BitBake parses it and executes the
467specified task. If you do not specify a task, BitBake executes the 467specified task. If you do not specify a task, BitBake executes the
468default task, which is "build. BitBake obeys inter-task dependencies 468default task, which is "build". BitBake obeys inter-task dependencies
469when doing so. 469when doing so.
470 470
471The following command runs the build task, which is the default task, on 471The following command runs the build task, which is the default task, on
diff --git a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst
index ec5d08590e..7ea68ade72 100644
--- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst
+++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst
@@ -516,8 +516,8 @@ variable.
516- *Selecting a Variable:* The ``OVERRIDES`` variable is a 516- *Selecting a Variable:* The ``OVERRIDES`` variable is a
517 colon-character-separated list that contains items for which you want 517 colon-character-separated list that contains items for which you want
518 to satisfy conditions. Thus, if you have a variable that is 518 to satisfy conditions. Thus, if you have a variable that is
519 conditional on arm, and arm is in ``OVERRIDES``, then the 519 conditional on "arm", and "arm" is in ``OVERRIDES``, then the
520 arm-specific version of the variable is used rather than the 520 "arm"-specific version of the variable is used rather than the
521 non-conditional version. Here is an example: :: 521 non-conditional version. Here is an example: ::
522 522
523 OVERRIDES = "architecture:os:machine" 523 OVERRIDES = "architecture:os:machine"
@@ -1917,8 +1917,8 @@ This command returns the signature data in a readable
1917format that allows you to examine the inputs used when the OpenEmbedded 1917format that allows you to examine the inputs used when the OpenEmbedded
1918build system generates signatures. For example, using 1918build system generates signatures. For example, using
1919``bitbake-dumpsigs`` allows you to examine the ``do_compile`` task's 1919``bitbake-dumpsigs`` allows you to examine the ``do_compile`` task's
1920sigdata for a C application (e.g. ``bash``). Running the command also 1920"sigdata" for a C application (e.g. ``bash``). Running the command also
1921reveals that the CC variable is part of the inputs that are hashed. 1921reveals that the "CC" variable is part of the inputs that are hashed.
1922Any changes to this variable would invalidate the stamp and cause the 1922Any changes to this variable would invalidate the stamp and cause the
1923``do_compile`` task to run. 1923``do_compile`` task to run.
1924 1924
diff --git a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
index 3de2a9ffd9..74a3eb8095 100644
--- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
+++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
@@ -553,7 +553,7 @@ overview of their function and contents.
553 device. To select the scheduler, use the following command form where 553 device. To select the scheduler, use the following command form where
554 device is the device (e.g. sda, sdb, and so forth): :: 554 device is the device (e.g. sda, sdb, and so forth): ::
555 555
556 $ sudo sh -c echo cfq > /sys/block/device/queu/scheduler 556 $ sudo sh -c "echo cfq > /sys/block/device/queu/scheduler"
557 557
558 :term:`BB_TASK_NICE_LEVEL` 558 :term:`BB_TASK_NICE_LEVEL`
559 Allows specific tasks to change their priority (i.e. nice level). 559 Allows specific tasks to change their priority (i.e. nice level).