On Thu, Oct 25, 2012 at 03:06:35PM +0200, Hendrik Leppkes wrote: > On Wed, Oct 24, 2012 at 7:04 PM, Diego Biurrun <di...@biurrun.de> wrote: > > On Thu, Oct 18, 2012 at 07:50:31PM +0200, Diego Biurrun wrote: > >> --- > >> configure | 6 +++++- > >> libavcodec/Makefile | 1 - > >> libavformat/matroskadec.c | 9 +++++++-- > >> libavutil/Makefile | 6 ++++-- > >> 4 files changed, 16 insertions(+), 6 deletions(-) > > > > OKed by Kostya on IRC. > > lzo.h is/was a public installed header, isn't it?
Almost everything in libavutil is, not necessarily a good idea IMO. > Isn't rather bad to be able to enable/disable parts of the public API? Why? If you don't want LZO support, why shouldn't you be allowed to disable it, API or not? Of course this reduces the available API, but I don't see which kind of problem this might cause ... That said, it's currently open season for libavutil API, so we could just make the header entirely private... Diego _______________________________________________ libav-devel mailing list libav-devel@libav.org https://lists.libav.org/mailman/listinfo/libav-devel
