docs: make DISTRO_FEATURES description more explicit

Make DISTRO_FEATURES description more explicit by specifying
that DISTRO_FEATURES alone can't select build configurations,
and need mechanisms like PACKAGECONFIG setup to take care of
selecting build configurations.

Signed-off-by Aatir Manzur <aatrapps@gmail.com>
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>

(From yocto-docs rev: 4b39a4434ee658512050c50f6ebd5ad5dc900fb1)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
aatir
2022-06-23 13:37:10 -04:00
committed by Richard Purdie
parent 17d0d15be1
commit 22a70fbc3e
2 changed files with 7 additions and 2 deletions

View File

@@ -100,7 +100,9 @@ packages, and they can go beyond simply controlling the installation of
a package or packages. In most cases, the presence or absence of a
feature translates to the appropriate option supplied to the configure
script during the :ref:`ref-tasks-configure` task for
the recipes that optionally support the feature.
the recipes that optionally support the feature. Appropriate options
must be supplied, and enabling/disabling :term:`PACKAGECONFIG` for the
concerned packages is one way of supplying such options.
Some distro features are also machine features. These select features
make sense to be controlled both at the machine and distribution

View File

@@ -1873,7 +1873,10 @@ system and gives an overview of their function and contents.
optionally support the feature. For example, specifying "x11" in
:term:`DISTRO_FEATURES`, causes every piece of software built for the
target that can optionally support X11 to have its X11 support
enabled.
enabled. Note: just enabling :term:`DISTRO_FEATURES` alone doesn't
enable feature support for packages, mechanisms such as making
:term:`PACKAGECONFIG` track :term:`DISTRO_FEATURES` are used
to enable/disable package features.
Two more examples are Bluetooth and NFS support. For a more complete
list of features that ships with the Yocto Project and that you can