FFMPEG and MPV are required during automated testing. Explicitly add
these to ti-test.

Also add the commercial_ffmpeg setting to LICENSE_FLAGS_ACCEPTED for the
layer.

Signed-off-by: Brandon Brnich <[email protected]>
Signed-off-by: Ryan Eatmon <[email protected]>
---
v3: Move mpv behind the guard too.
v2: Move ffmpeg to be tied to building a ti-soc to bypass yocto-check-layers
    error.

 meta-arago-test/conf/layer.conf                       | 5 +++++
 meta-arago-test/recipes-core/packagegroups/ti-test.bb | 5 +++++
 2 files changed, 10 insertions(+)

diff --git a/meta-arago-test/conf/layer.conf b/meta-arago-test/conf/layer.conf
index ea0a3398..7e8bf1ab 100644
--- a/meta-arago-test/conf/layer.conf
+++ b/meta-arago-test/conf/layer.conf
@@ -26,3 +26,8 @@ LAYERDEPENDS_meta-arago-test = " \
 BBFILES_DYNAMIC += " \
     qt6-layer:${LAYERDIR}/dynamic-layers/qt6-layer/recipes*/*/*.bbappend \
 "
+
+# Codecs in ffmpeg with questionable patent status are not included by
+# default.  As this entire layer is purely optional for testing purposes only
+# and not meant to be shipped, add support for the ffmpeg commercial license.
+LICENSE_FLAGS_ACCEPTED:append:ti-soc = " commercial_ffmpeg"
diff --git a/meta-arago-test/recipes-core/packagegroups/ti-test.bb 
b/meta-arago-test/recipes-core/packagegroups/ti-test.bb
index d3458b9d..8067f4c1 100644
--- a/meta-arago-test/recipes-core/packagegroups/ti-test.bb
+++ b/meta-arago-test/recipes-core/packagegroups/ti-test.bb
@@ -91,6 +91,11 @@ TI_TEST_MULTIMEDIA = "\
     yavta \
 "
 
+TI_TEST_MULTIMEDIA:append:ti-soc = " \
+    mpv \
+    ffmpeg \
+"
+
 TI_TEST_NETWORKING = "\
     bridge-utils \
     ethtool \
-- 
2.43.0



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17208): 
https://lists.yoctoproject.org/g/meta-arago/message/17208
Mute This Topic: https://lists.yoctoproject.org/mt/118118247/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-arago/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-


Reply via email to