Re: Gst-plugin dependencies

[Tom Rini <tom_rini@mentor.com>]

On 03/04/2011 10:12 AM, Koen Kooi wrote:
>
> Op 4 mrt 2011, om 17:54 heeft Mark Hatle het volgende geschreven:
>
>> On 3/4/11 10:46 AM, Khem Raj wrote:
>>> On 3/4/2011 7:58 AM, Koen Kooi wrote:
>>>> Hi,
>>>>
>>>> The current gst-plguin-<foo>   in oe-core is a bit anemic and the ones in OE are really full featured. How do we want to handle this going forward? I'm a big fan of shifting the pain to buildtime so people can install any plugin they want at runtime instead of needing to rebuild it.
>>>> At TI we have cut-down versions of the recipes to save buildtime[1], but it's a pain to maintain those and keep them up to date. It would be nice to come with a way to say you want full featured gstreamer or not. With my angstrom hat on, I would like the full feature set :)
>>>>
>>>
>>> May be controlling it with distro features
>>
>> Due to the licensing issues in the gst-plugins..  I'd be inclined to say they're
>> out of the core myself.  Move it to the distro specific layers.
>
> Even outside of licensing issues with things like MP3, I would like to have some kind of framework in OE (-core) for gst-plugins that layers can extend to their liking. Having dealt with the recipes over the years, too many things change between versions. It takes someone familiar with gst to maintain those recipes, and there aren't a lot of such people in OE :(

I agree with Koen, gstreamer is pretty core to doing a lot of stuff in 
real world applications.  We just need a way to handle in a good way the 
use flag type requirements this brings up.

Is the TSC ready to talk about USE flags again yet?  I think that could 
help with the Angstrom hat vs TI hat problem Koen describes too, at 
least in good part.

-- 
Tom Rini
Mentor Graphics Corporation