From e1453702a57de2b39b42671040cfec6069480a0e Mon Sep 17 00:00:00 2001 From: "Robert P. J. Day" Date: Wed, 29 Oct 2025 06:32:09 -0400 Subject: [PATCH] dev-manual/new-recipe.rst: replace 'bitbake -e' with 'bitbake-getvar' Replace the legacy call to 'bitbake -e' to get the value of a recipe's variable with the newer call to 'bitbake-getvar'. (From yocto-docs rev: 042c4cb8c6291be857a672144b573a5eb10f1ead) Signed-off-by: Robert P. J. Day Reviewed-by: Quentin Schulz Signed-off-by: Antonin Godard (cherry picked from commit ed7c0766ef5f13b90943a69e64f8e8713d05e864) Signed-off-by: Antonin Godard Signed-off-by: Steve Sakoman --- documentation/dev-manual/new-recipe.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/documentation/dev-manual/new-recipe.rst b/documentation/dev-manual/new-recipe.rst index b97e807ead..c9c5689ecc 100644 --- a/documentation/dev-manual/new-recipe.rst +++ b/documentation/dev-manual/new-recipe.rst @@ -219,9 +219,9 @@ compilation and packaging files, and so forth. The path to the per-recipe temporary work directory depends on the context in which it is being built. The quickest way to find this path -is to have BitBake return it by running the following:: +is to use the ``bitbake-getvar`` utility:: - $ bitbake -e basename | grep ^WORKDIR= + $ bitbake-getvar -r basename WORKDIR As an example, assume a Source Directory top-level folder named ``poky``, a default :term:`Build Directory` at