10099 2016-08-08 20:42:57 +0000 Clarifying and fleshing out debugging with 'bitbake -e' 2016-08-08 21:43:28 +0000 1 1 9 Documentation Reference handbook 2.2 x86 Multiple RESOLVED FIXED 08 August 2016: RESOLVED Undecided normal 2.2 M4 1 ulfalizer srifenbark bluelightning poky.doc.watcher poky.watcher srifenbark --- --- Done (doc changes complete) oldest_to_newest 64969 0 ulfalizer 2016-08-08 20:42:57 +0000 I suggest the following changes. 'bitbake -e' is a very important debugging aid, hence why I think it should be moved earlier. I have also seen people being confused about the "scope" of variables, so I'll piggyback a note that might help. * Rename '2.3.1. Task Failures' to '2.3.1. Viewing logs from failed tasks'. * Move '2.3.8 Variables' to 2.3.2. and rename it to '2.3.2. Viewing variable values' (this makes it consistent with 2.3.1). Rewrite it like this to clarify and flesh it out: BitBake's -e option is used to display variable values after parsing. The following command displays the variable values after the configuration (local.conf, bblayers.conf, etc.) has been parsed. $ bitbake -e The following command displays variable values after a specific recipe has been parsed. This includes variables from the configuration as well. $ bitbake -e recipename Note { Each recipe has its own private set of variables (datastore). Internally, after parsing the configuration, a copy of the resulting datastore is made prior to parsing each recipe. This implies that variables set in one recipe won't be visible to other recipes. Likewise, each task within a recipe gets a private datastore based on the recipe datastore, meaning variables set within one task won't be visible to other tasks. } In the output of bitbake -e, each variable is preceded by a description of how the variable got its value, including temporary values that were later overriden. This description also includes variable flags (varflags) set on the variable. This can be a very handy debugging aid. Cheers, Ulf 64972 1 ulfalizer 2016-08-08 21:10:28 +0000 Here's another thing that could be added to the end. I picked CC since it's an important variable. Variables that are exported to the environment are preceded by 'export' in the output of 'bitbake -e', like in the example below. export CC="i586-poky-linux-gcc -m32 -march=i586 --sysroot=/home/ulf/poky/build/tmp/sysroots/qemux86" 64973 2 srifenbark 2016-08-08 21:17:23 +0000 Ulf, See http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#usingpoky-debugging-viewing-logs-from-failed-tasks for the rename of the log section. See http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#usingpoky-debugging-viewing-variable-values for the renamed and repositions section on viewing variable values. Thanks, Scott 64974 3 ulfalizer 2016-08-08 21:20:33 +0000 "The output can be a very help during debugging." Looks fine other than that. :) Note the 'export' section I added too. Thanks, Ulf 64975 4 srifenbark 2016-08-08 21:24:25 +0000 ok - see http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#usingpoky-debugging-viewing-variable-values. Had a mid-air collision on Comment 1... Had a finger failure on that last sentence... :) Check it out now :) http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#usingpoky-debugging-viewing-variable-values 64976 5 ulfalizer 2016-08-08 21:27:22 +0000 Looks good now! Thanks, Ulf 64977 6 srifenbark 2016-08-08 21:43:28 +0000 Thanks - resetting doc flag and putting as RESOLVED Scott