Hi all libavdevice uses teh same ABI as libavformat so extending that ABI without major bump leads to problems
input devices and input formats use the same struct FFInputFormat now you cant add a new field to that because the old libavdevice would not have it and the newer libavformat would so things would blow up. The 2 solutions suggested where 1. merge libavdevice and libavformat 2. make libavdevice actually great again, aka a seperate API designed for devices (3. maybe a bunch of flags checks version whatever can be used to make it work as is) comments ? Is anyone against "1. merge libavdevice and libavformat" ? Is anyone volunteering for "2. make libavdevice actually great again, aka a seperate API designed for devices" thx -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB If the United States is serious about tackling the national security threats related to an insecure 5G network, it needs to rethink the extent to which it values corporate profits and government espionage over security.-Bruce Schneier
signature.asc
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list -- [email protected] To unsubscribe send an email to [email protected]
