MAME Compiler 64 v2.0.197

[headkaze]

You need to download mingw-mame-20121207.exe

Please read the instructions here

[Yoeddy1]

Just compiled with MAME 0.149 x64.  Worked great!

Thanks,
Jason

[trickyd]

When you install MinGW do you have to run the setenv.bat, setup_pythhon.bat, and the setup_qt.bat files to work with MC64 1.3

[headkaze]

When you install MinGW do you have to run the setenv.bat, setup_pythhon.bat, and the setup_qt.bat files to work with MC64 1.3

No it does it internally.

[trickyd]

Fantastic! No warnings or errors. Thanks very much

Can you compile UME with it


Many Many Thanks!

[headkaze]

Fantastic! No warnings or errors. Thanks very much

Can you compile UME with it

Yes. Check the Target tab.

[Yoeddy1]

Just compiled with MAME 0.151 x64.  Worked great!

Thanks,
Jason

[CWorley]

I'm trying to compile Mame0145.  The 3 patches and hi score patch apply fine.  Then 5 seconds after I click "go", I get this error:

Compiling src/osd/windows/vconv.c...
Linking obj/windows/build/vconv.exe...
c:/arcade/mingw/mingw64-w32/bin/../lib/gcc/i686-w64-mingw32/4.6.3/../../../../i686-w64-mingw32/bin/ld.exe: cannot find -lunicows
Finished!
0 Hours 0 Minutes and 5 Seconds Elapsed.
collect2: ld returned 1 exit status
make: *** [obj/windows/build/vconv.exe] Error 1

Any help would be appreciated.  Thanks!

[trickyd]

Fantastic app ;)ever think of including hbmame

[trickyd]

I'm trying to compile Mame0145.  The 3 patches and hi score patch apply fine.  Then 5 seconds after I click "go", I get this error:

Compiling src/osd/windows/vconv.c...
Linking obj/windows/build/vconv.exe...
c:/arcade/mingw/mingw64-w32/bin/../lib/gcc/i686-w64-mingw32/4.6.3/../../../../i686-w64-mingw32/bin/ld.exe: cannot find -lunicows
Finished!
0 Hours 0 Minutes and 5 Seconds Elapsed.
collect2: ld returned 1 exit status
make: *** [obj/windows/build/vconv.exe] Error 1

Any help would be appreciated.  Thanks!

I believe you have to use the mingw for that build which is mingw-mame-20110519.exe
http://www.mamedev.org/tools/previous-20110519.html

[juggle50]

Can anybody tell me why I'm getting this error?  Thank you so much.

[trickyd]

With all the changes lately I'm sure when 153 comes out most of the bugs will be worked out. But I've been able to compile regular mame, but when I try to add ui it doesn't do anything but set parameters. Was able to compile ui from command so it must be in MC64.

[Jumpstile]

I have the same exact problem. .net Framework 4.5.1 issue perhaps? This worked fine when I was compiling .152 in December...

 - J*

[headkaze]

Mame Compiler v1.3.1 Released
- Added fix for output in MameUI 0153+ and FASTDEBUG option

[Jumpstile]

headkaze, you are awesome. It works perfectly. Thank you so much for an excellent piece of software!!

 - J*

[trickyd]

Thanks for the update.

[Mordwaffe]

hmmmm... What am i doing wrong?

C:\MinGW (Checked the Dir is there)

C:\MinGW\source\mame153 (check the source is there, downloaded directly from the mame website)

C:\MinGW\patches\hi_153.diff (Freshly downloaded)


I get the following applying the DIFF:

Code: [Select]

Applying Diff Patch...
Error Applying Patch.
PatchDiff(): The system cannot find the file specified

EDIT: for some reason the patch.exe was not in my bin dir. Retrying...

EDIT 2: ok That wasn't it. Still getting the error.

EDIT 3: Got it, I needed the MAME specific MinGW in your link, I just googled and got the one from sourceforge 

[Brian B]

Sorry for the Noob (dumb) question, but why would I want to compile my own version of MAME?  What are the benefits?

Thanks in advance, or, if you can point me to a thread/page where this has been explained...

B.

[Nuexzz]

guys leave here I attached my error. Is this normal?

[Yarb]

Thanks Headkaze,

I always thought compiling MAME would be difficult but with your tool it went smooth as silk!!!

[withalligators]

Trying to compile a 64 bit version of 153 and followed the instructions here but am getting an error right at the outset.

I created a C:\MinGW folder and downloaded the file and extracted to that directory
I created a folder C:\MinGW\source and then a subfolder \Mame0153
I downloaded the 153 .txt file from the Hiscore diff thread
I created a C:\MinGW\patch folder and placed the hi_153.txt file there
I downloaded the mame153s.zip file from here
I extracted mame153s.zip to C:\MinGW\Source\Mame0153 the first subdirectory is "mame" and everything is inside that
153 has no updates yet so I didn't download any
I don't want MameUI as I'm going to use Hyperspin so I didn't download it
I opened Mame Compiler 64 and confirmed C:\MinGW was my MinGW folder, set C:\MinGW\source\Mame0153 as my Mame Source Folder, and set C:\MinGW\patches\hi_153.txt as the patch.
In the General tab, I confirmed that I had a 64 bit processor, confirmed I had a quad -core CPU, and left No Warnings as Errors checked. 
In the Target tab, I changed OSD from Windows to WinUI
I can apply the patch, and get no errors, this also creates an src folder in C:\MinGW\source that has an emu folder inside it.

