From: Nikolay Dimitrov <picmaster@mail.bg>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: How to enable bad plugins on gstreamer1.0 (dizzy)
Date: Fri, 06 Feb 2015 15:15:18 +0200 [thread overview]
Message-ID: <54D4BE66.1000404@mail.bg> (raw)
In-Reply-To: <CAP9ODKp7iVksFAn+_FEgsjnmsyyvucxC2k5UX3656mH2egwtEw@mail.gmail.com>
Hi Otavio,
On 02/06/2015 02:19 PM, Otavio Salvador wrote:
> On Fri, Feb 6, 2015 at 9:21 AM, Nikolay Dimitrov <picmaster@mail.bg> wrote:
>> On 02/06/2015 12:51 PM, Daiane Angolini wrote:
>>> 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.
>
> This happens here:
>
> http://git.openembedded.org/openembedded-core/tree/meta/recipes-multimedia/gstreamer/gst-plugins-package.inc#n15
>
Thanks.
>>> 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.
>
> We have this in fsl-image-multimedia since long time ago.
Well, here's the content of fsl-image-multimedia.bb:
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-fsl-gstreamer \
packagegroup-fsl-tools-gpu \
${@base_contains('DISTRO_FEATURES', 'directfb',
'packagegroup-core-directfb', '', d)} \
${@base_contains('DISTRO_FEATURES', 'x11', '', \
base_contains('DISTRO_FEATURES', 'wayland', \
'weston weston-init weston-examples \
gtk+3-demo
clutter-1.0-examples', '', d), d)} \
"
It seems like it's using gstreamer-0.10, and not gstreamer1.0. Please
tell me if I'm looking at the wrong place.
> I double checked the meta package:
>
> dpkg -I ~/.../tmp/deploy/ipk/cortexa9hf-vfp-neon-mx6qdl/gstreamer1.0-plugins-bad-meta_1.4.5-r0.1_cortexa9hf-vfp-neon-mx6qdl.ipk
> | grep Depends: | tr ',' '\n' | grep mpegts
> gstreamer1.0-plugins-bad-mpegtsmux
> libgstmpegts-1.0-0
> gstreamer1.0-plugins-bad-mpegtsdemux
>
> So it seems alright.
>
Regards,
Nikolay
next prev parent reply other threads:[~2015-02-06 13:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 17:50 How to enable bad plugins on gstreamer1.0 (dizzy) Nikolay Dimitrov
2015-02-06 10:51 ` Daiane Angolini
2015-02-06 11:21 ` Nikolay Dimitrov
2015-02-06 12:19 ` Otavio Salvador
2015-02-06 13:15 ` Nikolay Dimitrov [this message]
2015-02-06 13:22 ` Otavio Salvador
2015-02-06 14:08 ` Daiane Angolini
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=54D4BE66.1000404@mail.bg \
--to=picmaster@mail.bg \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.