From 22a70fbc3e37b9139aa4a4eff6254e9a8444390b Mon Sep 17 00:00:00 2001 From: aatir Date: Thu, 23 Jun 2022 13:37:10 -0400 Subject: 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 Reviewed-by: Michael Opdenacker (From yocto-docs rev: 4b39a4434ee658512050c50f6ebd5ad5dc900fb1) Signed-off-by: Richard Purdie --- documentation/ref-manual/features.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'documentation/ref-manual/features.rst') diff --git a/documentation/ref-manual/features.rst b/documentation/ref-manual/features.rst index a8d0dac996..17521ac2a8 100644 --- a/documentation/ref-manual/features.rst +++ b/documentation/ref-manual/features.rst @@ -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 -- cgit v1.2.3-54-g00ecf