[APP] MAME Compiler 64 v2.0.165

[Visitor Q]

I still to this day have not had any luck with compiling the 64 bit version correctly even though when I do the 32 bit version I have zero problemsâ?¦ I must be the only one.

[lalandev]

I still to this day have not had any luck with compiling the 64 bit version correctly even though when I do the 32 bit version I have zero problems… I must be the only one.

On my Vista x64 box, I had a few issues compiling the x64 version. I can't explain why, but after a couple minutes of troubleshooting, I've installed .NET Framework 2.0 Service Pack 1 and for me, it solved the problem.

But as Head explains in the tutorial, you still have a few "99 errors" at the beginning. But after a few "GO" clicks, it goes away and compile properly.

http://www.microsoft.com/downloads/details...0e-4cd851c5fcc4

Good luck!

[lalandev]

Someone succeded compiling 127.u6 x64? On my side, it crashes after 2 minutes with this error:

c:\mingw\source\mame0127s\src\emu\machine\ldcore.c(911) : error C2220: warning treated as error - no 'object' file generated

c:\mingw\source\mame0127s\src\emu\machine\ldcore.c(911) : warning C4701: potentially uninitialized local variable 'vbidata' used

mingw32-make: *** [obj/winui/vmame/emu/machine/ldcore.o] Error 2

BTW, I use Head's tool since 3-4 months and I never had any problems before...

