[FFmpeg-devel] [RFC v2] avdevice: lock to minor version of avformat
Diederick C. Niehorster
dcnieho at gmail.com
Thu Mar 3 11:03:55 EET 2022
Hi Andreas,
On Mon, Jan 3, 2022 at 12:03 PM Diederick C. Niehorster <dcnieho at gmail.com>
wrote:
> Hi Andreas,
>
> Thanks for the comments!
>
> On Mon, Jan 3, 2022 at 11:02 AM Andreas Rheinhardt
> <andreas.rheinhardt at outlook.com> wrote:
> >
> > Diederick Niehorster:
> > > As per discussion on the list (
> > > https://ffmpeg.org/pipermail/ffmpeg-devel/2021-June/281513.html, see
> > > especially
> https://ffmpeg.org/pipermail/ffmpeg-devel/2021-June/281586.html),
> > > to resolve the the unholy ABI-relationship between libavdevice and
> > > libavformat and allow easier working on the part of the avdevice API
> > > that lives in avformat, lock avdevice to a specific major and minor
> > > version of avformat.
> > >
> > > Signed-off-by: Diederick Niehorster <dcnieho at gmail.com>
> > > ---
> >
> > 1. If this patch intends to make it illegal to use libavdevice together
> > with libavformat with a different minor version than it was compiled
> > against, then the most basic requirement of this is to actually properly
> > document it and not add stuff that might cause linking failure if used
> > in a way that runs afoul of your undocumented new requirements.
>
> Absolutely, documentation is required. Should that be in (amongst
> local to the function in the header)?
>
I want to prepare a next version to get this discussion going. Where should
i document that it is illegal to use libavdevice together with libavformat
with a different minor version?
The versioning documentation starting on line 47 in /libavutil/avutil.h?
All the best,
Dee
More information about the ffmpeg-devel
mailing list