Re: How to enable bad plugins on gstreamer1.0 (dizzy)

[Nikolay Dimitrov <picmaster@mail.bg>]

Hi Daiane,

On 02/06/2015 12:51 PM, Daiane Angolini wrote:
> On Thu, Feb 5, 2015 at 3:50 PM, Nikolay Dimitrov <picmaster@mail.bg> wrote:
>> Hi guys,
>>
>> I'm trying to build and use gstreamer1.0 for sabresd, and "bad" plugins
>> specifically (for the mpegtsdemux plugin). The "bad" plugins are not
>> included in the build. I'm now looking at recipe packagegroup-
>> fslc-gstreamer1.0-full.bb, which looks like this:
>>
>>
>> DESCRIPTION = "Freescale package group which provides all GStreamer plugins
>> from the \
>>   base, good, and bad packages, as well as the ugly and libav ones if
>> commercial packages \
>>   are whitelisted, and plugins for the required hardware acceleration (if
>> supported by the SoC)."
>> SUMMARY = "Freescale package group - full set of all GStreamer 1.0 plugins"
>> LICENSE = "MIT"
>> LIC_FILES_CHKSUM =
>> "file://${COREBASE}/LICENSE;md5=3f40d7994397109285ec7b81fdeb3b58 \
>>
>> file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
>>
>> inherit packagegroup
>>
>> RDEPENDS_${PN} = " \
>>      packagegroup-fslc-gstreamer1.0 \
>>      ${@base_contains('LICENSE_FLAGS_WHITELIST', 'commercial',
>> 'packagegroup-fslc-gstreamer1.0-commercial', '', d)} \
>>      gstreamer1.0-plugins-base-meta \
>>      gstreamer1.0-plugins-good-meta \
>>      gstreamer1.0-plugins-bad-meta \
>>      ${@base_contains('LICENSE_FLAGS_WHITELIST', 'commercial',
>> 'gstreamer1.0-plugins-ugly-meta', '', d)} \
>>      ${@base_contains('LICENSE_FLAGS_WHITELIST', 'commercial',
>> 'gstreamer1.0-libav', '', d)} \
>> "
>>
>>
>> Please note the line containing "gstreamer1.0-plugins-bad-meta". I can't
>> find any recipe or file that has this name (find/grep didn't help).
>
> As I understand, any *-meta is not supposed to be a recipe, but a
> sub-package instead.

Yes, I found the same this morning. I'm still not sure of all the
complications of marking a recipe with "-meta", this "requires more
thinking" :D.

> And, I'm not sure if 'mpegtsdemux' would be part of bad-meta, as
> bad-meta only have a set of plugins, some of them are not included in
> -meta (due to license, e.g.)

Well, it should be there - it's available in the upstream repo, and
also I just was able to add it to my build. It turned out that in my
edit/build cycle I somehow had the wrong configuration (packagegroup-
fslc-gstreamer1.0-full was not enabled), so thus my issue.

Here's my recipe for testing gstreamer1.0 (it's copied/edited from the
other recipes in meta-fsl-demos):


diff --git 
a/sources/meta-fsl-demos/recipes-fsl/images/fsl-image-gstreamer1.0.bb 
b/sources/meta-fsl-demos/recipes-fsl/images/fsl-image-gstreamer1.0.bb
new file mode 100644
index 0000000..90e2715
--- /dev/null
+++ b/sources/meta-fsl-demos/recipes-fsl/images/fsl-image-gstreamer1.0.bb
@@ -0,0 +1,16 @@
+DESCRIPTION = "A console-only image that includes gstreamer packages and \
+Freescale's multimedia packages (VPU and GPU) when available for the 
specific \
+machine."
+
+IMAGE_FEATURES += "\
+    ${@base_contains('DISTRO_FEATURES', 'x11', 'x11-base', '', d)} \
+"
+
+LICENSE = "MIT"
+
+inherit core-image
+
+CORE_IMAGE_EXTRA_INSTALL += " \
+    packagegroup-fslc-gstreamer1.0-full \
+    packagegroup-fsl-tools-gpu \
+"


So I guess this solves my issue.

>> How I'm supposed to add the bad plugins to my build?
>>
>> Thanks in advance. Regards,
>> Nikolay
>> --
>> _______________________________________________
>> meta-freescale mailing list
>> meta-freescale@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-freescale

Regards,
Nikolay