From: Antonin Godard <antonin.godard@bootlin.com>
To: docs@lists.yoctoproject.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Antonin Godard <antonin.godard@bootlin.com>
Subject: [PATCH 10/10] ref-manual/variables.rst: mention built-in fragments for MACHINE/DISTRO
Date: Fri, 11 Sep 2026 16:56:10 +0200 [thread overview]
Message-ID: <20260911-assorted-fixes-v1-10-0d92a8112918@bootlin.com> (raw)
In-Reply-To: <20260911-assorted-fixes-v1-0-0d92a8112918@bootlin.com>
In the MACHINE and DISTRO variable description, mention that these can
be set either with their built-in fragments, or from the local.conf
file.
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
documentation/ref-manual/variables.rst | 33 +++++++++++++++++++++++++++------
1 file changed, 27 insertions(+), 6 deletions(-)
diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index 4a41e3501..f76e5ba4d 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -2441,6 +2441,20 @@ system and gives an overview of their function and contents.
of the distribution, see the :term:`DISTRO_NAME`
variable.
+ You can define the :term:`DISTRO` in two ways:
+
+ - with the :ref:`ref-fragments-builtin-core-distro` fragment:
+
+ .. code-block:: console
+
+ $ bitbake-config-build enable-fragment distro/<DISTRO>
+
+ Replace ``<DISTRO>`` with the name of the distro in the above
+ command.
+
+ - in the :ref:`structure-build-conf-local.conf` file found in the
+ :term:`Build Directory`.
+
The :term:`DISTRO` variable corresponds to a distribution configuration
file whose root name is the same as the variable's argument and whose
filename extension is ``.conf``. For example, the distribution
@@ -6121,13 +6135,20 @@ system and gives an overview of their function and contents.
in-use.
:term:`MACHINE`
- Specifies the target device for which the image is built. You define
- :term:`MACHINE` in the ``local.conf`` file found in the
- :term:`Build Directory`. By default, :term:`MACHINE` is set to
- "qemux86", which is an x86-based architecture machine to be emulated
- using QEMU::
+ Specifies the target device for which the image is built. You can define
+ the :term:`MACHINE` in two ways:
- MACHINE ?= "qemux86"
+ - with the :ref:`ref-fragments-builtin-core-machine` fragment:
+
+ .. code-block:: console
+
+ $ bitbake-config-build enable-fragment machine/<MACHINE>
+
+ Replace ``<MACHINE>`` with the name of the machine in the above
+ command.
+
+ - in the :ref:`structure-build-conf-local.conf` file found in the
+ :term:`Build Directory`.
The variable corresponds to a machine configuration file of the same
name, through which machine-specific configurations are set. Thus,
--
2.55.0
next prev parent reply other threads:[~2026-09-11 14:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 14:56 [PATCH 00/10] Assorted fixes and additions Antonin Godard
2026-09-11 14:56 ` [PATCH 01/10] security-manual/securing-images.rst: remove "your" in "your OE-Core" Antonin Godard
2026-09-11 14:56 ` [PATCH 02/10] bsp-manual/bsp.rst: fix a "local.conf" -> "layer.conf" typo Antonin Godard
2026-09-11 14:56 ` [PATCH 03/10] ref-manual/structure.rst: " Antonin Godard
2026-09-11 14:56 ` [PATCH 04/10] ref-manual/varlocality.rst: mention built-in fragments for distro/machine Antonin Godard
2026-09-11 14:56 ` [PATCH 05/10] ref-manual/varlocality.rst: remove BBFILES from local configuration assignments Antonin Godard
2026-09-11 14:56 ` [PATCH 06/10] ref-manual/features.rst: add tools-profile Antonin Godard
2026-09-11 14:56 ` [PATCH 07/10] ref-manual/variables.rst: BBMULTICONFIG: fix a typo Antonin Godard
2026-09-11 14:56 ` [PATCH 08/10] dev-manual/poky-manual-setup.rst: suggest use of fragment instead of assignments Antonin Godard
2026-09-11 14:56 ` [PATCH 09/10] ref-manual/variables.rst: fix local.conf.extended obsolete path Antonin Godard
2026-09-11 14:56 ` Antonin Godard [this message]
2026-09-17 14:52 ` [PATCH 00/10] Assorted fixes and additions Antonin Godard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260911-assorted-fixes-v1-10-0d92a8112918@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=thomas.petazzoni@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.