From 68bd063fb96f9190885d305d0141c0a66c77662b Mon Sep 17 00:00:00 2001
From: Scott Rifenbark <scott.m.rifenbark@intel.com>
Date: Tue, 1 Jul 2014 09:26:12 +0300
Subject: 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>
---
 documentation/bsp-guide/bsp.xml | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

(limited to 'documentation/bsp-guide/bsp.xml')

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
-- 
cgit v1.2.3-54-g00ecf