Main > Software Forum
MAME Compiler 64 v2.0.197
rooter:
Any chance this works with the 64bit version of Mame? If not, will it in the future?
headkaze:
--- Quote from: rooter on December 13, 2007, 03:55:10 pm ---Any chance this works with the 64bit version of Mame? If not, will it in the future?
--- End quote ---
Not until there is a 64 bit version of the GCC compiler. Right now the only way to compile the 64-bit versions is with the command line compiler included with the Microsoft Platform SDK and a recent version of the DirectX SDK. I'll take a look at adding support for it one day, but people will have to download those tools separately in any case and it kinda defeats the purpose of what Mame Compiler was trying to achive which is an all in one tool for compiling Mame.
bent98:
I just tried it with mame .121 with 121u4.diff.
patched then hit go.
Got hunk errors on patch and got these errors after pressing GO
Compiling src/mame/drivers/starwars.c...
Compiling src/mame/machine/starwars.c...
src/mame/machine/starwars.c:208:47: error: macro "timer_alloc" passed 2 arguments, but takes just 1
src/mame/machine/starwars.c: In function 'starwars_mproc_init':
src/mame/machine/starwars.c:208: error: 'timer_alloc' undeclared (first use in this function)
src/mame/machine/starwars.c:208: error: (Each undeclared identifier is reported only once
Finished!
0 Hours 1 Minutes and 29 Seconds Elapsed.
src/mame/machine/starwars.c:208: error: for each function it appears in.)
mingw32-make: *** [obj/windows/mamepm/mame/machine/starwars.o] Error 1
mingw32-make: *** Waiting for unfinished jobs....
all I selected was pentium m/ Core Duo options and also cheked Dual core.
MKChamp:
Did you patch 121u1 then 121u2 then 121u3 AND THEN 121u4....or did you just patch 121u4? Looks like you skipped the other u releases...
edit: They changed the parms for the timer_alloc function is 121u2...
bent98:
ah yea my bad.
Question what if i want to compile 0121u1-u4 and then apply hi_0121u2. Will that be a problem? they havent come out with hi_0121u4 yet