mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-09-19 00:49:33 +02:00
Code Issues Packages Projects Releases Wiki Activity

bitbake: sphinx: fix links inside notes

Browse Source 
For some notes with links, the links were lost during the pandoc
conversion.

(Bitbake rev: e11d2dd1adbcb35b45d6d0f3a47f8d06caab0b49)

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-07-30 18:05:38 +02:00
committed by Richard Purdie
parent 2df3190f13
commit b232a4b504
3 changed files with 13 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
bitbake/doc/bitbake-user-manual/bitbake-user-manual-hello.rst
View File

@@ -79,8 +79,8 @@ discussion mailing list about the BitBake build tool.
.. note:: .. note::
This example was inspired by and drew heavily from This example was inspired by and drew heavily from
Mailing List post - The BitBake equivalent of "Hello, World!" `Mailing List post - The BitBake equivalent of "Hello, World!"
. <http://www.mail-archive.com/yocto@yoctoproject.org/msg09379.html>`_.
As stated earlier, the goal of this example is to eventually compile As stated earlier, the goal of this example is to eventually compile
"Hello World". However, it is unknown what BitBake needs and what you "Hello World". However, it is unknown what BitBake needs and what you
@@ -277,9 +277,8 @@ Following is the complete "Hello World" example.
.. note:: .. note::
You can find additional information on layers in the " You can find additional information on layers in the
Layers ":ref:`bitbake-user-manual/bitbake-user-manual-intro:Layers`" section.
" section.
Minimally, you need a recipe file and a layer configuration file in Minimally, you need a recipe file and a layer configuration file in
your layer. The configuration file needs to be in the ``conf`` your layer. The configuration file needs to be in the ``conf``

18
bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst
View File

@@ -639,7 +639,7 @@ definitions: include test_defs.inc
directive does not produce an error when the file cannot be found. directive does not produce an error when the file cannot be found.
Consequently, it is recommended that if the file you are including is Consequently, it is recommended that if the file you are including is
expected to exist, you should use expected to exist, you should use
require :ref:`require <require-inclusion>`
instead of instead of
include include
. Doing so makes sure that an error is produced if the file cannot be . Doing so makes sure that an error is produced if the file cannot be
@@ -756,9 +756,7 @@ recipename do_foo: fourth
.. note:: .. note::
Overrides and override-style operators can be applied to any shell Overrides and override-style operators can be applied to any shell
function, not just function, not just :ref:`tasks <bitbake-user-manual/bitbake-user-manual-metadata:Tasks>`.
tasks
.
You can use the ``bitbake -e`` recipename command to view the final You can use the ``bitbake -e`` recipename command to view the final
assembled function after all overrides have been applied. assembled function after all overrides have been applied.
@@ -1009,9 +1007,7 @@ Additionally, the ``do_printdate`` task becomes dependent upon the
after that initial run. If you want to force the task to always be after that initial run. If you want to force the task to always be
rerun for experimentation purposes, you can make BitBake always rerun for experimentation purposes, you can make BitBake always
consider the task "out-of-date" by using the consider the task "out-of-date" by using the
[ :ref:`[nostamp] <bitbake-user-manual/bitbake-user-manual-metadata:Variable Flags>`
nostamp
]
variable flag, as follows: variable flag, as follows:
:: ::
@@ -1082,7 +1078,7 @@ the build machine cannot influence the build.
things exported or listed in its whitelist to ensure that the build things exported or listed in its whitelist to ensure that the build
environment is reproducible and consistent. You can prevent this environment is reproducible and consistent. You can prevent this
"cleaning" by setting the "cleaning" by setting the
BB_PRESERVE_ENV :term:`BB_PRESERVE_ENV`
variable. variable.
Consequently, if you do want something to get passed into the build task Consequently, if you do want something to get passed into the build task
@@ -1397,11 +1393,11 @@ incarnations are buildable. These features are enabled through the
The mechanism for this class extension is extremely specific to the The mechanism for this class extension is extremely specific to the
implementation. Usually, the recipe's implementation. Usually, the recipe's
PROVIDES :term:`PROVIDES`
, ,
PN :term:`PN`
, and , and
DEPENDS :term:`DEPENDS`
variables would need to be modified by the extension class. For variables would need to be modified by the extension class. For
specific examples, see the OE-Core specific examples, see the OE-Core
native native

4
bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.rst
View File

@@ -484,7 +484,7 @@ overview of their function and contents.
.. note:: .. note::
This variable works similarly to the This variable works similarly to the
BB_TASK_NICE_LEVEL :term:`BB_TASK_NICE_LEVEL`
variable except with a task's I/O priorities. variable except with a task's I/O priorities.
Set the variable as follows: BB_TASK_IONICE_LEVEL = "class.prio" For Set the variable as follows: BB_TASK_IONICE_LEVEL = "class.prio" For
@@ -764,7 +764,7 @@ overview of their function and contents.
The bias provided by The bias provided by
DEFAULT_PREFERENCE DEFAULT_PREFERENCE
is weak and is overridden by is weak and is overridden by
BBFILE_PRIORITY :term:`BBFILE_PRIORITY`
if that variable is different between two layers that contain if that variable is different between two layers that contain
different versions of the same recipe. different versions of the same recipe.