Re: [Mjpeg-users] Compilation problem on mjpeg. (fwd)

[Steven M. S. <sms@2BSD.COM>]

Hi!

> From: Gernot Ziegler <gz...@ly...>
> 
> I don't know very much about this since I don't have a DVCam on my own,
> but I think there were some changes in libDV - if you need DV-support, you

	It's the same old problem that's come up a number of times before.
	That is one reason why a mjpegtools release (and moving quicktime4linux
	to where folks can not easily find it ;)) needs to be done.

	libdv and the patched "quicktime4linux" are incompatible.

	People should "rm -r quicktime4linux" and install libquicktime
	(libquicktme.sf.net if I recall correctly).

> need the CVS version (I think), if you don't, you'll have to use some
> configure-switch to turn it off ...

> (someone please verify this advice ;) )
	...
>       - Quicktime source in         : /tmp/quicktime4linux-1.4-patch

	ARGH!  rm -r /tmp/quicktime4linux-1.4-patch

	Then get the libquicktime from their Sourceforge download area
	(or check out the cvs version).

> lav_io.c: In function `check_DV2_input':
> lav_io.c:1385: too many arguments to function `dv_decoder_new'
> lav_io.c:1415: warning: implicit declaration of function `dv_decoder_free'

	Yes, that's the problem - libdv and quicktime4linux incompatibility.

> I guess it is a change in the API of libDV, but I'm not sure: is it libDV or
> mjpeg that changed ?

	Use the CVS versions of mjpegtools and libquicktime if the quicktime
	capability is required.   Much cleaner and it will work with libdv.

	Cheers,
	Steven Schultz