From: <va...@us...> - 2004-07-31 19:04:02
|
Hi Stephen, Mike and Michael, V So, 31. 07. 2004 v 14:35, Michael Roitzsch p=C3=AD=C5=A1e: > Hi Mike, >=20 > > > Does this mean that we don't have to include ffmpeg inside xine-lib= ? Is > > > there any advantage of keeping it the way we have it now versus usi= ng > > > ffmpeg as a external shared library? > > But we still need one internal header file of ffmpeg. :-) > > Sure there are advantages to the current method. Mostly for the > > end user. It's not fun for the user to have to install so much extern= al > > stuff to get a minimally functional player. > > > > I do not know of any plan to make ffmpeg support external. Maybe I > > missed something? >=20 > You did not. I think having external ffmpeg as a configure option is a = good=20 > idea, but we should still maintain our local copy. >=20 Yes, I agree. For the most users is the current way better. Already now has xine many of optional dependencies, but main funcionalities work out-of-the-box. Possibility to have ffmpeg external has also advantages (update the "codecs" only on one place in the system, faster building of fresh clean snapshots, and other advantages of shared libraries). Users can share one ffmpeg library with video-editing tools and other SW. Little improved version of the patch is in CVS. Use: ./configure --with-external-ffmpeg[=3DPREFIX] or FFMPEG_CFLAGS=3D... FFMPEG_LIBS=3D... ./configure --with-external-ffmpe= g Cheers, Frantisek |