Re: [Mesa3d-users] Mesa3.2/Win32-3dfx issue --FIXED--

[Brian P. <br...@va...>]

Alessandro Pisani wrote:
> 
> Preliminar note: this patch is against Mesa 3.2-final
> Okay, i've fixed the bi**h : now it works fine ;)
> Thanks to Eero Pajarre for helping me understand what was wrong :)
> 
> The attached file will replace these files:
> win32\nmake.mak
> win32\nmake.mif
> win32\rules\lib.fxmesa
> win32\rulelib.fxmesa32
> 
> With these changes you will be able to recompile Mesa+3dfx from mesae32.bat
> or nmake /f win32\nmake.mak without receiving "unresolved external" errors.
> 
> I tested the new files with my MS-VC 6.0, enabling ALL optimizations (asm
> x86, mmx, 3dnow) and all of them now work ;)
> Note: for some strange reason i can't understand, NASM 0.98 does not want a
> NASM variabile is set in the environment WHEN called from win32/nmake.mak
> (that's strange 'cos the same thing doesn't happen with makefile.fx), so i
> changed the NASM variable in all the files above to USENASM.
> 
> (if you try to compile mesa+3dfx from win32/nmake.mak with NASM=whatever,
> you will receive an error like "more than one input file specified"... it
> seems like NASM read the env-variable NASM and uses "whatever" as first
> input-file value.... ?!?)
> 
> More patches for MSVC6 are under testing ... ;)
> Hope that helps,
> TXM
> 
> PS: the file attached is intended to be unzipped in the mesa root dir.

Done. I've checked in the new changes to the Mesa 3.2 branch.  They'll
be in the 3.2.1 release which I hope to finish this week.

-Brian