[FFmpeg-devel] [PATCH] configure: enable libavresample by default

wm4 nfxjfg at googlemail.com
Mon Oct 21 20:33:51 CEST 2013

On Mon, 21 Oct 2013 20:05:37 +0200
Michael Niedermayer <michaelni at gmx.at> wrote:

> On Mon, Oct 21, 2013 at 05:47:56PM +0200, wm4 wrote:
> > On Mon, 21 Oct 2013 17:17:43 +0200
> > Clément Bœsch <u at pkh.me> wrote:
> > 
> > > On Sun, Oct 20, 2013 at 07:23:23PM +0200, wm4 wrote:
> [...]
> > 
> > > I don't have a good or simple solution for the problem you raise, but I
> > > don't agree with that patch, because I find this reckless for the future
> > > of the project.
> > 
> > I really find this funny. Look at all the crappy ABI hacks Michael is
> > adding to all libav* libraries just to be ABI compatible to Libav, and
> if you have suggestions on how code can be made less crappy, these are
> always welcome

It's sort of inherent to achieving ABI compatibility with a foreign,
non-cooperating project. Though I still don't get why users are
supposed to use setters and getters for fields that are accessed
directly in Libav. (Perhaps to make it possible that a ffmpeg with
Libav ABI hacks enabled is compatible to a ffmpeg without Libav ABI?)

> leaving the political stuff and the main subject of this thread for a
> moment aside
> technically you should be able to use swresample with libav.
> If that doesnt work, iam quite interrested in bug reports
> the only issue i could imagine is that you might need libavutil from
> ffmpeg too, but thats compatible with libavs so it can be safely
> droped in if its needed and iam not sure it is

I think the possibility of distros just packaging ffmpeg proper is
infinitely higher than doing such a weird, intrusive hack.

More information about the ffmpeg-devel mailing list