|
From: Brian P. <bri...@tu...> - 2008-05-28 15:05:41
|
sdc395 wrote: > I've attempted to build 7.1 RC 1 using Visual Studio 2005 and can report the > following issues... > > Building mesa... > > >> \src\mesa\main\texcompress_fxt1.c(668) : warning C4293: '<<' : shift count >> negative or too big, undefined behavior >> \src\mesa\main\texcompress_fxt1.c(715) : warning C4293: '<<' : shift count >> negative or too big, undefined behavior >> \src\mesa\main\texcompress_fxt1.c(721) : warning C4293: '<<' : shift count >> negative or too big, undefined behavior >> \src\mesa\main\texcompress_fxt1.c(886) : warning C4293: '<<' : shift count >> negative or too big, undefined behavior >> \src\mesa\main\texcompress_fxt1.c(892) : warning C4293: '<<' : shift count >> negative or too big, undefined behavior >> \src\mesa\main\texcompress_fxt1.c(1106) : warning C4293: '<<' : shift >> count negative or too big, undefined behavior >> \src\mesa\main\texcompress_fxt1.c(1275) : warning C4293: '<<' : shift >> count negative or too big, undefined behavior >> > > Can't Fx64 by typedef'd as unsigned __int64 rather then using that generic > struct solution? The code in that file should probably just be rewritten to use the GLuint64EXT type that's defined in glext.h. I may take a stab at that later. > > Building gdi... > > >> \src\mesa\drivers\windows\gdi\wgl.c(606) : warning C4013: >> 'WMesaShareLists' undefined; assuming extern returning int >> >> mesa.def : error LNK2001: unresolved external symbol _mesa_attach_shader >> mesa.def : error LNK2001: unresolved external symbol >> _mesa_bind_attrib_location >> mesa.def : error LNK2001: unresolved external symbol _mesa_compile_shader >> mesa.def : error LNK2001: unresolved external symbol _mesa_create_program >> mesa.def : error LNK2001: unresolved external symbol _mesa_create_shader >> mesa.def : error LNK2001: unresolved external symbol _mesa_delete_program2 >> mesa.def : error LNK2001: unresolved external symbol _mesa_delete_shader >> mesa.def : error LNK2001: unresolved external symbol _mesa_detach_shader >> mesa.def : error LNK2001: unresolved external symbol >> _mesa_get_active_attrib >> mesa.def : error LNK2001: unresolved external symbol >> _mesa_get_active_uniform >> mesa.def : error LNK2001: unresolved external symbol >> _mesa_get_attached_shaders >> mesa.def : error LNK2001: unresolved external symbol >> _mesa_get_attrib_location >> mesa.def : error LNK2001: unresolved external symbol _mesa_get_handle >> mesa.def : error LNK2001: unresolved external symbol >> _mesa_get_program_info_log >> mesa.def : error LNK2001: unresolved external symbol _mesa_get_programiv >> mesa.def : error LNK2001: unresolved external symbol >> _mesa_get_shader_info_log >> mesa.def : error LNK2001: unresolved external symbol >> _mesa_get_shader_source >> mesa.def : error LNK2001: unresolved external symbol _mesa_get_shaderiv >> mesa.def : error LNK2001: unresolved external symbol >> _mesa_get_uniform_location >> mesa.def : error LNK2001: unresolved external symbol _mesa_get_uniformfv >> mesa.def : error LNK2001: unresolved external symbol _mesa_is_program >> mesa.def : error LNK2001: unresolved external symbol _mesa_is_shader >> mesa.def : error LNK2001: unresolved external symbol _mesa_link_program >> mesa.def : error LNK2001: unresolved external symbol _mesa_shader_source >> mesa.def : error LNK2001: unresolved external symbol _mesa_uniform >> mesa.def : error LNK2001: unresolved external symbol _mesa_uniform_matrix >> mesa.def : error LNK2001: unresolved external symbol >> _mesa_validate_program >> > > All of those unresolved functions are defined as static in shader_api.c I'm attaching a new mesa.def file. Could you please try it and see if that fixes these errors? > Also, it would be nice to have the project dependencies configured in the > solution file. It would save me having to do it every time I download a new > version. I'm not familiar with that. Maybe a Windows developer can contribute what's needed. > Might this release have addressed the heap corruption issue I reported? Can you remind me what that was? Did you file a bug report? -Brian |