generic-poky/documentation/ref-manual/eclipse/html/poky-ref-manual/other-variables-related-to-...

61 lines
3.2 KiB
HTML
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>3.4.2.2. Other Variables Related to Commercial Licenses</title>
<link rel="stylesheet" type="text/css" href="../book.css">
<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
<link rel="home" href="index.html" title="The Yocto Project Reference Manual">
<link rel="up" href="enabling-commercially-licensed-recipes.html" title="3.4.2. Enabling Commercially Licensed Recipes">
<link rel="prev" href="license-flag-matching.html" title="3.4.2.1. License Flag Matching">
<link rel="next" href="migration.html" title="Chapter 4. Migrating to a Newer Yocto Project Release">
</head>
<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">
<div class="titlepage"><div><div><h4 class="title">
<a name="other-variables-related-to-commercial-licenses"></a>3.4.2.2. Other Variables Related to Commercial Licenses</h4></div></div></div>
<p>
Other helpful variables related to commercial
license handling exist and are defined in the
<code class="filename">$HOME/poky/meta/conf/distro/include/default-distrovars.inc</code> file:
</p>
<pre class="literallayout">
COMMERCIAL_AUDIO_PLUGINS ?= ""
COMMERCIAL_VIDEO_PLUGINS ?= ""
COMMERCIAL_QT = ""
</pre>
<p>
If you want to enable these components, you can do so by making sure you have
the following statements in your <code class="filename">local.conf</code> configuration file:
</p>
<pre class="literallayout">
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"
COMMERCIAL_QT ?= "qmmp"
LICENSE_FLAGS_WHITELIST = "commercial_gst-plugins-ugly commercial_gst-plugins-bad commercial_qmmp"
</pre>
<p>
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 <code class="filename">LICENSE_FLAGS</code> containing
"commercial", which you may or may not want:
</p>
<pre class="literallayout">
LICENSE_FLAGS_WHITELIST = "commercial"
</pre>
<p>
</p>
<p>
Specifying audio and video plug-ins as part of the
<code class="filename">COMMERCIAL_AUDIO_PLUGINS</code> and
<code class="filename">COMMERCIAL_VIDEO_PLUGINS</code> statements
or commercial qt components as part of
the <code class="filename">COMMERCIAL_QT</code> statement (along
with the enabling <code class="filename">LICENSE_FLAGS_WHITELIST</code>) includes the
plug-ins or components into built images, thus adding
support for media formats or components.
</p>
</div></body>
</html>