I've been meaning to ask the same questions, since I need both orc and external
libav to make gstreamer (0.10, but still) useable on my platforms. I came up
with the following ideas:
1) Make every external dep a PACKAGECONFIG option in OE-core gstreamer
2) Add bbappends with extra PACKAGECONF
On 9 April 2013 10:50, Carlos Rafael Giani wrote:
> Okay, sounds good. But just liborc? Or yasm as well? yasm is crucial for
> ffmpeg and libav.
Good question and I can't give an instant answer for that.
Ross
___
Openembedded-core mailing list
Openemb
On 2013-04-09 11:32, Burton, Ross wrote:
On 9 April 2013 00:00, Carlos Rafael Giani wrote:
thinking about this whole issue I began to wonder: why is gstreamer in
oe-core and not in meta-multimedia?
wouldnt it be easier then to move liborc into meta-multimedia as well?
Or is gstreamer considered
On 9 April 2013 00:00, Carlos Rafael Giani wrote:
> thinking about this whole issue I began to wonder: why is gstreamer in
> oe-core and not in meta-multimedia?
> wouldnt it be easier then to move liborc into meta-multimedia as well?
> Or is gstreamer considered an essential component for many ins
Hello,
thinking about this whole issue I began to wonder: why is gstreamer in
oe-core and not in meta-multimedia?
wouldnt it be easier then to move liborc into meta-multimedia as well?
Or is gstreamer considered an essential component for many
installations, thus justifying its presence in oe-
On Sun, Apr 7, 2013 at 8:38 PM, Carlos Rafael Giani
wrote:
> Hello all,
>
> to start working with GStreamer 1.0 on several embedded platforms, I decided
> to adapt the existing GStreamer recipes from danny for 1.0. Out of this I
> created a layer, which is hosted at https://github.com/dv1/meta-gst
On 2013-04-08 13:09, Paul Eggleton wrote:
Returning to the original topic, a case could be made for just bringing orc
and libav into OE-Core. That's not going to work for every situation but we
ought to be looking at these kind of things on a case-by-case basis.
Cheers,
Paul
You should ad
On Monday 08 April 2013 12:47:51 Koen Kooi wrote:
> Op 8 apr. 2013, om 11:35 heeft "Burton, Ross" het
volgende geschreven:
> > On 8 April 2013 08:57, Koen Kooi wrote:
> >> I've been meaning to ask the same questions, since I need both orc and
> >> external libav to make gstreamer (0.10, but sti
Op 8 apr. 2013, om 11:35 heeft "Burton, Ross" het
volgende geschreven:
> Op 8 apr. 2013, om 01:38 heeft Carlos Rafael Giani
> het volgende geschreven:
>> to start working with GStreamer 1.0 on several embedded platforms, I decided
>> to
>> adapt the existing GStreamer recipes from danny for 1
On 2013-04-08 09:57, Koen Kooi wrote:
Op 8 apr. 2013, om 01:38 heeft Carlos Rafael Giani
het volgende geschreven:
I am also considering some kind of autodetection for when yasm and liborc are
available (for example, because meta-oe was added to bblayers.conf), and then
switches on Orc and
Op 8 apr. 2013, om 01:38 heeft Carlos Rafael Giani
het volgende geschreven:
> to start working with GStreamer 1.0 on several embedded platforms, I decided
> to
> adapt the existing GStreamer recipes from danny for 1.0. Out of this I
> created a layer,
> which is hosted at https://github.com/dv1/
Op 8 apr. 2013, om 01:38 heeft Carlos Rafael Giani
het volgende geschreven:
> Hello all,
>
> to start working with GStreamer 1.0 on several embedded platforms, I decided
> to adapt the existing GStreamer recipes from danny for 1.0. Out of this I
> created a layer, which is hosted at https://
Hello all,
to start working with GStreamer 1.0 on several embedded platforms, I
decided to adapt the existing GStreamer recipes from danny for 1.0. Out
of this I created a layer, which is hosted at
https://github.com/dv1/meta-gstreamer1.0 .
I write this RFC, because I figure that GStreamer 1
13 matches
Mail list logo
