[MPlayer-dev-eng] [PATCH] vdpau

Reimar Doeffinger Reimar.Doeffinger at stud.uni-karlsruhe.de
Mon Feb 16 12:24:25 CET 2009


On Mon, Feb 16, 2009 at 11:43:51AM +0100, Gwenole Beauchesne wrote:
> On Mon, 16 Feb 2009, Reimar Doeffinger wrote:
> > On Mon, Feb 16, 2009 at 09:43:43AM +0100, Gwenole Beauchesne wrote:
> >> Again, it would have been the role of the library to explicitly link
> >> against libdl if it uses dlopen() et al., not MPlayer's. Don't bloat
> >> MPlayer deps if there is no need to, and there isn't.
> >
> > You misunderstand, MPlayer dlopens libvdpau, that's why it is a dependency.
> 
> Ah, didn't notice it was the new way to operate. Why is it so?

Because vdpau is a proprietary library, thus most distributions will have to
(and should!) compile MPlayer without vdpau-support unless it is dlopened, or
in short: see the libdvdcss case (though we do not have the dlopen in MPlayer
itself, it is in the external libdvdread).

> Besides, dlopen() an *.so is generally wrong as it implies *-dev{,evel} 
> packages at a distribution level...

I will have to check, but again, VDPAU is proprietary and so far I am not
aware of the nvidia drivers ever been split into a -dev package (I admit I
mainly use gentoo though).

> Beyond the fact that if their is an 
> API change (and thus, a SONAME change), you'd pick up the wrong library.

The API used via dlopen/dlsym consists of _exactly_ one single function,
vdp_device_create_x11.
Again this certainly is not "the new way to operate" but mostly the
established way to deal with libraries with redistribution issues,
except that maybe the version number should added to the dlopen
file name.



More information about the MPlayer-dev-eng mailing list