Re: [xine-devel] The livXV.so issue

[Eduard H. <ed...@ao...>]

Hi Siggi.

On Tue, Jul 31, 2001 at 08:53:37PM +0200, Siggi Langauf wrote:
> Hi folks,
> 
> after a few terribly busy weeks, I'm finding a bit more time to work on
> xine...
> 
> I just started to make Debian packages for the current CVS version, and I
> hit something which had already annoyed lots of people, and which could
> become a showstopper here:
> 
> Xine requires libXv to be available as .so, whereas the XFree folks (and
> therefore the XFree packages on pretty much any distribution) only provide
> a static (.a) library.

I cannot confirm this (SuSE 7.1):

# rpm -qf /usr/X11R6/lib/libXv.so.1
xshared-4.0.2-4

Available as shared object.

> This may be easy to "fix", but I can't simply create the library, as it
> belongs to another package. (policy issues...)
> Moreover, I suspect a reason for XFree providing this only as a static
> library. How would xine behave without the lib? I haven't found any
> binary, not even the xv plugin, that is dynamically linked to libXv.so, so
> I guess it's dlopen()ed somewhere...

No I dont think so, "grep dlopen video_out_xv.c" gives no results.
Furthermore:

ldd xineplug_vo_out_xv.so
        libXv.so.1 => /usr/X11R6/lib/libXv.so.1 (0x40010000)
        libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x40015000)
        libc.so.6 => /lib/libc.so.6 (0x40023000)
        libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x40136000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)

> The question is: Where? And more important: Why??
> Couldn't we link it statically instead?

IMHO only a makefile issue. If your distro only supplies the .a, the
.a will be linked in. If not, something which I do not expect happens.
 
Just my 0.02 Euro :-)
-- 
Eduard Hasenleithner
student of
Salzburg University of Applied Sciences and Technologies