From: "Khem Raj" <raj.khem@gmail.com>
To: yocto@lists.yoctoproject.org
Cc: Khem Raj <raj.khem@gmail.com>, Armin Kuster <akuster808@gmail.com>
Subject: [yocto-autobuilder-helper][PATCH] config.json: Add meta-multimedia to meta-oe job
Date: Mon, 16 Dec 2019 19:52:10 -0800 [thread overview]
Message-ID: <20191217035210.3237811-1-raj.khem@gmail.com> (raw)
meta-oe recipes/packagegroups needs meta-multimedia packagegroups
Whitelist ffmpeg so packages depending on it can be tested
Fixes
ERROR: Nothing PROVIDES 'ffmpeg' (but /home/pokybuild/yocto-worker/meta-oe/build/meta-openembedded/meta-oe/recipes-graphics/libvncserver/libvncserver_0.9.12.bb DEPENDS on or otherwise requires it)
ffmpeg was skipped: because it has a restricted license 'commercial'. Which is not whitelisted in LICENSE_FLAGS_WHITELIST
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Cc: Armin Kuster <akuster808@gmail.com>
---
config.json | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/config.json b/config.json
index b0856a0..a790d08 100644
--- a/config.json
+++ b/config.json
@@ -729,8 +729,12 @@
"ADDLAYER" : [
"${BUILDDIR}/../meta-openembedded/meta-oe",
"${BUILDDIR}/../meta-openembedded/meta-python",
+ "${BUILDDIR}/../meta-openembedded/meta-multimedia",
"${BUILDDIR}/../meta-openembedded/meta-networking",
"${BUILDDIR}/../meta-openembedded/meta-filesystems"
+ ],
+ "extravars" : [
+ "LICENSE_FLAGS_WHITELIST_append = ' commercial_ffmpeg commercial_x264 '"
]
},
"meta-virt" : {
--
2.24.0
next reply other threads:[~2019-12-17 3:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 3:52 Khem Raj [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-12-11 3:56 [yocto-autobuilder-helper][PATCH] config.json: Add meta-multimedia to meta-oe job Khem Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191217035210.3237811-1-raj.khem@gmail.com \
--to=raj.khem@gmail.com \
--cc=akuster808@gmail.com \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox