From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] gst-ffmpeg: Use internal libav instead of external ffmpeg
Date: Wed, 15 Jan 2014 21:14:49 +0100 [thread overview]
Message-ID: <87ha95t32e.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <52D6EACE.8020403@zacarias.com.ar> (Gustavo Zacarias's message of "Wed, 15 Jan 2014 17:08:46 -0300")
>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:
> On 01/15/2014 05:02 PM, Peter Korsgaard wrote:
>> But what about all the CPU optimization flags we have in ffmpeg? Don't
>> we need to reproduce those as well here?
> I'm a bit wary about using the builtin ffmpeg support at all, all of the
> security fixes from newer versions of the unbundled library will be gone.
> And i also think the bump was fine, it was time to move along (and mpd's
> support for ffmpeg needed it for example, it won't work with oldish
> ffmpeg versions).
> Maybe it's a bit harsh but we should consider deprecating gst-ffmpeg?
s/gst-ffmpeg/gstreamer 0.10/, but yeah. Upstream officially announced
that almost a year ago:
http://lists.freedesktop.org/archives/gstreamer-announce/2013-March/000273.html
I do think moving to the internal libav copy for gst-ffmpeg until we can
completely remove it is OK though. If people really need it, then the
(outdated) bundled library is still better than no gst-ffmpeg.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2014-01-15 20:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 18:44 [Buildroot] [PATCH 1/1] gst-ffmpeg: Use internal libav instead of external ffmpeg Bernd Kuhls
2014-01-15 20:02 ` Peter Korsgaard
2014-01-15 20:08 ` Gustavo Zacarias
2014-01-15 20:14 ` Peter Korsgaard [this message]
2014-01-16 13:05 ` Sven Neumann
2014-01-16 13:13 ` Peter Korsgaard
2014-01-16 13:57 ` Sven Neumann
2014-01-29 8:00 ` Thomas Petazzoni
2014-01-29 18:33 ` Bernd Kuhls
2014-01-30 19:20 ` Thomas Petazzoni
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=87ha95t32e.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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