diff mbox series

[1/3] kernel-dev: common: migrate bitbake -e to bitbake-getvar

Message ID 20251029-bitbake-e-v1-1-c06ad212db9e@cherry.de
State New
Headers show
Series migrate most bitbake -e instructions to bitbake-getvar | expand

Commit Message

Quentin Schulz Oct. 29, 2025, 5:42 p.m. UTC 
From: Quentin Schulz <quentin.schulz@cherry.de>

It's recommended to use bitbake-getvar for a few releases now so let's
use that instead of bitbake -e.

While at it, use a cross-reference for "OpenEmbedded Build System".

Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
 documentation/kernel-dev/common.rst | 12 +++++-------
 1 file changed, 5 insertions(+), 7 deletions(-)
diff mbox series

Patch

diff --git a/documentation/kernel-dev/common.rst b/documentation/kernel-dev/common.rst
index bd6c3fb2c..ef9a8d8fe 100644
--- a/documentation/kernel-dev/common.rst
+++ b/documentation/kernel-dev/common.rst
@@ -1431,15 +1431,13 @@  Expanding Variables
 ===================
 
 Sometimes it is helpful to determine what a variable expands to during a
-build. You can examine the values of variables by examining the
-output of the ``bitbake -e`` command. The output is long and is more
-easily managed in a text file, which allows for easy searches::
+build. You can examine the value of a variable by running the ``bitbake-getvar``
+command::
 
-   $ bitbake -e virtual/kernel > some_text_file
+   $ bitbake-getvar -r virtual/kernel VARIABLE
 
-Within the text file, you can see
-exactly how each variable is expanded and used by the OpenEmbedded build
-system.
+The output of the command explains exactly how the variable is expanded and used
+by the :term:`OpenEmbedded Build System`.
 
 Working with a "Dirty" Kernel Version String
 ============================================