Diego Biurrun <[email protected]> writes: > On Mon, Jun 20, 2011 at 05:45:43PM +0100, Måns Rullgård wrote: >> Diego Biurrun <[email protected]> writes: >> >> > --- >> > configure | 2 ++ >> > 1 files changed, 2 insertions(+), 0 deletions(-) >> > >> > diff --git a/configure b/configure >> > index 2a1883b..84dbaf4 100755 >> > --- a/configure >> > +++ b/configure >> > @@ -3203,6 +3203,7 @@ if enabled source_path_used; then >> > doc >> > libavcodec >> > libavcodec/$arch >> > + libavcodec/mlib >> > libavdevice >> > libavfilter >> > libavfilter/$arch >> > @@ -3212,6 +3213,7 @@ if enabled source_path_used; then >> > libpostproc >> > libswscale >> > libswscale/$arch >> > + libswscale/mlib >> > tests >> > tools >> > " >> > -- >> >> Before we do this: >> >> 1. Does anyone have mlib? >> 2. Does anyone use mlib? >> 3. Does it work? > > Michael Kostylev notified me that enabling it for his FATE machine > failed because out-of-tree builds cannot work due to the bug this > patch fixes. So applying this patch is a prerequisite for a FATE > box that tests mlib. > > I have not tested mlib myself and I have no idea if mlib support is > worth keeping if that's what you are alluding to.
Find if it 1) works, and 2) is of any use. If the answer to either is no, we should simply delete it entirely. I have the feeling it has bit-rotted rather badly. -- Måns Rullgård [email protected] _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
