MAME Compiler 64 v2.0.197

[Deadly]

Unable to get MAMEUI64 compiled. I've quadruple checked the docs on Headkazes site. When I attempt to patch it always ends up stating:
Applying Diff patch...
can't find file to patch at input line 4
I've tried the GUI compiler as well as batch filing it and both produce same result. .  

Diff patch taken off first page (hi_146.txt) and renamed to .diff
Source code downloaded from Mameui directly.
Again I've quadruple checked my file/folder placement
Uninstalled compiler 64 and reinstalled as well.
 
Thanks for any help.

EDIT: Someone told me the diff file has to be specific to the flavor of Mame. If this is true I think the documentation on Headkazes site should be updated to reflect this. Is anyone making a mameui 146 .diff?
 

[CZakalwe]

Nevermind

BTW thanks Headkaze for this

[Dazz]

Does new compiles not create the additional files?  When compiling MAME 146 all I'm getting is the MAME.exe.  I'm no longer getting any of the additional files such as chdman.exe, ledutil.exe, etc.  Is there something that I'm missing now?

BTW - I'm using MC64 v1.23

[DNA Dan]

I got the same result. Are those files no longer needed? I don't even know what they are for.

[wild_eyed]

hi my processor is a phenom x4 9600, what would the best processor selection in MAME Compiler be for me?

[xefned]

It's working great with version .145!

For beginners like me having trouble, here be snags:

Q.) I compiled but I'm still getting nag screens, WTF?

A.) Don't forget to click Apply Patch over at the left before you click Go. It's easy to miss.

Q.) I apply patch and something about chunks? Patches are skipped, WTF?

A.) Be sure to point to the directory with the Make file, not the src directory.

Hope that helps!   

[gman314]

I am trying to compile mame147u2 (with hiscore patch/no nag screens) and something is going wrong. When I attempt to apply the u1 diff, the compile screen never seems to finish working.  Last time, I gave up at about 90 minutes. I have followed all of the directions to compile standard MAME (i skipped the ui steps).
I took a two pictures while the screen was scrolling so that you can get an idea of what the problem might be. Thanks in advance.

[headkaze]

I am trying to compile mame147u2 (with hiscore patch/no nag screens) and something is going wrong. When I attempt to apply the u1 diff, the compile screen never seems to finish working.  Last time, I gave up at about 90 minutes. I have followed all of the directions to compile standard MAME (i skipped the ui steps).
I took a two pictures while the screen was scrolling so that you can get an idea of what the problem might be. Thanks in advance.

It looks like you have tried to apply the patch twice or something. Delete the source and start again.

[gman314]

I tried a few more times and it still doesn't work.  I'm almost certain that I didn't try to apply the diff twice.  How long should it usually take to apply the u1 diff?  I'm assuming far less than 90 minutes.

Could the problem be that I am directing the compiler to the wrong folders?  Obviously, I had to change the default 143s to 147s. 

Another thing that I notice is that the speed of the scrolling slows down as more time passes.  After about an hour, I could almost read line by line as they pass by.

[gman314]

I did it! I compiled both 147u2 (no nag/hiscore) and 127 (no nag/hiscore). I noticed a slight ambiguity in the readme file. When you extract the mame127s.zip or mame147s.zip files into c:/mingw/source/mamexxx/  this results in a file called mame.zip. It was necessary for me to extract this file and point the source folder (in mame compiler 64) to the folder that you extracted these files to. I just put them in the same folder as the mame.zip. The thing is that there is a file called "makefile" that the source needs to point to. 

[equlizer]

I would like to compile mame to be able to recognize the Z axis and also be able to set the save to 1 button (save and press 1 at the same time) and the same with loading.  How do i go about adding those 2 things in?

[flyguy0101]

Alright i have run the compiler and hi score patch it all seemed to work perfectly- THX- simple question since i ran the compiler on one computer and will be using the newly compiled file on my arcade computer do i need to move anything other than the application file. ie mame.exe.
thanks

[brihyn]

is there a direct link for version 1.17? I need to compile a .141 rom and the link on the Headsoft site doesn't seem to take me to the compiler.

[headkaze]

is there a direct link for version 1.17? I need to compile a .141 rom and the link on the Headsoft site doesn't seem to take me to the compiler.

It is on the website.

