On Mon, Jun 20, 2011 at 11:48:51AM -0400, Ronald S. Bultje wrote: > > On Mon, Jun 20, 2011 at 4:57 AM, Anton Khirnov <[email protected]> wrote: > > From: Stefano Sabatini <[email protected]> > > > > Fix compilatin after removal of FF_INTERNAL_MEM_TYPE_MAX_VALUE. > > > > Signed-off-by: Stefano Sabatini <[email protected]> > > Signed-off-by: Anton Khirnov <[email protected]> > > --- > > libavfilter/vf_libopencv.c | 2 +- > > 1 files changed, 1 insertions(+), 1 deletions(-) > > OK. > > Has anyone tested with libopencv to make sure it works now? Can we add > it to the external libraries fate machine?
I haven't had time to verify this myself, but Michael Kostylev tells me that: Enabling libopencv leads to FTBS for various reasons. E.g. what happens when using the version 2.1 from Debian testing: CC libavfilter/vf_libopencv.o /home/mik/src/fate/src/libavfilter/vf_libopencv.c: In function ‘read_shape_from_file’: /home/mik/src/fate/src/libavfilter/vf_libopencv.c:161:18: error: ‘FF_INTERNAL_MEM_TYPE_MAX_VALUE’ undeclared (first use in this function) /home/mik/src/fate/src/libavfilter/vf_libopencv.c:161:18: note: each undeclared identifier is reported only once for each function it appears in make: *** [libavfilter/vf_libopencv.o] Error 1 When using self-compiled 2.2 configure passes but building vf_libopencv.o dies early because of missing opencv/cxtypes.h (IMO opencv/cxcore.h should be included instead). Probably at least configure should be changed. Diego _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
