From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: Gst-plugin dependencies
Date: Fri, 4 Mar 2011 10:54:06 -0600 [thread overview]
Message-ID: <4D71192E.3050706@windriver.com> (raw)
In-Reply-To: <4D71175D.4050307@gmail.com>
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.
--Mark
>> regards,
>>
>> Koen
>>
>> [1] As well as dealing with the inabiltiy to build opencv with a specific CSL toolchain
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2011-03-04 16:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 15:58 Gst-plugin dependencies Koen Kooi
2011-03-04 16:46 ` Khem Raj
2011-03-04 16:54 ` Mark Hatle [this message]
2011-03-04 17:12 ` Koen Kooi
2011-03-04 18:50 ` Tom Rini
2011-03-04 19:01 ` Mark Hatle
2011-03-04 19:07 ` Khem Raj
2011-03-04 19:32 ` Tom Rini
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=4D71192E.3050706@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox