[FFmpeg-devel] [RFC] Split libavformat
Mon Nov 26 12:22:22 CET 2007
On Mon, Nov 26, 2007 at 11:24:10AM +0100, Michael Niedermayer wrote:
> > I did not want to create new dependencies, because one of my goal is to
> > reduce the number of changes needed to libav* users.
> the number of changes needed for libav* users is of low relevance its much
> more important that the final design is sane
> its a one time annoyance vs. permanent annoyance question
> also iam starting to think that the way you split lavf is extreemly bad
> spliting out random (de)muxers and protocols is quite similar to what can
> already and much cleaner be done with --disable-demuxer/...
maybe "extreemly bad" is exagerating but the way you split things is a little
as if libavcodec and libavformat where together and you would split rarely
used codecs and (de)muxers out into a seperate lib instead of spliting
codecs from (de)muxers
for static linking spliting net/grabing off makes no difference, they can
just be disabled configure style
for a system which doesnt have grabbing or network they as well can just
be disabled configure style no matter if static or shared libs
and for a system which supports and user who wants grabing/net support
wheres the point of not having it available to all applications?
the little memory for pages of shared libs which contain both grabing
and non grabing code?
the time needed for loading the shared lib?
dynamic loading of libavdevice/net? but then why not dynamically load
whatever dependancies are needed from the URLProtocols? it would be
much simpler from the applications point of view, more fine grained
and also avoid dependancies
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Good people do not need laws to tell them to act responsibly, while bad
people will find a way around the laws. -- Plato
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Digital signature
More information about the ffmpeg-devel