From bfa2803f8e626fbba9f1b012e999fb852d3044de Mon Sep 17 00:00:00 2001 From: Quentin Schulz Date: Wed, 29 Oct 2025 18:42:40 +0100 Subject: [PATCH] kernel-dev: common: migrate bitbake -e to bitbake-getvar 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". (From yocto-docs rev: 29836a95c01cdb99c38802f55a92f32377b8c524) Signed-off-by: Quentin Schulz Signed-off-by: Antonin Godard (cherry picked from commit 54585646d8220f8de1ba2c7246cb3f2fcbc59583) Signed-off-by: Antonin Godard Signed-off-by: Steve Sakoman --- documentation/kernel-dev/common.rst | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/documentation/kernel-dev/common.rst b/documentation/kernel-dev/common.rst index 9ff6ec221b..c0df39e391 100644 --- a/documentation/kernel-dev/common.rst +++ b/documentation/kernel-dev/common.rst @@ -1433,15 +1433,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 ============================================