[FFmpeg-devel] Next developer meeting

[Nicolas George]

Ronald S. Bultje (12020-11-11):
> > Also, I believe it would be good for us internally, since it would
> > - allow other libraries to do IO cleanly without depending on lavf
> > - force us to clean up avio public API, which is not in a great shape
> 
> Avio public API would be great, regardless of library split. Certain
> companies using ffmpeg in their transcoding system want only their own I/O.

We completely can decide to clean up the public API without splitting
any library. And I completely agree, this would be an excellent and
useful task.

> I doubt they care much for the binary size saved from not linking to lavio,
> but stable public API is important.

Anyway, any project that cares about the binary size will not rely on
pre-built FFmpeg, they will build their own. That is why splitting the
libraries is useless in that regard: the ability to disable components
gives the same benefits, but more and better.

Regards,

-- 
  Nicolas George
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20201112/80a245c0/attachment.sig>