diff options
Diffstat (limited to 'bitbake')
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 to mark newer and more experimental recipe versions until they have 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 recipe in question has a :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. 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. Thus, 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: - *"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 removed. 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 Executing tasks for a single recipe file is relatively simple. You specify the file in question, and BitBake parses it and 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. The 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. - *Selecting a Variable:* The ``OVERRIDES`` variable is a colon-character-separated list that contains items for which you want to satisfy conditions. Thus, if you have a variable that is - conditional on “arm”, and “arm” is in ``OVERRIDES``, then the - “arm”-specific version of the variable is used rather than the + conditional on "arm", and "arm" is in ``OVERRIDES``, then the + "arm"-specific version of the variable is used rather than the non-conditional version. Here is an example: :: 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 build system generates signatures. For example, using ``bitbake-dumpsigs`` allows you to examine the ``do_compile`` task's -“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. +"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. Any changes to this variable would invalidate the stamp and cause the ``do_compile`` task to run. 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. device. To select the scheduler, use the following command form where 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` Allows specific tasks to change their priority (i.e. nice level). |