Home Esplora Aiuto
Accedi
crispAudio
/
poky
mirror da git://git.yoctoproject.org/poky
5
0
Forka 0
File Problemi 0 Wiki
Albero (Tree): 7681523408
Rami (Branch) Tag
poky
/
documentation
/
ref-manual
/
eclipse
/
html
/
poky-ref-manual
/
other-variables-related-to-commercial-licenses.html

other-variables-related-to-commercial-licenses.html 3.2 KB
Cronologia Originale

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960 
  1. <html>
    2. 

  2. <head>
    3. 

  3. <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
    4. 

  4. <title>3.4.2.2. Other Variables Related to Commercial Licenses</title>
    5. 

  5. <link rel="stylesheet" type="text/css" href="../book.css">
    6. 

  6. <meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
    7. 

  7. <link rel="home" href="index.html" title="The Yocto Project Reference Manual">
    8. 

  8. <link rel="up" href="enabling-commercially-licensed-recipes.html" title="3.4.2. Enabling Commercially Licensed Recipes">
    9. 

  9. <link rel="prev" href="license-flag-matching.html" title="3.4.2.1. License Flag Matching">
    10. 

  10. <link rel="next" href="migration.html" title="Chapter 4. Migrating to a Newer Yocto Project Release">
    11. 

  11. </head>
    12. 

  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. 

  13. <div class="titlepage"><div><div><h4 class="title">
    14. 

  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. 

  15. <p>
    16. 

  16.                 Other helpful variables related to commercial
    17. 

  17.                 license handling exist and are defined in the
    18. 

  18.                 <code class="filename">$HOME/poky/meta/conf/distro/include/default-distrovars.inc</code> file:
    19. 

  19.                 </p>
    20. 

  20. <pre class="literallayout">
    21. 

  21.      COMMERCIAL_AUDIO_PLUGINS ?= ""
    22. 

  22.      COMMERCIAL_VIDEO_PLUGINS ?= ""
    23. 

  23.      COMMERCIAL_QT = ""
    24. 

  24.                 </pre>
    25. 

  25. <p>
    26. 

  26.                 If you want to enable these components, you can do so by making sure you have
    27. 

  27.                 the following statements in your <code class="filename">local.conf</code> configuration file:
    28. 

  28.                 </p>
    29. 

  29. <pre class="literallayout">
    30. 

  30.      COMMERCIAL_AUDIO_PLUGINS = "gst-plugins-ugly-mad \
    31. 

  31.         gst-plugins-ugly-mpegaudioparse"
    32. 

  32.      COMMERCIAL_VIDEO_PLUGINS = "gst-plugins-ugly-mpeg2dec \
    33. 

  33.         gst-plugins-ugly-mpegstream gst-plugins-bad-mpegvideoparse"
    34. 

  34.      COMMERCIAL_QT ?= "qmmp"
    35. 

  35.      LICENSE_FLAGS_WHITELIST = "commercial_gst-plugins-ugly commercial_gst-plugins-bad commercial_qmmp"
    36. 

  36.                 </pre>
    37. 

  37. <p>
    38. 

  38.                 Of course, you could also create a matching whitelist
    39. 

  39.                 for those components using the more general "commercial"
    40. 

  40.                 in the whitelist, but that would also enable all the
    41. 

  41.                 other packages with <code class="filename">LICENSE_FLAGS</code> containing
    42. 

  42.                 "commercial", which you may or may not want:
    43. 

  43.                 </p>
    44. 

  44. <pre class="literallayout">
    45. 

  45.      LICENSE_FLAGS_WHITELIST = "commercial"
    46. 

  46.                 </pre>
    47. 

  47. <p>
    48. 

  48.             </p>
    49. 

  49. <p>
    50. 

  50.                 Specifying audio and video plug-ins as part of the 
    51. 

  51.                 <code class="filename">COMMERCIAL_AUDIO_PLUGINS</code> and 
    52. 

  52.                 <code class="filename">COMMERCIAL_VIDEO_PLUGINS</code> statements
    53. 

  53.                 or commercial qt components as part of
    54. 

  54.                 the <code class="filename">COMMERCIAL_QT</code> statement (along
    55. 

  55.                 with the enabling <code class="filename">LICENSE_FLAGS_WHITELIST</code>) includes the
    56. 

  56.                 plug-ins or components into built images, thus adding
    57. 

  57.                 support for media formats or components.
    58. 

  58.             </p>
    59. 

  59. </div></body>
    60. 

  60. </html>
    61.