]> git.ipfire.org Git - thirdparty/openembedded/openembedded-core-contrib.git/commitdiff
dev-manual: Added reasoning blurb to "Viewing Variables" section.
authorScott Rifenbark <srifenbark@gmail.com>
Fri, 19 Apr 2019 16:51:59 +0000 (09:51 -0700)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Tue, 7 May 2019 09:23:41 +0000 (10:23 +0100)
I put a new introductory paragraph in the "Viewing Variables"
section that alludes to why you might want to see variables.
Also, I linked to the section "Modifying Variable Values" in
the BB manual.

(From yocto-docs rev: 6e18524ba62d2ff1231184467b0dd24dab33cfe6)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
documentation/dev-manual/dev-manual-common-tasks.xml

index 5ac167d05127a601b44c1de11fe31c0776496561..0fcb7b706476cb8e563124a6fded8e9d05b0bd60 100644 (file)
         <section id='dev-debugging-viewing-variable-values'>
             <title>Viewing Variable Values</title>
 
+            <para>
+                Sometimes you need to know the value of a variable as a
+                result of BitBake's parsing step.
+                This could be because some unexpected behavior occurred
+                in your project.
+                Perhaps an attempt to
+                <ulink url='&YOCTO_DOCS_BB_URL;#modifying-existing-variables'>modify a variable</ulink>
+                did not work out as expected.
+            </para>
+
             <para>
                 BitBake's <filename>-e</filename> option is used to display
                 variable values after parsing.