MAME Compiler 64 v2.0.197

[Huggybaby]

I'll try again after some sleep, but the folder that's supposed to contain the finished exe didn't pop up after compiling, and there is no mame.exe:

Deleting Object Folder...
Compiling Mame...
Using Parameters OSD=winui TARGETOS=win32 -j5 ARCHOPTS=-march=native PTR64=1 -f MameUI.mak
MameUI.mak:40: warning: overriding commands for target `mameui64.exe'
makefile:542: warning: ignoring old commands for target `mameui64.exe'
mkdir.exe -p obj/winui/mame
.
.
.
Compiling src/osd/windows/strconv.c...
.
.
.
cc1.exe: warnings being treated as errors
src/osd/winui/columnedit.c: In function 'DoExchangeItem':
src/osd/winui/columnedit.c:60: error: value computed is not used
src/osd/winui/columnedit.c:62: error: value computed is not used
src/osd/winui/columnedit.c: In function 'DoMoveItem':
src/osd/winui/columnedit.c:95: error: value computed is not used
src/osd/winui/columnedit.c:97: error: value computed is not used
src/osd/winui/columnedit.c: In function 'InternalColumnDialogProc':
src/osd/winui/columnedit.c:180: error: value computed is not used
src/osd/winui/columnedit.c:186: error: value computed is not used
src/osd/winui/columnedit.c:411: error: value computed is not used
src/osd/winui/columnedit.c:421: error: value computed is not used
make: *** [obj/winui/mame/osd/winui/columnedit.o] Error 1
make: *** Waiting for unfinished jobs....
cc1.exe: warnings being treated as errors
src/osd/winui/directories.c: In function 'UpdateDirectoryList':
src/osd/winui/directories.c:220: error: value computed is not used
src/osd/winui/directories.c:231: error: value computed is not used
src/osd/winui/directories.c:235: error: value computed is not used
src/osd/winui/directories.c:241: error: value computed is not used
src/osd/winui/directories.c: In function 'Directories_OnInitDialog':
src/osd/winui/directories.c:305: error: value computed is not used
make: *** [obj/winui/mame/osd/winui/directories.o] Error 1
Finished!
0 Hours 3 Minutes and 13 Seconds Elapsed.

[headkaze]

It compiled fine for me. I would delete your Mame source and try again from the beginning.

[Huggybaby]

OK, MameUI 136.2 works fine, it's MameUI 136 that doesn't. Which makes sense, because the new tools only work with 136.1+. I had forgotten about that. Thanks for the update headkaze, and sorry for the confusion. 

[u_rebelscum]

Hmm, a little OT and just for curiosity, has anyone compared a ms 64 compiled mame vs a gcc 64 bit compiled mame?  I don't have a 64 bit OS to test on, yet.  And headkaze implied that the MS c compiler still works on 0.136.1+....

[Huggybaby]

Not that I've heard. It would be cool if headkaze's compiler would let you choose, then we could really get down to some A/B comparisons.

[u_rebelscum]

Agree. 

FWIW, I looked over at mameworld, and one of the bigger MameDev said that gcc 64 bit is "significantly faster" than MS compiler.  surprised but good to hear. 

But I'd like some hard numbers, dang it.   ...    ... 

[gargoyle67]

Is there anyway to download an older Mame Compiler 64 as I've done a search and can't seem to find one. I'm trying to compile an old mame 129 for someone and the new version won't do it 

[headkaze]

Is there anyway to download an older Mame Compiler 64 as I've done a search and can't seem to find one. I'm trying to compile an old mame 129 for someone and the new version won't do it 

You can Download Mame Compiler 64 1.17 from here 

[Necro]

Anyone know if the following (64-bit processor is checked):
Using Parameters OSD=windows TARGETOS=win32 -j3 ARCHOPTS=-march=athlon64 PTR64=1

I know the PTR64 SHOULD make a 64-bit native binary, but the TARGETOS thing is what's throwing me off.  I'm using Win7 x64 and just want to be sure that win32 is appropriate.

