[ATrpms-devel] nvidia includes

[Jarod Wilson]

On Wednesday 20 September 2006 09:08, Axel Thimm wrote:
> On Wed, Sep 20, 2006 at 09:23:12AM -0300, Paulo Cavalcanti wrote:
> > On 9/20/06, Axel Thimm <Axel.Thimm at atrpms.net> wrote:
> > >On Sat, Sep 02, 2006 at 06:41:24PM -0300, Paulo Cavalcanti wrote:
> > >> Hi, Axel
> > >>
> > >> would you mind copying
> > >>
> > >> /usr/share/doc/nvidia-graphics8774-devel-1.0_8774/include/GL/*.h
> > >>
> > >> to
> > >>
> > >> /usr/include/GL
> > >>
> > >> In the next nvidia release?
> > >
> > >They will conflict with xorg-x11-devel or mesa-libGL-devel.
> >
> > The idea is to replace them.
> >
> > >For those who program the cards using extensions these files should
> > >
> > >> replace the original ones. And they will not affect anythibng else
> > >> otherwise.
> > >
> > >They would remove the other mentioned packages completely.
> >
> > Yes. I know that. But the original ones could have their names changed to
> >
> > glext.h.orig
> > gl.h.orig
> > glxext.h.orig
> > glx.h.orig
>
> That would break on the next update of xorg-x11-devel and/or
> mesa-libGL-devel. Or ATrpms would need to keep patched up verisons of
> these files to not have this happen, and it would be a race each time.

There's also a better solution... Its possible to simply point MythTV at the 
current location of the nvidia bits and compile against them there, which 
won't break xorg/mesa. There's a bit to overcome in that the nvidia bits go 
in versioned directories, but there are ways around it... The simple way to 
get said build happening against the latest nvidia bits is to add these to 
settings.pro:

QMAKE_LIBDIR_OPENGL += %{_libdir}/nvidia-graphics-1.0-8774/ to settings.pro
CONFIG_INCLUDEPATH += %{_docdir}/nvidia-graphics8774-devel-1.0_8774/include

At least, this seems to work for me on an FC6 system, where the mesa headers 
have changed such that MythTV can't currently build against them. (Of course, 
plugins are still bombing on other things, but that's another discussion...)

> AFAIU the gl.h and libGL.so of mesa are upwards compatible to any
> vendor specific library, e.g. that's what the GL API was for. You only
> miss proprietary GL extensions, and that's in general a good thing,
> otherwise your packages would require nvidia even on non-nvidia
> hardware and would thus not work there.
>
> There are two exeptions that deal with it properly, mplayer and
> mythtv.

Dunno if the above would work for people w/non-nvidia hardware.

-- 
Jarod Wilson
jarod at wilsonet.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.atrpms.net/pipermail/atrpms-devel/attachments/20060920/d1989b9c/attachment.bin