Re: [MPlayer-dev-eng] [PATCH 2/2] Fix compilation with recent FFmpeg on ARM
- Date: Tue, 21 Apr 2015 04:13:01 +0200
- From: Reimar Döffinger <Reimar.Doeffinger@xxxxxx>
- Subject: Re: [MPlayer-dev-eng] [PATCH 2/2] Fix compilation with recent FFmpeg on ARM
On 16.04.2015, at 17:05, Laurent <laurent.aml@xxxxxxxxx> wrote:
> On Tue, Apr 14, 2015 at 3:33 AM, Ingo Brückl <ib@xxxxxxxxxxxxxxx> wrote:
>> Reimar Döffinger wrote on Tue, 14 Apr 2015 09:02:31 +0200:
>>> On 13.03.2015, at 23:27, Laurent <laurent.aml@xxxxxxxxx> wrote:
>>>> By the way... is there still benefits to compile MPlayer with the internal
>>>> FFmpeg instead of using an external one (as the later is less subject to
>>>> configure breakage)?
>>> Minor performance advantages due to more inlining.
>>> Ensuring you do not build against an outdated FFmpeg.
>>> But mostly convenience to not have to download FFmpeg, configure it correctly (especially if static linking and you want MPlayer as PIE) and get MPlayer to use the correct one.
>>> People testing and helping improve compilation against external FFmpeg
>>> is quite welcome though.
>> I'm compiling against external FFmpeg from day one, it's hassle-free.
> Thanks for the feedback.
> I already compile FFmpeg (bin + dynamic libraries)...
> Switching to external FFmpeg for MPlayer will save me quite some
> compilation time, disk space and hassle :)
Note that on old architectures (anything 32 bit at least) dynamic libraries are likely to be measurably slower due to inefficient support for PIC, relocations etc.
If performance is relevant to you, you might want to benchmark and/or link against a static-only build of FFmpeg.
Admittedly most systems are fast enough nowadays that wasting 5% or so of performance is not an issue (and on ARM you probably waste most due to crappy video output modules anyway).
MPlayer-dev-eng mailing list