For Mame versions earlier than 0143u1 you cannot use Mame Compiler v1.18 to compile MAME you must use v1.17. You can download Mame Compiler v1.17 from here.

I guess the fact my links don't highlight in any way is a little confusing. I should fix that.

[brihyn]

Heh....I can't believe I've missed that link. I first went to your page a month ago and have re-read it a few times since....always hitting the link below. While the colors aren't perfect, I certainly should have been smart enough to realize that "here" was a link.
Anyway, thanks for the reply, and larger thanks for what looks like will be a really helpful tool!

[bullrees]

I've used this great tool to compile mame several times but I'm having a problem compiling mameui now. I know UI seems to be  on it's last legs but I still really like it over many of the more flashy front ends.
The steps I followed are:
1. Get the mame 147 source and the patches U1, U2, U3.
2. Get mamui64 147 source.
3. Copy mame 147 source to ..minigw/source/mame147u3
4. Copy mameui/src to ...minigw/source/mame147u3/src   (overwriting files)
5. Copy mame U1, U2, U3, and hiscore.diff patches to minigw/patches
6. Start mame compiler and apply U1, U2, U3, and  hiscore.
7. Check 64bit and mame ui on the compiler.(tried with many other combos but this is the least that I need)


Everything seems to go well until the very end. I get the following error and even though it says it was completed there is no .EXE generated.
Thanks for any help or ideas.
System is:
Intel E6400 C2D
2G DDR2 800

Code: [Select]

Compiling src/osd/winui/columnedit.c...
cc1plus.exe: warnings being treated as errors
src/osd/winui/directories.c:46: error: unknown option after '#pragma GCC diagnostic' kind
make: *** [obj/winui64/osd/winui/directories.o] Error 1
make: *** Waiting for unfinished jobs....
cc1plus.exe: warnings being treated as errors
src/osd/winui/columnedit.c:38: error: unknown option after '#pragma GCC diagnostic' kind
make: *** [obj/winui64/osd/winui/columnedit.o] Error 1
Finished!
0 Hours 24 Minutes and 32 Seconds Elapsed.


[txjoker]

I'm having the exact same issue -- I've cleaned out the source tree twice and repatched with the same results.

[headkaze]

Mame Compiler 64 v1.24 Released

- Updated to the new toolchain
- Added Force Direct Input option

Tested and working with Mame 0147u3 and Mame UI 0147 u3 (if you get an error with the latter just press GO! again).

NOTE: MinGW is no longer included in the MC64 install. You have to download it separately from here.

Download Mame Compiler 64 v1.24

[txjoker]

Mame Compiler 64 v1.24 Released

- Updated to the new toolchain
- Added Force Direct Input option

Tested and working with Mame 0147u3 and Mame UI 0147 u3 (if you get an error with the latter just press GO! again).

NOTE: MinGW is no longer included in the MC64 install. You have to download it separately from here.

Download Mame Compiler 64 v1.24

Building now!  Thanks!

[txjoker]

Success!  Thanks for the update!

[bullrees]

Thanks headkaze. Works great.


EDIT: What does the Force Direct Input option do?

[txjoker]

Tested successfully with Mame0147u4 (had to click "Go!" twice to get the binary).

[headkaze]

EDIT: What does the Force Direct Input option do?

It's for the people who want to be able to send keys to MAME using a tool like AutoHotkey.

[bullrees]

EDIT: What does the Force Direct Input option do?

It's for the people who want to be able to send keys to MAME using a tool like AutoHotkey.

Thanks for the explanation.

[headkaze]

Mame Compiler 64 1.3 Released
- Many new compiler options added

[griffindodd]

I'm sure these error questions must sound like a stuck record to you but I am also getting patchDiff erros complaining the sytem cannot find the file.

Trying to compile x64 version

extracted the 147 source so I have folders and the make file in the mingw\source\ dir, I have patches 0147u1,u2,u3,u4 and hi score in the patch folder. 64-bit checked, not trying to build a UI version.

First time doing this so I'm pretty lost on the subject

[txjoker]

Tested successfully with Mame 0.148 (hiscore diff and non-UI)

[Yoeddy1]

Hi headkaze,

