[APP] MAME Compiler 64 v2.0.165

[stephenp1983]

That's correct.

Ok cool I will try this again tonight. I tried compiling a couple of days ago when I was in a rush, and I messed something up because there was no mame32.exe in the source folder.

[stephenp1983]

It seemed to work great this time, I don't know what I did differently lol

So all I need to do is move the mame32.exe that i just created and replace the one in my current mame32 directory?

[Adultery]

Yes that's exactly right.

[kris2]

Hello everyone, this is my first post, and I had some problem when i tried to compile mame, I made as following the instruction like is down, but i had a terribles errors and i didn¡'t compile

How to compile MameUI 0126 u4 (Skip the MameUI steps to compile standard Mame)

1. Install Mame Compiler

2. Download the Mame source from mamedev.org (ie. mame0126s.exe)

3. Download the Intermediate Updates from mamedev.org (ie. 0126u1_diff.zip, 0126u2_diff.zip, 0126u3_diff.zip, 0126u4_diff.zip)

4. Download MameUI source from here (ie. MameUIs.126.4)

5. Download the hiscore diff patch from here (ie. hi_126u4.txt)

6. Rename hi_126u4.txt to hi_126u4.diff and copy the file into C:\MinGW\patches

7. Extract the Intermediate Update diff's to C:\MinGW\patches

8. Run mame0126s.exe and extract it to C:\MinGW\source\Mame0126u4

9. Run MameUIs.exe and extract it to C:\Temp\MameUI then copy "mameui.mak" to C:\MinGW\source\Mame0126u4 and the "winui" folder to C:\MinGW\source\Mame0126u4\src\osd\winui.

10. Run Mame Compiler (Start->Program Files->Mame Compiler->MameCompiler)

11. Click the [...] button to browse for the "Mame Source Folder" and point it to C:\MinGW\source\Mame0126u4

12. Click the [...] button to browse for the "Diff Patch File" and point it to C:\MinGW\patches\126u1.diff

13. Click the "Apply Patch" button.

14. Repeat step 12 for 0126u2.diff, 0126u3.diff and 0126u4.diff, then hi_126u4.diff

15. Put a tick next to the "Mame UI" option if your compiling MameUI

16. Press the "GO!" button to compile Mame

17. When it's finished compiling it should create a "mame.exe" file in the C:\MinGW\source\Mame0126u4 folder

I tried with version of mame126,128,129, but it doesn't work when i used that version i used to hi_126, hi_128, hi_129, respectibly, but i don't how i can make it.

The errors it was

src/lib/util/palette.c:251: error: redefinition of 'palette_get_max_index'

src/lib/util/palette.c:239: error: previous definition of 'palette_get_max_index' was here

src/lib/util/palette.c:263: error: redefinition of 'palette_get_max_index'

src/lib/util/palette.c:239: error: previous definition of 'palette_get_max_index' was here

Finished!

0 Hours 1 Minutes and 1 Seconds Elapsed.

mingw32-make: *** [obj/windows/mamed/lib/util/palette.o] Error 1

If some one can help me I'll be apreciate, tks.

error.bmp

[bkenobi]

Just to make sure the program is working right in the first place, try starting with a fresh MAME source and compiling without any patches.

[headkaze]

Just to make sure the program is working right in the first place, try starting with a fresh MAME source and compiling without any patches.

What bk said plus there is no reason for you to compile the debug version is there? Turn that setting off.

[kris2]

Just to make sure the program is working right in the first place, try starting with a fresh MAME source and compiling without any patches.

[Stu1983]

I can't seem to compile MAME 130 using the 64bit option

I get this log everytime:

