mirror of
https://git.yoctoproject.org/poky
synced 2026-01-29 21:08:42 +01:00
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 <quentin.schulz@cherry.de> Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> (cherry picked from commit 54585646d8220f8de1ba2c7246cb3f2fcbc59583) Signed-off-by: Antonin Godard <antonin.godard@bootlin.com> Signed-off-by: Steve Sakoman <steve@sakoman.com>
This commit is contained in:
committed by
Steve Sakoman
parent
a6b0e3d404
commit
bfa2803f8e
@@ -1433,15 +1433,13 @@ Expanding Variables
|
|||||||
===================
|
===================
|
||||||
|
|
||||||
Sometimes it is helpful to determine what a variable expands to during a
|
Sometimes it is helpful to determine what a variable expands to during a
|
||||||
build. You can examine the values of variables by examining the
|
build. You can examine the value of a variable by running the ``bitbake-getvar``
|
||||||
output of the ``bitbake -e`` command. The output is long and is more
|
command::
|
||||||
easily managed in a text file, which allows for easy searches::
|
|
||||||
|
|
||||||
$ bitbake -e virtual/kernel > some_text_file
|
$ bitbake-getvar -r virtual/kernel VARIABLE
|
||||||
|
|
||||||
Within the text file, you can see
|
The output of the command explains exactly how the variable is expanded and used
|
||||||
exactly how each variable is expanded and used by the OpenEmbedded build
|
by the :term:`OpenEmbedded Build System`.
|
||||||
system.
|
|
||||||
|
|
||||||
Working with a "Dirty" Kernel Version String
|
Working with a "Dirty" Kernel Version String
|
||||||
============================================
|
============================================
|
||||||
|
|||||||
Reference in New Issue
Block a user