ref-manual, bsp-guide: Added several cross-references to LICENSE_FLAGS.

Needed to add several links to the newly described
LICENSE_FLAGS variable in the glossary.  Three links added to the
ref-manual and a single link added to the BSP Guide.

(From yocto-docs rev: 2ca6e556c299814d6ef847ed059a4f0a2d48adb3)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

2 files changed, 14 insertions, 10 deletions

diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml
index 00d94b2009..26434c7c09 100644
--- a/documentation/bsp-guide/bsp.xml
+++ b/documentation/bsp-guide/bsp.xml
@@ -1002,9 +1002,10 @@
                 satisfy the licensing requirements for an encumbered BSP.
                 The following list describes them in order of preference:
                 <orderedlist>
-                    <listitem><para><emphasis>Use the <filename>LICENSE_FLAGS</filename> variable
-                        to define the recipes that have commercial or other types of
-                        specially-licensed packages:</emphasis>
+                    <listitem><para><emphasis>Use the
+                        <ulink url='&YOCTO_DOCS_REF_URL;#var-LICENSE_FLAGS'><filename>LICENSE_FLAGS</filename></ulink>
+                        variable to define the recipes that have commercial or other
+                        types of specially-licensed packages:</emphasis>
                         For each of those recipes, you can
                         specify a matching license string in a
                         <filename>local.conf</filename> variable named
diff --git a/documentation/ref-manual/technical-details.xml b/documentation/ref-manual/technical-details.xml
index 8bba42bdd4..446e9ed7c3 100644
--- a/documentation/ref-manual/technical-details.xml
+++ b/documentation/ref-manual/technical-details.xml
@@ -1207,8 +1207,9 @@
             components that have commercial or other special licensing
             requirements.
             Such requirements are defined on a
-            recipe-by-recipe basis through the <filename>LICENSE_FLAGS</filename> variable
-            definition in the affected recipe.
+            recipe-by-recipe basis through the
+            <ulink url='&YOCTO_DOCS_REF_URL;#var-LICENSE_FLAGS'><filename>LICENSE_FLAGS</filename></ulink>
+            variable definition in the affected recipe.
             For instance, the
             <filename>poky/meta/recipes-multimedia/gstreamer/gst-plugins-ugly</filename>
             recipe contains the following statement:
@@ -1269,9 +1270,10 @@
                         License flag matching allows you to control what recipes the
                 OpenEmbedded build system includes in the build.
                 Fundamentally, the build system attempts to match
-                <filename>LICENSE_FLAGS</filename> strings found in
-                recipes against <filename>LICENSE_FLAGS_WHITELIST</filename>
-                strings found in the whitelist.
+                <ulink url='&YOCTO_DOCS_REF_URL;#var-LICENSE_FLAGS'><filename>LICENSE_FLAGS</filename></ulink>
+                strings found in recipes against
+                <filename>LICENSE_FLAGS_WHITELIST</filename> strings found in
+                the whitelist.
                 A match causes the build system to include a recipe in the
                 build, while failure to find a match causes the build system to
                 exclude a recipe.
@@ -1393,8 +1395,9 @@
                 Of course, you could also create a matching whitelist
                 for those components using the more general "commercial"
                 in the whitelist, but that would also enable all the
-                other packages with <filename>LICENSE_FLAGS</filename> containing
-                "commercial", which you may or may not want:
+                other packages with
+                <ulink url='&YOCTO_DOCS_REF_URL;#var-LICENSE_FLAGS'><filename>LICENSE_FLAGS</filename></ulink>
+                containing "commercial", which you may or may not want:
                 <literallayout class='monospaced'>
      LICENSE_FLAGS_WHITELIST = "commercial"
                 </literallayout>