On 02/05/15 5:22 AM, Luca Barbato wrote: > On 02/05/15 06:23, Anton Khirnov wrote: >> Quoting Vittorio Giovara (2015-05-02 01:17:08) >>> The enum is used by lavc, lavf and lavfi, and it is referenced by lavu, >>> so it sementically belongs to lavu more than any other. >>> >>> This change allows to drop an avcodec.h inclusion from avfilter.h. >>> >> >> I would disagree here, since this logic would apply to any side data >> struct whatsoever. And I don't think they should all be in lavu. > > libav(meta)data ? =) > > Might be nice split libavutil a little so: > > libavu -> mem, basic data types, compat, version machinery > > libavdata -> packet, frame, samples and pixels
Sounds like libavcore. > > libavcomp -> compressors > > libavhash -> hashes Might as well just drop all these modules and make libgcrypt a mandatory dependency if it comes to this... I don't think anyone links to lavu exclusively for the crypto modules. A library like this would exist only to be linked against lavc/lavf. > > This is something I'd like to have soon if nobody is strongly against it. > > lu > _______________________________________________ > libav-devel mailing list > libav-devel@libav.org > https://lists.libav.org/mailman/listinfo/libav-devel > _______________________________________________ libav-devel mailing list libav-devel@libav.org https://lists.libav.org/mailman/listinfo/libav-devel