Deleting Object Folder...
Compiling Mame64...
Using Parameters  ARCHOPTS="-march=pentium-m -msse3" MSVC_BUILD=1 PTR64=1
mkdir.exe -p obj/windows/vmame
mkdir.exe -p obj/windows/vmame/build
mkdir.exe -p obj/windows/vmame/emu/audio
mkdir.exe -p obj/windows/vmame/emu/cpu
mkdir.exe -p obj/windows/vmame/emu/cpu/adsp2100
mkdir.exe -p obj/windows/vmame/emu/cpu/alph8201
mkdir.exe -p obj/windows/vmame/emu/cpu/apexc
mkdir.exe -p obj/windows/vmame/emu/cpu/arm
mkdir.exe -p obj/windows/vmame/emu/cpu/arm7
mkdir.exe -p obj/windows/vmame/emu/cpu/asap
mkdir.exe -p obj/windows/vmame/emu/cpu/ccpu
mkdir.exe -p obj/windows/vmame/emu/cpu/cdp1802
mkdir.exe -p obj/windows/vmame/emu/cpu/cop400
mkdir.exe -p obj/windows/vmame/emu/cpu/cp1610
mkdir.exe -p obj/windows/vmame/emu/cpu/cubeqcpu
mkdir.exe -p obj/windows/vmame/emu/cpu/dsp32
mkdir.exe -p obj/windows/vmame/emu/cpu/dsp56k
mkdir.exe -p obj/windows/vmame/emu/cpu/e132xs
mkdir.exe -p obj/windows/vmame/emu/cpu/esrip
mkdir.exe -p obj/windows/vmame/emu/cpu/f8
mkdir.exe -p obj/windows/vmame/emu/cpu/g65816
mkdir.exe -p obj/windows/vmame/emu/cpu/h6280
mkdir.exe -p obj/windows/vmame/emu/cpu/h83002
mkdir.exe -p obj/windows/vmame/emu/cpu/hd6309
mkdir.exe -p obj/windows/vmame/emu/cpu/i386
mkdir.exe -p obj/windows/vmame/emu/cpu/i8085
mkdir.exe -p obj/windows/vmame/emu/cpu/i86
mkdir.exe -p obj/windows/vmame/emu/cpu/i860
mkdir.exe -p obj/windows/vmame/emu/cpu/i960
mkdir.exe -p obj/windows/vmame/emu/cpu/jaguar
mkdir.exe -p obj/windows/vmame/emu/cpu/konami
mkdir.exe -p obj/windows/vmame/emu/cpu/lh5801
mkdir.exe -p obj/windows/vmame/emu/cpu/lr35902
mkdir.exe -p obj/windows/vmame/emu/cpu/m37710
mkdir.exe -p obj/windows/vmame/emu/cpu/m6502
mkdir.exe -p obj/windows/vmame/emu/cpu/m6800
mkdir.exe -p obj/windows/vmame/emu/cpu/m68000
mkdir.exe -p obj/windows/vmame/emu/cpu/m6805
mkdir.exe -p obj/windows/vmame/emu/cpu/m6809
mkdir.exe -p obj/windows/vmame/emu/cpu/mb86233
mkdir.exe -p obj/windows/vmame/emu/cpu/mb88xx
mkdir.exe -p obj/windows/vmame/emu/cpu/mc68hc11
mkdir.exe -p obj/windows/vmame/emu/cpu/mcs48
mkdir.exe -p obj/windows/vmame/emu/cpu/mcs51
mkdir.exe -p obj/windows/vmame/emu/cpu/minx
mkdir.exe -p obj/windows/vmame/emu/cpu/mips
mkdir.exe -p obj/windows/vmame/emu/cpu/nec
mkdir.exe -p obj/windows/vmame/emu/cpu/pdp1
mkdir.exe -p obj/windows/vmame/emu/cpu/pic16c5x
mkdir.exe -p obj/windows/vmame/emu/cpu/powerpc
mkdir.exe -p obj/windows/vmame/emu/cpu/rsp
mkdir.exe -p obj/windows/vmame/emu/cpu/s2650
mkdir.exe -p obj/windows/vmame/emu/cpu/saturn
mkdir.exe -p obj/windows/vmame/emu/cpu/sc61860
mkdir.exe -p obj/windows/vmame/emu/cpu/se3208
mkdir.exe -p obj/windows/vmame/emu/cpu/sh2
mkdir.exe -p obj/windows/vmame/emu/cpu/sh4
mkdir.exe -p obj/windows/vmame/emu/cpu/sharc
mkdir.exe -p obj/windows/vmame/emu/cpu/sm8500
mkdir.exe -p obj/windows/vmame/emu/cpu/spc700
mkdir.exe -p obj/windows/vmame/emu/cpu/ssp1601
mkdir.exe -p obj/windows/vmame/emu/cpu/t11
mkdir.exe -p obj/windows/vmame/emu/cpu/tlcs90
mkdir.exe -p obj/windows/vmame/emu/cpu/tms32010
mkdir.exe -p obj/windows/vmame/emu/cpu/tms32025
mkdir.exe -p obj/windows/vmame/emu/cpu/tms32031
mkdir.exe -p obj/windows/vmame/emu/cpu/tms32051
mkdir.exe -p obj/windows/vmame/emu/cpu/tms34010
mkdir.exe -p obj/windows/vmame/emu/cpu/tms57002
mkdir.exe -p obj/windows/vmame/emu/cpu/tms7000
mkdir.exe -p obj/windows/vmame/emu/cpu/tms9900
mkdir.exe -p obj/windows/vmame/emu/cpu/upd7810
mkdir.exe -p obj/windows/vmame/emu/cpu/v30mz
mkdir.exe -p obj/windows/vmame/emu/cpu/v60
mkdir.exe -p obj/windows/vmame/emu/cpu/v810
mkdir.exe -p obj/windows/vmame/emu/cpu/z180
mkdir.exe -p obj/windows/vmame/emu/cpu/z80
mkdir.exe -p obj/windows/vmame/emu/cpu/z8000
mkdir.exe -p obj/windows/vmame/emu/debug
mkdir.exe -p obj/windows/vmame/emu/drivers
mkdir.exe -p obj/windows/vmame/emu/layout
mkdir.exe -p obj/windows/vmame/emu/machine
mkdir.exe -p obj/windows/vmame/emu/sound
mkdir.exe -p obj/windows/vmame/emu/video
mkdir.exe -p obj/windows/vmame/lib/expat
mkdir.exe -p obj/windows/vmame/lib/util
mkdir.exe -p obj/windows/vmame/lib/zlib
mkdir.exe -p obj/windows/vmame/mame/audio
mkdir.exe -p obj/windows/vmame/mame/drivers
mkdir.exe -p obj/windows/vmame/mame/layout
mkdir.exe -p obj/windows/vmame/mame/machine
mkdir.exe -p obj/windows/vmame/mame/video
mkdir.exe -p obj/windows/vmame/osd/windows
mkdir.exe -p obj/windows/vmame/tools
Compiling src/osd/windows/vconv.c...
process_begin: CreateProcess(C:\MinGW\psdk\bin\amd64\cl.exe, cl.exe /nologo /O1 -D_CRT_SECURE_NO_DEPRECATE -c src/osd/windows/vconv.c /Foobj/windows/vmame/osd/windows/vconv.o, ...) failed.
Finished!
0 Hours 0 Minutes and 3 Seconds Elapsed.
make (e=193): Error 193
mingw32-make: *** [obj/windows/vmame/osd/windows/vconv.o] Error 193

