On Fri, 8 Dec 2023, Kalev Lember wrote:

As for dlopening, I think instead of version checks, it would make sense to
try to dlsym() all of the actual required symbols, and error out in init if
anything is missing. That should make it all super flexible and resilient to
e.g. struct size changes that would normally be an ABI change.

How would that help, if e.g. the SEncParamExt struct in svc_encode_init would change layout/size - which part would notice that change?

In Fedora, we are planning on changing things up a bit and starting to build
packages that link with openh264 against the "noopenh264" stub
implementation and replacing it at runtime with the actual openh264 library
downloaded directly from Cisco. Flathub flatpak runtimes already use that
approach and it seems to work well there. This should hopefully let us take
advantage of the Cisco patent grant and fit well in the build system
architecture that we have.

Ah, interesting, that sounds like a reasonable way to take advantage of that patent grant without having everybody to do the dlopening.

// Martin

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

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

Reply via email to