Thomas Tanner wrote:
On 13-Feb-00 Brian Paul wrote:
Is there any reason Mesa 3.3 is building without link information
in the library? Those of us who dlopen() the library get a dl_error
because we can't anticipate the need of, say, Glide.
I guess you're using the GNU configure scripts,
As I wrote earlier, I changed the old-style Makefile so that the
libGL, libGLU, and libglut libraries are implicitly linked with
the libraries that each is dependent on.
This is done with the GL_LIB_DEPS, GLU_LIB_DEPS, GLUT_LIB_DEPS and
APP_LIB_DEPS vars in the Make-config file. These are used
This is all with respect to software Mesa:
Where can I find information about the values in
ctx-ProjectionMatrix? I'm tracing through the glFog code, and for the
code I'm testing the value of eyez is always zero, so for EXP and EXP2
modes, the e^tmp value is always 1.0, and therefore no fogging
Brian Paul [EMAIL PROTECTED] writes
The span-writing functions use the LFB_WRITE_SPAN_MESA macro which
is conditionally defined for RGB vs BGR order.
AFAIK, the RGB vs BGR problem was only on pixel read-back, not
writing. If we indeed have to write different pixel formats depending
on a runtime
Neal Tringham wrote:
> Brian Paul [EMAIL PROTECTED]> writes
> >The span-writing functions use the LFB_WRITE_SPAN_MESA macro which
> >is conditionally defined for RGB vs BGR order.
> >
> >AFAIK, the RGB vs BGR problem was only on pixel read-back, not
> >writing. If we indeed have to write