I've tried fresh source and 2 different PCs

I've successfully compiled 128, 125 and a few other earlier versions with the 64bit option ticked using your tool headkaze just not this version

Thanks

Stu

[headkaze]

I have successfully compiled Mame 32, Mame 64, MameUI 32, MameUI 64 all version 0130u2 so there is no problem AFAIK. Sometimes when it fails pressing GO! again will continue the compile which did happen to me.

[Stu1983]

I have successfully compiled Mame 32, Mame 64, MameUI 32, MameUI 64 all version 0130u2 so there is no problem AFAIK. Sometimes when it fails pressing GO! again will continue the compile which did happen to me.

Just tried a third PC and it compiles 64bit ok but it but errors while applying the hi score patch, so I used the first PC to apply the patch and the 3rd PC to compile Mame

It's all very strange

Stu

[headkaze]

If you try to apply a hiscore patch twice it will show errors or if you apply a patch designed for a different version it may have an error or succeed using offsets.

[dwight]

Any chance of a Core i7 "compile option" version of mame compiler coming out? Today I just use Intel Core 2, Quad Core, 64-bit settings, but there might be another 1% that can be dragged out of an i7 option.

Thanks,

Dwight.

[DJ Infinity]

Will there be a new version to compile the newer Mame(s). From what I read there has been a tool change

