All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: RFC: libav, ffmpeg, and OE-Core
Date: Thu, 30 May 2013 21:07:58 +0100	[thread overview]
Message-ID: <1369944478.14887.331.camel@ted> (raw)
In-Reply-To: <3311603.tBhLUzvcSX@helios>

On Thu, 2013-05-30 at 20:59 +0100, Paul Eggleton wrote:
> Hi all,
> 
> Video decoding is an important function for a lot of devices. We currently
> have gst-ffmpeg, which includes the ffmpeg sources, in OE-Core but we don't have
> ffmpeg or libav itself that is a bit more re-usable outside of GStreamer. This
> brings up a few questions:
> 
> 1) Which is the preferred option for OE; ffmpeg or its "fork" libav? libav
> seems to be better suited to use as a library but on the other hand ffmpeg
> isn't exactly dead. Some background:
> 
> http://aballier.wordpress.com/2013/01/18/ffmpeg-vs-libav-a-distribution-maintainer-point-of-view-almost-two-years-after-the-split/
> 
> http://blog.pkh.me/p/13-the-ffmpeg-libav-situation.html
> 
> 2) Following on from that, should we pull the preferred library into OE-Core
> and avoid the need for the current bbappend in meta-oe for gst-ffmpeg? (One of
> my personal motivations for sorting this out). This would of course be
> protected by LICENSE_FLAGS as we currently do with gst-ffmpeg.
> 
> Thoughts?

I think having ffmpeg in core might be a good idea since it allows us to
test various video playback and also allows us to test LICENSE_FLAGS in
the core...

Cheers,

Richard



  reply	other threads:[~2013-05-30 20:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-30 19:59 RFC: libav, ffmpeg, and OE-Core Paul Eggleton
2013-05-30 20:07 ` Richard Purdie [this message]
2013-05-30 20:12 ` Koen Kooi

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=1369944478.14887.331.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    /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.