[meta-freescale] [meta-fsl-arm][PATCH v5] gstreamer1.0-imx: Add GStreamer 1.0 plugins

[Rogerio Nunes]

Done renaming. :-)

One more question:

When I bake both versions of gstreamer in the same environment, I get
a bunch of WARNINGS:

WARNING: gstreamer-0.10.36 was registered as shlib provider for
libgstcoreelements.so, changing it to gstreamer1.0-1.2.2 because it
was built later
WARNING: QA Issue: libglade: configure was passed unrecognised
options: --disable-schemas-install
WARNING: gst-plugins-base-adder-0.10.36 was registered as shlib
provider for libgstadder.so, changing it to
gstreamer1.0-plugins-base-adder-1.2.2 because it was built later
WARNING: gst-plugins-base-alsa-0.10.36 was registered as shlib
provider for libgstalsa.so, changing it to
gstreamer1.0-plugins-base-alsa-1.2.2 because it was built later
...
WARNING: gst-plugins-base-ximagesink-0.10.36 was registered as shlib
provider for libgstximagesink.so, changing it to
gstreamer1.0-plugins-base-ximagesink-1.2.2 because it was built later
WARNING: gst-plugins-base-xvimagesink-0.10.36 was registered as shlib
provider for libgstxvimagesink.so, changing it to
gstreamer1.0-plugins-base-xvimagesink-1.2.2 because it was built later

Does anybody know how to solve this issue?

Both versions are supposed to coexist in a Linux system, but maybe the
base recipes do not support this properly?

Thinking out loud... Would it be an option to mark all gstreamer
plugin libraries as PRIVATE_LIBS?

Thanks,
Rogerio.

On Thu, Feb 13, 2014 at 2:54 PM, Carlos Rafael Giani
<dv at pseudoterminal.org> wrote:
> Hi Rogeiro,
>
> sure, no problem. I just chose it based on the github repository's name. I
> agree with your suggestion.
>
> regards,
> Carlos
>
>
> On 2014-02-13 18:43, Rogerio Nunes wrote:
>>
>> Hi Carlos,
>>
>> I'd like to rename the recipe to gstreamer1.0-plugins-imx, but wanted
>> to check first if you had any particular reason to avoid using
>> "plugins" in the name of the recipe.
>> Since the recipe requires gst-plugins-package.inc, I think the name
>> I'm suggesting will make it clear that the package is a set of plugin
>> packages actually, following what I'm assuming to be the standard in
>> poky.
>>
>> Do you agree?
>>
>> Thanks,
>> Rogerio.
>>
>> On Thu, Feb 6, 2014 at 3:22 PM, Otavio Salvador <otavio at ossystems.com.br>
>> wrote:
>>>
>>> On Thu, Feb 6, 2014 at 2:04 PM, Carlos Rafael Giani
>>> <dv at pseudoterminal.org> wrote:
>>>>
>>>> gstreamer-imx is an ongoing project to write GStreamer 1.0 plugins for
>>>> using the i.MX VPU,IPU, and GPU. With the plugins, the VPU en- and
>>>> decoding
>>>> features can be used, the IPU can transform images (deinterlacing,
>>>> colorspace conversion etc.), and the GPU can display frames using
>>>> OpenGL ES and the Vivante direct textures. Currently, the plugins have
>>>> only been tested with the i.MX6 SoC series.
>>>>
>>>> All plugins are based on appropriate GStreamer base classes. Physical
>>>> memory metadata structures make it possible to avoid costly frame
>>>> copies,
>>>> making it possible to use transcoding chains that do not involve
>>>> CPU copies for example.
>>>>
>>>> This recipe is sent to meta-fsl-arm to make these plugins more visible
>>>> and available to others.
>>>>
>>>> Signed-off-by: Carlos Rafael Giani <dv at pseudoterminal.org>
>>>
>>> I applied this so we start getting more people testing this in their
>>> system. Carlos, thanks for doing this work :-)
>>>
>>> --
>>> Otavio Salvador                             O.S. Systems
>>> http://www.ossystems.com.br        http://code.ossystems.com.br
>>> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
>>> _______________________________________________
>>> meta-freescale mailing list
>>> meta-freescale at yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/meta-freescale
>
>