[headkaze]

Will there be a new version to compile the newer Mame(s). From what I read there has been a tool change

Hey DJ Infinity. Yeah I will update this soon. Looks like they are using a 64 bit GCC compiler now. So I will probably replace the Microsoft one.

[DJ Infinity]

Hey DJ Infinity. Yeah I will update this soon. Looks like they are using a 64 bit GCC compiler now. So I will probably replace the Microsoft one.

Thanx. You know slow people like me can't make sense of this stuff and need a lil help. I want to get back into Mame again. I have updated Rom(s) & CHD(s) for 136. Thanx again

[headkaze]

Okay MC64 has been updated to use the latest toolchain. I did have an issue compiling a 32-bit version on my 64-bit machine "png2bdc.exe" crashes. I've looked this up and it appears to be a problem that doesn't relate to MC64 (more info)

Also MC64 will now detect how many cores you have and if you're running 64-bit and set the options for you. So default options to compile for your PC should be fine.

[fRequEnCy]

Okay MC64 has been updated to use the latest toolchain. I did have an issue compiling a 32-bit version on my 64-bit machine "png2bdc.exe" crashes. I've looked this up and it appears to be a problem that doesn't relate to MC64 (more info)

Also MC64 will now detect how many cores you have and if you're running 64-bit and set the options for you. So default options to compile for your PC should be fine.

Thanks for the update HK. This makes things even more simple for users who haven't compiled before.

Just compiled again and experienced no issues where I had them before with the new version of MAME. Thanks again!

[Drakendoder]

perhaps its because english isn't my first language, or maybe its because i'm just a plain ol'noob, but what does this program do exactly, what is compiling?

--i see x64 and i see quad core so it has my natural interest---

[fRequEnCy]

perhaps its because english isn't my first language, or maybe its because i'm just a plain ol'noob, but what does this program do exactly, what is compiling?

--i see x64 and i see quad core so it has my natural interest---

Taken from the BYOAC Forums:

HISCORE DIFF's for all MAME versions without hiscore support (107u2 - current)

The diff performs the following:

1) Adds hiscore support back into MAME

2) Removes all nag screens

3) Removes loading messages (decoding/decrypting/Updating Artwork, etc.) and the 'white box' when loading. (This was added to the diffs starting with hi_120)

4) Disables crosshairs by default. You can turn them back on in the game with F1 This was removed starting with hi_130u3 since MAME core now has the ability to change crosshair settings in the menu.

5) Tab button(menu) also pauses MAME and 1 acts as 'Enter'. Remove the inptport.c section if you do not want this(or just remove it from the ingame menu) This was removed starting with hi_124. You can configure this in the in game menu.

So applying these patches adds those features into MAME. This program makes it easy to do that and create your own version of MAME with those capabilities.

[Tempest]

Okay MC64 has been updated to use the latest toolchain. I did have an issue compiling a 32-bit version on my 64-bit machine "png2bdc.exe" crashes. I've looked this up and it appears to be a problem that doesn't relate to MC64 (more info)

Also MC64 will now detect how many cores you have and if you're running 64-bit and set the options for you. So default options to compile for your PC should be fine.

The default settings feature will be sweet!

[Drakendoder]

Taken from the BYOAC Forums:

So applying these patches adds those features into MAME. This program makes it easy to do that and create your own version of make with those capabilities.

wow, thats awesome! Do i have to use MAME without GUI, or can i use it with MAMEXT64? Because i those features aren't readily available in some of the UIfriendly packages right?

also, with nagscreen you hopefully mean those (type 'ok' or leftright to continue)screens?

[bkenobi]

There are some guides in this thread on how to compile non-standard versions of MAME. I don't think MAMEXT64 is one of those, but it might be close enough to fake it. And yes, compiling with the hiscore patch disables the 'ok' screens that you are referring to.

[Drakendoder]

cool i'll make work of it

[Brian Hoffman]

Thanks for the update!

[Drakendoder]

question:

i think i got it all to work, and thank god the nagscreens are gone but the hiscores aren't working so far. It's not THAT big of a deal, but surely it would be nice. Do i have to enable it somewhere?