diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2014-07-01 09:26:12 +0300 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2014-07-03 13:57:11 +0100 |
commit | 68bd063fb96f9190885d305d0141c0a66c77662b (patch) | |
tree | 7bf91c983630b683bc89d14776000ef343e6d154 /documentation/ref-manual/technical-details.xml | |
parent | a53950ad2c9f468ef1700d71e26163bd5f204c21 (diff) | |
download | openembedded-core-contrib-68bd063fb96f9190885d305d0141c0a66c77662b.tar.gz |
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>
Diffstat (limited to 'documentation/ref-manual/technical-details.xml')
-rw-r--r-- | documentation/ref-manual/technical-details.xml | 17 |
1 files changed, 10 insertions, 7 deletions
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> |