Thanks!

[gargoyle67]

Thank you headkaze 

[Huggybaby]

Anyone know if the following (64-bit processor is checked):
Using Parameters OSD=windows TARGETOS=win32 -j3 ARCHOPTS=-march=athlon64 PTR64=1

I know the PTR64 SHOULD make a 64-bit native binary, but the TARGETOS thing is what's throwing me off.  I'm using Win7 x64 and just want to be sure that win32 is appropriate.

Thanks!

I wondered that too.

[headkaze]

win32 is used for both 32 and 64-bit compiles so with PTR64=1 you should get a binary called Mame64.exe. Yes it's 64-bit and you can check it by downloading Process Explorer, run it and select View->Select Columns->Process Image tab and put a tick next to "Image Type (64 vs 32-bit)" and it will add a column showing you which processes are running 32 or 64-bit. Run Mame and it should show up as 64-bit.

Just a note with the latest MC64 version you should be able to select "Auto Detect" for optimize and it uses a new GCC option that will detect your CPU and compile for it. So it really shouldn't be necessary to select the CPU you want unless you're compiling for a CPU other than the one you're using.

[Huggybaby]

Headkaze, any chance of adding a MS/GCC compile option? If it's a lot of work forget it of course.

[Necro]

Thanks Headkaze.  I'm compiling on my main PC (4 core, much faster, no idea if it matters for the compiler) instead of my cab. 

Oddly...I didn't get a mame64.exe out of that...just a mame.exe.  I'll have to confirm that it's proper   In Win7 it should also just have a *32 next to it in the Task Manager I believe if it's not 64-bit.

[Harakiri]

Hello everyone! Long time no see, he he!


I have no skills whatsoever compiling MAME, but i wanted to compile my own MameUI version to get rid of legal warnings and other nag screens. I am confused because i dunno how to setup the mameui source files inside MingW folders and i can't find the updated High-score diff regarding the latest version of mame.

I would be extremely thankful if someone could give me some hints regarding this matter or link me to a compiled version of MameUI without the nag screens.


Thank you all in advance!

<edit>

I followed the instructions provided on the site with no exception whatsoever and by the time i hit "apply patch" or "GO!" i get the following error screens:





</edit>


Help...  :'(

[headkaze]

It looks like you haven't followed the instructions because it can't find those files. The instruction are for an older version of Mame so you understand you have to download the latest ones? The instructions are just a guide.

For MameUI 0136u3 follow these instructions.

