The software (gdi) driver is maintained, and as Michal points out, you
may be able to detect your problem with that.
There is also an 'icd' driver that someone submitted, but I don't know
how it works or what sort of state it is in. I would guess that it
just calls the ICD interface, and might
On Tue, Sep 8, 2009 at 9:17 AM, Brian Paul bri...@vmware.com wrote:
Dimitar Kodjabachev wrote:
Hello,
I sent this to mesa3d-dev, which was probably not the right place.
mesa3d-dev is OK since there may be a bug in the Mesa wgl code. I'm
cc'ing mesa3d-dev.
I have the following
On Tue, Sep 8, 2009 at 11:19 AM, José Fonseca jfons...@vmware.com wrote:
On Tue, 2009-09-08 at 09:20 -0700, Karl Schultz wrote:
On Tue, Sep 8, 2009 at 9:17 AM, Brian Paul bri...@vmware.com wrote:
Dimitar Kodjabachev wrote:
Hello,
I sent
On Wed, Sep 9, 2009 at 10:03 AM, Dimitar Kodjabachev dkodjabac...@gmail.com
wrote:
On Tue, Sep 8, 2009 at 8:31 PM, Karl Schultzkarl.w.schu...@gmail.com
wrote:
On Tue, Sep 8, 2009 at 11:19 AM, José Fonseca jfons...@vmware.com
wrote:
On Tue, 2009-09-08 at 09:20 -0700, Karl Schultz
Yeah, I'm preparing a set of changes to allow Mesa 7.6 to build on Visual
Studio. Right now, the 7.6 tarballs do not build.
And I'm sitting here watching the image code compile for a LONG time.
I think I can put this at the top of the file:
#if _MSC_VER == 1400
#pragma optimize(, off)
#endif
I submitted a patch to Brian to make 7.6 compile on VS2005. I sent a copy
of the patch to Delle today. I suspect that the fixes are in the current
tip.
I think that the problem below was caused by new api calls being added
without GL_APIENTRY in the function signature. The patch fixes that.
It looks like you are not compiling all the files.
Be sure you have these files in your project:
Added files to project list:
hash_table.[ch]
lex.yy.c with -D
YY_NO_UNISTD_H
YY_USE_CONST
_CRT_SECURE_NO_DEPRECATE
_CRT_NONSTDC_NO_DEPRECATE
program_parse_extra.c
program_parse_tab.[ch] with -D
was not properly saved
across a function call
Maybe this http://www.codeguru.com/forum/showthread.php?t=366290 LINK
will
help...
Thank you.
http://old.nabble.com/file/p26391769/Runtime%2Berror.PNG Runtime+error.PNG
Delle wrote:
Karl Schultz wrote:
It looks like you
was
not prope...)
I use Mesa32 in Debug version (dynamic linking CRT)
Hope this is helpful to you... ;-)
Delle
Karl Schultz wrote:
This is caused by a mismatch in function signatures in the area of
calling
convention, cdecl vs stdcall.
Did you REBUILD your mesa project after applying
Jose
From: mesa-commit-boun...@lists.freedesktop.org
[mesa-commit-boun...@lists.freedesktop.org] On Behalf Of Karl Schultz
[kschu...@kemper.freedesktop.org]
Sent: Wednesday, February 10, 2010 22:30
To: mesa-com...@lists.freedesktop.org
Subject
- almost to the
point of looking rather automatic.
2010/2/12 Michel Dänzer mic...@daenzer.net:
On Thu, 2010-02-11 at 15:51 -0800, Karl Schultz wrote:
Module: Mesa
Branch: master
Commit: 92098438784887fd6005918794476cfbbeac5035
URL:
http://cgit.freedesktop.org/mesa/mesa/commit/?id
Am getting these warnings in the Windows build:
2Compiling...
2lex.yy.c
2program_lexer.l(327) : warning C4244: '=' : conversion from 'double' to
'float', possible loss of data
2program_lexer.l(331) : warning C4244: '=' : conversion from 'double' to
'float', possible loss of data
12 matches
Mail list logo
