mirror of
git://git.openembedded.org/meta-openembedded
synced 2026-05-16 10:52:31 +00:00
8c80754a52
* resolves bitbake world error:
ERROR: Nothing PROVIDES 'ffmpeg' (but meta-multimedia/recipes-multimedia/musicpd/mpd_0.20.22.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
ERROR: Required build target 'meta-world-pkgdata' has no buildable providers.
Missing or unbuildable dependency chain was: ['meta-world-pkgdata', 'mpd', 'ffmpeg']
* aac is conditionally included in PACKAGECONFIG based on LICENSE_FLAGS
since:
commit f5d271fd545c5b78d4a8fbc81e54df454fa0d5e4
Author: Armin Kuster <akuster808@gmail.com>
Date: Mon Oct 1 08:05:28 2018 -0700
mpd: enable aac PACKAGECONFIG only with commercial LICENSE_FLAGS
maybe we could use the same for ffmpeg, but the conditional should
be a bit more complicated, because the aac support is whitelisted by
either commercial, commercial_faad2 or faad2 in LICENSE_FLAGS_WHITELIST
not just currently checked 'commercial'.
and we cannot use LICENSE_FLAGS conditional in both, because that leads to
bb.data_smart.ExpansionError: Failure expanding variable LICENSE_FLAGS, expression was
${@bb.utils.contains('PACKAGECONFIG', 'ffmpeg', 'commercial', '', d)}
which triggered exception RecursionError: maximum recursion depth exceeded
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
This layer depends on: URI: git://github.com/openembedded/oe-core.git branch: master revision: HEAD URI: git://github.com/openembedded/meta-oe.git layers: meta-oe branch: master revision: HEAD Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-multimedia]' in the subject' When sending single patches, please use something like: 'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-multimedia][PATCH You are encouraged to fork the mirror on github https://github.com/openembedded/meta-openembedded to share your patches, this is preferred for patch sets consisting of more than one patch. Other services like GitLab, repo.or.cz or self hosted setups are of course accepted as well, 'git fetch <remote>' works the same on all of them. We recommend github because it is free, easy to use, has been proven to be reliable and has a really good web GUI. Layer maintainer: Andreas Müller <schnitzeltony@gmail.com>