Re: [FFmpeg-devel] [PATCH v2 0/3] hwcontext_vaapi: dlopen libva-x11 and libva-drm

[Emil Velikov <emil.l.velikov@gmail.com>]

Greetings Timo,

On Wed, 27 Jul 2022 at 21:00, Timo Rothenpieler <timo@rothenpieler.org> wrote:

> That sounds incredibly broken and will of course cause stuff to break.
> I see the issue lies with that magic script, not with ffmpeg.
>

Apologies, never meant to imply that ffmpeg is broken - far from it.
Simply put libva broke their ABI, without bumping the major version.

Hence the libva ABI should be cleaned up and fixed - as mentioned in
my original cover letter and the hunk of my previous email that got
mysteriously removed :-P
As also mentioned, the maintainers are slow, so the odds of having a
fix that reaches end users this year are very close to zero.

What I'm asking here is for a quick short-to-mid term workaround, to
be applied in ffmpeg.

While the startup script is fragile, a similar issue can happen _even
without_ it.

> You could make that exact argument for literally every single external
> library, and we don't dlopen() most of them.

I tried to clarify why and how the libva use-case varies from other
libraries, in my email that you've trimmed out. If my analysis is
incomplete or off, kindly point me to the place that comes as such.

If any developers feel like it might be easier moving some of this
discussion to IRC, do let me know. I can hop on the ffmpeg-devel.

Thanks
Emil
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".