|author||Tom Zanussi <firstname.lastname@example.org>||2012-09-14 14:07:34 -0500|
|committer||Tom Zanussi <email@example.com>||2012-09-15 15:02:17 -0500|
meta-intel: make video acceleration choice dependent on LICENSE_FLAGS
The gst-ffmpeg recipe in oe-core had LICENSE_FLAGS added to make it "commercial", so to avoid build errors the BSPs that use it (via the gst-va-intel VA_FEATURE) should only include it if the user has added "commercial" to LICENSE_FLAGS_WHITELIST when building. This adds a conditional to detect that, along with a NOTE in the README to explain the need for the flag. Signed-off-by: Tom Zanussi <firstname.lastname@example.org>
Diffstat (limited to 'meta-crownbay/README')
1 files changed, 15 insertions, 0 deletions
diff --git a/meta-crownbay/README b/meta-crownbay/README
index 25214326..f7aeffac 100644
@@ -92,6 +92,21 @@ At the end of a successful build, you should have a live image that
you can boot from a USB flash drive (see instructions on how to do
that below, in the section 'Booting the images from /binary').
+NOTE: The 'crownbay' machine will include support for hardware video
+acceleration via gstreamer if and only if the "commercial" string is
+added to the the LICENSE_FLAGS_WHITELIST variable in your local.conf.
+ LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin_1.14 commercial"
+The reason this is needed is to prevent the image from including
+anything that might violate the license terms of the packages used to
+implement the the video acceleration feature, such as gst-ffmpeg and
+ffmpeg. As always, please consult the licenses included in the
+specific packages for details if you use packages that require
As an alternative to downloading the BSP tarball, you can also work
directly from the meta-intel git repository. For each BSP in the
'meta-intel' repository, there are multiple branches, one