When I try to compile Mame, I get an instant error:
makefile 793: src/osd/winui/winui.mak: No such file or directory
make: ***No rule to make target 'src/osd/winui/winui.mak'. Stop.

If I go into the target tab and change winUI to Windows, I get a different error, sometimes a few seconds in, sometimes more than a minute in, that is a lot of letters and numbers.  Any ideas?

NEVERMIND- solved while typing this out.  I had to change the Target OSD in the General Tab from Auto-Detect to none.  I'm on an i5 4670K

hope my solution helps somebody.

Cheers,
Alex

[Gatsu]

Trying to compile a version of .149 command line mame without the nag screens. It goes for about 45 minutes, then I get the following errors. Not sure what else to do.

Does anyone have a version of .149 command line mame already compiled and is willing to share?

[trickyd]

Now that there is new tools, is there going to be an update for MC64

[headkaze]

Now that there is new tools, is there going to be an update for MC64

MC64 will only need an update if the compile fails but I haven't had a chance to check it out yet. MinGW is a separate install from MC64 so you need to download and install it. Download and install mingw-mame-20140905.exe from http://www.mamedev.org/tools/

[trickyd]

Already tried it did get error but since old one still works will use it till I figuere out the new one. The error I got was for python. Earlier I inquired about setting the python,qt, and env bat files and you said it wasn't necessary that MC64 did it internally.

[smalltownguy]

Maybe I'm missing something, but how do I compile a 32 bit version of MAME using this program if I'm running the compiler on a 64bit system? Do I need to run the compiler on a 32 bit version of windows to get a 32 bit flavor of MAME?

EDIT: Never mind, I think I figured it out. I deleted the MinGW64 folder and it picked up the 32 bit info.

[EMDB]

Maybe I'm missing something, but how do I compile a 32 bit version of MAME using this program if I'm running the compiler on a 64bit system? Do I need to run the compiler on a 32 bit version of windows to get a 32 bit flavor of MAME?

EDIT: Never mind, I think I figured it out. I deleted the MinGW64 folder and it picked up the 32 bit info.

Setting the target to 32 bits should do the trick.

[B2K24]

Already tried it did get error but since old one still works will use it till I figuere out the new one. The error I got was for python. Earlier I inquired about setting the python,qt, and env bat files and you said it wasn't necessary that MC64 did it internally.

You need to run the setup bat files in \mingw\mingw64-w64 then you won't hit the errors anymore.

[fleskebacon]

Already tried it did get error but since old one still works will use it till I figuere out the new one. The error I got was for python. Earlier I inquired about setting the python,qt, and env bat files and you said it wasn't necessary that MC64 did it internally.

I get the exact same error. I ran all the setup files in the new mingw, doesn't change a thing. I get the same error when compiling from the command line, so it's probably not MC64's fault.

Going to try the old mingw, see what happens then.

[trickyd]

I always had good luck with MC64 so I'll just wait and see if it's updated before the next release.

[fleskebacon]

The old mingw works perfectly, both with command line and with MC64.
The new one fails in the same place both with command line and MC64.

Probably some problem with the new mingw, then.

[B2K24]

The old mingw works perfectly, both with command line and with MC64.
The new one fails in the same place both with command line and MC64.

Probably some problem with the new mingw, then.

Try manually moving mingw64-w32 (if compiling for 32-bit) or mingw64-w64 (if compiling 64-bit) into the location where you either downloaded or extracted the source. Run the Setup-bat files then compile should go fine.

[Hituro]

So every time I'm compiling I keep getting an error

make (e=2) The system cannot find the file specified
make *** [obj/windows/emu/cpu/h8/h8inc) Error 2

I've tried running several compilers and always get the same error.  I can see the h8 source files in the correct directory and everything else runs fine.  What am I doing wrong exactly?

[trickyd]

A few posts before http://forum.arcadecontrols.com/index.php/topic,71845.msg1462905.html#msg1462905 I had the same problem. Within the mingw64-w64 or mingw64-w32 folder are three bat files setenv, setup-Python and setup-Qt. These set up the paths within mingw. This particular error is with python.

[Hituro]

Yes I know the batch files your talking about. I ran all three. Is there something wrong with the Python one?  If so where should I be correcting the path?

[Hituro]

I am going to do what Fleskebacon did and try using an older version of MinGW.  I have checked the paths for Python, even manually entered the set path for it manually, but it just does not work.  I think there just might be a bug with this new MinGW.  I'm sure it will be fixed as it just came out earlier this month.  I cannot for the life of me see where the code is going awry but then again I'm not exactly a master at coding >.<

[Hituro]

So I was able to compile successfully with the previous version of MinGW. I'm pretty sure that there is something wrong with the newest MinGW and the coding for Python is probably the cause.

[B2K24]

Newest tools have always worked for me since they got added.

[fleskebacon]

Moved the new mingw to another folder, works perfectly.

It's probably getting errors when the path name is getting too long. I can see the python.exe is moved from the bin-folder to opt/bin. Might be just enough for the path name to get too long.

Moved it all down to \mamesrc\mingw-64 and everything's smooth. Thanks!

[Jollywest]

I'm having issues compiling MAME 0.155.

I've followed the instructions on the Headsoft website, (apart from the MameUI settings as I'm just want standard MAME), extracted all the necessary files to the correct paths and changed the path names in Mame Compiler to suit.
I've tried MinGW20121207 and MinGW20140905 but I can't get past the error shown in the attachments.
I'm using Windows 8.1 by the way, in case it matters.