Daryll Strauss wrote:
>
> Huh? You misunderstood what I wrote. I guess it wasn't clear.
>
> Glide as a stand alone 3D interface is dead. People shouldn't be writing
> applications to Glide they should be using OpenGL. Glide as a hardware
> abstraction layer is fine.
>
> So, all I was saying is
On Mon, May 07, 2001 at 01:16:59AM +1000, Gareth Hughes wrote:
> I wrote:
> > The DRI glide is ONLY useful for the DRI. It won't function in stand
> > alone mode at all. In other words, there isn't just V3 and V5 versions,
> > but also V3-non-DRI, V3-DRI, V5-DRI versions. But, Glide is dead and I
Daryll Strauss wrote:
>
> On Sun, May 06, 2001 at 03:12:46AM -0400, Mike A. Harris wrote:
> > On Fri, 4 May 2001, Daryll Strauss wrote:
> >
> > >It depends on what part of the process you want to solve.
> > >
> > >For the DRI, the easiest solution would be to have the dri_tdfx.o
> > >dynamically
On Sun, May 06, 2001 at 03:12:46AM -0400, Mike A. Harris wrote:
> On Fri, 4 May 2001, Daryll Strauss wrote:
>
> >It depends on what part of the process you want to solve.
> >
> >For the DRI, the easiest solution would be to have the dri_tdfx.o
> >dynamically load the appropriate Glide. The X serv
Ah, I see you're running into the same problem I did a while back.
(I'm the Debian glide maintainer.)
What we do is actually pretty close to that, I use debconf for the
interface though with a little work it could easily be split out.
Basicly at install time I use lspci to find the cards in the
On Fri, May 04, 2001 at 11:02:05AM -0400, Jon Niehof wrote:
> > For the DRI, the easiest solution would be to have the dri_tdfx.o
> > dynamically load the appropriate Glide. The X server knows what
> > hardware it is running on and passes that to the client (via the PCI
> > id). If you did this, y
It depends on what part of the process you want to solve.
For the DRI, the easiest solution would be to have the dri_tdfx.o
dynamically load the appropriate Glide. The X server knows what hardware
it is running on and passes that to the client (via the PCI id). If you
did this, you could also cha
I'd like opinions on what would be the best way of determining at
runtime what glide library to use? The current problem is that
there are 2 Glide libraries for Glide3 - one for Voodoo 3, and
another for Voodoo 5. This is inconvenient to say the least.
Currently, we symlink libglide3.so.3.10.0