It looks like things have changed quite a bit.  I downloaded the new version of MC64Setup.exe (1.3).  I've used this for the several past revisions of MAME, but as you mentioned, MinGW is no longer bundled in with MC64Setup.exe.  I downloaded mingw-mame-w64-20121207.exe from MAMEDev.  This is where I get lost.  It's a 156 meg file and when I extract it, it's HUGE and has a lot of new files that the old one didn't contain.

So do I create a MinGW folder on C:\ still and extract the entire contents of this new mingw....exe there?  I guess I just need to understand how the file structure is supposed to look and what files need to go where.  Your instructions above don't appear to correspond with the new files.  Could you provide a new set of instructions to match?  Like I said, I've used MC64Setup.exe for a long time, but the mingw.exe and where the source files are supposed to go have me confused.  Trying to set this up for 148.

Thanks so much!
Jason

[txjoker]

So do I create a MinGW folder on C:\ still and extract the entire contents of this new mingw....exe there?  I guess I just need to understand how the file structure is supposed to look and what files need to go where.

That's exactly right -- Extract the huge MinGW that you downloaded to C:\MinGW (I think the instructions specify this).  You should end up with two directories there:

mingw64-w32
mingw64-w64

That's also where you'll put your "source" and "patch" directories. 

In Mame Compiler, you specify "C:\MinGW" under MinGW folder, and you're all set.

Hope that helps.

[Yoeddy1]

Txjoker, yep that did it!

Thanks my friend.

Jason

[gamepimp]

Headkaze, I used v1.3 for the first time today to compile UME 0.148. I enabled "64-bit processor", "Quad Core", and "No Warnings as Errors" in the General tab which is what I always compile with. I had "Win32", "UME", "Default", and "Windows" respectively in the 4 fields on the Target tab. Nothing was enabled on the Build or Symbols tabs. I ended up getting the following error msgs just before completion of the compiling process and no .exe was created. Any thoughts on what might have gone wrong here? At a glance, it looks like there was trouble locating the makefile perhaps?

Compiling src/emu/cpu/mcs51/mcs51.c...
Generating i8x9x source file...
process_begin: CreateProcess(NULL, python src/emu/cpu/mcs96/mcs96make.py mcs96 src/emu/cpu/mcs96/mcs96ops.lst obj/windows64/emu/cpu/mcs96/mcs96.inc, ...) failed.
make (e=2): The system cannot find the file specified.
make: *** [obj/windows64/emu/cpu/mcs96/mcs96.inc] Error 2
make: *** Waiting for unfinished jobs....
Finished!
0 Hours 9 Minutes and 46 Seconds Elapsed.

[raungst]

Has anyone gotten 0.148 to compile? I'm trying with the hi_score diff, and I get the following error. Any ideas? Since it's update_hi, is there something in the patch that's wrong?

Compiling src/osd/windows/video.c...
src/osd/windows/video.c:257:6: error: redefinition of 'void windows_osd_interface::update_hi(bool)'
src/osd/windows/video.c:235:6: error: 'virtual void windows_osd_interface::update_hi(bool)' previously defined here
src/osd/windows/video.c:279:6: error: redefinition of 'void windows_osd_interface::update_hi(bool)'
src/osd/windows/video.c:235:6: error: 'virtual void windows_osd_interface::update_hi(bool)' previously defined here
src/osd/windows/video.c:301:6: error: redefinition of 'void windows_osd_interface::update_hi(bool)'
src/osd/windows/video.c:235:6: error: 'virtual void windows_osd_interface::update_hi(bool)' previously defined here
Finished!
0 Hours 43 Minutes and 45 Seconds Elapsed.
make: *** [obj/windows/osd/windows/video.o] Error 1

[paracai2]

Hi, Iīm trying to compile mame version 1.47.

Iīve installed everything I think I need (mingw-get-inst-20120426.exe, MC64setup.exe and the hi_147.diff file).

When I press the Apply Patch or the Go buttom, the compiler says "The system cannot find the specified path". I,ve read the previous posts and found that I donīt have a file called patch.exe in the C:\MinGV\bin directory.

Iīve reinstalled several times and checked that path name donīt have blank spaces but no results.

Whatīs the problem?.

Thanks in advance.

[paracai2]

Hi, Iīm trying to compile mame version 1.47.

Iīve installed everything I think I need (mingw-get-inst-20120426.exe, MC64setup.exe and the hi_147.diff file).

