Re: [xine-devel] X library conditionals clarification

[Michael R. <mr...@us...>]

Hi Chris,

> 	While browsing through the latest xine-lib (1.0 release), I found that
> the latest development version of xorg-x11 has the option of making Xv
> conditional.  Now, there are some people that have done this, and go to
> build xine-lib, which complains at them about not having Xv setup.  Is
> libXv something that's tied to X11 support?

Yes. Xv makes no sense without X11, if that's what you mean.

> If so, the latest xorg users aren't going to have it ok.  I was looking over 
> the configure.ac but wasn't quite sure how one would go about disabling Xv 
> support if the user doesn't have it built in.  As far as configure flags, I 
> notice:   
>
> --enable-static-xv
> --with-xv-path=path

configure should automatically disable Xv, if no usable library for it is 
found. This went wrong in the 1.0 release, but it has been fixed in CVS. 
Checkout HEAD for the latest unstable or the xine-1_0 branch for the latest 
stable version.

> Also, if someone disables libXv support, is that the only driver avaliable?  
> I recall something like XImage for standard x11 playback.. I'm wondering if 
> it falls back to that if Xv is not enabled.  

There is still the XShm plugin, which should be available in (almost) all 
standard X11 installation. Lacking the hardware acceleration of Xv, it will 
be much slower, though.

> Also as a quick note, I had a user that had aalib and libcac support 
> installed for other programs, but didn't want it installed for xine-lib.  
> Turns out it wanted it anyways and there was no way to disable it.  

I guess that's true. If the libraries are found, the plugins will be built. As 
a workaround, you can always delete unwanted plugins afterwards.

Michael

-- 
In the beginning was the word, and the word was content-type: text/plain