mirror of
https://git.yoctoproject.org/poky-contrib
synced 2025-10-14 03:05:35 +08:00
bitbake: doc: extend classes and include/require documentation
The current documentation is lacking details on the different kinds of directories for putting classes as well as the order in which BitBake includes files (classes or include files). This patch does the following changes: - Mention the missing classes-recipe and classes-global when applicable. - Add a Class Types section detailed the three different directories for putting classes. - Move the existing section on locating classes/include files below the documentation on the different directives (include/require/inherit). - Extend the documentation on locating files with include/require and inherit to give proper examples, hopefully demystifying this mechanism a bit. [YOCTO #15724] (Bitbake rev: 7bd36f6c6d33211bb2a6b6fc6d40bdbd83b8b7c3) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Antonin Godard
committed by
Richard Purdie
Richard Purdie
parent
44029f9fb5
commit
ae290dd402
@@ -64,11 +64,11 @@ data itself is of various types:
|
||||
together.
|
||||
|
||||
The ``layer.conf`` files are used to construct key variables such as
|
||||
:term:`BBPATH` and :term:`BBFILES`.
|
||||
:term:`BBPATH` is used to search for configuration and class files under the
|
||||
``conf`` and ``classes`` directories, respectively. :term:`BBFILES` is used
|
||||
to locate both recipe and recipe append files (``.bb`` and
|
||||
``.bbappend``). If there is no ``bblayers.conf`` file, it is assumed the
|
||||
:term:`BBPATH` and :term:`BBFILES`. :term:`BBPATH` is used to search for
|
||||
configuration files under the ``conf`` directory and class files under the
|
||||
``classes-global``, ``classes-recipe`` and ``classes`` directories.
|
||||
:term:`BBFILES` is used to locate both recipe and recipe append files (``.bb``
|
||||
and ``.bbappend``). If there is no ``bblayers.conf`` file, it is assumed the
|
||||
user has set the :term:`BBPATH` and :term:`BBFILES` directly in the environment.
|
||||
|
||||
Next, the ``bitbake.conf`` file is located using the :term:`BBPATH` variable
|
||||
|
||||
@@ -206,17 +206,33 @@ installing (empty by default) and packaging (empty by default). These
|
||||
tasks are often overridden or extended by other classes added during the
|
||||
project development process.
|
||||
|
||||
.. note::
|
||||
Class Types
|
||||
~~~~~~~~~~~
|
||||
|
||||
While BitBake comes with just the one ``base.bbclass`` file in the
|
||||
``classes`` directory, it supports class files also being installed
|
||||
in related directories ``classes-global`` and ``classes-recipe`` and
|
||||
will automatically search all three directories for a selected class
|
||||
file.
|
||||
BitBake supports class files installed in three different directories:
|
||||
|
||||
This means that, in this documentation, when you see a reference to
|
||||
class files being in the ``classes`` directory, you can interpret that
|
||||
as meaning in any one of the above three directories.
|
||||
- ``classes-global/``: these classes must be inherited globally through the
|
||||
:term:`INHERIT` variable in a :ref:`configuration file
|
||||
<bitbake-user-manual/bitbake-user-manual-intro:Configuration Files>`. These
|
||||
classes are included for every recipe being built. For example, you would use
|
||||
the global class named ``myclass`` like so::
|
||||
|
||||
INHERIT += "myclass"
|
||||
|
||||
- ``classes-recipe/``: these classes must be inherited from a recipe using the
|
||||
:ref:`inherit <ref-bitbake-user-manual-metadata-inherit>` directive. They do
|
||||
not support being inherited globally. For example, you would use the recipe
|
||||
class named ``myclass`` like so::
|
||||
|
||||
inherit myclass
|
||||
|
||||
- ``classes/``: this final directory is meant for classes that can be used in
|
||||
the two contexts explain above. In other words, they can be inherit either
|
||||
globally or in a recipe.
|
||||
|
||||
For details on how BitBake locates class files, see the
|
||||
:ref:`bitbake-user-manual/bitbake-user-manual-metadata:Locating Class Files`
|
||||
section of the Bitbake User Manual.
|
||||
|
||||
Layers
|
||||
------
|
||||
|
||||
@@ -758,21 +758,6 @@ directives. There is also a higher-level abstraction called
|
||||
``configuration fragments`` that is enabled with ``addfragments``
|
||||
directive.
|
||||
|
||||
Locating Include and Class Files
|
||||
--------------------------------
|
||||
|
||||
BitBake uses the :term:`BBPATH` variable to locate
|
||||
needed include and class files. Additionally, BitBake searches the
|
||||
current directory for ``include`` and ``require`` directives.
|
||||
|
||||
.. note::
|
||||
|
||||
The BBPATH variable is analogous to the environment variable PATH .
|
||||
|
||||
In order for include and class files to be found by BitBake, they need
|
||||
to be located in a "classes" subdirectory that can be found in
|
||||
:term:`BBPATH`.
|
||||
|
||||
.. _ref-bitbake-user-manual-metadata-inherit:
|
||||
|
||||
``inherit`` Directive
|
||||
@@ -874,6 +859,8 @@ becomes a no-op.
|
||||
See also :term:`BB_DEFER_BBCLASSES` for automatically promoting classes
|
||||
``inherit`` calls to ``inherit_defer``.
|
||||
|
||||
.. _ref-include-directive:
|
||||
|
||||
``include`` Directive
|
||||
---------------------
|
||||
|
||||
@@ -908,6 +895,8 @@ if the file cannot be found.
|
||||
If you need to include all matching files, you need to use the
|
||||
``include_all`` directive, explained below.
|
||||
|
||||
.. _ref-include-all-directive:
|
||||
|
||||
``include_all`` Directive
|
||||
-------------------------
|
||||
|
||||
@@ -1062,6 +1051,103 @@ bitbake will treat that as direct value assignment in its configuration::
|
||||
|
||||
SOMEVARIABLE = "somevalue"
|
||||
|
||||
Locating Include Files
|
||||
----------------------
|
||||
|
||||
BitBake uses the :term:`BBPATH` variable to locate needed include files.
|
||||
Additionally, BitBake searches the current directory for :ref:`include
|
||||
<ref-include-directive>` and :ref:`require <require-inclusion>` directives.
|
||||
|
||||
.. note::
|
||||
|
||||
The BBPATH variable is analogous to the environment variable PATH .
|
||||
|
||||
For these two directives, BitBake includes the first file it finds.
|
||||
|
||||
.. note::
|
||||
|
||||
It is also possible to include *all* occurences of a file with the same name
|
||||
with the :ref:`include_all <ref-include-all-directive>` directive.
|
||||
|
||||
Let's consider the following statement called from a recipe file located in
|
||||
``/layers/meta-custom2/recipes-example/example_0.1.bb``::
|
||||
|
||||
require myfile.inc
|
||||
|
||||
Where ``myfile.inc`` is located in ``/layers/meta-custom2/recipes-example/``.
|
||||
|
||||
And let's assume that the value of :term:`BBPATH` is
|
||||
``/layers/meta-custom1:/layers/meta-custom2``. Then BitBake will try to find
|
||||
``myfile.inc`` in this order::
|
||||
|
||||
/layers/meta-custom2/recipes-example/example/myfile.inc
|
||||
/layers/meta-custom1/myfile.inc
|
||||
/layers/meta-custom2/myfile.inc
|
||||
|
||||
In this case the first path of the list matches and BitBake includes this file
|
||||
in ``example_0.1.bb``.
|
||||
|
||||
Another common example would be::
|
||||
|
||||
require recipes-other/other/otherfile.inc
|
||||
|
||||
Where ``otherfile.inc`` is located in
|
||||
``/layers/meta-custom1/recipes-other/other/``.
|
||||
|
||||
In this case, the following paths would be searched::
|
||||
|
||||
/layers/meta-custom2/recipes-example/example/recipes-other/other/otherfile.inc
|
||||
/layers/meta-custom1/recipes-other/other/otherfile.inc
|
||||
/layers/meta-custom2/recipes-other/other/otherfile.inc
|
||||
|
||||
This time, the second item of this list would be matched.
|
||||
|
||||
.. note::
|
||||
|
||||
In the above examples, the exact same search order applies for the
|
||||
:ref:`include <ref-include-directive>` directive.
|
||||
|
||||
Locating Class Files
|
||||
--------------------
|
||||
|
||||
Like include files, class files are located using the :term:`BBPATH` variable.
|
||||
The classes can be included in the ``classes-recipe``, ``classes-global`` and
|
||||
``classes`` directories, as explained in the
|
||||
:ref:`bitbake-user-manual/bitbake-user-manual-intro:Class types` section of the
|
||||
Bitbake User Manual. Like for the :ref:`include <ref-include-directive>` and
|
||||
:ref:`require <require-inclusion>` directives, BitBake stops and inherits the
|
||||
first class that it finds.
|
||||
|
||||
For classes inherited with the :ref:`inherit
|
||||
<ref-bitbake-user-manual-metadata-inherit>` directive, BitBake will try to
|
||||
locate the class under each ``classes-recipe`` directory for each path in
|
||||
:term:`BBPATH`, and then do the same for each ``classes`` directory for each
|
||||
path in :term:`BBPATH`.
|
||||
|
||||
For example, if the value :term:`BBPATH` is
|
||||
``/layers/meta-custom1:/layers/meta-custom2`` then the ``hello`` class
|
||||
would be searched in this order::
|
||||
|
||||
/layers/meta-custom1/classes-recipe/hello.bbclass
|
||||
/layers/meta-custom2/classes-recipe/hello.bbclass
|
||||
/layers/meta-custom1/classes/hello.bbclass
|
||||
/layers/meta-custom2/classes/hello.bbclass
|
||||
|
||||
.. note::
|
||||
|
||||
Note that the order of the list above does not depend on where the class in
|
||||
inherited from.
|
||||
|
||||
Likewise, for classes inherited with the :term:`INHERIT` variable, the
|
||||
``classes-global`` directory is searched first, and the ``classes`` directory is
|
||||
searched second. Taking the above example, this would result in the following
|
||||
list::
|
||||
|
||||
/layers/meta-custom1/classes-global/hello.bbclass
|
||||
/layers/meta-custom2/classes-global/hello.bbclass
|
||||
/layers/meta-custom1/classes/hello.bbclass
|
||||
/layers/meta-custom2/classes/hello.bbclass
|
||||
|
||||
Functions
|
||||
=========
|
||||
|
||||
|
||||
Reference in New Issue
Block a user