Andreas Rheinhardt (12020-03-24): > I reconsidered this and I think I got it exactly wrong: libavdevice is > linked against libavformat, not the other way around. Therefore one can > swap the libavformat against a newer one, but one is not allowed to > update libavdevice without also updating libavformat. (This presumes > that the usual rules apply in this scenario; I haven't seen any > exception documented for the special case of the heavily interwoven > libavdevice and libavformat, so I guess there is none.) > > This means that adding new fields to AVInputFormat (and using them) is > not possible, because said AVInputFormat might come from an older > version of libavdevice and might therefore not have these fields.
I would like to emphasize that this whole issue is again a drawback of having the libraries reside in separate shared objects. A situation for which I have yet to be told a single actual benefit. Regards, -- Nicolas George
signature.asc
Description: PGP signature
_______________________________________________ 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".