1. Create a folder C:\MinGW\source\MameUI0136u3
2. Download the hiscore hi_136u2.txt from here and copy it into the C:\MinGW\patches (you can rename it to hi_136u2.diff if you like but it doesn't matter)
3. Download the mame0136s.zip from here and extract to C:\MinGW\source\MameUI0136u3
4. Download the updates from here (0136u1_diff, 0136u2_diff and 0136u3_diff) and extract them to C:\MinGW\patches
5. Download MameUI source from here extract somewhere then copy the winui folder to C:\MinGW\source\MameUI0136u3\src\osd and copy the MameUI.mak to C:\MinGW\source\MameUI0136u3
6. Apply the official Mame patches 0136u1_diff, 0136u2_diff then 0136u3_diff. Apply them by browsing to each one selecting it from the file browser then selecting "Apply Patch"
7. Now apply the Hiscore patch you downloaded from step 2 (Eg. hi_136u2.diff or hi_136u2.txt depending on how you saved it)
8. Set your "Mame Source Folder" to C:\MinGW\source\MameUI0136u3 and check you have MameUI Compile Option ticked
9. Click GO! to compile.

NOTE: To compile "vanilla" Mame skip the MameUI related steps or just take the tick off "MameUI" as you can still compile standard Mame aswell.

[Harakiri]

Thanks for the reply Head!


That was "exactly" what i did, i'm so confused as you probably are...

I'm running windows 7 using admin privileges, does that make any difference?

 
I'm deeply sorry for my lack of attention on this one.

I did mess around with the MinGW instalation and scrambled things up. I did a fresh install of Mame Compiler and it runs like a champ!

I'm very sorry for taking your time... 

[iAtoria]

Headkaze amazing contribution!  I used to do compiling manually, but this saved me the trouble of trying to find a mistyped "p" or misplaced "2".

I do have a question:
I know the 64-bit option increases performance, but are the dual-core and quad-core options simply for compiling speed or does it actually effect the performance?  If so, is the quad-core setting sufficient for a core i7?

[headkaze]

Headkaze amazing contribution!  I used to do compiling manually, but this saved me the trouble of trying to find a mistyped "p" or misplaced "2".

I do have a question:
I know the 64-bit option increases performance, but are the dual-core and quad-core options simply for compiling speed or does it actually effect the performance?  If so, is the quad-core setting sufficient for a core i7?

The Dual Core and Quad Core are really just how many threads it spawns during the compile process so all it does is make compiling faster.

[iAtoria]

Worked like a charm for the 136 compile, but gave me issues with 135 and below.  Is the reason because of the the updated mingw binaries?

[Huggybaby]

Yes, it only works with 136u1 and up.

[iAtoria]

Headkaze, last time I'm going to bother you.  Can you make a version available (I guess 1.17) that is compatible with the older builds.  I don't need crazy old builds like .77 or .99, but I probably need the latest stable build.  The only reason I ask is because .136 has issues with some of my favorites (xmen and simpsons).  I looked on your site but I couldn't find it.  If you could make this happen I will hump your leg up and down the street.

[headkaze]

I need to put this in a more prominate place but you can download MC64 1.17 from here. LOL @ humping my leg.. well comon then, start the humping 

[brian_hoffman]

If you could make this happen I will hump your leg up and down the street.

LOL

[iAtoria]

 
^--This is the closest thing to a hump emote thanks headkaze

[smalltownguy]

After a few unsuccessful attempts, I was able to successfully compile a 64 bit version of Mame version 128. Where I went wrong was I was trying to apply diffs to the Mame0128s.zip file source before compiling. It took me a while to realize that because I was downloading the source files from a previous version of Mame, I didn't need to worry about applying any of the intermediate diffs -- the previous versions are already up to date with updates included.

Once I tried putting the 128 source in the MinGW/source folder, applied JUST the hiscore diff, I was able to compile correctly. Then I renamed the 'vmame.exe' file to 'mame.exe' and dropped it into my mame folder, overwriting the 32 bit exe. I also copied and overwrote the other .exe files too.

Headkaze, thanks for pointing me to the "Process Explorer" program. Very cool utility, and made it very easy to verify that my mame.exe was in fact running in 64 bit.

[Haterot]

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.

HK I am getting this error too. Was there something specific you did to correct this?

[headkaze]

Okay managed to get the 32-bit version compiling by doing the following..

1. Download png2bdc.zip and extract png2bdc.exe to Mamexxxx\obj\windows\mame\build
2. Open Mamexxxx\src\build\build.mak and edit the following (Add '#' to the beginning of the last line shown below)

Code: [Select]

#-------------------------------------------------
# png2bdc
#-------------------------------------------------

PNG2BDCOBJS = \
$(BUILDOBJ)/png2bdc.o \

$(PNG2BDC): $(PNG2BDCOBJS) $(LIBUTIL) $(LIBOCORE) $(ZLIB)
@echo Linking $@...
# $(LD) $(LDFLAGS) $^ $(LIBS) -o $@

[Haterot]

Once again HK, thanks. Worked like a charm first go through.

[Harakiri]

I managed to compile MAMEUI32 successfully with the latest diff (Mame0136u4). I load about 3 or 4 games with no problems very "smoothly", but then MAME crashes randomly. Is anyone else experiencing this problem as well? Is there a way to overcome this annoyance and make MAME to run flawlessly?

Thanks for your attention in advance!

*UPDATE*

Compiled and tested MAME command-line version and it doesn't crash. Either MAMEUI or compiler bugs/errors.

[dasfool]

I attempted to compile mame136u4 tonight on windows xp pro 32 bit.  I was getting the png2bdc error so I followed the directions posted above.

copying png2bdc.exe to folder specified and commenting out the line suggested gives the error below:

Code: [Select]

process_begin: CreateProcess(C:\MinGW\source\Mame136u4\obj\windows\mame\build\png2bdc.exe, obj/windows/mame/build/png2bdc.exe src/emu/uismall.png obj/windows/mame/temp.bdc, ...) failed.
just commenting out the line suggested gives this error:

Code: [Select]

process_begin: CreateProcess(NULL, obj/windows/mame/build/png2bdc.exe src/emu/uismall.png obj/windows/mame/temp.bdc, ...) failed.
Converting src/mame/layout/spacewin.lay...
make (e=2): The system cannot find the file specified.

[headkaze]

Harakiri can you run MameUI and go into Options->Default Game Options->Debug tab. Put a tick next to "Output log to Logfile" and "Output diagnostic information" run the game until it crashes then post the error.log file it generates. It might help track down the problem.

dasfool: Try copying the file over again and then compiling again. You could also try copying the attached temp.bdc to obj/windows/mame and see if it will continue past that point.

[Harakiri]

I did what you said, let the program crash twice and got this message in the error.log file:

Physical width 1920, height 1080

Nothing more. I find it strange if it is a resolution conflict because command line version doesn't have the same behaviour.

[headkaze]

I did what you said, let the program crash twice and got this message in the error.log file:

Physical width 1920, height 1080

Nothing more. I find it strange if it is a resolution conflict because command line version doesn't have the same behaviour.

You will find that it writes that even if it doesn't crash so it really tells us nothing. It's annoying because I tried the command line option -verbose on MameUI and it doesn't output anything. With command line Mame you can get all sorts of debug information output to the command line using "-verbose". If we can figure out a way to get verbose output into the log file for MameUI we might get some more useful information. BTW Can you do a snapshot of the Windows crash dialog?

[Harakiri]

I get this:



Contents:

Problem signature:
  Problem Event Name:   APPCRASH
  Application Name:   mameui32.exe
  Application Version:   0.136.4.0
  Application Timestamp:   4b90ce82
  Fault Module Name:   mameui32.exe
  Fault Module Version:   0.136.4.0
  Fault Module Timestamp:   4b90ce82
  Exception Code:   c0000005
  Exception Offset:   011b81e0
  OS Version:   6.1.7600.2.0.0.256.1
  Locale ID:   2070

...

I'm too much of a newbie not to understand the "additional information" values, so i decided to conceal that information as a matter of safety. My apologies.

[headkaze]

I think you may need to report this to the MameUI developers. They will probably know how to get more info about what is happening too.

[Huggybaby]

Does the mingw folder no longer contain a source directory? It used to have one with Mame0128 in it, now it needs to be created manually I think.

[200X]

I got one error

make *** [......blah..blah.../drivers/snesb.o] Error 1

But then it finished. So is that bad?

[200X]

I got one error

make *** [......blah..blah.../drivers/snesb.o] Error 1

But then it finished. So is that bad?

OK, Started over again and the same thing happened but it was a different file this time: uismall.fh

What's the problem?

[dasfool]

I tried again, copying the png2bdc to the proper directory and commenting out the line of code, and got the same error as last time.  I tried copying png2bdc, commenting out the line, and copying over temp.bdc and got the same error.  Isn't temp.bdc just a temporary file that get's overwritten multiple times?  If so, it is probably getting overwritten beforehand.

Here's the error again windows xp pro x86, Intel Core i3 CPU (dual core with hyperthreading):

Code: [Select]

process_begin: CreateProcess(C:\MinGW\source\Mame136u4\obj\windows\mame\build\png2bdc.exe, obj/windows/mame/build/png2bdc.exe src/emu/uismall.png obj/windows/mame/temp.bdc, ...) failed.
Is it possible that uismall.png is corrupt in the archive or something?

Edit: uismall.png seems to open fine in windows.  Looks like a character map.