Can someone fix this? I can't commit
Jon
___
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev
Brian Paul wrote:
I'd like to make a 3.1 beta 3 release by the end of next week.
There have been quite a few bug fixes since beta 2 but I'm not
quite confident enough that a final release is appropriate yet.
I'd like to do more conformance testing and get more end user
feedback.
2) What's the best way to handle multiple drivers for different chipsets?
Well, the best way that I have found to handle it is to use GGIMesa,
which lets you keep the exact same libGL.so core and dynamically load
driver modules on a per-hardware or per-rendering-system basis.
Jon
Stephen J Baker wrote:
On Wed, 8 Sep 1999, Jon Taylor wrote:
Here's another issue. There's an effort underway to standardize
the OpenGL environment on Linux.
...Which explicitly states that this "standardization effort" is
predicated on the existence and us
In Mesa/src/FX/Makefile.am, the "if HAVE_X86" block should also be
wrapped in "if HAVE_FX".
Jon
___
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev
Gerard Saraber wrote:
ps. I'm trying to get S3 to give me the register specs for the Savage4
card, I'm planning on
writing a "glue" .so that has to be (unfortunately) closed source to
interface with the video card,
and a Mesa driver that interfaces with the "glue" library. (just like
the
Thomas Tanner wrote:
On 25-Jul-99 [EMAIL PROTECTED] wrote:
The problem was that it was trying to build the glide and GGI drivers,
even though I don't have the headers (or libraries) for those.
Nor do I and it works fine for me (except for the FX/X86 driver,
which I just fixed).
Stephen J Baker wrote:
On Thu, 10 Jun 1999, Jon Taylor wrote:
1. Linux (Unix) and Windows are, by far, the most popular platforms for
Mesa/OpenGL. The GLX and WGL interfaces are very well established.
Nobody will use a Mesa-specific interface instead of GLX/WGL since
they'd
"Christopher R. Bowman" wrote:
At 07:42 PM 5/20/99 -0700, Jon Taylor wrote:
Brian Paul wrote:
Jon Taylor wrote:
I cannot build any of the demos due to include/GL/glut.h being
missing. Is anyone else seeing this?
GLUT isn't in CVS. I asked Mark Kilgard for
Brian Paul wrote:
Kendall Bennett wrote:
Currently Mesa does all geometry and lighting transformations into
its own internal geometry pipelin, which is in it's own internal
format. The geometry pipeline is then read by the back end graphics
hardware driver (ie: our Direct3D or the
Brian Paul wrote:
Jon Taylor wrote:
I cannot build any of the demos due to include/GL/glut.h being
missing. Is anyone else seeing this?
GLUT isn't in CVS. I asked Mark Kilgard for permission a while back
but didn't get a reply. I'll ask again. In the mean time, use
11 matches
Mail list logo