Skip to content

slides: yocto: mention use of bitbake-getvar -r sooner #348

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
antznin wants to merge 1 commit into
base: master
Choose a base branch
from
Open

slides: yocto: mention use of bitbake-getvar -r sooner #348

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions slides/yocto-advanced/yocto-advanced.typ
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -226,11 +226,14 @@
- `bitbake-getvar` can be used to understand and debug how variables are
assigned

- `bitbake-getvar <VARIABLE>`

- Lists each configuration file touching the variable, the pre-expansion
value and the final value

- `bitbake-getvar <VARIABLE>`: dump the variable value in the *global* scope

- `bitbake-getvar -r <recipe> <VARIABLE>`: dump the variable value in the
*local* scope of `recipe`

#v(0.5em)

```console
Expand Down
8 changes: 4 additions & 4 deletions slides/yocto-recipe-basics/yocto-recipe-basics.typ
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -581,16 +581,16 @@ SRC_URI[sha256sum] = "731140004fdb6..."

- These can be inspected to understand what is being done by the tasks

=== Debugging variable assignment
=== Debugging variable assignments

- `bitbake-getvar` can dump the per-recipe variable value using the `-r`
- (Reminder) `bitbake-getvar` can dump the per-recipe variable value using the `-r`
option

- `bitbake-getvar -r ncurses SRC_URI`

- Similarly, `bitbake -e` dumps the entire environment, and also the
task code

- `bitbake -e`
- `bitbake -e` (*global* environment)

- `bitbake -e ncurses`
- `bitbake -e ncurses` (environment of `ncurses`)
Loading