Maybe something changed and the compiler can't compile this release? (stupid assumption, I know, but hey, I'm no programmer!(

[headkaze]

lalandev: Yes it looks like they have broken the compiling in MC64 (again). I've uploaded a new version, so install it over the top, and turn on "Disable Warnings as Error" and try again, it should compile okay.

[lalandev]

lalandev: Yes it looks like they have broken the compiling in MC64 (again). I've uploaded a new version, so install it over the top, and turn on "Disable Warnings as Error" and try again, it should compile okay.

I've just installed the 1.17 version and ticked the "Disable Warnings ar Error" box. Everything is now compiling properly. Thx for the quick intervention!

[jeffremiller]

I just attempted an compile of 128 with the hiscore patch. It compiled along for about 4 minutes and then errored out.

The error was related to osd_update_hi being redefined. in the windows/video.c

I looked at the file and found a subroutine called osd_update_hi and removed it from the file.

All compiled fine after that.

Will I miss this snippet of code? Did I fix my problem or just mask it?

[headkaze]

I don't know but I just tried compiling 128 both 32 and 64 bit versions with the hiscore patch and there was no error message. I would probably delete your source folder and try again.

[jeffremiller]

That worked... weird.

I don't know but I just tried compiling 128 both 32 and 64 bit versions with the hiscore patch and there was no error message. I would probably delete your source folder and try again.

[Visitor Q]

headkaze,

When installing new versions of the program does the old version need to be uninstalled first?

Thanks.

[bkenobi]

wrong thread...sorry

[Visitor Q]

No. Be aware that if you have a customized CP with the same name as the one that comes with CPWizard, it will be copied over. You should either make the file read-only or rename it to mame-VisitorQ.xml or something like that.

This has to do with the compiler?

[Visitor Q]

I still to this day have not had any luck with compiling the 64 bit version correctly even though when I do the 32 bit version I have zero problemsâ?¦ I must be the only one.

Looks like with the new build and new version of mame things are looking up, seems to be working with my newly compiled 64 bit version!

[Visitor Q]

Is it normal for a 64 bit compliled version to compile in half the amount of time as a 32 bit? Seems to be the case for me, just what to make sure this is of the norm.

[lalandev]

Is it normal for a 64 bit compliled version to compile in half the amount of time as a 32 bit? Seems to be the case for me, just what to make sure this is of the norm.

Hmm, I've never really timed the compiling time.

But I'll check next time.

Quick question for HeadKaze: When I optimize my mame64 build for Core 2 Duo, Dual-Core and/or Quad-Core, what is happening in the background? Is it really faster with theses processors/cores? Is it about SSE3?

[headkaze]

When compiling the 64-bit version your actually using a different compiler than when you compile 32 bit.

The Dual Core and Quad Core options only make compiling faster by running the compiler in multiple threads. They are -j3 and -j5 options for mingw32-make respectively which just mean run the compiler on 3 or 5 threads. So they don't actually optimize the compiled binary.

[lalandev]

When compiling the 64-bit version your actually using a different compiler than when you compile 32 bit.

The Dual Core and Quad Core options only make compiling faster by running the compiler in multiple threads. They are -j3 and -j5 options for mingw32-make respectively which just mean run the compiler on 3 or 5 threads. So they don't actually optimize the compiled binary.

Thx! I was naively thinking that the optimize options were making the compiled binary running the games faster!

[Visitor Q]

Thx! I was naively thinking that the optimize options were making the compiled binary running the games faster!

Me too.

So the 64 bit option compiles Mame64 but the dual core option makes it compile faster?

[headkaze]

Sorry I didn't understand your entire question. The combo box underneath the "Optimize for:" label *does* optimize the binary. The two checkboxes "Dual Core" and "Quad Core" only make compiling faster.

The "Intel Core2" option uses the "ARCHOPTS=-msse3" option which uses the SSE3 instruction set.

[Visitor Q]

So if I have a dual core (which I do), I should always check the dual core box whether I am compiling for 32 or 64 bit Mame? With that box check, it will compile Mame faster, using my dual core processor to do so.

Dropping the box down and selecting Intel Core2 will optimize Mame more for my dual core processor, not the compiler but Mame it's self.

Did I get that right?

[headkaze]

Did I get that right?

Yes

[Visitor Q]

Thanks!

One last thing and sorry to go round and round with this but I jsut want to make sure I am 100% on it.

"64-bit processor" when checked compiles a 64 bit version of mame, correct?

"dual core" when checked compiles mame faster using my dual core processor but has no effect on the version it's shelf that I am compiling of mame, correct?

"Optimize for IntelCore2" compiles mame in a way that does effect the outputed version of mame and in turn will be a better version to run and play on my dual core system, correct?

In other words.

"64-bit processor"compiles mame64

"dual core" compiles mame faster but does not create a mame 64 bit version unless "64-bit processor" is checked.

"Optimize for IntelCore2" selected when "64-bit processor" is checked to compile the best mame "64 bit" version of mame for my setup, Intel Core 2 Duo E8500.

[bkenobi]

I need to compile an older version of MAME (0.104u6) to get my guns working. I am able to apply patches and edit the code manually to get what I want, but when I try to compile I get an error. I'm assuming this is due to different MinGW versions, but I don't know.

Does anyone have a suggestion?

Deleting Object Folder...
Compiling Mame...
Using Parameters  ARCHOPTS=-march=athlon-xp
...
cc1.exe: error: unrecognized command line option "-Wno-unused-functions"
mingw32-make: *** [obj/mame/artwork.o] Error 1
Finished!
0 Hours 0 Minutes and 2 Seconds Elapsed.

After playing around for a few more minutes, I found that if I set "Disable Warnings as Errors" I can get farther, but it still crashes. Here's the much longer error...

Deleting Object Folder...
Compiling Mame...
* snip for readablility *

[bkenobi]

Ok, so I think I've figured out why I'm getting an error. I'm trying to compile an older version of MAME that was designed to be compiled with a different version of MinGW etc. I found a discussion of what's required to compile an older version of MAME on the MAME compiling board at MAMEworld, but the files are all dead links.

Link

It sounds like I need this:

Does anyone have these files backed up somewhere that they could post or email to me? Thanks

[bkenobi]

Ok, I guess I may have posted a fraction of a second too soon. I found on logiqx site a guide and files for compiling MAME 104u4. I'm going to give it a try this evening, but I'm assuming all should work fine. It won't be as clean as using HK's tool, but if it works, it works!

Link

[headkaze]

Sorry I didn't get back to you earlier BK

Mame Compiler has been tested with Mame 0105 with "Disable Warnings as Errors" option enabled and it compiled successfully. I think that's the earliest version I tested.