From: Scott Rifenbark <srifenbark@gmail.com>
Date: Fri, 19 Apr 2019 16:51:59 +0000 (-0700)
Subject: dev-manual: Added reasoning blurb to "Viewing Variables" section.
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=f60698d54b5bda031eab9f24359a9fd44669c23b;p=thirdparty%2Fopenembedded%2Fopenembedded-core-contrib.git

dev-manual: Added reasoning blurb to "Viewing Variables" section.

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>
---

diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 5ac167d0512..0fcb7b70647 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -12525,6 +12525,16 @@
         <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.