mirror of
https://git.yoctoproject.org/poky
synced 2026-05-09 17:39:31 +00:00
sphinx: fix custom term links
Some term links have custom 'text', and require manual update, since they were not caught by the generic Python regexp. (From yocto-docs rev: 519355ba9daf7630e8d477b2f6f511be51fd8b2e) Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
committed by
Richard Purdie
parent
7b87ca796a
commit
4bf6fc5281
@@ -1366,10 +1366,10 @@ release notes
|
||||
Kernel Module Autoloading
|
||||
-------------------------
|
||||
|
||||
The ```module_autoload_*`` <#var-module_autoload>`__ variable is now
|
||||
The :term:`module_autoload_* <module_autoload>` variable is now
|
||||
deprecated and a new
|
||||
:term:`KERNEL_MODULE_AUTOLOAD` variable
|
||||
should be used instead. Also, ```module_conf_*`` <#var-module_conf>`__
|
||||
should be used instead. Also, :term:`module_conf_* <module_conf>`
|
||||
must now be used in conjunction with a new
|
||||
:term:`KERNEL_MODULE_PROBECONF` variable.
|
||||
The new variables no longer require you to specify the module name as
|
||||
|
||||
@@ -377,12 +377,12 @@ information.
|
||||
Stages (copies) a subset of the files installed by the
|
||||
:ref:`ref-tasks-install` task into the appropriate
|
||||
sysroot. For information on how to access these files from other
|
||||
recipes, see the ```STAGING_DIR*`` <#var-STAGING_DIR_HOST>`__ variables.
|
||||
recipes, see the :term:`STAGING_DIR* <STAGING_DIR_HOST>` variables.
|
||||
Directories that would typically not be needed by other recipes at build
|
||||
time (e.g. ``/etc``) are not copied by default.
|
||||
|
||||
For information on what directories are copied by default, see the
|
||||
```SYSROOT_DIRS*`` <#var-SYSROOT_DIRS>`__ variables. You can change
|
||||
:term:`SYSROOT_DIRS* <SYSROOT_DIRS>` variables. You can change
|
||||
these variables inside your recipe if you need to make additional (or
|
||||
fewer) directories available to other recipes at build time.
|
||||
|
||||
@@ -451,7 +451,7 @@ section for information on checking the upgrade status of a recipe.
|
||||
|
||||
To build the ``checkpkg`` task, use the ``bitbake`` command with the
|
||||
"-c" option and task name: $ bitbake core-image-minimal -c checkpkg By
|
||||
default, the results are stored in ```$LOG_DIR`` <#var-LOG_DIR>`__ (e.g.
|
||||
default, the results are stored in :term:`$LOG_DIR <LOG_DIR>` (e.g.
|
||||
``$BUILD_DIR/tmp/log``).
|
||||
|
||||
.. _ref-tasks-checkuri:
|
||||
|
||||
@@ -1473,7 +1473,7 @@ system and gives an overview of their function and contents.
|
||||
assignment: DEPENDS = "bar" The practical effect of the previous
|
||||
assignment is that all files installed by bar will be available in
|
||||
the appropriate staging sysroot, given by the
|
||||
```STAGING_DIR*`` <#var-STAGING_DIR>`__ variables, by the time the
|
||||
:term:`STAGING_DIR* <STAGING_DIR>` variables, by the time the
|
||||
:ref:`ref-tasks-configure` task for ``foo`` runs.
|
||||
This mechanism is implemented by having ``do_configure`` depend on
|
||||
the :ref:`ref-tasks-populate_sysroot` task of
|
||||
@@ -3599,7 +3599,7 @@ system and gives an overview of their function and contents.
|
||||
expects to find ``module_conf_``\ modname values that specify
|
||||
configuration for each of the modules. For information on how to
|
||||
provide those module configurations, see the
|
||||
```module_conf_*`` <#var-module_conf>`__ variable.
|
||||
:term:`module_conf_* <module_conf>` variable.
|
||||
|
||||
KERNEL_PATH
|
||||
The location of the kernel sources. This variable is set to the value
|
||||
|
||||
Reference in New Issue
Block a user