From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 2/7] package/ffmpeg: bump to version 3.1.1
Date: Sat, 2 Jul 2016 15:38:15 +0200 [thread overview]
Message-ID: <20160702153815.58f45f35@free-electrons.com> (raw)
In-Reply-To: <1467466339-19422-2-git-send-email-bernd.kuhls@t-online.de>
Hello,
On Sat, 2 Jul 2016 15:32:14 +0200, Bernd Kuhls wrote:
> From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
>
> - Remove non-existing configure options:
> - --disable-mips32r2
> - --disable-libvo-aacenc
> - --enable-libdcadec
> (https://github.com/FFmpeg/FFmpeg/commit/e259dc86a80398d56d1aabcf6203f80616a4d04d)
>
> - Amend renamed configure options:
> - --disable-mipsdspr1 has been renamed to --disable-mipsdsp
>
> Remove all Kodi-related patches according to upstream repo:
> https://github.com/xbmc/FFmpeg/commits/release/3.1-xbmc
>
> Kodi now uses an unpatched ffmpeg.
>
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
We're still a bit reluctant to upgrade ffmpeg to 3.x if there is no
released version of VLC that is ffmpeg 3.x compatible. What are the
main benefits of upgrading to ffmpeg 3.x ? Are there some other
packages you want to add that absolutely need ffmpeg in version 3.x ?
Of course, the removal of the ffmpeg patches is very nice, so we
definitely want to upgrade to ffmpeg 3.x at some point, but I'm not
sure we want to do that until VLC releases a compatible version. Do you
have an idea when VLC plans on making its 3.x release ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-07-02 13:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-02 13:32 [Buildroot] [PATCH v4 1/7] package/freerdp: add support for ffmpeg 3.0 Bernd Kuhls
2016-07-02 13:32 ` [Buildroot] [PATCH v4 2/7] package/ffmpeg: bump to version 3.1.1 Bernd Kuhls
2016-07-02 13:38 ` Thomas Petazzoni [this message]
2016-07-02 14:41 ` Bernd Kuhls
[not found] ` <E1bJM6V-0004mv-DY@fli4l.lan.fli4l>
2016-07-02 14:47 ` Thomas Petazzoni
2016-07-02 15:16 ` Bernd Kuhls
2016-07-02 13:32 ` [Buildroot] [PATCH v4 3/7] package/ffmpeg: cosmetic change for the mips fpu option Bernd Kuhls
2016-07-02 13:42 ` Peter Korsgaard
2016-07-02 13:32 ` [Buildroot] [PATCH v4 4/7] package/ffmpeg: default to --cpu=generic for MIPS architecture Bernd Kuhls
2016-07-02 14:08 ` Peter Korsgaard
2016-07-02 13:32 ` [Buildroot] [PATCH v4 5/7] package/ffmpeg: re-enable for mips64r2 and mips64r6 Bernd Kuhls
2016-07-02 13:32 ` [Buildroot] [PATCH v4 6/7] package/vlc: bump version to git master (to be released as 3.0) Bernd Kuhls
2016-07-02 13:32 ` [Buildroot] [PATCH v4 7/7] package/tvheadend: remove compat patch for ffmpeg < 3.x Bernd Kuhls
2016-07-02 13:39 ` [Buildroot] [PATCH v4 1/7] package/freerdp: add support for ffmpeg 3.0 Peter Korsgaard
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=20160702153815.58f45f35@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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