On Sat, 23 Mar 2002, Keith Whitwell wrote:
> Mark Vojkovich wrote:
> >
> > Currently, for libXvMC, Intel and NVIDIA have static libraries
> > that work essentially like libGLcore and is used in conjuction
> > with libXvMC.a. I want to move to a libXvMC.so plus libXvMCcore.so
> > type operation where libXvMC dlopens the appropriate core for
> > the hardware being used.
> >
> > Does the DRI do this sort of thing? How do you know which
> > core to load?
>
> It does if I understand the question. It gets the driver name from a DRI
> extension protocol request to the server - the ddx driver knows which module
> to load.
>
> The path to the driver.so is from a hardcoded default or overridden by an
> environment variable - however, I kindof believe it would have made more sense
> for the server to give an absolute path.
>
OK. It sounds like I'll need to have separate behavior for
libXvMC.a and libXvMC.so. Static libraries are needed because
companies dealing with encrypted content don't want to let data
outside of their binaries.
static - app links in libXvMC.a and vendor-specific file
(eg. libXvMCNVIDIA.a).
dynamic - app links to libXvMC.so which gets the name of the core
file to open via new protocol in the extension.
Mark.
_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
