diff options
| author | Timo Mueller <timo.mueller@bmw-carit.de> | 2013-02-08 09:16:33 -0600 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-02-14 17:25:35 +0000 |
| commit | a41a805500cab281fba15bd8e5d3e60b88d0d4be (patch) | |
| tree | 9973678912b57cfdef5b1f9676794a556b4d8966 /documentation/ref-manual/eclipse/html/poky-ref-manual/other-variables-related-to-commercial-licenses.html | |
| parent | 768152340898cbb9faed6e8865a4e35c69833230 (diff) | |
| download | poky-a41a805500cab281fba15bd8e5d3e60b88d0d4be.tar.gz | |
documentation: Part 1 of 2 updates to integrating docs to Eclipse help.
Hi,
the generation of eclipse help files has been merged from the timo
branch to the master. Since the creation of the timo branch there have
been some changes to the master branch (e.g. new documentation,
renamed documentation).
This patch set does some cleanup for the renamed documentation and
adds eclipse help generation support to the new documentation.
01: Removes the 'the' from the document titles
02..04: Cleanup obsolete artifacts resulting from the merge
05..08: Add eclipse help generation for ref-manual
09..13: Add eclipse help generation for kernel-dev
14..18: Add eclipse help generation for profile-manual
Best regards,
Timo
This patch set originally contained 18 patches. I (Scott Rifenbark)
had to push these changes as two parts. This is the first part.
It does not include creation of the three cusomization files.
(From yocto-docs rev: 9b1889f6e31ee70dae704fa08763fb9196616dad)
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/eclipse/html/poky-ref-manual/other-variables-related-to-commercial-licenses.html')
| -rw-r--r-- | documentation/ref-manual/eclipse/html/poky-ref-manual/other-variables-related-to-commercial-licenses.html | 60 |
1 files changed, 0 insertions, 60 deletions
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/other-variables-related-to-commercial-licenses.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/other-variables-related-to-commercial-licenses.html deleted file mode 100644 index 31b096ec73..0000000000 --- a/documentation/ref-manual/eclipse/html/poky-ref-manual/other-variables-related-to-commercial-licenses.html +++ /dev/null | |||
| @@ -1,60 +0,0 @@ | |||
| 1 | <html> | ||
| 2 | <head> | ||
| 3 | <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> | ||
| 4 | <title>3.4.2.2. Other Variables Related to Commercial Licenses</title> | ||
| 5 | <link rel="stylesheet" type="text/css" href="../book.css"> | ||
| 6 | <meta name="generator" content="DocBook XSL Stylesheets V1.76.1"> | ||
| 7 | <link rel="home" href="index.html" title="The Yocto Project Reference Manual"> | ||
| 8 | <link rel="up" href="enabling-commercially-licensed-recipes.html" title="3.4.2. Enabling Commercially Licensed Recipes"> | ||
| 9 | <link rel="prev" href="license-flag-matching.html" title="3.4.2.1. License Flag Matching"> | ||
| 10 | <link rel="next" href="migration.html" title="Chapter 4. Migrating to a Newer Yocto Project Release"> | ||
| 11 | </head> | ||
| 12 | <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.4.2.2. Other Variables Related to Commercial Licenses"> | ||
| 13 | <div class="titlepage"><div><div><h4 class="title"> | ||
| 14 | <a name="other-variables-related-to-commercial-licenses"></a>3.4.2.2. Other Variables Related to Commercial Licenses</h4></div></div></div> | ||
| 15 | <p> | ||
| 16 | Other helpful variables related to commercial | ||
| 17 | license handling exist and are defined in the | ||
| 18 | <code class="filename">$HOME/poky/meta/conf/distro/include/default-distrovars.inc</code> file: | ||
| 19 | </p> | ||
| 20 | <pre class="literallayout"> | ||
| 21 | COMMERCIAL_AUDIO_PLUGINS ?= "" | ||
| 22 | COMMERCIAL_VIDEO_PLUGINS ?= "" | ||
| 23 | COMMERCIAL_QT = "" | ||
| 24 | </pre> | ||
| 25 | <p> | ||
| 26 | If you want to enable these components, you can do so by making sure you have | ||
| 27 | the following statements in your <code class="filename">local.conf</code> configuration file: | ||
| 28 | </p> | ||
| 29 | <pre class="literallayout"> | ||
| 30 | COMMERCIAL_AUDIO_PLUGINS = "gst-plugins-ugly-mad \ | ||
| 31 | gst-plugins-ugly-mpegaudioparse" | ||
| 32 | COMMERCIAL_VIDEO_PLUGINS = "gst-plugins-ugly-mpeg2dec \ | ||
| 33 | gst-plugins-ugly-mpegstream gst-plugins-bad-mpegvideoparse" | ||
| 34 | COMMERCIAL_QT ?= "qmmp" | ||
| 35 | LICENSE_FLAGS_WHITELIST = "commercial_gst-plugins-ugly commercial_gst-plugins-bad commercial_qmmp" | ||
| 36 | </pre> | ||
| 37 | <p> | ||
| 38 | Of course, you could also create a matching whitelist | ||
| 39 | for those components using the more general "commercial" | ||
| 40 | in the whitelist, but that would also enable all the | ||
| 41 | other packages with <code class="filename">LICENSE_FLAGS</code> containing | ||
| 42 | "commercial", which you may or may not want: | ||
| 43 | </p> | ||
| 44 | <pre class="literallayout"> | ||
| 45 | LICENSE_FLAGS_WHITELIST = "commercial" | ||
| 46 | </pre> | ||
| 47 | <p> | ||
| 48 | </p> | ||
| 49 | <p> | ||
| 50 | Specifying audio and video plug-ins as part of the | ||
| 51 | <code class="filename">COMMERCIAL_AUDIO_PLUGINS</code> and | ||
| 52 | <code class="filename">COMMERCIAL_VIDEO_PLUGINS</code> statements | ||
| 53 | or commercial qt components as part of | ||
| 54 | the <code class="filename">COMMERCIAL_QT</code> statement (along | ||
| 55 | with the enabling <code class="filename">LICENSE_FLAGS_WHITELIST</code>) includes the | ||
| 56 | plug-ins or components into built images, thus adding | ||
| 57 | support for media formats or components. | ||
| 58 | </p> | ||
| 59 | </div></body> | ||
| 60 | </html> | ||