From ae06e04cd225d2c2147ca355e2dd39b4f6cf6775 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Mon, 29 Jan 2018 15:18:03 -0800 Subject: documentation: Created new "Getting Started" manual. Creation involved removing the overview-manual and replacing it with the getting-started manual. All links to the string "&YOCTO_DOCS_OVERVIEW_URL" had to be replaced with "&YOCTO_DOCS_GS_URL" across the entire YP manual set. I renamed files used to create the manual with prefixes suited for the new manual name, which is "Getting Started With Yocto Project". The style sheet for the new manual needed updating to display the new .PNG image for the title page. The mega-manual file had to be updated to include the files. The mega-manual.sed file had to be updated to include the new manual and not use the overview manual. (From yocto-docs rev: 6c7abf9192390121000f577d6c98f259d290d15d) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- ...r-variables-related-to-commercial-licenses.html | 59 ++++++++++++++++++++++ 1 file changed, 59 insertions(+) create mode 100644 documentation/getting-started/eclipse/html/getting-started/other-variables-related-to-commercial-licenses.html (limited to 'documentation/getting-started/eclipse/html/getting-started/other-variables-related-to-commercial-licenses.html') diff --git a/documentation/getting-started/eclipse/html/getting-started/other-variables-related-to-commercial-licenses.html b/documentation/getting-started/eclipse/html/getting-started/other-variables-related-to-commercial-licenses.html new file mode 100644 index 0000000000..73d152bb40 --- /dev/null +++ b/documentation/getting-started/eclipse/html/getting-started/other-variables-related-to-commercial-licenses.html @@ -0,0 +1,59 @@ + + + +3.7.2.2. Other Variables Related to Commercial Licenses + + + + + + + +
+

+3.7.2.2. Other Variables Related to Commercial Licenses

+

+ Other helpful variables related to commercial + license handling exist and are defined in the + poky/meta/conf/distro/include/default-distrovars.inc file: +

+
+     COMMERCIAL_AUDIO_PLUGINS ?= ""
+     COMMERCIAL_VIDEO_PLUGINS ?= ""
+
+

+ If you want to enable these components, you can do so by + making sure you have statements similar to the following + in your local.conf configuration file: +

+
+     COMMERCIAL_AUDIO_PLUGINS = "gst-plugins-ugly-mad \
+        gst-plugins-ugly-mpegaudioparse"
+     COMMERCIAL_VIDEO_PLUGINS = "gst-plugins-ugly-mpeg2dec \
+        gst-plugins-ugly-mpegstream gst-plugins-bad-mpegvideoparse"
+     LICENSE_FLAGS_WHITELIST = "commercial_gst-plugins-ugly commercial_gst-plugins-bad commercial_qmmp"
+
+

+ 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 + LICENSE_FLAGS + containing "commercial", which you may or may not want: +

+
+     LICENSE_FLAGS_WHITELIST = "commercial"
+
+

+

+

+ Specifying audio and video plug-ins as part of the + COMMERCIAL_AUDIO_PLUGINS and + COMMERCIAL_VIDEO_PLUGINS statements + (along with the enabling + LICENSE_FLAGS_WHITELIST) includes the + plug-ins or components into built images, thus adding + support for media formats or components. +

+
+ -- cgit v1.2.3-54-g00ecf