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.
Here are my notes on the patch:
The changes are:
windows/VC8/mesa/mesa/mesa.
vcproj:
Removed unneeded files from project list:
grammar.c
grammar_crt.c
vsnprintf.c
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
YYMALLOC=malloc
YYFREE=free
prog_parameter_layout.[ch]
symbol_table.[ch]
syncobj.[ch]
syncobj.[ch]:
Need to add GLAPIENTRY to six function signatures.
IsSync, DeleteSync, FenceSync, ClientWaitSync, WaitSync, GetSynciv
get.c:
Cast 1 to (GLint64) in three places for bitwise shifting (warning, but could
be a latent bug).
mesa.def:
Remove obsolete entry points
_mesa_begin_query
_mesa_buffer_data
_mesa_buffer_get_subdata
_mesa_buffer_map
_mesa_buffer_subdata
_mesa_buffer_unmap
_mesa_delete_buffer_object
_mesa_delete_query
_mesa_end_query
_mesa_new_buffer_object
_mesa_new_query_object
_mesa_wait_query
On Mon, Nov 16, 2009 at 11:55 AM, tom fogal <tfo...@alumni.unh.edu> wrote:
> Delle <dell...@gmail.com> writes:
> > Delle wrote:
> > >
> > > When I try to buld Mesa version 7.6 onto Win32 I get this error
> message:
> > >
> > > Compiling...
> > > api_exec.c
> > > ..\..\..\..\src\mesa\main\api_exec.c(831) : error C2440: '=' : cannot
> > > convert from 'GLboolean (__cdecl *)(GLsync)' to 'GLboolean (__stdcall
> > > *)(GLsync)'
> > > ..\..\..\..\src\mesa\main\api_exec.c(832) : error C2440: '=' : cannot
> > > convert from 'void (__cdecl *)(GLsync)' to 'void (__stdcall *)(GLsync)'
> > > ..\..\..\..\src\mesa\main\api_exec.c(833) : error C2440: '=' : cannot
> > > convert from 'GLsync (__cdecl *)(GLenum,GLbitfield)' to 'GLsync
> (__stdcall
> > > *)(GLenum,GLbitfield)'
>
> It looks like the calling convention is wrong.
>
> I think you can change the default calling convention in the MSVC
> project file; changing it to stdcall might fix this.
>
> api_exec.c or some other code included therein is probably explicitly
> setting the calling convention for these functions though. Try to
> track down where that happens and change it to stdcall. I'm sure a
> patch would be welcome, especially if you could identify why this
> started happening.
>
> Cheers,
>
> -tom
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Mesa3d-dev mailing list
> Mesa3d-dev@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
>
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Mesa3d-dev mailing list
Mesa3d-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