When I press the Apply Patch or the Go buttom, the compiler says "The system cannot find the specified path". I,ve read the previous posts and found that I donīt have a file called patch.exe in the C:\MinGV\bin directory.

Iīve reinstalled several times and checked that path name donīt have blank spaces but no results.

Whatīs the problem?.

Thanks in advance.

I got it. Now, the apply patch goes ok but when I press Go, it says "make: *** windows32_openpipe(): DuplicateHandle(In) failed (e=6)".

What is this?

Thanks again.

[paracai2]

Hi, Iīm trying to compile mame version 1.47.

Iīve installed everything I think I need (mingw-get-inst-20120426.exe, MC64setup.exe and the hi_147.diff file).

When I press the Apply Patch or the Go buttom, the compiler says "The system cannot find the specified path". I,ve read the previous posts and found that I donīt have a file called patch.exe in the C:\MinGV\bin directory.

Iīve reinstalled several times and checked that path name donīt have blank spaces but no results.

Whatīs the problem?.

Thanks in advance.

I got it. Now, the apply patch goes ok but when I press Go, it says "make: *** windows32_openpipe(): DuplicateHandle(In) failed (e=6)".

What is this?

Thanks again.

Hi, please, any help with this error? thanks.

[shaddow76]

Hi could anyone please help me?
I am currently using mame 0.141 but would really like to remove mame white box nag screens and add high screen saves I have found a detailed thread that gives instruction on compiling the official mame releases first with source updates and then a diff file produced by MKChamp to achieve this result.
Http://forum.arcadecontrols.com/index.php?topic=64298.0
The thread also gives details on Mr Do's guide on compiling
see
http://mrdo.mameworld.info/compile.html
(This link states that it will only compile mame starting at version 0.1465u)
I have attempted to compile updates & MKChamps diff file using both official mame releases 0.141 & 0.146
I seem to apply source updates and MKChamps diff file successfully to 0.146 but do not get a new mame. exe in mamescr file as the instructions suggest? When compiling 0.141 I can apply source updates but get an error message when compiling MKChamps diff file.
Could anyone please help me?
I would prefer to compile mame 0.141 so I don't need to change the mame currently working in my project but would change to remove nag screens
Sorry for the long post and if im behind the times only just found this thread

Shaddow76

[syncmaster]

Hello there
Please
I used to compile MAMEplus fine with older version but now MC 1.3 seems to skip the "console" part of MAMEplus 0.148 (sms,nes, pce...)
Anybody to confirm these?
Thank you

[Harakiri]

Mame compiler is outputting this error message though everything seems to be correctly set-up.



I also need to know if mameUI "SRC" folder replaces the current or updates it's content?

Thanks in advance!

*EDIT: Nevermind this cry for help. I decided to compile the program following Mr. Do's tutorial. It's actually easier than setting up mame compiler. The only aspect that should be regarded is the arguments explained in detail here >http://www.hyperspin-fe.com/forum/showthread.php?15103-Simple-Mame-Compiling-Handbook.

Go ahead and give it a try, you won't regret it!

[PiriPT]

Well i have a question and i hope someone can help me out.

I performed the compilation and evertyhing went well, without errors, and the executable is created.

But what are now the next steps? I copied the new executable into my original mame directory but i get an error: "missing libstdc++-6 file" I also tried to copy the missing file from the minGW folder, this eliminated the screen with the error of the missing file, but now the application crashes directly. Hope you can help me out

[LeedsFan]

Hi, Iīm trying to compile mame version 1.47.

Iīve installed everything I think I need (mingw-get-inst-20120426.exe, MC64setup.exe and the hi_147.diff file).

When I press the Apply Patch or the Go buttom, the compiler says "The system cannot find the specified path". I,ve read the previous posts and found that I donīt have a file called patch.exe in the C:\MinGV\bin directory.

Iīve reinstalled several times and checked that path name donīt have blank spaces but no results.

Whatīs the problem?.

Thanks in advance.

I got it. Now, the apply patch goes ok but when I press Go, it says "make: *** windows32_openpipe(): DuplicateHandle(In) failed (e=6)".

What is this?

Thanks again.

Hi, please, any help with this error? thanks.

I'm having this exact same error. The patch goes fine.

But clicking GO! gives the same error you are getting: "make: *** windows32_openpipe(): DuplicateHandle(In) failed (e=6)".

Hoe do we solve this please?