All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Ege <k4230r6@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] RFC: libav vs. ffmpeg, redux
Date: Thu, 9 Jul 2015 12:35:15 +0200	[thread overview]
Message-ID: <CAALGJZbmg2kqahBp5jFL4mk2N6upacQpmi9bpd3jSf5A-c4T8A@mail.gmail.com> (raw)
In-Reply-To: <CAJTo0La0qFDC36msPioX=-=xsdWrhGSUrKC-9DokxV9Htx003Q@mail.gmail.com>

Am 09.07.2015 12:31 nachm. schrieb "Burton, Ross" <ross.burton@intel.com>:
>
> On 9 July 2015 at 11:24, Paul Eggleton <paul.eggleton@linux.intel.com>
> wrote:
>
> > What do people think? Should we be looking to make the switch back in
OE as
> > well?
> >
>
> I say we switch back to ffmpeg, and do it as soon as possible so we're not
> making this change during M3.
Switching to ffmpeg will be great, because kodi requires ffmpeg.

Another option could be supporting both.

Regards,
Christian
>
> Ross
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel


  reply	other threads:[~2015-07-09 10:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09 10:24 RFC: libav vs. ffmpeg, redux Paul Eggleton
2015-07-09 10:30 ` Burton, Ross
2015-07-09 10:30   ` [OE-core] " Burton, Ross
2015-07-09 10:35   ` Christian Ege [this message]
2015-07-09 11:41     ` [oe] " Burton, Ross
2015-07-09 11:41       ` [OE-core] " Burton, Ross
2015-07-09 14:57 ` akuster808
2015-07-09 14:57   ` [OE-core] " akuster808
2015-07-09 15:02   ` [oe] " Burton, Ross
2015-07-09 15:02     ` [OE-core] " Burton, Ross
2015-07-11  5:46     ` [oe] " Khem Raj
2015-07-11  5:46       ` [OE-core] " Khem Raj
2015-07-10 14:19 ` 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=CAALGJZbmg2kqahBp5jFL4mk2N6upacQpmi9bpd3jSf5A-c4T8A@mail.gmail.com \
    --to=k4230r6@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@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 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.