The NEW Build Your Own Arcade Controls

Main => Software Forum => Topic started by: headkaze on September 29, 2007, 02:51:06 pm

Title: Mame Compiler 64 v2.0.197
Post by: headkaze on September 29, 2007, 02:51:06 pm
Mame Compiler 64 Homepage (http://www.headsoft.com.au/index.php?category=mame&page=mc64)

Note that v1.18 is for compiling MAME 0.136u1+. For earlier versions you must use v1.17. For instructions and downloads please visit the website above.
Title: Re: Mame Compiler v0.1 Released
Post by: MKChamp on September 30, 2007, 01:34:33 am
Nice little app. Hopefully, this will please the people that would have benefited from the *cough* binary *cough*.

I added the white box/decoding/decrypting/updating/etc. removal to the hicore diff. There's a new one posted as hi_119u2, it actually can be used in place of the hi_117u3 (for versions 117u3 - present) but was generated and only tested with 119u2.
Title: Re: Mame Compiler v0.1 Released
Post by: headkaze on September 30, 2007, 01:45:22 am
Nice little app. Hopefully, this will please the people that would have benefited from the *cough* binary *cough*.

I added the white box/decoding/decrypting/updating/etc. removal to the hicore diff. There's a new one posted as hi_119u2, it actually can be used in place of the hi_117u3 (for versions 117u3 - present) but was generated and only tested with 119u2.

The hi_119.diff included in the Mame Compiler archive had to get created manually. I tried applying hi_117u3.diff to 119 then adding the disclaimer skips manually. It produced a really strange diff file. So I went through modifying it manually using the hi_117u3.diff in a text editor. The resulting diff looked right this time (20 KB instead of 100 KB +).

I also had to add a -w switch to diff for removing whitespace. So the command I was using is

Code: [Select]
diff -w -r -c -N old src >hi_119.diff
Not sure why I had to add that switch while you didn't. Are you using the Unix version of diff or something?
Title: Re: Mame Compiler v0.1 Released
Post by: MKChamp on September 30, 2007, 02:00:18 am
The reason the diff that it created was so huge was because when a patch is applied to a version that had 'little' changes here and there from the version the diff was created from (117u3) what it does is create a "~" copy of the file it patched. So, then when you diff the new source, it sees new files (the ~ ones) and creates them in the diff. Since those files aren't called in the make file, they don't affect the compile.
Title: Re: Mame Compiler v0.1 Released
Post by: headkaze on September 30, 2007, 02:18:01 am
The reason the diff that it created was so huge was because when a patch is applied to a version that had 'little' changes here and there from the version the diff was created from (117u3) what it does is create a "~" copy of the file it patched. So, then when you diff the new source, it sees new files (the ~ ones) and creates them in the diff. Since those files aren't called in the make file, they don't affect the compile.

Ahhh okay, I getcha, mystery solved then!
Title: Re: Mame Compiler v0.2 Released
Post by: headkaze on October 01, 2007, 04:00:19 am
Minor update
Title: Re: Mame Compiler v0.2 Released
Post by: edge on October 01, 2007, 08:49:31 am
Thanks, headkaze, for the app.  Will try it out this week.
Title: Re: Mame Compiler v0.2 Released
Post by: Neilyboy on October 01, 2007, 09:30:00 am
very cool app headkaze!! this is very much appreciated.

Neil
Title: Re: Mame Compiler v0.2 Released
Post by: mcfreak on October 01, 2007, 10:14:19 am
Very nice.  :notworthy:
Title: Re: Mame Compiler v0.2 Released
Post by: MKChamp on October 01, 2007, 02:59:44 pm
Added a link to here from the hiscore diff thread. Not sure if you plan on this thread being the place to always grab the latest version of your app...
Let me know if it would be better to point the link somewhere else.
Title: Re: Mame Compiler v0.2 Released
Post by: Encryptor on October 01, 2007, 06:35:59 pm
When using the program should you do the 119u1 & 119u2 patches before or after applying the high diff no nag patch?


Encryptor
Title: Re: Mame Compiler v0.2 Released
Post by: loadman on October 01, 2007, 09:33:21 pm
 :notworthy:
Title: Re: Mame Compiler v0.2 Released
Post by: headkaze on October 02, 2007, 01:44:14 am
When using the program should you do the 119u1 & 119u2 patches before or after applying the high diff no nag patch?

Encryptor

1. Apply 119u1.diff
2. Apply 119u2.diff
3. Apply hi_119u2.diff
Title: Re: Mame Compiler v0.2 Released
Post by: headkaze on October 02, 2007, 01:50:31 am
Added a link to here from the hiscore diff thread. Not sure if you plan on this thread being the place to always grab the latest version of your app...
Let me know if it would be better to point the link somewhere else.

Cheers mate, yeah I will keep this thread for all future Mame Compiler releases.

Also gonzo90017 has made a tutorial in Spanish (http://marcianitos.org/foro/showthread.php?p=81977).
Title: Re: Mame Compiler v0.2 Released
Post by: Encryptor on October 02, 2007, 08:57:33 am

1. Apply 119u1.diff
2. Apply 119u2.diff
3. Apply hi_119u2.diff


Thank you!

Encryptor
Title: Re: Mame Compiler v0.2 Released
Post by: TheBrokentoken on October 03, 2007, 11:40:51 am
Great, great tool.  Many thanks for putting this together.

Is your site down right now?  I cannot get either of the files downloaded.  Thanks.
Title: Re: Mame Compiler v0.3 Released
Post by: headkaze on October 07, 2007, 10:28:10 am
Update to v0.3. This is to support compiling older versions of Mame (<0.118u5). It adds an option called "Disable WError" which will enable the newer version of GCC to compile older versions of Mame. You may get some warnings but compile should still finish. Any problems, post here.
Title: Re: Mame Compiler v0.3 Released
Post by: gonzo90017 on October 07, 2007, 02:14:31 pm
How old?
Title: Re: Mame Compiler v0.3 Released
Post by: headkaze on October 08, 2007, 01:59:05 am
How old?

I have no idea, but your welcome to try and compile an old version and report any problems here. I can't be sure the really old stuff will compile okay but I did try 109 and that worked with this new "Disable WError" option selected.
Title: Re: Mame Compiler v0.3 Released
Post by: headkaze on October 20, 2007, 08:00:38 pm
Heh there must a limit to how old you can edit posts. Anyways this release is for 0.120+ which has a make error.

Mame Compiler v0.4 Released

21-10-07 - Version 0.4 - Fixed make error for 0.120+
Title: Re: Mame Compiler v0.3 Released
Post by: TeutonicDarkness on October 23, 2007, 08:43:03 pm
Hello,

 Does this work with the newest version .120?

I did try but either I just don't know what I'm doing
( A very likely case )

or it just didn't work.


After compiling It did load Mame fine ...
However all the Roms issued error messages
and now Mame crashes as well.


My assumptions are using .120 and I only wanted the
High Score - No nag patch i would just apply..

hi_119u2.diff
then compile.


Is that correct?


Thanks in Advance....
Title: Re: Mame Compiler v0.3 Released
Post by: SGT on October 23, 2007, 09:29:51 pm
Did you click <APPLY PATCH> before clicking <GO> to compile?  It worked well for me when I tried it yesterday with .120.  How old are your roms (what version was working successfully)?

Kudos to headkaze. :applaud: :notworthy:
Title: Re: Mame Compiler v0.3 Released
Post by: TeutonicDarkness on October 23, 2007, 10:14:36 pm
Did you click <APPLY PATCH> before clicking <GO> to compile?  It worked well for me when I tried it yesterday with .120.  How old are your roms (what version was working successfully)?

Kudos to headkaze. :applaud: :notworthy:


 Honestly don't know how old roms are I attained them
from various sources on the net.

I have tested with 117 and 120 and roms work.

Yes I clicked apply patch ...just thought I was overlooking
something maybe?

Am I right though with only having to apply:
hi_119u2.diff .......


Thanks...
Title: Re: Mame Compiler v0.3 Released
Post by: SGT on October 24, 2007, 08:34:20 am
Quote
Am I right though with only having to apply:
hi_119u2.diff .......

That's all that I did.  Is it possible that you put the compiled executables into an existing folder where an older version resided?
Title: Re: Mame Compiler v0.3 Released
Post by: TeutonicDarkness on October 24, 2007, 07:09:22 pm
Quote
Am I right though with only having to apply:
hi_119u2.diff .......

That's all that I did.  Is it possible that you put the compiled executables into an existing folder where an older version resided?

No Definitely not...
I Put them in a New folder called:
 Mame120_No_Nag

I'm going to keep messing around ...
I don't know what I could have done wrong
but something is obviously going wrong here.

Thanks for clearing that up..
Title: Re: Mame Compiler v0.3 Released
Post by: Lakersfan on October 27, 2007, 01:46:12 pm
Thanks for this app! It was fun compiling manually, but this sure makes things easier and quicker.  :cheers:

TeutonicDarkness: Is it possible you accidently applied the hi diff prior to the u update? EDIT - reread your post, nevermind this question...

My question: what is the Clean Compile option and should I be using it?

Thanks guys,
LF
Title: Re: Mame Compiler v0.3 Released
Post by: headkaze on October 27, 2007, 07:47:28 pm
Thanks for this app! It was fun compiling manually, but this sure makes things easier and quicker.  :cheers:

TeutonicDarkness: Is it possible you accidently applied the hi diff prior to the u update? EDIT - reread your post, nevermind this question...

My question: what is the Clean Compile option and should I be using it?

Thanks guys,
LF

Generally you don't need to use the Clean Compile option. All it does is delete the obj folder so it will do a fresh compile. If you start compiling Mame and hit stop mid way then click start again it takes off where it left off and compiles the remaining souce. Clean Compile makes it start from the beginning again.
Title: Re: Mame Compiler v0.3 Released
Post by: Lakersfan on October 28, 2007, 01:31:05 pm
Thanks for the reply, headkaze. I used it for a compile of .120 and it worked perfectly!  :woot
Title: Re: Mame Compiler v0.3 Released
Post by: topher0002 on December 04, 2007, 06:06:27 pm
Great tool,  I really wish i could get it to work for 116 though, all my roms are 116 and i have everything set up the way I want it except the nag screens.   I can recompile other version but this version gets almost to the end and give me an error about N64.O 

Ive researched and cannot find anything, ive spend well over 2 hours trying to find the answer and couldnt,  so i apologize if its somewhere easy i  just missed.

Im applying updates in correct order and each one is successful,  i am using the correct TXT file i believe of 114,115,116.   

Any ideas anyone?
Title: Re: Mame Compiler v0.3 Released
Post by: headkaze on December 04, 2007, 11:23:53 pm
Mame Compiler v0.5 Released

- Added support for compiling Mame 116.

Here's what you need to do

1. Download the new version of Mame Compiler and install it
2. Run Mame Compiler
3. Point your "Mame Souce Folder" to your Mame 116 source
4. Browse to the hi_116u4.diff patch file and click the "Apply Patch" button
5. Put a tick next to the "Disable WError (<0.118u5) option and any other optimization options you want
6. Click "GO!"

I tested Mame Compier v0.5 with Mame 116 and it works ok.
Title: Re: Mame Compiler v0.5 Released
Post by: rooter on December 13, 2007, 03:55:10 pm
Any chance this works with the 64bit version of Mame?  If not, will it in the future?
Title: Re: Mame Compiler v0.5 Released
Post by: headkaze on December 13, 2007, 05:57:34 pm
Any chance this works with the 64bit version of Mame?  If not, will it in the future?

Not until there is a 64 bit version of the GCC compiler. Right now the only way to compile the 64-bit versions is with the command line compiler included with the Microsoft Platform SDK and a recent version of the DirectX SDK. I'll take a look at adding support for it one day, but people will have to download those tools separately in any case and it kinda defeats the purpose of what Mame Compiler was trying to achive which is an all in one tool for compiling Mame.
Title: Re: Mame Compiler v0.5 Released
Post by: bent98 on December 13, 2007, 06:39:47 pm
I just tried it with mame .121 with 121u4.diff.

patched then hit go.

Got hunk errors on patch and got these errors after pressing GO

Compiling src/mame/drivers/starwars.c...
Compiling src/mame/machine/starwars.c...
src/mame/machine/starwars.c:208:47: error: macro "timer_alloc" passed 2 arguments, but takes just 1
src/mame/machine/starwars.c: In function 'starwars_mproc_init':
src/mame/machine/starwars.c:208: error: 'timer_alloc' undeclared (first use in this function)
src/mame/machine/starwars.c:208: error: (Each undeclared identifier is reported only once
Finished!
0 Hours 1 Minutes and 29 Seconds Elapsed.
src/mame/machine/starwars.c:208: error: for each function it appears in.)
mingw32-make: *** [obj/windows/mamepm/mame/machine/starwars.o] Error 1
mingw32-make: *** Waiting for unfinished jobs....


all I selected was pentium m/ Core Duo options and also cheked Dual core.


Title: Re: Mame Compiler v0.5 Released
Post by: MKChamp on December 13, 2007, 07:08:53 pm
Did you patch 121u1 then 121u2 then 121u3 AND THEN 121u4....or did you just patch 121u4? Looks like you skipped the other u releases...

edit: They changed the parms for the timer_alloc function is 121u2...
Title: Re: Mame Compiler v0.5 Released
Post by: bent98 on December 13, 2007, 09:20:59 pm
ah yea my bad.

Question what if i want to compile 0121u1-u4 and then apply hi_0121u2. Will that be a problem? they havent come out with hi_0121u4 yet
Title: Re: Mame Compiler v0.5 Released
Post by: headkaze on December 13, 2007, 09:49:14 pm
Question what if i want to compile 0121u1-u4 and then apply hi_0121u2. Will that be a problem? they havent come out with hi_0121u4 yet

"they" is MKChamp ;)
Title: Re: Mame Compiler v0.5 Released
Post by: bent98 on December 13, 2007, 09:58:19 pm
haha. Will it cause a problem though?
Title: Re: Mame Compiler v0.5 Released
Post by: MKChamp on December 13, 2007, 11:54:32 pm
Someone hasn't 'read' the hiscore thread....

121u2 - CURRENT         hi_121u2.txt

So, hi_121u2.txt works for all versions 121u2 to current...which includes 121u4 ;-)

On a side note,
Hey Headkaze, I did an app for picture resizing/renaming/watermarking /batch processing/etc and spent alot of time searching the forums over at xtremevbtalk and ran across some posts from some nut named Headkaze ;-)
I was gonna say hi but my name over there was CokeDealer and the admins thought that name was 'offensive'...so I am saying Hi here!
(that IS you, right??)
Title: Re: Mame Compiler v0.5 Released
Post by: headkaze on December 14, 2007, 02:19:41 am
On a side note,
Hey Headkaze, I did an app for picture resizing/renaming/watermarking /batch processing/etc and spent alot of time searching the forums over at xtremevbtalk and ran across some posts from some nut named Headkaze ;-)
I was gonna say hi but my name over there was CokeDealer and the admins thought that name was 'offensive'...so I am saying Hi here!
(that IS you, right??)

Ahhh good ol' xtremevbtalk hehe, yep that's me although I don't visit the forums anymore because I don't code in VB6 anymore. It was a great forum though :)
Title: Re: Mame Compiler v0.5 Released
Post by: bent98 on December 18, 2007, 01:52:15 pm
I want to compile a 64bit version of mame. How do I do it? I have a Core d process and I select that at the drop down menu of com piler, but when I check 64bit check box I get errors.
Title: Re: Mame Compiler v0.5 Released
Post by: headkaze on December 18, 2007, 01:56:02 pm
I want to compile a 64bit version of mame. How do I do it? I have a Core d process and I select that at the drop down menu of com piler, but when I check 64bit check box I get errors.

See Reply #31
Title: Re: Mame Compiler v0.5 Released
Post by: bent98 on December 18, 2007, 02:00:43 pm
Im sure there is enuff people that would have a need for it. Come on Headkaze you figure something out to make it easier even if it ment d/ling a few extra pieces of software Think of all those people wanting to play blitz at full speed with no nag screens :)
Title: Re: Mame Compiler v0.5 Released
Post by: DeLuSioNal29 on January 09, 2008, 07:10:55 pm
Again, can't say enough about this program.  Great work Headkaze!  Your hard work is appreciated for this great FREE program.

I tried this on my .119 version of MAME and it worked like a champ.  However, I wanted to try it on a friend's who has version .108 and I'm having trouble.

-  I downloaded the source code for .108 and put it in the directory (removed my .119 from the previous compile)
-  downloaded the hi_108.diff file and placed it in the patches directory.

I get this error:
cc1.exe: error: unrecognized command line option "-Wno-unused-functions"
cc1.exe: error: unrecognized command line option "-Wno-unused-functions"
mingw32-make: *** [obj/mame64/audit.o] Error 1
mingw32-make: *** Waiting for unfinished jobs....
mingw32-make: *** [obj/mame64/cdrom.o] Error 1

Do i have to use the stand alone version to complile this older version?

Now I'm confused.

Thanks in advance!

~ DeLuSioNaL
Title: Re: Mame Compiler v0.5 Released
Post by: headkaze on January 09, 2008, 07:53:00 pm
Again, can't say enough about this program.  Great work Headkaze!  Your hard work is appreciated for this great FREE program.

I tried this on my .119 version of MAME and it worked like a champ.  However, I wanted to try it on a friend's who has version .108 and I'm having trouble.

-  I downloaded the source code for .108 and put it in the directory (removed my .119 from the previous compile)
-  downloaded the hi_108.diff file and placed it in the patches directory.

I get this error:
cc1.exe: error: unrecognized command line option "-Wno-unused-functions"
cc1.exe: error: unrecognized command line option "-Wno-unused-functions"
mingw32-make: *** [obj/mame64/audit.o] Error 1
mingw32-make: *** Waiting for unfinished jobs....
mingw32-make: *** [obj/mame64/cdrom.o] Error 1

Do i have to use the stand alone version to complile this older version?

Now I'm confused.

Thanks in advance!

~ DeLuSioNaL

Tick the option "Disable WError (<0.118u5)". That should fix it ;)
Title: Re: Mame Compiler v0.5 Released
Post by: DeLuSioNal29 on January 10, 2008, 01:01:52 am
Tick the option "Disable WError (<0.118u5)". That should fix it ;)

I will give it a shot tomorrow, thanks.
Title: Re: Mame Compiler v0.5 Released
Post by: rockmes on January 10, 2008, 01:02:41 am
would like to thank you Headkaze for this great ease of use program. Makes it so easy to complie your own .exe.
Do you think you will in the future add anything else to it? eg optimizing mame
Title: Re: Mame Compiler v0.5 Released
Post by: DeLuSioNal29 on January 10, 2008, 01:09:07 am
One other thing.  I noticed that with the hack installed, when I press the tab button, I cannot enter any of the options (any of them)  no matter how many times I press enter.  I reverted back to the original mame.exe and then I am able to enter the options in the tab menu.  Is this normal for the hack?

Also, I simply replaced my original mame.exe with the newly compiled mame64.exe and renamed the files (i.e. original mame.exe to mame.bak and mame64.exer to mame.exe).  Is that all I needed to do or should I have replaced all of the exe files that were newly compiled?

Thanks!

 ~ D
Title: Re: Mame Compiler v0.5 Released
Post by: headkaze on January 10, 2008, 01:22:13 am
One other thing.  I noticed that with the hack installed, when I press the tab button, I cannot enter any of the options (any of them)  no matter how many times I press enter.  I reverted back to the original mame.exe and then I am able to enter the options in the tab menu.  Is this normal for the hack?

Also, I simply replaced my original mame.exe with the newly compiled mame64.exe and renamed the files (i.e. original mame.exe to mame.bak and mame64.exer to mame.exe).  Is that all I needed to do or should I have replaced all of the exe files that were newly compiled?

Thanks!

 ~ D

Yes MKChamps diff patches use the "1" key for select. That is a more common key for Mame cabs which is why he chose it. You can always remap the UI_SELECT key to something else.
Title: Re: Mame Compiler v0.5 Released
Post by: superbigjay on January 10, 2008, 09:04:02 am
Hello,

I've got a quick question for the Mame Compiler Options.

I have an AMD 4600+ chiptset
and I want to compile mame 0.110.

What Option should I check?

- disable error <0.119
- optimized for ??? (amd or athlon?  there 2 choices that seem to fit?)

Thanks
Jay  :cheers:

Title: Re: Mame Compiler v0.5 Released
Post by: headkaze on January 11, 2008, 02:11:55 am
Hello,

I've got a quick question for the Mame Compiler Options.

I have an AMD 4600+ chiptset
and I want to compile mame 0.110.

What Option should I check?

- disable error <0.119
- optimized for ??? (amd or athlon?  there 2 choices that seem to fit?)

Thanks
Jay  :cheers:



There is only one option called "AMD Athlon". Not sure why you think they are two separate options.
Title: Re: Mame Compiler v0.5 Released
Post by: superbigjay on January 11, 2008, 08:03:00 am
Quote from: superbigjay link=topic=71845.msg781177#msg781177
date=1199973842
...
- optimized for ??? (amd or athlon?  there 2 choices that seem to fit?)
...

There is only one option called "AMD Athlon". Not sure why you think they
are two separate options.

The 2 options I'm refering to are:
- Athlon 64
- AMD Athlon


Since the AMD 4600+ is a 64-bit processor, should I used ATHLON 64, or
simply AMD ATHLON?

thanks for the reply
Jay  :cheers:


Title: Re: Mame Compiler v0.5 Released
Post by: headkaze on January 11, 2008, 04:15:04 pm
You can't compile a 64 bit version of Mame using Mame Compiler anyway, so I would just try AMD Athlon.
Title: Re: Mame Compiler v0.5 Released
Post by: lettuce on January 12, 2008, 10:01:29 am
I get a message saying

 "C:\Program: Interrupt/Exception caught (code  = 0xc00000fd, addr = 0x41e743)
Finshed!
0 Hours 0 Minutes and 0 Seconds Elapsed.

Why does this happen??
Title: Re: Mame Compiler v0.5 Released
Post by: headkaze on January 12, 2008, 05:49:14 pm
I get a message saying

 "C:\Program: Interrupt/Exception caught (code  = 0xc00000fd, addr = 0x41e743)
Finshed!
0 Hours 0 Minutes and 0 Seconds Elapsed.

Why does this happen??

Are you using the full setup version? If your using the Standalone verison you have to overwrite the mingw32-make.exe with the one provided in the archive.

Other than that I wouldn't have a clue?? Never seen that error before!
Title: Re: Mame Compiler v0.5 Released
Post by: livelike on January 17, 2008, 05:12:25 pm
Hi Headkaze, just wondering, can I complile Mame plus with this FE as well? I'm not sure if it is basically the same as mame32 or not.

Thanks!
Title: Re: Mame Compiler v0.5 Released
Post by: Antropus on February 09, 2008, 07:52:37 pm
I get a message saying

 "C:\Program: Interrupt/Exception caught (code  = 0xc00000fd, addr = 0x41e743)
Finshed!
0 Hours 0 Minutes and 0 Seconds Elapsed.

Why does this happen??
I was getting the exact same error in my Windows x64 machine. I tried it again, same steps, in my Windows XP sp2 system and it worked just fine. I guess there's something to do with the windows version you're running. Is it x64?

-Kris
Title: Re: Mame Compiler v0.5 Released
Post by: headkaze on February 09, 2008, 09:45:48 pm
Good news I now have access to a 64-bit machine so I will be testing out Mame Compiler on there and also seeing if I can get a special Mame 64 compiler version out too. Stay tuned folks :)
Title: Re: Mame Compiler 64 v1.0 Released!
Post by: headkaze on February 11, 2008, 05:25:24 am
Version 1.0 Released

- Adding support for compiling Mame64

Uninstall the old version of Mame Compiler if you already have it installed. This version of Mame Compiler extracts MinGW to your System Drive (Eg. C:\MinGW). Source is now placed in MinGW\source and patches are placed in MinGW\patches.

NOTE: If your doing a Mame64 compile you may have to press GO! again a few times when you get an "Error -99"

Moderators: Should this be pinned?
Title: Re: Mame Compiler 64 v1.0 Released!
Post by: Jdurg on February 11, 2008, 08:47:07 am
Version 1.0 Released

- Adding support for compiling Mame64

Uninstall the old version of Mame Compiler if you already have it installed. This version of Mame Compiler extracts MinGW to your System Drive (Eg. C:\MinGW). Source is now placed in MinGW\source and patches are placed in MinGW\patches.

NOTE: If your doing a Mame64 compile you may have to press GO! again a few times when you get an "Error -99"

Moderators: Should this be pinned?

Sweet!  So is this all we need to compile MAME64, or are there other items needed in order to get it to compile?  I had been hearing that only the MS SDK was able to compile the 64-bit version so I'm a bit confused.   ;D
Title: Re: Mame Compiler 64 v1.0 Released!
Post by: headkaze on February 12, 2008, 01:44:07 am
Sweet!  So is this all we need to compile MAME64, or are there other items needed in order to get it to compile?  I had been hearing that only the MS SDK was able to compile the 64-bit version so I'm a bit confused.   ;D

Yes it includes a cutdown version of the Platform SDK so you don't need to download any additional files.
Title: Re: Mame Compiler 64 v1.0 Released!
Post by: Jdurg on February 12, 2008, 09:24:49 am
Sweet!  So is this all we need to compile MAME64, or are there other items needed in order to get it to compile?  I had been hearing that only the MS SDK was able to compile the 64-bit version so I'm a bit confused.   ;D

Yes it includes a cutdown version of the Platform SDK so you don't need to download any additional files.

Fantastic.  Thank you so much for this!   :applaud: :cheers:
Title: Re: Mame Compiler 64 v1.11 Released!
Post by: bent98 on February 14, 2008, 07:26:59 am
This is probably a dumb question, but in order to compile a 64 bit version of mame you need to run 64 bit OS?
Title: Re: Mame Compiler 64 v1.11 Released!
Post by: Jdurg on February 17, 2008, 07:43:51 pm
This is probably a dumb question, but in order to compile a 64 bit version of mame you need to run 64 bit OS?

Yes.  You MUST be on a 64-bit OS to compile the 64-bit version.
Title: Re: Mame Compiler 64 v1.11 Released!
Post by: TheShanMan on February 18, 2008, 12:31:04 am
Just a suggestion. How about notifying the user that it's going to install stuff at C:\MinGW, hopefully with an option to change it. Otherwise, love the concept and thanks so much for the effort! :cheers:
Title: Re: Mame Compiler 64 v1.11 Released!
Post by: rooter on February 18, 2008, 03:38:59 pm
Dear headkaze,

Thank you so much for this!  I love you.
If I had a womb in which to make babies with, I would build you some, and they would be delicious.  For now I offer my sincerest gratitude and best wishes.

Word to your mother,
    rooter
Title: Re: Mame Compiler 64 v1.11 Released!
Post by: headkaze on February 18, 2008, 04:11:03 pm
Thank you so much for this!  I love you.
If I had a womb in which to make babies with, I would build you some, and they would be delicious.  For now I offer my sincerest gratitude and best wishes.

 :o  ;D
Title: Re: Mame Compiler 64 v1.11 Released!
Post by: SGT on February 18, 2008, 09:14:05 pm
If I had a womb in which to make babies with, I would build you some, and they would be delicious.  For now I offer my sincerest gratitude and best wishes.

That was . . . uh . . . scary. :laugh2:  Please tell me this was the result of translate.google.com.  If not, you and Headkaze need to get a room.
Title: Re: Mame Compiler 64 v1.11 Released!
Post by: Games001 on February 18, 2008, 11:10:04 pm
Hi folks.

I have a set of MAME roms given to me during the age of v122 from a friendly local rom-burner.

I have decided to use MAME UI 123 as the newest emu in my GameEX FE cab, but I have an issue.

The full rom set is over 6800 games.. of which about 98% seem to work and show up in the MAME UI, but when I am in GameEX only about 1800 of them will show up.

I have setup the FE to allow clones, etc but even when setup correctly the files are not being shown as available.  I must assume this has something to do with the v122 - v123 change of emus I have made.

If this is the case, what steps does one take to move from MAME v122 to MAME UI V123 as far as compiler setings and .diff files go?  What diffs need to be updated for this simple step up, etc?

Thanks all.
Title: Re: Mame Compiler 64 v1.11 Released!
Post by: headkaze on February 19, 2008, 07:03:29 am
Hi folks.

I have a set of MAME roms given to me during the age of v122 from a friendly local rom-burner.

I have decided to use MAME UI 123 as the newest emu in my GameEX FE cab, but I have an issue.

The full rom set is over 6800 games.. of which about 98% seem to work and show up in the MAME UI, but when I am in GameEX only about 1800 of them will show up.

I have setup the FE to allow clones, etc but even when setup correctly the files are not being shown as available.  I must assume this has something to do with the v122 - v123 change of emus I have made.

If this is the case, what steps does one take to move from MAME v122 to MAME UI V123 as far as compiler setings and .diff files go?  What diffs need to be updated for this simple step up, etc?

Thanks all.

Is this in some way related to Mame Compiler?
Title: Re: Mame Compiler 64 v1.11 Released!
Post by: Games001 on February 19, 2008, 10:35:26 am
I would imagine so, being that the v123 and v122 difference is the question I think needs answering. 

Since the compiler is used to update rom sets from version to version, at least that's what I have understood it does from this and some other posts, I think that's the problem I have been faced with. 

I just wanted to understand more about the .diff process and what steps should be taken for a v122 to v123 UI upgrade.
Title: Re: Mame Compiler 64 v1.11 Released!
Post by: Jdurg on February 19, 2008, 11:29:11 am
I would imagine so, being that the v123 and v122 difference is the question I think needs answering. 

Since the compiler is used to update rom sets from version to version, at least that's what I have understood it does from this and some other posts, I think that's the problem I have been faced with. 

I just wanted to understand more about the .diff process and what steps should be taken for a v122 to v123 UI upgrade.

Ummm, you couldn't be any more wrong than you are right now.  MameCompiler is a program that takes the source code of MAME and compiles it into the executeable.  It in no way whatsoever does ANYTHING with the ROMs.  The "diff" files you have read about are files that update the source code from one version to another.  Once again, there are absolutely ZERO bits of ROM Data in the source code. 

Once again, MAMECompiler is software that compiles the MAME source code into a functional executeable and nothing else.   ;D
Title: Re: Mame Compiler 64 v1.11 Released!
Post by: Games001 on February 19, 2008, 03:34:37 pm
OOhhhhh... I understand now how this item works.  TY.

This posting sent me in the wrong direction I think.  :dizzy:
http://forum.arcadecontrols.com/index.php?topic=76711.0

So what then would one be looking for to update the rom sets from v122 to v123?
Title: Re: Mame Compiler 64 v1.11 Released!
Post by: Jdurg on February 20, 2008, 10:39:27 am
You would need to find some ROM Managing software and then find the updated ROMs that would be required.  You're on your own with regards to finding the ROMs since it's against the rules to ask for them, and it's illegal to download them.
Title: Re: Mame Compiler 64 v1.11 Released!
Post by: Games001 on February 20, 2008, 10:43:46 am
Hence why I asked only how it was done, not where to find the roms themselves. :)  Thanks.
Title: Re: Mame Compiler 64 v1.11 Released!
Post by: sosimple on February 21, 2008, 07:23:11 am
Hi to all. I register to th forum just for this amazing program. I used it to compile mame v123, and apply the hi_123.diff patch It worked excellent but I have a problem with the compiled version  I made.
When I press tab in the emulator to see the menu there, I dont see the letters of tha menu , I cant see what it write to select one. Why is this? Is it a problem because i apply  tha patch hi_123.diff  ?
Is this happens to all ,or just me? Can I do anything to solve this?
  And another question. How can I compile the mameUI version with this compiler? Can anyone tell me what must I do for  this? Or it cant be done with Mame Compiler 64 ?  I copy the extra code for mameui to the folder
C:\MinGW\source\Mame0123 , but it didnt worked, i still created the simple version mame.exe
I did it by doing what i find there http://www.mameworld.net/mrdo/compile.html , but i try to do it with your
program as it is much more easy.
Thanks ,

Title: Re: Mame Compiler 64 v1.11 Released!
Post by: rooter on February 21, 2008, 10:30:36 pm
I can apply the patch, but when I try to compile, I get:

(http://root88.ice.org/temp/compilerError.png)
Title: Re: Mame Compiler 64 v1.11 Released!
Post by: TheShanMan on February 21, 2008, 10:55:43 pm
I'm guessing you didn't download the source and put it in that directory?
Title: Re: Mame Compiler 64 v1.11 Released!
Post by: rooter on February 21, 2008, 11:08:20 pm
I'm pretty sure that I did it correctly.

(http://root88.ice.org/temp/dirListing.png)
Title: Re: Mame Compiler 64 v1.11 Released!
Post by: headkaze on February 21, 2008, 11:21:08 pm
I'm pretty sure that I did it correctly.

I see no "src" folder or file called "makefile" there.
Title: Re: Mame Compiler 64 v1.11 Released!
Post by: rooter on February 21, 2008, 11:24:34 pm
On a hunch, I downloaded the .zip file instead of using the self extracting executable and sure enough the files were there.  Getting closer I guess.  Compile took 2 seconds and had errors.

(http://root88.ice.org/temp/compilerError2.png)
Title: Re: Mame Compiler 64 v1.0 Released!
Post by: headkaze on February 21, 2008, 11:33:23 pm
NOTE: If your doing a Mame64 compile you may have to press GO! again a few times when you get an "Error -99"
Title: Re: Mame Compiler 64 v1.11 Released!
Post by: rooter on February 22, 2008, 12:15:32 am
Thanks again for your help compiling everything.  I really appreciate your help.

It looks like I've got things going now.

Hit go again and it ran for 23 minutes.
Hit go again and it ran for 7 seconds.
Hit go again and it ran for 30 seconds.
Hit go again and it ran for 21 seconds.


Now every time I hit go, I just get:

Compiling Mame64...
Using Parameters -j3 MSVC_BUILD=1 PTR64=1
mingw32-make: *** No rule to make target `obj/windows/vmame/emu/hiscore.o', needed by `obj/windows/vmame/libemu.a'.  Stop.
Finished!
0 Hours 0 Minutes and 5 Seconds Elapsed.


I don't see any executable yet.  What else do I need to do?
Title: Re: Mame Compiler 64 v1.11 Released!
Post by: sosimple on February 22, 2008, 08:07:55 am
Hi to all. I register to th forum just for this amazing program. I used it to compile mame v123, and apply the hi_123.diff patch It worked excellent but I have a problem with the compiled version  I made.
When I press tab in the emulator to see the menu there, I dont see the letters of tha menu , I cant see what it write to select one. Why is this? Is it a problem because i apply  tha patch hi_123.diff  ?
Is this happens to all ,or just me? Can I do anything to solve this?
  And another question. How can I compile the mameUI version with this compiler? Can anyone tell me what must I do for  this? Or it cant be done with Mame Compiler 64 ?  I copy the extra code for mameui to the folder
C:\MinGW\source\Mame0123 , but it didnt worked, i still created the simple version mame.exe
I did it by doing what i find there http://www.mameworld.net/mrdo/compile.html , but i try to do it with your
program as it is much more easy.
Thanks ,


Anyone can help me with what I asked? Thanks,
Title: Re: Mame Compiler 64 v1.11 Released!
Post by: headkaze on February 22, 2008, 09:57:43 am
rooter: Your doing something wrong, but I don't know what. I would delete your source folder, download the source again, and try again. This time try reading the instructions first ;)

sosimple: Not sure what problem that is never heard of it. Selecting a menu item is changed to the '1' key when applying the hiscore patch. I don't compile MameUI version so I wouldn't know about that. I'll have a look at adding MameUI compiling support.
Title: Re: Mame Compiler 64 v1.11 Released!
Post by: headkaze on February 22, 2008, 11:32:06 am
Okay 1.12 is Released. I added support for compiling MameUI. I've tested it here and it seems to work okay including the 64 bit version.
Title: Re: Mame Compiler 64 v1.11 Released!
Post by: sosimple on February 22, 2008, 02:08:09 pm
Okay 1.12 is Released. I added support for compiling MameUI. I've tested it here and it seems to work okay including the 64 bit version.
You are the best man. Thanks for adding support for compiling MameUI .
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: headkaze on February 22, 2008, 02:46:26 pm
Make sure you extract the \winui directory to \src\osd\winui and MameUI.mak to root next to the core makefile.

Also set the "Mame UI" option in Mame Compiler.
Title: Re: Mame Compiler 64 v1.11 Released!
Post by: rooter on February 22, 2008, 04:58:01 pm
rooter: Your doing something wrong, but I don't know what. I would delete your source folder, download the source again, and try again. This time try reading the instructions first ;)

sosimple: Not sure what problem that is never heard of it. Selecting a menu item is changed to the '1' key when applying the hiscore patch. I don't compile MameUI version so I wouldn't know about that. I'll have a look at adding MameUI compiling support.

I did read the instructions.  You said to download the source.  There are two version of the source, both of which contain different files.  Only one works.  It would help if you specified which one.

It would also be great if you were doing a 64bit compile and and error -99 was reported that the compiler automatically restarted itself rather that the user having to guess if they are supposed to hit Go multiple times or not.
Title: Re: Mame Compiler 64 v1.11 Released!
Post by: headkaze on February 22, 2008, 05:05:41 pm
I did read the instructions.  You said to download the source.  There are two version of the source, both of which contain different files.  Only one works.  It would help if you specified which one.

It would also be great if you were doing a 64bit compile and and error -99 was reported that the compiler automatically restarted itself rather that the user having to guess if they are supposed to hit Go multiple times or not.

There is only one version of the source archived in two different ways, one is a self-extracting exe, and the other a zip file you have to extract manually. Both contain the exact same files.

Comon it's not that hard to press a button a few times. Next you will want me to come over and do up your shoe laces every morning  ;D
Title: Re: Mame Compiler 64 v1.11 Released!
Post by: Jdurg on February 22, 2008, 05:52:18 pm
I did read the instructions.  You said to download the source.  There are two version of the source, both of which contain different files.  Only one works.  It would help if you specified which one.

It would also be great if you were doing a 64bit compile and and error -99 was reported that the compiler automatically restarted itself rather that the user having to guess if they are supposed to hit Go multiple times or not.

There is only one version of the source archived in two different ways, one is a self-extracting exe, and the other a zip file you have to extract manually. Both contain the exact same files.

Comon it's not that hard to press a button a few times. Next you will want me to come over and do up your shoe laces every morning  ;D

Let me just say tha you rock.  This weekend I will have fun restoring the coin door/mechs that I bought, then compiling my own version of MAMEUI64 on my new laptop.  This will be fun.   :cheers:
Title: Re: Mame Compiler 64 v1.11 Released!
Post by: rooter on February 22, 2008, 06:21:39 pm
I did read the instructions.  You said to download the source.  There are two version of the source, both of which contain different files.  Only one works.  It would help if you specified which one.

It would also be great if you were doing a 64bit compile and and error -99 was reported that the compiler automatically restarted itself rather that the user having to guess if they are supposed to hit Go multiple times or not.

There is only one version of the source archived in two different ways, one is a self-extracting exe, and the other a zip file you have to extract manually. Both contain the exact same files.

Comon it's not that hard to press a button a few times. Next you will want me to come over and do up your shoe laces every morning  ;D

As for the files, the first time I tried to copy them, they were being updated on the server. 

"MAME 0.123u2
February 21st, 2008

Another update to MAME 0.123 has just been posted on the updates page. Have fun checking out the Naomi progress and other cool stuff!"


As for hitting go numerous times, I'm just trying to make helpful suggestions.  The whole point of the your process is to automate the compile.  Having to hit Go again is just unintuitive.  If you are going to have your software do something so odd, the instructions should show on the program, not in a place that only users of a certain message base will see.  Someone might not have even access to the internet during the install, especially in a MAME machine that probably doesn't need internet access.  If the docs are installed somewhere on the user's hard drive, there should be a link to them in the start menu group. 



Title: Re: Mame Compiler 64 v1.11 Released!
Post by: headkaze on February 22, 2008, 06:44:06 pm
As for hitting go numerous times, I'm just trying to make helpful suggestions.  The whole point of the your process is to automate the compile.  Having to hit Go again is just unintuitive.  If you are going to have your software do something so odd, the instructions should show on the program, not in a place that only users of a certain message base will see.  Someone might not have even access to the internet during the install, especially in a MAME machine that probably doesn't need internet access.  If the docs are installed somewhere on the user's hard drive, there should be a link to them in the start menu group.

Yeah I understand I was just making a joke. I did actually think about doing that just haven't got around to it.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: Jdurg on February 22, 2008, 09:29:08 pm
Hey headkaze.  I can't seem to get MAMEUI64 to compile as I keep getting the following error:

Compiling src/osd/windows/strconv.c...
LIBCMT.lib(gs_cookie.obj) : fatal error LNK1112: module machine type 'AMD64' conflicts with target machine type 'IA64'
mingw32-make: *** [obj/winui/vmame/osd/windows/vconv.exe] Error 1112
mingw32-make: *** Waiting for unfinished jobs....
mingw32-make: *** [obj/winui/vmame/build/file2str.o] Error -99
mingw32-make: *** [obj/winui/vmame/osd/windows/strconv.o] Error -99
Finished!
0 Hours 0 Minutes and 0 Seconds Elapsed.


This comes up no matter how many times I hit go.  Any suggestions?


Edit: Nevermind.  Got it working.  I had been messing around with my compiling environment and screwed some things up.  I re-installed my MinGW folder and everything now works fine.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: rooter on February 26, 2008, 06:13:26 pm
Well, I got everything compiled, but I'm still having problems.  When I tried running MAME, everything was super slow.  It was completely unplayable.  Hitting the esc key took over 30 seconds to exit a game.  I thought I might have screwed up the compile somehow, so I downloaded the official binaries and had the same problem.  I'm running 64bit Vista with a 2.8ghz AMD dual core chip with 4gigs of ram.  Did anyone else have a similar problem?
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: TheShanMan on February 26, 2008, 08:09:19 pm
If you had the same problem with the official binaries then I suggest starting a new thread to get help. This thread isn't the place, and you're likely to get more help in a new thread anyway. Hope you get it figured out though!
Title: Re: Mame Compiler 64 v1.11 Released!
Post by: rooter on February 29, 2008, 08:12:26 pm
Okay 1.12 is Released. I added support for compiling MameUI. I've tested it here and it seems to work okay including the 64 bit version.

Thanks again man.  This pretty much solved all my problems.  Now if I can just get MALA to work with a 64bit build without major slowdown.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: FhM on March 07, 2008, 08:57:18 pm
Hmm though I would try this out and kept getting errors. I decided just to try and compile the 123 source with no updates to rule anything out but I get:

src/emu/sound/ay8910.c: In function 'AY8910_set_volume':
Finished!
0 Hours 27 Minutes and 55 Seconds Elapsed.
src/emu/sound/ay8910.c:589: internal compiler error: in assign_386_stack_local, at config/i386/i386.c:13482


I have deleted the source and copied it in again but no luck. Any ideas?
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: FhM on March 10, 2008, 06:04:44 pm
Ok I figured this out. It only does it when you compile for Pentium 4 +SSE3
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: Dustin Mustangs on March 11, 2008, 04:09:36 pm
I'm trying to get rid of the left-right nag screens on v0.104u6 (the actlabs lightgun version) and am kinda confused.  I believe by this version the -skip_disclaimer option was removed so I will need to recompile to remove these.  I also believe that this version still has hiscore support so there is no hiscore diff for me to use.  I have searched and searched and can't figure out how to handle this version which I am pretty much stuck using.  Some posts seem to hint towards me having to modify the source by hand and then recompiling but they don't seem say where and what edits are needed.  Am I on the right track here?  Is there a post that goes over these source edits?? 

I can't seem to figure this one out and this seemed like a beneficial place to put this question and (hopefully) answer.  Thanks for any help.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: brian_hoffman on March 12, 2008, 05:18:18 pm
You can find that info right here. :)

http://www.gameex.info/forums/index.php?s=&showtopic=3964&view=findpost&p=24068
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: TeutonicDarkness on March 12, 2008, 07:22:50 pm
I'm trying to get rid of the left-right nag screens on v0.104u6 (the actlabs lightgun version) and am kinda confused.  I believe by this version the -skip_disclaimer option was removed so I will need to recompile to remove these.  I also believe that this version still has hiscore support so there is no hiscore diff for me to use.  I have searched and searched and can't figure out how to handle this version which I am pretty much stuck using.  Some posts seem to hint towards me having to modify the source by hand and then recompiling but they don't seem say where and what edits are needed.  Am I on the right track here?  Is there a post that goes over these source edits?? 

I can't seem to figure this one out and this seemed like a beneficial place to put this question and (hopefully) answer.  Thanks for any help.



 Yes...

I was just going to ask about this myself!.. ;)

You beat me too it!


I will have to try this!

@Dustin

Have you managed to confirm whether
the 104 build listed on
http://mamedev.org/oldrel.html
will even work with Act Lab guns?..
as compared to Act Labs version: 104u6?



This will be awesome if it will work for
Lightguns and we can re-compile with this tool!



[edit] Well I read that other thread but....
In this version of Mame there is no
"src\emu\ui.c "

Any other sugestions? I'm sure many lightgun users
will appreciate this.  :) [/edit]







Title: Re: Mame Compiler 64 v1.12 Released!
Post by: Dustin Mustangs on March 13, 2008, 02:48:10 pm
Crap.  I didn't think about the fact that the actlabs version isn't likely the standard 104u6 release.  Is there any way to tell for sure?  I noticed the one who is credited with putting that version together is a member here.  I wonder if he would be willing to put together a .diff for the required source changes?  What a big bump in the road this could be...

 :hissy:
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: TeutonicDarkness on March 13, 2008, 07:07:51 pm
Crap.  I didn't think about the fact that the actlabs version isn't likely the standard 104u6 release.  Is there any way to tell for sure?  I noticed the one who is credited with putting that version together is a member here.  I wonder if he would be willing to put together a .diff for the required source changes?  What a big bump in the road this could be...

 :hissy:

 I tested that version last night...
No Go... :(

When you start Mame it displays the Date and version.
The Act labs Mame and the on Mame.net are
indeed different versions.
The one on Mame.net will not work with
Act Labs "currently anyway".

 However I have found a hidden diif on the Mame Server
that is named 104u6.

I have tried to Apply it to
The MAME.NET 104 source to bring it
up to 104u6....

I get nothing but errors; well even if it had worked
that still would not have fixed Our Nag screen problem.


I just hope someone here on the forums
does indeed have a soultion for Act Lab gun owners.


Title: Re: Mame Compiler 64 v1.12 Released!
Post by: Dustin Mustangs on March 13, 2008, 07:48:51 pm
You'd need to apply all the diffs up to u6 (u1, u2, u3...) for it to work, not just the one you want.  I'm pretty sure the version on actlabs site has a modified source so this will not work unless we are able to figure out what mods are needed up to this point or get a diff that takes care of it for us.  The actlabs site gives credit for the version to one of the mame devs.  From what I understand he won't likely be willing to help us with something that will be used to rid mame of a disclaimer so I don't think contacting him about this is a good idea.

I messed with this a bit today and have found a couple of work arounds.  For one, this version does have the option to skip game info (it's almost at the end of mame.ini).  This makes it so you only need to do the left-right buisness the first time a game is played.  From then on it just goes right into it.  Also, one of headkaze's other apps called cpwizard (which I highly recommend regardless) has an option that will send mame the keystrokes for you.  You still breifly see the screen(s), but they disappear without any input from the user.  I am using a combo of both and it is working great.



Sorry for taking your thread on a tangent headkaze.

:)
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: lettuce on March 15, 2008, 09:01:29 am
So ive downloaded the source for mame 0123, and want to apply the hi_123u5.diff, before doing this do i need to download 0123u1, 0123u2, 0123u3, 0123u4 diffs and compile them before compiling hi_123u5.diff, or can i just go straight to compling hi_123u5.diff?
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: headkaze on March 15, 2008, 10:40:32 am
So ive downloaded the source for mame 0123, and want to apply the hi_123u5.diff, before doing this do i need to download 0123u1, 0123u2, 0123u3, 0123u4 diffs and compile them before compiling hi_123u5.diff, or can i just go straight to compling hi_123u5.diff?

You only compile once. But you must apply all the diff's in order (ie. 0123u1, 0123u2, 0123u3, 0123u4, 0123u5) then apply hi_123u5. Then compile.

A diff file is a patch. The version it patches is indicated in it's file name. So you must patch up to match the version of the hiscore patch.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: lettuce on March 15, 2008, 11:44:45 am
Ok done that, but when a patch with the Hi_0123u5.diff file it said that it ignored or skipped almost all the files as they had already been patch, is this normal?
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: headkaze on March 15, 2008, 03:48:46 pm
Ok done that, but when a patch with the Hi_0123u5.diff file it said that it ignored or skipped almost all the files as they had already been patch, is this normal?

Start again just to be sure you do it in the right order. If it's skipping parts of the patch most likely you've already applied it. Just extract the Mame 0123 source again and start from scratch.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: crummy on March 16, 2008, 01:20:14 pm
Hmm though I would try this out and kept getting errors. I decided just to try and compile the 123 source with no updates to rule anything out but I get:

src/emu/sound/ay8910.c: In function 'AY8910_set_volume':
Finished!
0 Hours 27 Minutes and 55 Seconds Elapsed.
src/emu/sound/ay8910.c:589: internal compiler error: in assign_386_stack_local, at config/i386/i386.c:13482


I have deleted the source and copied it in again but no luck. Any ideas?
Ok I figured this out. It only does it when you compile for Pentium 4 +SSE3
Same thing happened to me. Pentium 4 (-SSE3) seemed to work fine.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: headkaze on March 16, 2008, 02:06:16 pm
Same thing happened to me. Pentium 4 (-SSE3) seemed to work fine.

EDIT: I see what you mean seems the "Pentium 4 (+SSE3)" optimize option won't allow Mame to compile. So yeah use "Pentium 4 (-SSE3)" option instead.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: rdenis on March 17, 2008, 10:56:05 pm
I can't compile a 64 bit version of Mame 123 optimized for my quad core 6600.  No diffs have been applied this is strictly Mame 0123.  I have deleted and reinstalled source code and MC64 several times and I keep getting these errors at the same place:

Archiving obj/windows/vmame/mame/shared.a...
Archiving obj/windows/vmame/libosd.a...
Linking obj/windows/vmame/emu/cpu/m68000/m68kmake.exe...
Archiving obj/windows/vmame/libsound.a...
Linking ledutil.exe...
LINK : fatal error LNK1101: incorrect MSPDB80.DLL version; recheck installation of this product
mingw32-make: *** [obj/windows/vmame/emu/cpu/m68000/m68kmake.exe] Error 1101
Linking romcmp.exe...
mingw32-make: *** Waiting for unfinished jobs....
LINK : fatal error LNK1101: incorrect MSPDB80.DLL version; recheck installation of this product
LINK : fatal error LNK1101: incorrect MSPDB80.DLL version; recheck installation of this product
mingw32-make: *** [ledutil.exe] Error 1101
mingw32-make: *** [romcmp.exe] Error 1101
Finished!
0 Hours 2 Minutes and 49 Seconds Elapsed.


Any ideas?

Rich
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: headkaze on March 17, 2008, 11:27:54 pm
Any ideas?

What options are you using? Do you have a 64-bit OS?
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: rdenis on March 18, 2008, 12:27:24 am
I'm running Vista 64 Premium.  In the drop down menu I selected 'Core 2' and then ticked '64 Bit' and 'Quad'. 

I also just tried running 'Duo' instead of 'Quad' to see if I could get it to compile but same error.


Rich
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: headkaze on March 18, 2008, 12:38:07 am
I'm running Vista 64 Premium.  In the drop down menu I selected 'Core 2' and then ticked '64 Bit' and 'Quad'. 

I also just tried running 'Duo' instead of 'Quad' to see if I could get it to compile but same error.

Rich

There was an older release of MC64 that had some problems. Uninstall MC64, download MC64 again and re-install. Extract the source again and try again.

BTW Do you have any version of Visual Studio or Platform SDK installed?
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: rdenis on March 18, 2008, 12:55:22 am
I'll give it a try.  I don't have Visual Studio or Platform SDK.  There are a couple of VS folders in my "Programs X86" folder but they only have dll files etc. - no executables.

I'll let you know how the redownload/reinstall goes.

Rich
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: rdenis on March 18, 2008, 01:13:13 am
Didn't work - same error same place :(
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: crummy on March 18, 2008, 03:33:26 am
Am I able to compile MESS with this?

Or, phrased differently: How do I get hiscore support with MESS?
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: rdenis on March 18, 2008, 03:43:26 pm
HK - couple of things - I scanned my system to make sure I didn't have another version of this dll somewhere causing problems and there wasn't.

I managed to find a guy in France who has the same error - he solved it with a patch from MS.  There is a later patch for VS2005 that will update the build version to 8.0.50727.824 from the current 8.0.50727.762.  The update is available at http://support.microsoft.com/kb/935225/en-us.

It doen't seem to have anything to do with the error I am getting but who knows.

Title: Re: Mame Compiler 64 v1.12 Released!
Post by: headkaze on March 18, 2008, 04:39:03 pm
rdenis: Okay can you download and try again. If it still doesn't work can you PM me.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: headkaze on March 19, 2008, 02:55:26 pm
Looks like this problem rdenis was having was a permissions issue with Vista 64. He now has it compiling okay. I will probably need to update the installer to give the appropriate permissions.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: rdenis on March 19, 2008, 03:19:37 pm
Yep works great now that Vista 64 has the appropriate permissions!  :cheers:
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: hellothere123 on March 20, 2008, 10:09:42 pm
I have mame32 setup in folder C:arcade/mame32

Can I change the "source folder" for mame to that folder, then apply the patches, then the hi patch and then press "Go" and it should work?

Or am I missing something...like adding "Hi" folder to mame and hiscores dat file to the mame folder???


Thansk!
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: headkaze on March 21, 2008, 07:34:14 am
I have mame32 setup in folder C:arcade/mame32

Can I change the "source folder" for mame to that folder, then apply the patches, then the hi patch and then press "Go" and it should work?

Or am I missing something...like adding "Hi" folder to mame and hiscores dat file to the mame folder???

Don't mix your Mame binaries with the Mame source code. You should have a separate folder for compiling Mame, then copy the resulting exe to your binary folder.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: Chunce DeLeone on March 31, 2008, 02:33:22 pm
I ran the compiler and it looked like it went fine, where is the new mame.exe?
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: headkaze on March 31, 2008, 03:05:26 pm
I ran the compiler and it looked like it went fine, where is the new mame.exe?

It should open your source folder after a successful compile. Check the "Mame Source Folder" it should have the mame exe there if it worked. BTW it's not always called mame.exe, for example, if it's a 64-bit compile it will be called vmame.exe. Compiling should take 5 to 20 minutes depending on your CPU.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: Chunce DeLeone on March 31, 2008, 03:55:38 pm
thanks for the quick response!!!!!!!!

I got it, the problem was I was using the Hi 109hi diff and not the 109u2 hi diff, but when I run mame from a comand promp I am still getting nag screens, it tell me to press ok and then has the game info???? isn't that supposed to be removed?
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: rdenis on March 31, 2008, 04:10:14 pm
RTFM dude  ;D:

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
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.

For help compiling MAME, please see Mr. Do's excellent page. He's made it so simple, there's no excuse not to compile your own!
http://www.mameworld.net/mrdo/compile.html (http://www.mameworld.net/mrdo/compile.html)

You can also get Headkaze's MAME Compiler (http://forum.arcadecontrols.com/index.php?topic=71845.0) to make compiling even easier. Great app for those not too familier with making your own builds!

Also, you will need the hiscore.dat file by Leezer in your mame directory. You can grab that over at http://www.mameworld.net/highscore/ (http://www.mameworld.net/highscore/)

...and don't forget to create a sub folder under your mame directory named "hi"...that's it!

Here's the guide for what diff to download (change extention from .txt to .diff) Also, if you don't see your file attached to this post, check further down. Only 8 files per post allowed)

**Please note that Pitou found a bug with this diff causing MAME to not recognize the refreshspeed option. This was 'fixed' starting with hi_124**

Starting with hi_124, all modifications are preceeded with comments detailing what is occuring. You can search the diff for "MKChamp" to find all the comments.

MAME VERSION             DIFF VERION
-------------------             ----------------
108                               hi_108.txt
109                               hi_109.txt
110                               hi_110.txt
111                               hi_111.txt
112                               hi_112.txt
113                               hi_113.txt
114 - 116                       hi_114_15_116.txt
117                               hi_117.txt
118 - 119                       hi_118_119.txt
120                               hi_120.txt
121                               hi_121.txt
122                               hi_122.txt
123                               hi_123.txt
124 - CURRENT                  hi_124.txt
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: headkaze on March 31, 2008, 06:03:54 pm
If you are patching a intermediate update version of Mame (or 'u' release) you must also patch Mame up to the 'u' version before applying the hiscore patch. You can download them from here (http://mamedev.org/updates/).

BTW I recommend not to use a "u" version of an older Mame version. You will notice that pinned topic for the hiscore patches at the top of this forum only have the official releases now (no 'u' version patches). So I would download the hi_109.diff from there and start again from scratch using mame0109s.

And RTFM does help  :)
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: Chunce DeLeone on April 01, 2008, 09:04:09 am
Sorry guys still a little unsure what I missed here,  I patched from u1 to u5 then did the Hi Diff all for mame109.....is there still supposed to be the OK nag screen and game info screen?
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: headkaze on April 01, 2008, 10:51:51 am
Sorry guys still a little unsure what I missed here,  I patched from u1 to u5 then did the Hi Diff all for mame109.....is there still supposed to be the OK nag screen and game info screen?

If you read learning will come. Like I said forget the "u" versions of Mame. I've updated Mame Compiler 64 and removed the "u" diff's. So uninstall Mame Compiler, download the new version and install it again. Then just download mame109s.zip, extract it to MinGW\source\Mame0109 and hi_109.diff to MinGW\patches. Click the [...] buttons to browse to these folders. Apply the patch, then compile by pressing the GO! button.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: hokey1 on April 01, 2008, 11:42:49 am
  First off apologies if this is just something really simple.  Take a look at the screen shot below.  I want to compile for a athlon but there is no option in the drop down menu for compiling that version.  Am I just missing something?  I saw another picture in this thread where it was shown that the athlon option was available but I can't find it.   I re-downloaded and installed again and it made no difference.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: headkaze on April 01, 2008, 12:11:24 pm
  First off apologies if this is just something really simple.  Take a look at the screen shot below.  I want to compile for a athlon but there is no option in the drop down menu for compiling that version.  Am I just missing something?  I saw another picture in this thread where it was shown that the athlon option was available but I can't find it.   I re-downloaded and installed again and it made no difference.

My bad, recently Mame removed it's optimization options from it's make file so you have to specify them manually. I added some of them but missed a few AMD64 and AthlonXP being two of them. There are probably other ones from here (http://www.mameworld.net/mrdo/compile.html) I should add, but I'm not sure which ones.

Anyway I've uploaded a new version of Mame Compiler with these two options added. If anyone else thinks I should add some more options from Mr Do's compile page, let me know here and I'll add them to the list.

Right now I have the following (as of MC64 v1.14)

Code: [Select]
The following options take advantage of CPU features, but don't do any other fancy tricks:

Intel Core2 or P4 w/ SSE3 ARCHOPTS=-msse3 (*)
P4 w/o SSE3; Pentium M, Intel Core ARCHOPTS=-msse2 (*)
AMD64 ARCHOPTS=-march=athlon64 (++)
AthlonXP ARCHOPTS=-march=athlon-xp (++)
IBM G5, IBM Cell (PS3), IMB POWER5 ARCHOPTS="-mpowerpc64 -mpowerpc-gfxopt -mpowerpc-gpopt -maltivec" (*)
Motorola G4 ARCHOPTS="-mpowerpc -mpowerpc-gfxopt -maltivec" (*)
IBM G3 ARCHOPTS="-mpowerpc -mpowerpc-gfxopt" (*)

For architecture-specific optimizations and instruction tuning, you can try these options (note: may bring out some bugs in GCC):

Intel Core2 ARCHOPTS="-march=pentium-m -msse3" (+)
Pentium M, Intel Core ARCHOPTS=-march=pentium-m (+)
Pentium 4 (w/ 64-bit capability) ARCHOPTS=-march=nocona (+)
Pentium 4 (w/ SSE3) ARCHOPTS=-march=prescott (#)
Pentium 4 (w/o SSE3) ARCHOPTS=-march=pentium4 (+)
Motorola G4 (7450, later) ARCHOPTS=-mcpu=7450 (+)
Motorola G4 (7447, earlier) ARCHOPTS=-mcpu=7400 (+)
IBM G5 ARCHOPTS=-mcpu=G5 (+)
IBM G3 ARCHOPTS=-mcpu=G3 (+)

(+) Added in MC64 v1.11
(++) Added in MC64 v1.14
(*) Not added
(#) Can't compile with this option (internal compiler error)
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: Chunce DeLeone on April 02, 2008, 08:09:31 am
HeadKaze, just wanted to say thanks for the patience and thanks for this Utility, I have been waiting to do this for years but was always a little intimidated with the process, you Ultility makes it really easy,  everything is working, thanks allot !!!!!
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: joebells on April 05, 2008, 02:53:52 am
First off wanted to say thank you. Second I was wondering what this might mean.
Linking vmame.exe...
dinput.lib(dilib2.obj) : warning LNK4078: multiple '.text' sections found with different attributes (C0500040)
Finished!
I am running vista sp1 x64 compiling 124 and only applied the hi_124.diff. I got the error 99 once but after that it complied just fine(took about 6 minutes). I chose optimize for core 2, and checked 64bit and dual core. I was just wondering what this means? Also why does it give the 99 error? What does it mean?

Thanks again, nice program. I wasn't sure about some of the settings in the makefile so figured this would make it nice and simple.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: headkaze on April 05, 2008, 08:11:19 am
First off wanted to say thank you. Second I was wondering what this might mean.
Linking vmame.exe...
dinput.lib(dilib2.obj) : warning LNK4078: multiple '.text' sections found with different attributes (C0500040)
Finished!
I am running vista sp1 x64 compiling 124 and only applied the hi_124.diff. I got the error 99 once but after that it complied just fine(took about 6 minutes). I chose optimize for core 2, and checked 64bit and dual core. I was just wondering what this means? Also why does it give the 99 error? What does it mean?

Thanks again, nice program. I wasn't sure about some of the settings in the makefile so figured this would make it nice and simple.


The warning is fine, everyone gets that. The 99 error AFAIK is caused by the utilities that are compiled when using the 64-bit compiler for some reason have a problem executing the first time. Pressing Go again just continues the compile but this time it finds the utility that wasn't there before. Another possibility is that the file is locked because it's just been compiled and it can't execute it until starting again when the file handle is released.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: joebells on April 05, 2008, 10:35:21 am
thanks for the reply, what about

dinput.lib(dilib2.obj) : warning LNK4078: multiple '.text' sections found with different attributes (C0500040)

I imagine its nothing just figured I'd ask
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: joebells on April 06, 2008, 06:57:03 pm
ok I just tried to play using my 64 bit mame that I compiled using your tool and it runs but its uber choppy.  When I tried to setup my keys and such it worked at first but then it "Froze" as I was trying to set them up. I was able to escape out of the config menu and then escape out of the program all the way. When I exited it shows exception at eip=.(bunch of numbers)... : access violation in the command box. The second time I ran it, it just froze when I pressed tab and tried to adjust a key.

I've run the precompiled 64bit and it runs really well, I was hoping for high score support though. Hopefully its something simple, actually as I'm finishing this I remembered I did tune it for core 2 duo(which is what I have) I think I'll try to do it without that optimization.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: arzoo on April 10, 2008, 01:38:42 pm
If I'm running with an AMD Athlon Thunderbird processor, do you think the AthlonXP optimization will help (or harm)? Thanks!

Update: Putting aside the optimization question, the utility worked perfectly for me. Thanks Headkaze  :cheers:
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: keirondrk on April 12, 2008, 04:24:13 am
heyyy just to say a big thanks for the compiler.... I never got around to compiling mame myself until I found your app and thought why not give it a go , excellent !!! saved me eventually having to sit down with the step by step guide and do it myself (which I must admit until I found your app I wasn't in that much of a rush to get udiff updates applied)...


quick simple painless... always worked since day 1 for me....

now I apply the u diffs as they come out... (think I'm a Obsessive-compulsive MAME compiler?!)

now off to apply .124u2 ;) while I await a hiscore diff from MKChamp hehe

KEEP UP THE EXCELLENT WORK, YOU'VE SERIOUSLY IMPROVED MY MAME EXPERIENCE AND SIMPLIFIED IT GREATLY :)

--tested since .123 with all the u updates... and now onto .124 and pentium m builds
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: headkaze on April 12, 2008, 09:57:34 am
If I'm running with an AMD Athlon Thunderbird processor, do you think the AthlonXP optimization will help (or harm)? Thanks!

Update: Putting aside the optimization question, the utility worked perfectly for me. Thanks Headkaze  :cheers:

I actually don't know much about the optimization options. I guess without doing some benchmarking it's hard to say if there is much improvement using them.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: kingb33 on April 17, 2008, 12:05:13 am
Hi I'm new here!  Hey, I used the compiler and everything seemed to work fine....then when i used all the files it created and replaced my old ones....i booted up mame and all the games are like really really dark....like someone turned down my brightness setting on my monitor by like 85%.  Why is this happening? Any help would be greatly appreciated...i really want to add the hi-score function back into mame and get rid of the nag screens as well.

Thanks!
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: TheShanMan on April 17, 2008, 01:41:48 am
Can't imagine that has anything to do with the compiler or the hiscore diff. Try an official binary of the exact version you compiled and see if you get the same thing.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: massive88 on April 17, 2008, 02:40:41 pm
Link is coming up dead for me at work?

Works now!
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: kingb33 on April 17, 2008, 06:42:44 pm
Shanman said:

Can't imagine that has anything to do with the compiler or the hiscore diff. Try an official binary of the exact version you compiled and see if you get the same thing.

Hi Shanman, yes i already tried that and the binary works fine....i tried to compile it 4 different times and it comes out the same way every time.  The screen is dark....is there another way to add hi scores back into a mame build?  weird my screen is dark i wonder why or what would cause it?  i compiled using the version that automatically shows up with you install the compiler.  i didn't even attempt to do the 2 updates that have come out since.  (actually i did but i got errors so decided to try to just compile the last official release)
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: kingb33 on April 18, 2008, 04:39:45 am
When i run the compiler trying to add the 3 .diff patches to the latest source release 0124 i get this error when i try to compile......

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.
make (e=216): Error 216
mingw32-make: *** [obj/windows/vmame/osd/windows/vconv.o] Error 216
mingw32-make: *** Waiting for unfinished jobs....
mingw32-make: *** [obj/windows/vmame/emu/cpu/m68000/m68kmake.o] Error -99
mingw32-make: *** [obj/windows/vmame/osd/windows/main.o] Error -99

What does this mean?  Thanks.....
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: kingb33 on April 19, 2008, 12:58:03 am
Update: still trying....now with trying to add high score .diffs

Hi! Please help!!!  When I try to compile using headkaze's mame compiler i get errors.  I'm patching using:

hi_124
hi_124u1.diff
hi_124u2.diff

When i patch the 0124 source with the latest 2 updates to the source "without" the 3 high score .diffs it compiles just fine....

Here is the error i get at the end of the compile:

cc1.exe: warnings being treated as errors
src/osd/windows/video.c: In function 'osd_update_hi':
Finished!
0 Hours 16 Minutes and 38 Seconds Elapsed.
src/osd/windows/video.c:233: warning: passing argument 1 of 'winwindow_process_events' makes pointer from integer without a cast
src/osd/windows/video.c:233: error: too few arguments to function 'winwindow_process_events'
src/osd/windows/video.c:234: error: too few arguments to function 'wininput_poll'
src/osd/windows/video.c: At top level:
src/osd/windows/video.c:245: error: redefinition of 'osd_update_hi'
src/osd/windows/video.c:224: error: previous definition of 'osd_update_hi' was here
src/osd/windows/video.c: In function 'osd_update_hi':
src/osd/windows/video.c:254: warning: passing argument 1 of 'winwindow_process_events' makes pointer from integer without a cast
src/osd/windows/video.c:254: error: too few arguments to function 'winwindow_process_events'
src/osd/windows/video.c:255: error: too few arguments to function 'wininput_poll'
src/osd/windows/video.c: At top level:
src/osd/windows/video.c:266: error: redefinition of 'osd_update_hi'
src/osd/windows/video.c:224: error: previous definition of 'osd_update_hi' was here
mingw32-make: *** [obj/windows/mame/osd/windows/video.o] Error 1
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: headkaze on April 19, 2008, 01:16:10 am
You only apply one hiscore patch! The hiscore patch version must match your Mame version. I would recommend not bothering with the "u" versions as that will probably confuse you.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: jasonbar on April 19, 2008, 02:14:08 pm
Headkaze-

Very cool program--I think I've got it all squared away & am ready to try, but have 2 quick questions please:

1 - My MAME PC has a Pentium 4 1.5GHz, according to the System Properties box (right-click on My Computer, select Properties, & there it is).  I see on MC64 1.14's Optimize pull-down that there are 3 options for Pentium 4:
   Pentium 4 (+ 64-bit)   If this is referring to a 64-bit processor vs. 32-bit, then this is not for me
   Pentium 4 (+ SSE3)
   Pentium 4 (- SSE3)   Not quite sure what these are--did a little reading on Wikipedia--how do I determine if my processor has SSE3 or not?

2 - I plan on compiling the program on my laptop, which has a Celeron processor (to keep my MAME machine clean).  Any problem w/ compiling a MAME (or even running it) w/ a processor other than that used in the compiling optimization?


Thank you very much,
-Jason
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: Jdurg on April 19, 2008, 02:44:33 pm
If you P4 is running at 1.5 GHz, then it is probably an early generation P4 and would not have SSE3 optimizations.  So you should compile it with the -SSE3 flag. 

For your question about compiling for a different CPU, I don't think it will cause any issues at all.  The compiling with the optimizations is just compiling the source code wth extra instructions that will make it run a bit better on the system it was designed for.  There should only be issues if you actually try and run it, but none if you just try and compile it.  (64-bit aside.  I do believe you need to have a 64-bit system to compile 64-bit MAME).
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: jasonbar on April 19, 2008, 03:32:06 pm
Thanks, JDurg-

OK, I've moved on & hit a snag--I'm sure this is a basic goof on my part.

Per the readme.txt, I put my preferred MAME 115 source code into C:\MinGW\source\Mame115.

More specificallyh, I downloaded & unzipped the MAME0115s.zip file from http://mamedev.org/oldrel.html.  I unzipped the archive, where I found docs folder, source folder, makefile file, & whatsnew.txt.  I put all 4 of those items into c:\MinGW\source\Mame115.  I found that there was already a patch file in the patch directory: C:\MinGW\patches\hi_114_115_116.diff

I set the pull-down to optimize for Pentium 4 (- SSE3) & hit "Apply Patch"

The patch seems to have worked.

I hit "GO!" & got 3 seconds of compiling before it stopped w/ the following error (copying & pasting the last few lines of text in the Compile Output box):

Compiling src/version.c...
cc1.exe: error: unrecognized command line option "-Wno-unused-functions"
mingw32-make: *** [obj/mame/version.o] Error 1
Finished!
0 Hours 0 Minutes and 2 Seconds Elapsed.



Any ideas?


I tried running it again, and when I ran the patch, it gave me much feedback saying that the patch was already applied (I think this is a "no duh" comment from many of you...).  Should I be erasing some file & starting over each time I try compiling?


Thanks!!!

-Jason
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: headkaze on April 19, 2008, 03:49:16 pm
If your trying to compile Mame version earlier than 0.118u5 you need to set "Disable WError (<0.118u5)".
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: joebells on April 19, 2008, 07:23:58 pm
just wanted to say thanks for this headkaze, I could compile for regular just fine but x64 was over my head. The problem I had asked about earlier was caused because of a bug in mame itself. So thanks again for this program.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: jasonbar on April 23, 2008, 02:17:22 am
If your trying to compile Mame version earlier than 0.118u5 you need to set "Disable WError (<0.118u5)".

Doy on me--thanks not only for your wicked killer program but your patience for my lunkhead questions.  It compiled OK after clicking that box.  I did get a handful of red warnings & some white warning-ish text (sorry, that was 2 days ago...) that suggested everything didn't go perfectly.  Ought I be concerned?  The executable seems to work fine--I tested it briefly on just a few games & they were fine.


Thanks,
-Jason
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: headkaze on April 23, 2008, 05:32:21 am
Doy on me--thanks not only for your wicked killer program but your patience for my lunkhead questions.  It compiled OK after clicking that box.  I did get a handful of red warnings & some white warning-ish text (sorry, that was 2 days ago...) that suggested everything didn't go perfectly.  Ought I be concerned?  The executable seems to work fine--I tested it briefly on just a few games & they were fine.

Compiling older versions of Mame requires you to set the "Disable WError" option because the newer GCC compiler causes errors, and the only way for it to compile is to disable them. So those errors are normal, but it should compile okay without any problems.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: jasonbar on April 23, 2008, 11:32:06 am
Awesome, thank you, Headkaze.  I just compiled 115u2 last night & saw some red text.  Just for fun, here are samples of the 2 last sets of red text warnings in the build.

Thank you,
-Jason


Compiling src/tools/regrep.c...
src/tools/regrep.c:646: warning: 'copy_file' defined but not used


Compiling src/tools/romcmp.c...
src/tools/romcmp.c: In function 'filecompare':
src/tools/romcmp.c:369: warning: 'mask1' may be used uninitialized in this function
src/tools/romcmp.c:369: warning: 'base1' may be used uninitialized in this function
src/tools/romcmp.c:369: warning: 'mask2' may be used uninitialized in this function
src/tools/romcmp.c:369: warning: 'base2' may be used uninitialized in this function
src/tools/romcmp.c: In function 'utf8_main':
src/tools/romcmp.c:698: warning: 'end' may be used uninitialized in this function
src/tools/romcmp.c:698: warning: 'start' may be used uninitialized in this function
Title: Re: Mame Compiler v0.5 Released
Post by: jasonbar on April 24, 2008, 03:22:51 pm
Yes MKChamps diff patches use the "1" key for select. That is a more common key for Mame cabs which is why he chose it. You can always remap the UI_SELECT key to something else.


Howdy-

My 115 & 115u2 compiles MAMEs have been great so far, Headkaze--thank you!!!

I am, however, having trouble returning my Enter key to be the UI_SELECT key after I use TAB to bring up the in-MAME menu.  Digging in to this issue raised a few other questions:

I gather that the UI_SELECT line should be part of the default.cfg file in the cfg directory in mame.  My default.cfg file is only 6 lines long and seems to be mostly comments.  There is no UI_SELECT line to update.  If I delete it & rerun MAME, as suggested in other posts to return things to "normal", then this file gets regenerated as-is (6 lines only).

1 - I have mame32115.exe, mame115optpatch.exe, & mame115u2optpatch.exe all in the same mame folder.  I use mame115optpatch.exe to launch 99.9% of my games, mame115u2optpatch.exe to launch 4 games that don't work in 115, & mame32115u2 for occasional troubleshooting.  My MaLa FE launches a mame.cmd file per SGT's awesome setup post & instructions.  It looks for those 4 problem games' filenames & goes to a launch 115u2 if %1 matches one of those 4 names.  So, I realized that I have but 1 mame.ini file, and 1 mame32ui.ini file (which, strangely, appeared last night...).  Neither of these has the UI_SELECT line item in it.  Where do I find it?

2 - Perhaps more of a concern to me at this point is, am I getting myself into trouble by having multiple mame executables in the same directory?  Are they going to "fight" over the mame.ini file or other files like cfg/default.cfg?  Should I segregate all my various MAMEs?  (I'm going to add 1-2 more to run Phoenix & Turbo shortly).

3 - I realized that I might need to download a new hiscore.dat file.  The one in my mame directory is dated 2/7/06 & says v0.104 & 7.0 near the top, in the commented area.  I just downloaded a new hiscore.dat from http://www.mameworld.net/highscore/download.htm.  Its contents say its latest items are from 17/03.2007.  Is there any compatibility/matching required between a hiscore-patched MAME (I used the 114/115/116 diff when I compiled) & the hiscore.dat file in the mame folder?


Thanks!
-Jason

PS--I realize that this might be borderline off-topic to the compiler thread, but I think 1 & 3 are at least relevant questions!  :]
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: Jdurg on April 25, 2008, 09:51:04 am
The hiscore.diff file you get from here changes the default "Enter" key to the player 1 button 1 key.  This is for use in cabinets.  Unfortunately, this is NOT something that is documented very well.  To correct this, you'll just need to dig through the .diff file and fine the line that changes this key and remove it before applying the patch.  Otherwise, go into the MAME source after the patches are applied and change it back.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: headkaze on April 25, 2008, 10:30:09 am
The hiscore.diff file you get from here changes the default "Enter" key to the player 1 button 1 key.  This is for use in cabinets.  Unfortunately, this is NOT something that is documented very well.  To correct this, you'll just need to dig through the .diff file and fine the line that changes this key and remove it before applying the patch.  Otherwise, go into the MAME source after the patches are applied and change it back.

Can't you just remap UI_SELECT to be TAB again? Why do you have to modify the source to change it back?
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: MKChamp on April 25, 2008, 10:57:51 am
Yep...you can change it back to tab very easily in the in game menu.

On a side note, I took out the defaulting of the enter and select keys starting with hi_124...since this is easily changed and configured...and not really needed to be 'hard coded'.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: headkaze on April 25, 2008, 11:42:37 am
Yep...you can change it back to tab very easily in the in game menu.

On a side note, I took out the defaulting of the enter and select keys starting with hi_124...since this is easily changed and configured...and not really needed to be 'hard coded'.

Yeah good idea, I don't think it's worth the confusion it causes.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: jasonbar on April 25, 2008, 12:26:40 pm
Yep...you can change it back to tab very easily in the in game menu.


Thanks--finally found it in the in-game menus.  Duh on me.  Of course, first I goofed by assigning "None" to that key, so I had to delete my default.cfg & let MAME regenerate it & then do it right.  2nd time's the charm...


MKChamp, I'm running multiple versions of mame executables in the same directory, and they're all using the latest hiscore.dat that I downloaded this week from your site.  Any compatibility/version-matching that I need to do worry about, or will they all work fine w/ the same new hiscore.dat file?


Thanks,
-Jason
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: MKChamp on April 25, 2008, 12:41:25 pm
Actually the hiscore.dat is maintained and hosted by Leezer...not me. The newer hiscore.dat contains more corrections and more game support, so it is always a good idea to go with the latest...
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: jasonbar on April 25, 2008, 05:11:29 pm
Actually the hiscore.dat is maintained and hosted by Leezer...not me. The newer hiscore.dat contains more corrections and more game support, so it is always a good idea to go with the latest...

Thanks--I'll stick w/ the newest one since backward-compatibility isn't an issue.  I also didn't know that you & Leezer weren't the same person.  :)

-Jason
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: alfredbot9000 on April 30, 2008, 07:51:08 pm
Thanks so much headkaze it was super simple to compile mame with your software.

I have a question though.

I used the source code for .0124 and patched it with

.0124u1-4 and then the hiscore.diff

everything worked perfectly by the way and I have the hi score save working, but I did saw a new diff (0124a.diff) on the mame site and wasnt sure if I should have patched it in and if so what order I should have added it in.

The reason I ask is because I am having problems with Donkey Kong audio dropping and I figure my P4 1.8 Ghz should be able to run Donkey Kong.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: Jdurg on May 06, 2008, 08:45:30 am
Bumping this back to the first page.  We really should consider making this a sticky as it is a VERY useful program.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: lettuce on May 11, 2008, 02:37:20 pm
Why am i getting this error message when trying to compile

Compiling Mame...
mkdir.exe -p obj/windows/mame
process_easy: DuplicateHandle(In) failed (e=6)
Finished!
0 Hours 0 Minutes and 0 Seconds Elapsed.
process_easy() failed to launch process (e=6)
mkdir.exe -p obj/windows/mame
Counted 3 args in failed launch
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: lettuce on May 11, 2008, 02:57:00 pm
Fixed, got the latest version (1.14) glad to see it now installs the MinGW folder  :applaud:
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: lettuce on May 12, 2008, 03:46:07 pm
Do u have rename the 'vmame.exe' file to 'mame.exe' As i have removed the standard mame.exe file and replaced it with 'vmame' form up hi score complie, and renamed it to 'mame' but now when i do this and load a rom from mala ig gives me an error message,

Could not execute program 'mame.exe romname' Error code: 193
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: headkaze on May 13, 2008, 12:42:06 am
Do u have rename the 'vmame.exe' file to 'mame.exe' As i have removed the standard mame.exe file and replaced it with 'vmame' form up hi score complie, and renamed it to 'mame' but now when i do this and load a rom from mala ig gives me an error message,

Could not execute program 'mame.exe romname' Error code: 193

You can either rename vmame.exe to mame.exe or open up Mala's config and rename your mame exe to vmame.exe in there.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: lettuce on May 13, 2008, 01:19:40 pm
In the compile options, theres a drop down list where u can select 'AMD64', and then a tick box for' 64-bit processor'. If i have an AMD 64 Athlon 4200+ CPU, which option do i select?, both? Also any other compile options i should have ticked?? Im using Windows XP 32-bit version by the way
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: headkaze on May 14, 2008, 05:01:22 am
In the compile options, theres a drop down list where u can select 'AMD64', and then a tick box for' 64-bit processor'. If i have an AMD 64 Athlon 4200+ CPU, which option do i select?, both? Also any other compile options i should have ticked?? Im using Windows XP 32-bit version by the way

Don't select 64-bit processor if you only have a 32-bit OS. Your only running in 64-bit when you have both a 64-bit CPU and 64-bit OS. I guess you can select the Optimize for "AMD 64", I'm not sure though. I don't know much about the optimization settings for GCC.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: TheShanMan on May 16, 2008, 08:44:42 am
Hi headkaze,

I tried to do a compile last night and when I came back to my computer this morning, it still said it was compiling but it wasn't processing source files anymore. I clicked stop and got an exception. I believe I ran into this before and was able to just compile a second time and it completed. Here are the exception details. Not sure if it's enough to figure it out but figured I'd pass it on just in case. Let me know if I can provide any details that might help you track this one down.

Edit: one important detail I almost forgot: I also got one of those Windows messages stating that it needed to increase the virtual memory size, so perhaps that is the cause. If you don't see anything obvious in your code that might explain it, then let's blame Windows. :)

Quote
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
   at MameCompiler64.Form1.MameExited(Object sender, EventArgs e)
   at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
   at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
   at System.Threading.ExecutionContext.runTryCode(Object userData)
   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
   at System.Windows.Forms.Control.InvokeMarshaledCallbacks()


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///c:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
MameCompiler64
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/Mame%20Compiler%2064/MameCompiler64.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: Cero21 on May 16, 2008, 04:10:33 pm
I feel really dumb...  Where did my files compile to?  I can't seem to find it...

** edit  **  NM.  Found it.  Geez, I really am dumb...
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: Minwah on May 22, 2008, 06:46:28 am
I have only just tried this...and am well impressed.  Thanks once again HeadKaze!  :)
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: IDDQD on June 02, 2008, 05:58:11 pm
This program rules. I am an artard. Thanks a lot for this!
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: Topgun_68 on June 04, 2008, 03:02:23 pm
This program is awesome.

I was able to compile version .125 with u1, u2, u3, hi 125.u3 & bezel diff and everything works flawless. But I wanted to also compile the UI version and store them both in the same folder like Headkaze. I copied the winui folder into "\src\osd\winui" and the mak file into the root. Everything compiled perfect so I copied .exe into my binary folder but it just hangs when I run it. I compiled it about three times because I thought the optimizations we're causing it to fail so I left them all out and did a clean compile but I have the same issue.

I did all clean compiles by deleting all the files and starting fresh. I even tried compiling mame .125 first, then added the Winui files and compiled that with no luck. I also tried it without compiling mame .125 first. I'm out of ideas since it runs fine if I just download the binary but I'd like to get rid of the nags, and have it be able to save hi scores & use CPwizard in conjuntion with the non UI version running through my front end.

Thanks for any info.

P.S: I did read through the entire thread but did't see anyone else having this issue!  ;D

Topgun
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: jasonbar on June 04, 2008, 03:08:44 pm
Without bringing this too far off-topic, what is the bezel diff?  Is there a thread that discusses it?

From what I gather, it's a way to set up CP Wizard to trick MAME into showing a bezel that's actually a control panel description.

I plan on implementing Johnny 5 to display my control panel info upon launching a game from MaLa, but I want to research this topic too before I take the plunge on setting up a control panel viewer.


Thanks,
-Jason
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: Topgun_68 on June 04, 2008, 03:36:09 pm
It is another one of HeadKaze awesome programs and the bezel_124 patch has to compiled into mame to automatically unpause mame when you unpause CPwizard  ;D

You can download it here:
http://members.iinet.net.au/~freeaxs/cpwizard/

Thread to discuss it is here:
http://forum.arcadecontrols.com/index.php?topic=74091.0



Without bringing this too far off-topic, what is the bezel diff?  Is there a thread that discusses it?

From what I gather, it's a way to set up CP Wizard to trick MAME into showing a bezel that's actually a control panel description.

I plan on implementing Johnny 5 to display my control panel info upon launching a game from MaLa, but I want to research this topic too before I take the plunge on setting up a control panel viewer.


Thanks,
-Jason
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: ChoiceStriker on June 05, 2008, 03:43:49 pm
Okay everyone.  I know I'm a noob at this stuff, but obviously I'm doing SOMETHING wrong, probably just using the wrong file somewhere, or getting the steps out of order, because I've tried this like a dozen times and have not been able to get it to output anything correctly for me once.  I'm sure it's my own fault and ignorance...

Can someone please review the following steps I've taken and see if you can tell me exactly where I'm going wrong?  I've included links to the exact files I'm using, in case there's a compatibility issue.  This is exactly what I've done:

1. Download and run MC64Setup.exe to install.
2. Download the latest source for Mame from http://mamedev.org/downloader.php?&file=mame0125s.zip  (MAME 0.125 sources in ZIP format (all platforms)) and unzip enclosed mame.zip file to Mame folder (C:\MinGW\source\Mame0124). This gives me the following folders in C:\MinGW\source\Mame0124: docs, src, and files makefile and whatsnew.txt.
3. Download diff patches from http://mamedev.org/updates/ : (0125u1_diff.zip, 0125u2_diff.zip, 0125u3_diff.zip, 0125u4_diff.zip).  Unzip the enclosed .diff files to C:\MinGW\Patches.
4. Download hiscore.diff file (125u3 - CURRENT) from http://www.rcrsoftware.com/documents/files/hiscore/hi_125u3.txt 
5. Run MameCompiler64.
6. Verify correct directories are selected: MinGW folder = C:\MinGW\ ; Mame Source Folder = C:\MinGW\source\Mame0124.
7. Apply patches in order described: 0125u1.diff, 0125u2.diff, 0125u3.diff, 0125u4.diff, hi_125u3.txt (should I rename this to a .diff?)
8. Click Go.
9. Wait for it to finish compiling, scratch head when nothing appears to have been done.

I'm selecting Pentium 4, +SS3, but I don't think it works if I do -SS3 either (my P4 is a 3.2 GHz).  Everything else is unchecked.  I've tried this both at home and at work, and the only difference at home is that I end up with some .pf files somewhere on my system.  ???

Am I taking unnecessary steps or screwing up the order of things?  Thank you for holding my hand and walking this lamebrain through this stuff. 

Eric
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: MKChamp on June 05, 2008, 04:08:52 pm
Hit refresh on the hiscore thread...uploaded a new diff to work with 125u4. You're just too quick! ;-)
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: ChoiceStriker on June 05, 2008, 04:45:27 pm
Hmm... tried again with the 125u4 ... no joy.  Everything looked good until the very end, when I got this:

src/emu/sound/ay8910.c: In function 'ay8910_set_volume':
src/emu/sound/ay8910.c:749: internal compiler error: in assign_386_stack_local, at config/i386/i386.c:13482
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.mingw.org/bugs.shtml> for instructions.
mingw32-make: *** [obj/windows/mame/emu/sound/ay8910.o] Error 1

Searched everywhere for a mame.exe - nothing.   :dunno
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: headkaze on June 05, 2008, 11:02:10 pm
Hmm... tried again with the 125u4 ... no joy.  Everything looked good until the very end, when I got this:

src/emu/sound/ay8910.c: In function 'ay8910_set_volume':
src/emu/sound/ay8910.c:749: internal compiler error: in assign_386_stack_local, at config/i386/i386.c:13482
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.mingw.org/bugs.shtml> for instructions.
mingw32-make: *** [obj/windows/mame/emu/sound/ay8910.o] Error 1

Searched everywhere for a mame.exe - nothing.   :dunno

You patch Mame up to 0125u4 then you apply hi_125u3. You need to apply the hiscore diff to match your version of Mame. So Mame 0125u4 requires hi_125u4 and Mame 0125u3 required hi_125u3.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: ChoiceStriker on June 06, 2008, 10:58:02 am
Meh. No matter what I try, I get the 'ay8910_set_volume' error I posted above.  Same result both at home and at work.  I swear I'm following the above steps and files to a T.  Has anyone gotten this to successfully compile? 

Thanks for trying to help, MKChamp and headkaze. 
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: Marak on June 12, 2008, 02:19:01 am
Another awesome program.
Thanks so much headkaze  :cheers: :cheers:

Do you have any idea why my newly compiled 0125 will -listxml > file.txt
But when I add patches and compile, the -listxml fails?

Has anybody been able to -listxml with  Mame 0125u4

Title: Re: Mame Compiler 64 v1.12 Released!
Post by: keirondrk on June 12, 2008, 03:20:09 am
Hi there, yeop... there is a problem with clrmame with the last two builds... but I solved the issue with a patch diff I found on mameworld forums which I belive originated from Aaron..

got to leave for work now, but if ya stuck I will try get it to you guys.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: keirondrk on June 12, 2008, 03:26:37 am
arghh found the attach button... hopefully people don't mind me uploading but here is the Fix Diff from Aaron..

shouldn't be any major order really I did 125 all the u's upto 4.. then the fix diff then hiscore all worked fine.. as should doing this diff at the end of the chain...

enjoy!!!..
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: Marak on June 13, 2008, 03:07:00 am
That Got It!

Thanks keirondrk  ;D
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: keirondrk on June 15, 2008, 03:52:45 pm
Hi guys,  :dizzy:

 :cheers:

having my first MAME Compiler errors sadly , since I've attempted these new optimized settings it always does it with this combo...


Compiling Error Clean Source 125u5 and hiscore diff.

using compile options Intel Core2,
64bit Processor , Dual Core, and with or without MAMEUI
both give the error..

untick Dual core and it all works just fine , now here is the strange catch.. retick the dual core option without cleaning up the source leaving the same one that just did a compile and hit compile and last time I tried it did it without error ??...
for both MAME and MAMEUI builds.. odd... !
any clues...

MAME COMPILER LOG BELOW...

Compiling Mame64...
Using Parameters  -j3 ARCHOPTS="-march=pentium-m -msse3" MSVC_BUILD=1 PTR64=1 -f MameUI.mak
MameUI.mak:40: warning: overriding commands for target `vmameui64.exe'
makefile:526: warning: ignoring old commands for target `vmameui64.exe'
mkdir.exe -p obj/winui/vmame
mkdir.exe -p obj/winui/vmame/build
mkdir.exe -p obj/winui/vmame/emu/audio
mkdir.exe -p obj/winui/vmame/emu/cpu
mkdir.exe -p obj/winui/vmame/emu/cpu/adsp2100
mkdir.exe -p obj/winui/vmame/emu/cpu/alph8201
mkdir.exe -p obj/winui/vmame/emu/cpu/apexc
mkdir.exe -p obj/winui/vmame/emu/cpu/arm
mkdir.exe -p obj/winui/vmame/emu/cpu/arm7
mkdir.exe -p obj/winui/vmame/emu/cpu/asap
mkdir.exe -p obj/winui/vmame/emu/cpu/ccpu
mkdir.exe -p obj/winui/vmame/emu/cpu/cdp1802
mkdir.exe -p obj/winui/vmame/emu/cpu/cop400
mkdir.exe -p obj/winui/vmame/emu/cpu/cp1610
mkdir.exe -p obj/winui/vmame/emu/cpu/ds5002fp
mkdir.exe -p obj/winui/vmame/emu/cpu/dsp32
mkdir.exe -p obj/winui/vmame/emu/cpu/dsp56k
mkdir.exe -p obj/winui/vmame/emu/cpu/e132xs
mkdir.exe -p obj/winui/vmame/emu/cpu/f8
mkdir.exe -p obj/winui/vmame/emu/cpu/g65816
mkdir.exe -p obj/winui/vmame/emu/cpu/h6280
mkdir.exe -p obj/winui/vmame/emu/cpu/h83002
mkdir.exe -p obj/winui/vmame/emu/cpu/hd6309
mkdir.exe -p obj/winui/vmame/emu/cpu/i386
mkdir.exe -p obj/winui/vmame/emu/cpu/i8039
mkdir.exe -p obj/winui/vmame/emu/cpu/i8051
mkdir.exe -p obj/winui/vmame/emu/cpu/i8085
mkdir.exe -p obj/winui/vmame/emu/cpu/i86
mkdir.exe -p obj/winui/vmame/emu/cpu/i8x41
mkdir.exe -p obj/winui/vmame/emu/cpu/i960
mkdir.exe -p obj/winui/vmame/emu/cpu/jaguar
mkdir.exe -p obj/winui/vmame/emu/cpu/konami
mkdir.exe -p obj/winui/vmame/emu/cpu/lh5801
mkdir.exe -p obj/winui/vmame/emu/cpu/m37710
mkdir.exe -p obj/winui/vmame/emu/cpu/m6502
mkdir.exe -p obj/winui/vmame/emu/cpu/m6800
mkdir.exe -p obj/winui/vmame/emu/cpu/m68000
mkdir.exe -p obj/winui/vmame/emu/cpu/m6805
mkdir.exe -p obj/winui/vmame/emu/cpu/m6809
mkdir.exe -p obj/winui/vmame/emu/cpu/mb86233
mkdir.exe -p obj/winui/vmame/emu/cpu/mb88xx
mkdir.exe -p obj/winui/vmame/emu/cpu/mc68hc11
mkdir.exe -p obj/winui/vmame/emu/cpu/mips
mkdir.exe -p obj/winui/vmame/emu/cpu/nec
mkdir.exe -p obj/winui/vmame/emu/cpu/pdp1
mkdir.exe -p obj/winui/vmame/emu/cpu/pic16c5x
mkdir.exe -p obj/winui/vmame/emu/cpu/powerpc
mkdir.exe -p obj/winui/vmame/emu/cpu/rsp
mkdir.exe -p obj/winui/vmame/emu/cpu/s2650
mkdir.exe -p obj/winui/vmame/emu/cpu/saturn
mkdir.exe -p obj/winui/vmame/emu/cpu/sc61860
mkdir.exe -p obj/winui/vmame/emu/cpu/se3208
mkdir.exe -p obj/winui/vmame/emu/cpu/sh2
mkdir.exe -p obj/winui/vmame/emu/cpu/sh4
mkdir.exe -p obj/winui/vmame/emu/cpu/sharc
mkdir.exe -p obj/winui/vmame/emu/cpu/sm8500
mkdir.exe -p obj/winui/vmame/emu/cpu/spc700
mkdir.exe -p obj/winui/vmame/emu/cpu/ssp1601
mkdir.exe -p obj/winui/vmame/emu/cpu/t11
mkdir.exe -p obj/winui/vmame/emu/cpu/tlcs90
mkdir.exe -p obj/winui/vmame/emu/cpu/tms32010
mkdir.exe -p obj/winui/vmame/emu/cpu/tms32025
mkdir.exe -p obj/winui/vmame/emu/cpu/tms32031
mkdir.exe -p obj/winui/vmame/emu/cpu/tms32051
mkdir.exe -p obj/winui/vmame/emu/cpu/tms34010
mkdir.exe -p obj/winui/vmame/emu/cpu/tms7000
mkdir.exe -p obj/winui/vmame/emu/cpu/tms9900
mkdir.exe -p obj/winui/vmame/emu/cpu/upd7810
mkdir.exe -p obj/winui/vmame/emu/cpu/v30mz
mkdir.exe -p obj/winui/vmame/emu/cpu/v60
mkdir.exe -p obj/winui/vmame/emu/cpu/v810
mkdir.exe -p obj/winui/vmame/emu/cpu/z180
mkdir.exe -p obj/winui/vmame/emu/cpu/z80
mkdir.exe -p obj/winui/vmame/emu/cpu/z8000
mkdir.exe -p obj/winui/vmame/emu/cpu/z80gb
mkdir.exe -p obj/winui/vmame/emu/debug
mkdir.exe -p obj/winui/vmame/emu/drivers
mkdir.exe -p obj/winui/vmame/emu/layout
mkdir.exe -p obj/winui/vmame/emu/machine
mkdir.exe -p obj/winui/vmame/emu/sound
mkdir.exe -p obj/winui/vmame/emu/video
mkdir.exe -p obj/winui/vmame/lib/expat
mkdir.exe -p obj/winui/vmame/lib/util
mkdir.exe -p obj/winui/vmame/lib/zlib
mkdir.exe -p obj/winui/vmame/mame/audio
mkdir.exe -p obj/winui/vmame/mame/drivers
mkdir.exe -p obj/winui/vmame/mame/layout
mkdir.exe -p obj/winui/vmame/mame/machine
mkdir.exe -p obj/winui/vmame/mame/video
mkdir.exe -p obj/winui/vmame/osd/windows
mkdir.exe -p obj/winui/vmame/osd/winui
mkdir.exe -p obj/winui/vmame/tools
Compiling src/emu/cpu/m68000/m68kmake.c...
Compiling src/osd/windows/vconv.c...
Compiling src/osd/windows/strconv.c...
mingw32-make: *** [obj/winui/vmame/osd/windows/strconv.o] Error -99
mingw32-make: *** Waiting for unfinished jobs....
mingw32-make: *** [obj/winui/vmame/emu/cpu/m68000/m68kmake.o] Error -99
vconv.c
Finished!
0 Hours 0 Minutes and 3 Seconds Elapsed.

 :censored:  :laugh2:
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: headkaze on June 16, 2008, 07:03:54 am
keirondrk: From the readme.txt (easy to miss)

Quote
NOTE: If your doing a Mame64 compile you may have to press GO! again a few times when you get an "Error -99"
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: keirondrk on June 16, 2008, 11:09:56 am
ops sorry about that Mr Kaze... ;) .. I'll give that a go later and see what happens :) thanks..
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: KWeise on June 19, 2008, 12:31:35 pm
Does anyone know if there's a way to check the built version of MAME? I get an exe from compiling, but I want to be sure it's 64 bit and AMD64. I like to know I did it right  ;)
"-help" provides M.A.M.E. v0.125u6, so I at least got that right, but how do I check it was built for my processor? Thanks!
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: Jdurg on June 19, 2008, 08:24:02 pm
Try it out on a 32 bit operating system.  If it runs, then it's 32 bit.  If it never loads, then it's 64 bit.   :cheers:
Title: Re: Mame Compiler 64 v1.15 Released!
Post by: 9innail on July 02, 2008, 07:26:41 pm
Is it possible to compile AgeMame with "Mame Compiler 64"? thanks.  ???
Title: Re: Mame Compiler 64 v1.15 Released!
Post by: Jdurg on July 02, 2008, 09:52:29 pm
I don't see why not.  MAME Compiler 64 is simply a GUI for all the command line prompts that are needed to compile the source code.  As long as the makefile and build instructions are the same, there shouldn't be any problems at all.
Title: Re: Mame Compiler 64 v1.15 Released!
Post by: keirondrk on July 07, 2008, 02:40:29 pm
hey guys compile problem appeared again sadly :(

it's due to the options I select.... because if I do just a bare option compile it works just fine in standard and ui versions....

where as before I am pressing go about three times as mr kaze suggested that worked like a charm upto about 125u7 now no more...

just tried on 126 and no matter how many times I click go it just wont build with

intelcore2, 64bit, dual core, with or without ui...

any clues, or am I the only one heheh... tried removing and reinstalling mame compiler as well...

I tried unticking dual core and that didn't help so its between the 64bit and intel option.

it's strange.... I was hoping it would have all gone away when the source hit 126 but sadly not....

once I've hit go a few times it spends 20mins doing the build like normal and finishes but builds no final exe.


(using the latest 1.15)

[spotted this at the end of my last attempted build if any help.... src\osd\windows\debugwin.c(16) : fatal error C1083: Cannot open include file: 'zmouse.h': No such file or directory
mingw32-make: *** [obj/winui/vmame/osd/windows/debugwin.o] Error 2
Finished!
0 Hours 1 Minutes and 20 Seconds Elapsed.]
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: headkaze on July 07, 2008, 09:54:37 pm
Version 1.16 Released

- Added support for compiling Mame 0126

keirondrk: Your right there was a problem with compiling 0126 which is now fixed in 1.16
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: TheShanMan on July 07, 2008, 10:04:19 pm
Strange. 1.15 worked for me. Maybe it was my options? ??? Athlon/MameUI?
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: keirondrk on July 08, 2008, 04:36:08 pm
thanks !!! ;) will give it a shot but I'm sure it's all working now in your new 1.16...

 :notworthy:

[TheShanMan] yea the problem seemed option specific, it seemed that it was between
my intelcore2 option or my 64bit option...  [e6600 building on vista x64]
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: keirondrk on July 08, 2008, 05:05:10 pm
just a note to say all is fine and dandy....

just built a mame32 fine and now building a standard using my optimizations...

thanks again headkaze.
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: BradC on July 19, 2008, 07:55:42 pm
Thanks a lot headkaze. I just compiled one and it worked great!
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: Dazz on July 19, 2008, 08:13:54 pm
Hey HK,

Can this be used to patch previous versions of Mame?  I just downloaded it and it has 126 in the source  folder, but I am wanting to use 124 for now.
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: headkaze on July 19, 2008, 10:34:57 pm
Hey HK,

Can this be used to patch previous versions of Mame?  I just downloaded it and it has 126 in the source  folder, but I am wanting to use 124 for now.

It can compile most versions of Mame, I've tested as early as 105 and as late as 126.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: mikeveli20 on July 23, 2008, 11:20:44 pm
Don't select 64-bit processor if you only have a 32-bit OS. Your only running in 64-bit when you have both a 64-bit CPU and 64-bit OS. I guess you can select the Optimize for "AMD 64", I'm not sure though. I don't know much about the optimization settings for GCC.

So does this mean that if you want to compile a 64-bit version, you have to do the actual compiling on a 64-bit OS, not a 32?
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: Jdurg on July 24, 2008, 10:09:58 am
Don't select 64-bit processor if you only have a 32-bit OS. Your only running in 64-bit when you have both a 64-bit CPU and 64-bit OS. I guess you can select the Optimize for "AMD 64", I'm not sure though. I don't know much about the optimization settings for GCC.

So does this mean that if you want to compile a 64-bit version, you have to do the actual compiling on a 64-bit OS, not a 32?

Yes, I believe this is the case.  In all honesty, I see no reason to even attempt to compile it on a 32-bit OS since it will not work at all on that OS.  You'd need to copy it over to a 64-Bit OS to even run it, so why not just compile it on your 64-bit Operating System?
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: mikeveli20 on July 24, 2008, 01:29:42 pm
Yes, I believe this is the case.  In all honesty, I see no reason to even attempt to compile it on a 32-bit OS since it will not work at all on that OS.  You'd need to copy it over to a 64-Bit OS to even run it, so why not just compile it on your 64-bit Operating System?

Mostly because I haven't installed my 64-bit OS yet  :P

I'll be doing it shortly, so just wanted to know if I could compile it now or if I'd have to wait.
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: FrizzleFried on July 24, 2008, 07:34:53 pm
I used this compiler for the first time today.   :applaud:

It works awesome!  Even a complete moron shouldn't have too much trouble compiling their own.

I updated to .126u2 today.  Both cabs too.

Question:  I thought I remembered there being an optimization for both AMD Athlon XP and one for AMD Athlon 32... but all I see is XP and Athlon 64.

Title: Re: Mame Compiler 64 v1.16 Released!
Post by: headkaze on July 24, 2008, 08:12:28 pm
Question:  I thought I remembered there being an optimization for both AMD Athlon XP and one for AMD Athlon 32... but all I see is XP and Athlon 64.

I use the same compile options from Mr Do's site: http://www.mameworld.net/mrdo/compile.html

If you find a new option you want to add let me know and I'll put it in :)
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: TheShanMan on July 24, 2008, 11:08:07 pm
Yes, I believe this is the case.  In all honesty, I see no reason to even attempt to compile it on a 32-bit OS since it will not work at all on that OS.  You'd need to copy it over to a 64-Bit OS to even run it, so why not just compile it on your 64-bit Operating System?

I do: I compile mame on my desktop and copy it to my cab. That just works better for me. However, the compiler itself would have to support it for Mame Compiler to be able to do it. It's called "cross compiling" and my guess is mingw doesn't do that, but I could be wrong.
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: Dazz on July 25, 2008, 04:09:12 pm
How long does it normally take to compile using MC64?  I only told it to optimize for Dual Core and added Hi and CPWiz .diffs.  So far we are at 1.5 hours and is currently on Archiving obj/windows/make/libcpu.a...

I don't recall it taking this long when I did a manual compile on v 121.
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: headkaze on July 25, 2008, 04:35:06 pm
It will take the same amount of time as compiling from command line manually.

It takes me about 5 minutes when I compile with my Dual Core and XP 64. It shouldn't take 1.5 hours to compile on a Dual Core. I would try pressing the Stop button and then Go again.
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: TheShanMan on July 25, 2008, 07:01:02 pm
He might not be compiling ON a dual core though. My cab is dual core, but my desktop where I build isn't (my cab is a far better computer). I don't pay a lot of attention because I kick off the compile and walk away, but I think it takes on the order of one hour plus or minus 30 minutes on my desktop (it's a celeron 2.53 ghz w/1gb ram).
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: headkaze on July 25, 2008, 08:00:05 pm
He might not be compiling ON a dual core though. My cab is dual core, but my desktop where I build isn't (my cab is a far better computer). I don't pay a lot of attention because I kick off the compile and walk away, but I think it takes on the order of one hour plus or minus 30 minutes on my desktop (it's a celeron 2.53 ghz w/1gb ram).

The Dual Core option in Mame Compiler is only useful on a Dual Core because it just tells GCC to run on multiple threads to make compiling faster. Although it may give a slight improvement in compile speed on an old HT CPU.

Also I don't think you can cross compile with Mame Compiler because the makefile compiles and executes tools on the fly and they will fail to execute. I think you would have to do a manual compile if you want to cross-compile.
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: TheShanMan on July 25, 2008, 09:23:53 pm
Interesting. I thought that option was for optimizing MAME for dual core environments. I've been building with the dual core option on my celeron with no problem.
:dunno
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: headkaze on July 25, 2008, 09:33:05 pm
Interesting. I thought that option was for optimizing MAME for dual core environments. I've been building with the dual core option on my celeron with no problem.
:dunno

There will be no problem but on a single core CPU it will not improve speed much. HyperThreading CPU's might gain a slight speed improvement.

The Dual Core and Quad Core options add -j3 and -j5 flags respectively which specifies the number of processes to spawn during the compile. I doubt it will make much difference on a celeron.
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: lettuce on July 27, 2008, 07:20:24 am
headkaze, i want to use SailorSat cabmame, but he hasnt complied it for dual core, i have download his diff files for cabmane:

0126_changeres.diff
0126_cleanstretch.diff
0126_defaults.diff
0126_emuspped.diff
0126_frogger.diff
0126_hiscore.diff
0126_redraw.diff
0126_resolution.diff
0126_soundsync.diff

Now it it just a case of using complier64 and ticking the dual core box and just patching each of these files in turn and then after ive patched all 9 diff files complie the whole lot??
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: FrizzleFried on July 27, 2008, 11:08:47 am
Using a lowly Operon 165 I compiled an XP version and A64 version the other day...it took about 18 minutes each.

Title: Re: Mame Compiler 64 v1.16 Released!
Post by: yalborap on July 29, 2008, 08:31:42 pm
I just found this app, and I'm already having an issue.

Is there any way to take the latest version of MAME(0.126), and force it to use DirectInput for all commands so my keyboard-emulating software will work? The option is missing when I start up the Compiler app.
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: headkaze on July 29, 2008, 08:49:07 pm
I just found this app, and I'm already having an issue.

Is there any way to take the latest version of MAME(0.126), and force it to use DirectInput for all commands so my keyboard-emulating software will work? The option is missing when I start up the Compiler app.

I believe that option was removed from the Mame makefile a while ago so it's also been removed from Mame Compiler. Sorry but there is no way to use keyboard emulating software. I wonder why people need to use such software in Mame in the first place since it already has a very configurable input system. Perhaps if you explain why you need to send keys to Mame I can give you an alternative.
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: yalborap on July 29, 2008, 08:52:47 pm
I just found this app, and I'm already having an issue.

Is there any way to take the latest version of MAME(0.126), and force it to use DirectInput for all commands so my keyboard-emulating software will work? The option is missing when I start up the Compiler app.

I believe that option was removed from the Mame makefile a while ago so it's also been removed from Mame Compiler. Sorry but there is no way to use keyboard emulating software. I wonder why people need to use such software in Mame in the first place since it already has a very configurable input system. Perhaps if you explain why you need to send keys to Mame I can give you an alternative.

To quit the app from a gamepad. I can do stuff like get to the configuration menu and pause it, but there's no configurable 'exit' command.
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: headkaze on July 29, 2008, 09:16:52 pm
To quit the app from a gamepad. I can do stuff like get to the configuration menu and pause it, but there's no configurable 'exit' command.

Have you tried mapping your gamepad to "UI Cancel"? Everything is configurable in Mame, check out the "User Interface" mappings.
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: yalborap on July 29, 2008, 09:19:08 pm
To quit the app from a gamepad. I can do stuff like get to the configuration menu and pause it, but there's no configurable 'exit' command.

Have you tried mapping your gamepad to "UI Cancel"? Everything is configurable in Mame, check out the "User Interface" mappings.

Actually, no I had not. Lemme go give that a shot...

EDIT: IT WOOOOOORKS! Thanks, dude, you saved me hours of work! :) I've still got to use the keyboard emulation for my other emulators, but since I run those through MaLa, it works fine. Thanks a bunch.
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: lettuce on July 30, 2008, 12:08:20 pm
headkaze, i want to use SailorSat cabmame, but he hasnt complied it for dual core, i have download his diff files for cabmane:

0126_changeres.diff
0126_cleanstretch.diff
0126_defaults.diff
0126_emuspped.diff
0126_frogger.diff
0126_hiscore.diff
0126_redraw.diff
0126_resolution.diff
0126_soundsync.diff

Now it it just a case of using complier64 and ticking the dual core box and just patching each of these files in turn and then after ive patched all 9 diff files complie the whole lot??

Any help with this, im getting a message when patch some of these diff files say:

"Hunk#1 FAILED at 102." etc

Any help?
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: studmuff on July 30, 2008, 06:24:56 pm
Need help.  I think I'm doing every thing right but I guess I'm not.

I'm using MameUI32.1.0
I download source for MAMEUI32u1
Download 0126u1.dif placed in patches folder

Using Mame Compiler 64 v1.16
C:\MinGW
C:\MinGW\source\MameUI126
C:\MinGW\patches\0126u1.diff

Compile option checked for Mame UI

Apply patch - runs and stops
Go - Compile output reads:

Compling Mame...
Using Paramaters -f MameUI.mak
mingw32-make: MameUI.mak: No such file or directory
mingw32-make: *** No rule to make target 'MameUI.mak'. Stop.
Finished!
0 Hours 0 Minutes and 0 Seconds Elapsed.

I'm sure I'm not doing something right but not sure what.  Sorry for being an idiot but can someone help me.  Any help is greatly appreciated.
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: studmuff on July 30, 2008, 09:01:15 pm
 :timebomb: I'm Frustrated!
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: studmuff on July 30, 2008, 09:32:53 pm
What is a makefile?

mingw32-make: ***No targets specified and no make folder found. stop.

Trying to do u114
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: headkaze on July 30, 2008, 10:16:05 pm
studmuff: You can't just compile MameUI by itself, it is just code that adds a UI to Mame. So you need to copy vanilla Mame source first, then copy over MameUI files. Also read the "Compiling MameUI circa .118.txt" file that comes with MameUI, it tells you where to place the MameUI source.

Quote
\winui directory to \src\osd\winui

mameui.mak to root w/ the core makefile

That means copy the winui files to src\osd\winui where you have extracted vanilla mame source. Then copy the mameui.mak into the root folder (where the vanilla mame "makefile" is located)
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: studmuff on July 31, 2008, 08:46:55 am
studmuff: You can't just compile MameUI by itself, it is just code that adds a UI to Mame. So you need to copy vanilla Mame source first, then copy over MameUI files. Also read the "Compiling MameUI circa .118.txt" file that comes with MameUI, it tells you where to place the MameUI source.

Quote
\winui directory to \src\osd\winui

mameui.mak to root w/ the core makefile

That means copy the winui files to src\osd\winui where you have extracted vanilla mame source. Then copy the mameui.mak into the root folder (where the vanilla mame "makefile" is located)

I'm just making sure I have this right before i do it.  I did just run the regular source of mame126s.exe and it worked with the 0126u1.dif.  I did not swap files so I will redo it but I want to make sure I have this right.  Also I want to use the hi score diff or txt.

1. Again I want to make sure this is right.  I make a copy of the winui files from MAMEUI and I send them to the src/osd/winui in the extracted mame126s.exe source.  Then I copy the mameui.mak into the source folder and replace makefile.  Do I also click the MAMEUI in the compiler.

2. After I apply patch for 0126u1.dif and it finishes, do I then apply the hi score diff/txt or do I press go and then apply the hi score patch.

Again sorry for being an idiot I know this is easy, I'm just use to using the MAME32 and MAMEUI programs.  There just easier for people like me.   :laugh2:
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: headkaze on July 31, 2008, 12:14:57 pm
You don't replace the makefile you need both "makefile" and mameui.mak" in the same folder. Once you have your source extracted correctly apply the 0126u1.diff, then apply the hi_126u1.diff. Make sure the "Mame UI" option is ticked in Mame Compiler then press the Go button.
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: studmuff on July 31, 2008, 12:29:03 pm
Thanks for the reply.  Simplier than I thought.  Thank You.
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: studmuff on July 31, 2008, 06:57:41 pm
You don't replace the makefile you need both "makefile" and mameui.mak" in the same folder. Once you have your source extracted correctly apply the 0126u1.diff, then apply the hi_126u1.diff. Make sure the "Mame UI" option is ticked in Mame Compiler then press the Go button.
Well I finally did compiled MameUI126 the right way!  Thank You headkaze for your program and your help.  :notworthy:  Now I need to start working on CP wizard!  >:D

Thanks Again!
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: retrometro on August 03, 2008, 10:06:50 pm
headkaze, you are the man.   :applaud:

I've compiled mame several times before for the high score patch but for whatever reason had problems w/ my 64bit compile.  Ran your front end and it hosed the first time so i deleted everything and started again just in case the obj dir got messed up.

very cool and everything worked and i didn't even realized you included the hi socre diffs.  you rock


Title: Re: Mame Compiler 64 v1.16 Released!
Post by: Vash on August 07, 2008, 01:13:31 am
Grrr...I've been trying to compile a 64 bit version of MAME with the 64 bit processor and Dual core options selected, as well as the Intel Core2 from the drop down menu.  I'm compiling .119, and the only patch I'm applying is the corresponding hiscore.diff.  The patch applies fine, but I keep getting strange errors (the same ones).  I'm typing this on a different computer, but here's the rough idea:

src\mame\drivers\srmp6.c(101): error C2220: warning treated as error - no 'object' file generated
src\mame\drivers\srmp6.c(101): warning C4318 : passing constant zero as the length to memset
mingw32-make:  ***fobj/windows/mame/mame/drivers/smp6.0) error 2
mingw32-make: *** waitin for unfinished jobs

Finished!

Any help?
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: headkaze on August 07, 2008, 01:17:21 am
Hmm you might want to try setting the "Disable WError" option in Mame Compiler. It's supposed to be for 0.118u5 and lower but I guess it might be the same issue with .119.
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: Vash on August 07, 2008, 01:20:38 am
No good.  Same errors.  I should mention that I successfully compiled this on a 32 bit vista with different settings, but the same folders and directory options, so I'm really at a loss here.  There were two changes between this compile attempt and the last, and those were the operating system (64 bit XP) and the compile options (64 bit processor/dual core).  Thanks for the quick response though =D
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: headkaze on August 07, 2008, 01:53:10 am
No good.  Same errors.  I should mention that I successfully compiled this on a 32 bit vista with different settings, but the same folders and directory options, so I'm really at a loss here.  There were two changes between this compile attempt and the last, and those were the operating system (64 bit XP) and the compile options (64 bit processor/dual core).  Thanks for the quick response though =D

There are probably issues compiling the older Mame versions for 64-bit. I don't know of anyone whos tried doing that actually.
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: Vash on August 07, 2008, 02:24:55 am
This is a bit off-topic then, but if I compiled a newer version of MAME (124 or thereabouts), would I have any major compatibility issues if I were using a 119 romset?
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: headkaze on August 07, 2008, 02:30:05 am
This is a bit off-topic then, but if I compiled a newer version of MAME (124 or thereabouts), would I have any major compatibility issues if I were using a 119 romset?

Yup, you need to match your ROM set with your Mame version I'm afraid.
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: Vash on August 07, 2008, 02:36:22 am
Ugh...Okay, one more question then.  I remember a tool floating around that was used to upgrade romsets from previous versions, but I can't remember the name, and I remember it being fairly convoluted and difficult to use.  Any help in that regard?
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: headkaze on August 07, 2008, 02:40:34 am
Ugh...Okay, one more question then.  I remember a tool floating around that was used to upgrade romsets from previous versions, but I can't remember the name, and I remember it being fairly convoluted and difficult to use.  Any help in that regard?

I think you mean CLRMamePro. I don't think it can upgrade ROM sets though  :dunno

http://www.mameworld.net/easyemu/clrmameguide/clrmame-guide.html
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: scrapple on August 07, 2008, 09:15:32 am
im getting an error:

Compiling Mame...
mingw32-make: *** No targets specified and no makefile found.  Stop.
Finished!
0 Hours 0 Minutes and 0 Seconds Elapsed.
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: Vash on August 07, 2008, 09:33:35 am
Scrapple:

That means you don't have the source code, either at all or in the right place.   Make sure that you've selected the correct folder that houses the source code of the build you're compiling, and make sure that you're not just selecting the folder that says 'src'.  The parent folder of that one should have a makefile file in it, along with something else (I believe).   You want to select the parent folder of 'src'.


I just compiled MAME .120 in 64 bit, so the problem must stem from the .119 source code.  Oh well.  I'll live.
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: Teknique on August 11, 2008, 02:41:32 pm
thanks for your work on this Headkaze, its much appreciated!

Tek
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: lettuce on August 12, 2008, 12:22:18 pm
headkaze, i want to use SailorSat cabmame, but he hasnt complied it for dual core, i have download his diff files for cabmane:

0126_changeres.diff
0126_cleanstretch.diff
0126_defaults.diff
0126_emuspped.diff
0126_frogger.diff
0126_hiscore.diff
0126_redraw.diff
0126_resolution.diff
0126_soundsync.diff

Now it it just a case of using complier64 and ticking the dual core box and just patching each of these files in turn and then after ive patched all 9 diff files complie the whole lot??

Any help with this, im getting a message when patch some of these diff files say:

"Hunk#1 FAILED at 102." etc

Any help?

Any help with this please???
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: lettuce on August 12, 2008, 01:06:09 pm
Just applied patches 0.126u1.diff, 0.126u2.diff, 0.126u3.diff, 0.126u4.diff and Hi_0.126.diff. I noticed that i was getting messages like:

File to patch:
Skip this patch? [y]
Skipping patch.
2 out of 2 hunks ignored
can't find file to patch at input line 74654
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:

Numerous times, is this nomal? Do i have to apply each update or can i just apply 0.126u4 and none of the others?

Also once i applied all above patches and went to complie i got the message:

Compiling Mame64...
Using Parameters  -j3 ARCHOPTS="-march=pentium-m -msse3" MSVC_BUILD=1 PTR64=1
mingw32-make: *** No targets specified and no makefile found.  Stop.
Finished!
0 Hours 0 Minutes and 0 Seconds Elapsed.


What is happening here?



Title: Re: Mame Compiler 64 v1.16 Released!
Post by: headkaze on August 12, 2008, 01:26:31 pm
When you get the "Skip this patch" message that means your applying a patch that has already been applied. I would try again with a fresh extract of the Mame source code.

BTW If you want to force a recompile, then tick the "Clean Compile" option and it will start from the beginning.
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: u_rebelscum on August 12, 2008, 02:14:22 pm
Any help with this, im getting a message when patch some of these diff files say:

"Hunk#1 FAILED at 102." etc

Any help?

The diff files aren't working because one or more of the following:

The diff file version doesn't match the source version you're changing.
The diff files are being applied in the wrong order.
The diff file doesn't have the correct patch options (-p0 vs -p1 is most common wrong option if patching by hand).


If every line in a diff is failings, I'd guess it's the last reason for that diff.  If only some lines fail, it's probably one of the first two.

(Disclaimer: I've never used this app; I patch by hand or batch.)
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: MKChamp on August 12, 2008, 02:41:51 pm
Just applied patches 0.126u1.diff, 0.126u2.diff, 0.126u3.diff, 0.126u4.diff and Hi_0.126.diff. I noticed that i was getting messages like:

...What is happening here?

Also, you are using the hi_126u4 diff and not the hi_126 diff, right?
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: lettuce on August 12, 2008, 04:01:37 pm
^^Yeah, so i need to apply all 'u' updates 1-4 then?
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: lettuce on August 12, 2008, 04:14:57 pm
No luck, still getting this:

Applyinh Diff Patch...
cant find file to patch at input line 4
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
-------------------
|diff -Nru src-old/emu/cheat.c src/emu/cheat.c
|--src-old/emu/cheact.c      2008-07-06 11:49:27.00000000-0700
|+++src/emucheat.c           2008-97-12 13:18:25.00000000-0700
--------
File to patch:
Skip this patch?[y]
Slipped patch.
57 out of 57 hunks ignored
cant find file to patch at input line 684
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:

etc etc etc
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: lettuce on August 12, 2008, 04:36:01 pm
Edit, sorted it out now, had the mame source exe file in the MinGW folder and not the source zip  :angry:
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: MillmoorRon on August 15, 2008, 04:03:40 am
I compiled MAME (& MAMEUI) using MAME Compiler 64 with diff files u1 to u4 (applied in sequence) and the u4 high score diff file.

Compilation was successful and the games run OK, however the high score support is a bit flaky - it only works about 50% of the time.

Is this a common thing or did I maybe do something wrong?
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: Jdurg on August 15, 2008, 03:56:52 pm
It depends on whether or not there is hiscore support for your game in the hiscore.dat file that you have.  Not all games have hiscore support in there.
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: MillmoorRon on August 15, 2008, 04:58:53 pm
Sorry, I wasn't very clear.

On games that DO support the high score dat it randomly works!

eg Asteroids: sometimes it shows my previous scores, other times it doesn't.

Title: Re: Mame Compiler 64 v1.16 Released!
Post by: headkaze on August 16, 2008, 06:32:22 pm
I've updated the first post to include detailed instructions on how to compile Mame/MameUI. It also includes details of how to apply diff's. Should help a few new timers out there :)
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: MillmoorRon on August 18, 2008, 03:59:31 am
That's exactly how I did it.

Tried again (re-downloading all the files from your links) to be sure and also on a different machine at work but I still get the same intermittent effect.

Any suggestions?
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: Jdurg on August 18, 2008, 01:33:44 pm
That's exactly how I did it.

Tried again (re-downloading all the files from your links) to be sure and also on a different machine at work but I still get the same intermittent effect.

Any suggestions?

Are you perchance using cheats?  If any cheat is enabled, ANY of them, the high score will NOT save it at all for that session.
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: MillmoorRon on August 19, 2008, 03:55:27 am
Not using any cheats at all.

It DOES save the high scores but it doesn't always read them back again when the game starts up!

If I restart the game a few times eventually it picks them up.
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: bent98 on August 21, 2008, 02:47:08 pm
Head

Does 1.16 work with Mame 127?

I am getting an error applying a .diff made for 127.
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: headkaze on August 22, 2008, 02:59:37 am
Head

Does 1.16 work with Mame 127?

I am getting an error applying a .diff made for 127.


Just successfully applied hi_127.diff and compiled both a 32 and 64 bit version of Mame 127. So must be some issue your having with that patch.
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: retrometro on August 23, 2008, 03:15:09 am
Summary:  64bit compile with hi_126 exe works except hi scores aren't being read

I've been using a 32bit compile with only the hi_126 diff patch and it's been successfully reading and writing scores.  Just for full info, I'm using blockout.  As you'd expect, running without a hi_126 patch copy of mame, the default high score shows up upon game start.  Switching back to the hi_126 patched mame.exe and everything is fine again.  The time stamps on blockout.hi match when you leave the game so you know the file is being written to.

I've since used the tool to compile a 64bit version with only the hi_126 diff again and the compile completes without error and the resulting vmame.exe runs fine.  Another validation that it's 64bit is that for most games, the game percentage and fps are faster.

However, when I load blockout (as an example, other games also break this way), the default high scores show up as if it was a vanilla / downloaded copy of 64bit mame.  Just in case someone asks, before a compile, I not only delete the obj directory, but everything under mamesrc and I copy everything from the source download zip all over again just to be sure and then hi_126 diff patch again.  I've tried checking only the 64bit checkbox with and without the "optimize for" drop down list box for core2duo.  I've tried those combinations with and without the dual processor checkbox.  I've also tried checking clean compile but to no avail. 

As a control between these 64bit compile runs, I run a 32bit compile (I have all checkboxes turned off) with the hi_126 patch again just to make sure it cranks out a mame.exe that loads the high scores fine for blockout.

What would be very helpful would be if:

1)  Someone can verify that there's no difference between hi score data saved to __.hi files for 32bit or 64bit versions of mame.  That is, the 32bit "created" copy of a ___.hi file can be read/written to from a 64bit mame.exe.

2)  Can someone send me a hi_126 or hi_127 64bit compile of mame so I can test.  (headkaze?)

Thanks!


----
also posted this question to the hiscore_diff thread at:
http://forum.arcadecontrols.com/index.php?topic=64298.msg874466#msg874466


Title: Re: Mame Compiler 64 v1.16 Released!
Post by: lettuce on August 23, 2008, 07:47:01 am
Yeah ive had problems with my comnplied 64bit version not keep high scores also
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: retrometro on August 23, 2008, 10:03:55 am
Yeah ive had problems with my comnplied 64bit version not keep high scores also

Man, I hope this isn't the case.  I can't imagine why the same source wouldn't compile the right way for an application level feature like this.  The only reason I can think of is maybe because of how this hack works.  Since it's reading and writing to specific memory locations, maybe the memory location addresses are different in 64bit.

Just successfully applied hi_127.diff and compiled both a 32 and 64 bit version of Mame 127...


Simple question to headkaze then...  does your 64bit compile of 126 or 127 keep hi scores?


Title: Re: Mame Compiler 64 v1.16 Released!
Post by: retrometro on August 23, 2008, 03:16:46 pm
Update...

It turns out Lettuce had the same problem and found that when he used SailorSat's hiscore patch, 64bit compile worked fine.  So it looks like MKChamp's hiscore plus no-nag patch may need some looking at. 

I tried the same thing using HeadKaze's compiler tool and also got it working with all the checkboxes I need turned on:  64bit, core2duo, dual core.

http://forum.arcadecontrols.com/index.php?topic=64298.msg874592#msg874592


Title: Re: Mame Compiler 64 v1.16 Released!
Post by: retrometro on August 23, 2008, 10:10:55 pm
MKChamp's fixed the 127_diff and 64bit mame is happy w/ high scores again.


Title: Re: Mame Compiler 64 v1.16 Released!
Post by: headkaze on August 24, 2008, 02:23:01 am
I was going to mention that we need MKChamp to check this out, but looks like he's fixed it already  :cheers:
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: MKChamp on August 24, 2008, 08:53:18 pm
Don't mean to cross post...but since this thread and the hiscore thread should probably get married....here's a copy/paste.
(For those reading that have no idea what I am talking about, you can probably just ignore this)

Ok...instead of creating and maintaining separate diffs...I incorporated the ability to turn on/off portions of the patch via the mame.ini file. By default, the patches are enabled. To disable a portion of the patch add the appropiate line to your mame.ini file. Let me know how it works for you guys....

disable_hiscore_patch   1   <- To disable highscore support. Set to 0 or omit it entirely from ini file to enable.
disable_crosshair_patch   1  <- To disable crosshairs off by default. Set to 0 or omit it entirely from ini file to enable.
disable_nagscreen_patch   1  <- To disable removal of nagscreens /white box. Set to 0 or omit it entirely from ini file to enable.
disable_loading_patch   1      <- To disable suppresssion of loading/decypting/etc messages. Set to 0 or omit it entirely from ini file to enable.

Uploaded hi_127a.txt with this in it. If this works out, it'll be in all the future diffs.
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: MillmoorRon on August 25, 2008, 08:00:08 am
hi_127 works OK in 32bit too!
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: Turnarcades on September 05, 2008, 10:43:32 am
I've got a problem compiling MAME 0.103. I've just found this thread so I've posted the error log here already:

http://forum.arcadecontrols.com/index.php?topic=84130.msg880605#msg880605 (http://forum.arcadecontrols.com/index.php?topic=84130.msg880605#msg880605)

Can anyone help?
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: Twin-X on September 06, 2008, 01:41:57 pm
Quote
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 5 Seconds Elapsed.
make (e=216): Error 216
mingw32-make: *** [obj/windows/vmame/osd/windows/vconv.o] Error 216

Well i need some help here. I am trying to compile a 64bit processor core2 dcore marked version. (i read that these options are needed for my e8400 processor)

However i apply 127a diff patch and then click compile and i get above error?

*fixed.

To compile 64bit you need to do this on your 64bit os ;)
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: lettuce on September 07, 2008, 09:02:34 am
Cant seem to complie 127u1 or 127u2 updates which this for some reason get the error message:

mingw32-make: *** [obj/windows/vmame/emu/cpu/drcbex64.o] Error 2
mingw32-make: *** Waiting for unfinished jobs....
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: retrometro on September 07, 2008, 02:22:34 pm
Cant seem to complie 127u1 or 127u2 updates which this for some reason get the error message:

mingw32-make: *** [obj/windows/vmame/emu/cpu/drcbex64.o] Error 2
mingw32-make: *** Waiting for unfinished jobs....

Before retrying, did you at least delete the obj dir or everything in the mamesrc dir first?
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: headkaze on September 07, 2008, 09:01:41 pm
Before retrying, did you at least delete the obj dir or everything in the mamesrc dir first?

If you select the "Clean Compile" option before starting it will delete the obj dir for you.
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: cmoses on September 15, 2008, 11:46:18 am
Sorry if I missed it, but once you compile it and it is done it creates a mame.exe file in your folder.  Do you then copy that mame.exe to where the regular installation is and overwrite the existing mame.exe?  I know that all the regular folders are not created so I wasn't sure.  Also it seems to have also created some .exe files, chdman, jedutil, etc. do you need to do anything with these? 
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: cmoses on September 23, 2008, 12:17:30 pm
Sorry if I missed it, but once you compile it and it is done it creates a mame.exe file in your folder.  Do you then copy that mame.exe to where the regular installation is and overwrite the existing mame.exe?  I know that all the regular folders are not created so I wasn't sure.  Also it seems to have also created some .exe files, chdman, jedutil, etc. do you need to do anything with these? 

Anyone know the answer?  Once complied, what do I need to do?
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: massive88 on September 23, 2008, 12:26:22 pm
Sorry if I missed it, but once you compile it and it is done it creates a mame.exe file in your folder.  Do you then copy that mame.exe to where the regular installation is and overwrite the existing mame.exe?  I know that all the regular folders are not created so I wasn't sure.  Also it seems to have also created some .exe files, chdman, jedutil, etc. do you need to do anything with these? 

Anyone know the answer?  Once complied, what do I need to do?

All you really need for your average Mame-ing, is the Mame.exe

Put it in whatever folder you choose, it does not require any pre-existing install or anything of the sort.  When you first run it, it will create folders that its missing and so on.
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: encom on September 26, 2008, 11:20:16 am
I have a question please.

Can this ap be used to create an updated version of Dos MAME? Currently I'm running DMAME v96 , and have been for a few years , but I'd like to upgrade and try out some of the newer additions to MAME.



Title: Re: Mame Compiler 64 v1.16 Released!
Post by: Havok on September 27, 2008, 02:46:29 am
Hey headkaze - finally took the plunge and tried your app out on my test rig. Nice job.

I still won't forget my manual compiling roots, though.

 ;D
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: headkaze on September 27, 2008, 05:21:49 pm
Hey headkaze - finally took the plunge and tried your app out on my test rig. Nice job.

I still won't forget my manual compiling roots, though.

 ;D

I agree it's definately handy to have the skill to manually compile. I think Mr Do should update his site for instructions on compiling the 64-bit version as I think you can do that now with Visual Studio 2008 Express.
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: Martijn on September 30, 2008, 08:26:17 am
i tried it some times now, still getting errors

can someone compile me a mame0127 u3 and high score patch

optimised for windows xp 32bit and core2duo e8500

please....  :-[
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: FhM on October 05, 2008, 11:35:46 am
I cant seem to find it in this thread again but can you tell me if the following is true:

The optimise dropdown is for the processor optimistations and the cpu entries underneath that are tick boxes just relate to how the compiler is setup eg there is no optimisation for quad core but you can take advantage of it while compiling?
Title: Re: Mame Compiler 64 v1.16 Released!
Post by: headkaze on October 09, 2008, 05:10:06 am
MC64 v1.17 Released

- Now compiles Mame 0127u6 (you must turn on "Disable Warnings as Error" option)
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: Dazz on October 09, 2008, 11:37:15 am
Ok, I am going to give this app another try.  I know HK does some quality stuff, but for some reason I have not been able to get this to work.  I've had to compile the long way, but this looks nice if I can ever get it to work right.

Ok, I think where I get confused is... Is this only for MameUI?  I don't use MameUI, just regular Mame.  I guess I just don't check MameUI, eh?

Alrighty, I think it completed...  I got this error/warning, but I am assuming that is the reason for your post above.

Linking vmame.exe...
dinput.lib(dilib2.obj) : warning LNK4078: multiple '.text' sections found with different attributes (C0500040)


Next question...  If I want to do another compile; what files do I need to remove to start over on a compile?
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: headkaze on October 09, 2008, 11:40:27 pm
Dazz: That dinput.lib warning has been around for a long time and you can safely ignore it.

When you say "start over on a compile" it depends, if you mean the same version of Mame, then use the "Clean Compile" option. If you want to compile a new version of Mame I suggest you create a new folder (in MinGW\source\) and change the folders in MC64 and start a fresh compile from the beginning.
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: DP Louie on October 15, 2008, 12:56:15 am
Headkaze,

I've followed your instructions in the first post, but when I hit the "apply patch" button, I get this error:

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

I have double checked the paths for the everything (minGW, source, diff) and they are all correct.  Any ideas?  I am trying to compile 127u6 with the latest version of Mame Compiler (1.17).  Thanks!  :dizzy:
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: markronz on October 18, 2008, 12:59:07 pm
Hello, I'm new to MAME so I'm not sure how long version 128 has been out, but I was wondering if your compiler is supposed to work with 128 yet.   I tried it today and received these errors at the end:

src/osd/windows/video.c:237: error: redefinition of 'osd_update_hi'
src/osd/windows/video.c:216: error: previous definition of 'osd_update_hi' was here
src/osd/windows/video.c:258: error: redefinition of 'osd_update_hi'
src/osd/windows/video.c:216: error: previous definition of 'osd_update_hi' was here
mingw32-make: *** [obj/winui/mame/osd/windows/video.o] Error 1

Any ideas?

Thanks!
-Mark
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: headkaze on October 18, 2008, 01:20:14 pm
I successfully compiled Mame 128 both 32 and 64 bit versions today with hiscore patch applied without any error.

Your the second person to get that same error compiling 128 though. The only thing I can think of is the patch has accidently been applied twice.

I would delete the source folder and try again I guess?

EDIT: Just an update on the other person who had the same problem, he tried deleting the source folder and comping again and it worked ???
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: FrizzleFried on October 23, 2008, 01:34:41 pm
Is it correct that you have to compile a 64 bit version on a 64 bit OS?  My only 64 bit OS will be my mame rig which is sort of hard to work with at 640x480...
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: FrizzleFried on October 23, 2008, 08:09:24 pm
I am attempting to use Mame Compiler on a Win XP 64-bit OS for the first time.  Unfortunately,  all I am getting is an error that says the program failed to initialize properly.  What might I be doing wrong?
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: headkaze on October 24, 2008, 07:01:24 am
I am attempting to use Mame Compiler on a Win XP 64-bit OS for the first time.  Unfortunately,  all I am getting is an error that says the program failed to initialize properly.  What might I be doing wrong?

You must have the .NET 2.0 Framework or higher installed.
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: FrizzleFried on October 24, 2008, 09:57:49 am
I will double check,  but the version of Window x86 I got slipstreamed everything in up through Service Pack 2....

Just in case,  what are the chances of someone emailing me the compiled .128 exe with HS saves installed?

frizfry(at)gmail.com


Title: Re: Mame Compiler 64 v1.17 Released!
Post by: FrizzleFried on October 24, 2008, 11:01:46 am
Sure enough... no NET 2.0 framework going.  THANKS!


There's one issue resolved...now to work on:

MAMERes not working...MAMEWAH not working...

Title: Re: Mame Compiler 64 v1.17 Released!
Post by: cmoses on October 28, 2008, 03:17:45 pm
Can someone verify options I want to check for compiling?

I have a Pentium D, P4, 2.8Ghz processor, 2GB RAM, Windows XP

I think my only option would be to choose Pentium 4 (+SSE3) in the drop down box, but hoping to verify.

Title: Re: Mame Compiler 64 v1.17 Released!
Post by: Aabra on October 30, 2008, 02:24:03 pm
I received this error while attempting to compile 128.  I'm using a P4 3 ghz processor and had the +SSE3 option enabled but nothing else.  I'm going to try deleting the source and trying again maybe without that option but any help would be appreciated.


Compiling src/emu/sound/ay8910.c...
src/emu/sound/ay8910.c: In function 'ay8910_set_volume':
Finished!
0 Hours 32 Minutes and 59 Seconds Elapsed.
src/emu/sound/ay8910.c:749: internal compiler error: in assign_386_stack_local, at config/i386/i386.c:13482
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.mingw.org/bugs.shtml> for instructions.
mingw32-make: *** [obj/windows/mame/emu/sound/ay8910.o] Error 1


Edit:  I can compile it fine when I don't try to optimize it for P4.  However even when I check Disable Warnings as Error it doesn't work for +SSE3
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: headkaze on November 13, 2008, 02:56:45 am
If you are compiling Mame 128u3 and you get an error regarding "m68kconf.h" read this post from the Mame Worlds forum

Quote from: Aaron Giles
Create an empty file called m68kconf.h in src/emu/cpu/m68000. The -E flag for patch causes it to delete empty files, but in this particular case the file should have been left present but empty because it hasn't been removed from the includes yet.
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: OPM881 on November 18, 2008, 11:12:18 pm
just got this error:
Compiling src/osd/windows/sound.c...
Compiling src/osd/windows/video.c...
src/osd/windows/video.c: In function 'osd_update_hi':
Finished!
0 Hours 13 Minutes and 34 Seconds Elapsed.
src/osd/windows/video.c:231: error: too few arguments to function 'check_osd_inputs'
mingw32-make: *** [obj/windows/mame/osd/windows/video.o] Error 1

any ideas? I made sure i patched with hi_125.diff
I am compiling version 1.25, also applied all 9 patches before the hi patch
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: ideft on December 16, 2008, 11:25:29 pm
does anyone else gets this error?? or knows what it means??

cc1.exe: warnings being treated as errors
src/lib/util/huffman.c: In function 'huffman_import_tree':
src/lib/util/huffman.c:353: warning: passing argument 2 of 'bit_buffer_init' discards qualifiers from pointer target type
mingw32-make: *** [obj/windows/mame/lib/util/huffman.o] Error 1
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: deano728 on December 20, 2008, 03:04:39 am
Add me to the list of not working....

I double checked and even tried re-downloading the files.  There is definitely a problem with 0128 at least on my puter...  I couldn't add any diff file patches and I am certain I followed the instructions correctly.

applying diff patch...
error applying patch.
PatchDiff(): The system cannot find the file path specified.

Any ideas?
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: iano on January 22, 2009, 12:15:20 pm
Hi HK. I'm trying to compile MAME0.129 with MKChamps diff file but i keep getting the same error. I've no doubt that i'm doing something wrong because other people have compiled MAME0.129 without a hitch. Any help would be appreciated.

src/emu/sound/ay8910.c: 751: internal compiler error: in assign_386_stack_local, at config/i386/i386.c: 13482

Please submit a full bug report, with preprocessed source if appropriate.
see<URL: http://www.mingw.org/bugs.shtml> for instructions
mingw32-make: ***[obj/windows/mame/emu/sound/ay8910.o] error 1

I'm using the Pentium 4 +SSE3 option to compile.

Thanks,
ian.

 :)
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: FrizzleFried on January 22, 2009, 01:53:08 pm
Not sure what you're doing wrong but I just compiled an AMD32 version of .129u2 with HS support compiled in without issue.

EDIT: AMD XP version compiled fine as well...


Title: Re: Mame Compiler 64 v1.17 Released!
Post by: MKChamp on January 22, 2009, 02:32:25 pm
Hi HK. I'm trying to compile MAME0.129 with MKChamps diff file but i keep getting the same error. I've no doubt that i'm doing something wrong because other people have compiled MAME0.129 without a hitch. Any help would be appreciated.

src/emu/sound/ay8910.c: 751: internal compiler error: in assign_386_stack_local, at config/i386/i386.c: 13482

Please submit a full bug report, with preprocessed source if appropriate.
see<URL: http://www.mingw.org/bugs.shtml> for instructions
mingw32-make: ***[obj/windows/mame/emu/sound/ay8910.o] error 1

I'm using the Pentium 4 +SSE3 option to compile.

Thanks,
ian.

 :)


Like I posted to you in the other thread...someone had the same issue and the 'solution' was to change your option from +SSE3 to -SSE3. Try that and see if it compiles. Maybe Headkaze will chime in if this isn't the right thing to do.
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: FrizzleFried on January 23, 2009, 10:11:18 am
I DID get an error when I attempted to compile a 64-bit version last night on the arcade cab.  At about 1:39 it errored out.  I tried it twice.

ALSO,  I noticed when I compiled ALL versions that if I clicked DUAL CORE some red error messages would pop up and be ignored and would continue to compile... that said,  it made me nervous for each and I disabled dual core and all compiled as normal (except 64 bit).

I do think i recall reading Smittdog over at MAMEWORLD having issues compiling a 64-bit compile?!

Because it's a "u" release,  I am not stressing,  but I figured I'd mention the problem I had.

.129u2
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: headkaze on January 28, 2009, 02:15:28 am
If you get a warning it will still fail because the makefile is designed to fail on warnings. That is what the "Disable Warnings as Error" option is for. If you select that it will ignore the warning and continue to compile.

I did get a warning compiling 0129u2 but selecting that option and it completed successfully. I did a 64-bit/Intel Core2/Dual Core compile as well as a 32-bit compile. I also applied MKChamp's hiscore patch.

If you compile again just make sure you select the "Clean Compile" option.
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: dbaleckaitis on January 28, 2009, 12:58:52 pm
Just wanted to say thanks.....

This is the first time I have ever been able to compile and it to work.  After trying several times in the past years.   :applaud:  :applaud:  :applaud:

I decided to try again because my new computer is an AMD quad core and I am running XP 64 bit.

I am also happy because I was able to squeak out a few more percentage speed points using a build optimized for my machine rather than the Intel Core 2 optimized MAME that can be had on the MAMEworld forums.
Just one example: "Rival Schools" runs at 86-88%  instead of 82-83% with the Intel Core 2 build.

happy-happy
Dan
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: slapaham on February 04, 2009, 08:52:22 am
Okay... totally new to this! I just want to get rid of those darn nag screens! I'm using v0.84 and following the instructions give by the op, as reading through the first page of the spread implied it should be possible to use this process on old versions. However, the nag screens remain. :(

This may have something to do with me using the wrong .diff file and the wrong UI - as I can't find 0.84 versions anyway... to be honest (and whats probably quite clear) I don't have a clue as to what I'm really doing... could someone do a simpleton's breakdown of what I need to do.

Appreciate the help.
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: cmoses on March 30, 2009, 11:09:04 am
I have compiled MAME before without issue, but am having a problem with the 0130 version.  I am using the latest MameCompliler64 version, I downloaded the source and the update and the MameUI source.  I have MameUI and Disable Warnings as Errors both checked. I apply the patch fine, but when I begin the compile I get the following errors:

MameUI.mak:40: warning: overriding commands for target 'mameui32.exe'
makefile:543: warning: ignoring old commands for target 'mameui32.exe'

It continues to compile but then I get an error that says

Linking obj/winui/mame/osd/winui/mkhelp.exe
obj/winui/mame/ods/winui/mkhelp.exe src/osd/winui/mameui.rc >src/osd/winui/helpids.c
mingw32-make: *** [src/osd/winui/helpids.c] Error 1
Finished!

When I check there is no mameui.exe file created, so it appears to have failed.  Can anyone make any suggestions as to what is causing this?  I have compiled a few versions, but nothing since 0127.  I went back and looked but did not see anything in this thread that seems to help.

Thanks
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: headkaze on March 30, 2009, 02:40:33 pm
Its easy to make a mistake so generally the best thing to do is to start again with an empty source folder. I have successfully compiled Mame 0130 using Mame Compiler so there is no problem there. I haven't tried MameUI though.
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: cmoses on April 02, 2009, 06:24:00 pm
I have tried a few times, each time with a empty source folder.  Each time selected less options until the only one I had was UI checked.  I am hoping to try it on another computer just to see if I get the same issues.

Any chance you can try compiling MameUI?
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: headkaze on April 02, 2009, 11:28:09 pm
Okay just tried and successfully compiled the following in MC64

- Mame 0130u2
- Mame 64 0130u2
- MameUI 32 0130u2
- MameUI 64 0130u2

I did received an "Error 1" when compiling vanilla Mame64 but pressing "GO!" again continued on and completed the compile. I didn't need "Disable Warnings as Error". I optimized for Intel Core2 and set the "Dual Core" option so it used both cores during compile so it's quicker.

It works fine so I would try again and just press "GO!" again if it fails. It should work.
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: redketchup on April 12, 2009, 08:39:51 pm
Hi

Just a little question, just finish to compile mame version 129 and I have a little problem, i don't know if it's related. With my lightgun game, I don't have the red and the blue cross anymore... it reappear when I toggle F1 but when I exit the game and return to it there are not there again.... any idea
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: MKChamp on April 12, 2009, 11:12:01 pm
Hi

Just a little question, just finish to compile mame version 129 and I have a little problem, i don't know if it's related. With my lightgun game, I don't have the red and the blue cross anymore... it reappear when I toggle F1 but when I exit the game and return to it there are not there again.... any idea

That's one of the things the hiscore patch changes. If you want to keep the crosshairs on by default, add the following to the mame.ini file:

disable_crosshair_patch   1
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: redketchup on April 13, 2009, 01:26:08 pm
Thank's It's work

Is it possible to have only the blue crosshair showing up, and keep this configuration when i close mame...
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: MKChamp on April 13, 2009, 05:01:58 pm
Thank's It's work

Is it possible to have only the blue crosshair showing up, and keep this configuration when i close mame...

Actually, starting with MAME 130u3, they made it possible to do alot of crosshair configuring...take a look at the whatsnew txt over at mamedev.org.
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: redketchup on April 13, 2009, 08:31:08 pm
thank's a lot

I just installed version 0.130u3 and everything work like a charm, thank's for your help very appracieted

Gino
Title: Re: Mame Compiler 64 v1.17 Released! - font
Post by: danfman on May 25, 2009, 01:12:05 am
Link
http://forum.arcadecontrols.com/index.php?topic=92673.msg973463#msg973463


I recently upgraded from Mame .126 to the latest .131 including the High score/nag screen patch.  The roms work well, the high scores are retained, the nag screens are gone, but I have 1 problem.

When I bring up the In Game Setup menu to try to change the dip switch settings, instead of seeing the menu I'm use to seeing, all the letters in the words have been replaced by white squares.

So instead of seeing the typical,

Input (general)
Input (this game)

I now see something like,

00000 00000000
00000 00000000000


If you've ever taken a word document with special font and opened it up on a computer without that font loaded you see weird characters.  Other than being unreadable the menu still appears to be functional (i.e. I can enter sub-menus and back out).  This happens with any rom I try.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: gargoyle67 on May 26, 2009, 03:04:44 am
Sorry guys still a little unsure what I missed here,  I patched from u1 to u5 then did the Hi Diff all for mame109.....is there still supposed to be the OK nag screen and game info screen?

If you read learning will come. Like I said forget the "u" versions of Mame. I've updated Mame Compiler 64 and removed the "u" diff's. So uninstall Mame Compiler, download the new version and install it again. Then just download mame109s.zip, extract it to MinGW\source\Mame0109 and hi_109.diff to MinGW\patches. Click the [...] buttons to browse to these folders. Apply the patch, then compile by pressing the GO! button.

Ok I've just read the post's upto page 4, I want to compile a mame version with hiscore support and no nag screens for my cab, I'm running vista 64 with quad core pentium Q6600 on my main compiler system (XP Pro 32bit for my cab).
I'm using mame0130s (command line version) and hi_129.diff to patch, I've pointed MC 64 to C:\MinGW and Source folder to C:\MinGW\Source\Mame 130 and diff file set to C:\MinGW\Patches\hi_129.diff. But every time I hit the apply patch button I get "error applying patch, patch diff (): the system cannot find the path specfied"
This should be the easiest way of making a no nag\hiscore mame ?
Also of note when I downloaded mame0130s.zip and extracted it to my C:\MinGW\Source\Mame 130 dir it created mame.zip which I unziped again to the mame 130 folder which then made build,docs,emu and other folders.
Any pointers to where I'm going wrong, Thanks  :)
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: danfman on May 27, 2009, 12:42:37 pm
Add me to the list of not working....

I double checked and even tried re-downloading the files.  There is definitely a problem with 0128 at least on my puter...  I couldn't add any diff file patches and I am certain I followed the instructions correctly.

applying diff patch...
error applying patch.
PatchDiff(): The system cannot find the file path specified.

Any ideas?

When you install Mame Compiler it loads certain files into the MinGW folder.  You probably cleared the content of this folder.  To resolve just re-install Mame Compiler.
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: gargoyle67 on May 27, 2009, 03:35:34 pm
No all my folders are showing in the MinGW folder and I've done a re-install :banghead: , Looks like a cool programe if only I could get the dam thing to work  :dizzy:
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: gargoyle67 on May 28, 2009, 05:01:22 pm
Anyone ?  :cry:
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: headkaze on May 28, 2009, 07:28:43 pm
Anyone ?  :cry:

Do you have a file called C:\MinGW\bin\patch.exe?
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: gargoyle67 on May 29, 2009, 04:12:22 am
Yup I do, Also of note, Mame source is in c:\MinGW\source\Mame130\
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: headkaze on May 29, 2009, 04:18:27 am
Yup I do.

Perhaps rename your "Mame 130" folder so it's "Mame130" (without the space) and then point MC64 to the new directory.
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: gargoyle67 on May 29, 2009, 05:27:08 am
Thanks headkaze, I've changed a few things about and it's compiling now so fingers crossed :applaud:
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: gargoyle67 on May 29, 2009, 06:29:26 am
Ok it runs for a good while then throws up errors:

src/osd/windows/video.c:237:error:redifinition of 'osd_update_hi'

src/osd/windows/video.c:216:error: previous difinition of 'osd_update_hi' was here mingw32-make:***[obj/window/video.o] error 1

I'm just trying to compile on my cab's machine to see how C64 get's on with winxp
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: gargoyle67 on May 29, 2009, 07:04:01 am
Success ! Thanks headkaze :notworthy:
Just a quick question regarding optimization, I'm runing on an AMD 64 dual core machine running winxp 32bit, what options should I have selected ?
AMD 64 from the dropdown selector and 64bit proccessor + duel core in the tick boxes ?

(I take it I was missing some ms lib file on my vista machine when I was trying to compile on that ?)
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: headkaze on May 29, 2009, 07:55:29 am
Thanks headkaze, I've changed a few things about and it's compiling now so fingers crossed :applaud:

Care to share what you did so it can benefit others?

(I take it I was missing some ms lib file on my vista machine when I was trying to compile on that ?)

I have no idea. Others have tested it on Vista and it works okay for them. If you can shed any light on why it didn't work let me know.
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: gargoyle67 on May 29, 2009, 08:39:42 am
Not sure why it wouldn't compile on my vista machine :banghead:, Only that it came up with the listed errors.
I got it to compile on windows XP Pro without any hassle 1st try, Any answers to my optimize question's ?
Thanks Again :)
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: aevans0001 on May 31, 2009, 10:11:40 pm
Ok I think I know my own answer but can someone please help.... Ok i copiled a version of Mame .128, I would like to upgrade to the newest version.  How do I do it, Do I have to start over and get the new source and diffs and then use the compiler to add the high score and bezel? Or can i just add in the upgrade?
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: Dazz on July 04, 2009, 11:07:11 am
This should really be a sticky thread... one of the most helpful apps around.

BTW - what does this error/warning mean?  dinput.lib(dilib2.obj) : warning LNK4078: multiple '.text' sections found with different attributes (C0500040)
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: rooter on July 08, 2009, 11:01:40 am
Mame Compiler 64 Homepage (http://localhost/Headsoft/index.php?category=mame&page=mc64)

FYI, that link is incorrect.  The correct link is http://headsoft.com.au/index.php?category=mame&page=mc64
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: headkaze on July 08, 2009, 11:39:12 am
Mame Compiler 64 Homepage (http://localhost/Headsoft/index.php?category=mame&page=mc64)

FYI, that link is incorrect.  The correct link is http://headsoft.com.au/index.php?category=mame&page=mc64

Thanks for reporting that I've corrected it now
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: rooter on July 08, 2009, 02:30:33 pm
Add me to the list of not working....

I double checked and even tried re-downloading the files.  There is definitely a problem with 0128 at least on my puter...  I couldn't add any diff file patches and I am certain I followed the instructions correctly.

applying diff patch...
error applying patch.
PatchDiff(): The system cannot find the file path specified.

Any ideas?

When you install Mame Compiler it loads certain files into the MinGW folder.  You probably cleared the content of this folder.  To resolve just re-install Mame Compiler.

I reinstalled Mame Compiler, but I am receiving this error also.  Any other ideas?
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: headkaze on July 08, 2009, 02:42:39 pm
I reinstalled Mame Compiler, but I am receiving this error also.  Any other ideas?

The MinGW folder should be defaulted to C:\MinGW. Check inside C:\MinGW\bin there is a file called patch.exe.

Then check that the patch file your trying to apply exists as well.

Also what Windows version are you using?
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: rooter on July 08, 2009, 03:06:18 pm
I reinstalled Mame Compiler, but I am receiving this error also.  Any other ideas?

The MinGW folder should be defaulted to C:\MinGW. Check inside C:\MinGW\bin there is a file called patch.exe.

Then check that the patch file your trying to apply exists as well.

Also what Windows version are you using?

Yeah, I tried moving that folder because I don't like to clutter up the root of the C: drive.
I moved it back to C:\ and everything was ok.  I am running 64bit Vista and I did have to hit Go 3 times before I got the long compile.  By long, I mean it's taking a while to run, the first few times only took a few seconds.  Should I hit go one more time when it's done just to be safe?

Thanks!
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: headkaze on July 08, 2009, 03:10:07 pm
Yeah, I tried moving that folder because I don't like to clutter up the root of the C: drive.
I moved it back to C:\ and everything was ok.  I am running 64bit Vista and I did have to hit Go 3 times before I got the long compile.  By long, I mean it's taking a while to run, the first few times only took a few seconds.  Should I hit go one more time when it's done just to be safe?

Thanks!

Yeah I don't recommend moving the MinGW folder. Sometimes you have to hit "go" a few times when compiling a 64-bit version. After it's created the Mame exe you don't need to hit go anymore.
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: rooter on July 08, 2009, 03:37:18 pm
Yeah, I tried moving that folder because I don't like to clutter up the root of the C: drive.
I moved it back to C:\ and everything was ok.  I am running 64bit Vista and I did have to hit Go 3 times before I got the long compile.  By long, I mean it's taking a while to run, the first few times only took a few seconds.  Should I hit go one more time when it's done just to be safe?

Thanks!

Yeah I don't recommend moving the MinGW folder. Sometimes you have to hit "go" a few times when compiling a 64-bit version. After it's created the Mame exe you don't need to hit go anymore.

It worked!  Took 19 minutes.  Thanks!
Finally I can track my high scores.  I'm never updating again!
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: alui on July 10, 2009, 04:02:51 pm
Could someone point me to a place where I can download mame and mameui source for older releases?  The particular version I''m interested in is 0.122.  I can find the source at the official mame site.  However, it doesn't have the update sources, and I have no idea where to locate the source for mameui. 

Thanks
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: Dazz on July 18, 2009, 11:48:46 am
New compile of 132u5 with 64 bit & dual core

dinput.lib(dilib2.obj) : warning LNK4078: multiple '.text' sections found with different attributes (C0500040)

Would this warning have anything to do with why I can't get MAME to see my mouse devices or joysticks?
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: headkaze on July 18, 2009, 10:03:55 pm
New compile of 132u5 with 64 bit & dual core

dinput.lib(dilib2.obj) : warning LNK4078: multiple '.text' sections found with different attributes (C0500040)

Would this warning have anything to do with why I can't get MAME to see my mouse devices or joysticks?

The warning is normal and should not cause any problems.
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: zmartin34 on July 20, 2009, 03:41:02 pm
Can someone verify that this is correct before I waste a bunch of time please? I am trying to compile a 64-bit version of cabmame using .132 source and .129 cabmame diff files. I have heard that these diff files still work with .132 source but not sure if they are 64-bit compatible or not.

I keep running into errors with the 0129 changeres diff. Hunks failing (2 of 5). I'm working on a 32-bit machine right now though; not sure if this would be causing it or if I've got the wrong pieces to the puzzle.

Thanks for any help.
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: headkaze on July 20, 2009, 04:22:03 pm
The source code does not change between 32 and 64 bit so applying the patches does not make a difference.

So my guess is you have applied the wrong patch or in the wrong order. If you have any more problems with diff's perhaps try the hiscore diff pinned topic.
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: zmartin34 on July 20, 2009, 04:31:03 pm
Will do, I did several searches and was not able to find anything on cabmame diff order.
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: zmartin34 on July 20, 2009, 07:46:30 pm
opened up the .bat that came with the cabmame diffs and followed the order in the script. Ran the compiler on Vista x64, applied the patches and compiled the software. Worked perfect.

I set the dropdown in the compiler to Intel (+x64). I am running a 3.5 GHZ Wolfdale. I also ticked '64-bit' and 'dual core'. Does this sound right in terms of optimization?

Is there anyway that I can verify that it compiled an x64 version?
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: headkaze on July 20, 2009, 08:04:02 pm
opened up the .bat that came with the cabmame diffs and followed the order in the script. Ran the compiler on Vista x64, applied the patches and compiled the software. Worked perfect.

I set the dropdown in the compiler to Intel (+x64). I am running a 3.5 GHZ Wolfdale. I also ticked '64-bit' and 'dual core'. Does this sound right in terms of optimization?

Is there anyway that I can verify that it compiled an x64 version?

You need to set it to "Intel Core2" in the dropdown list and have "64-bit Processor" and "Dual Core" ticked. How can you tell if it's compiled for 64-bit? The name of the exe will be vmame.exe.
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: zmartin34 on July 20, 2009, 08:49:34 pm
opened up the .bat that came with the cabmame diffs and followed the order in the script. Ran the compiler on Vista x64, applied the patches and compiled the software. Worked perfect.

I set the dropdown in the compiler to Intel (+x64). I am running a 3.5 GHZ Wolfdale. I also ticked '64-bit' and 'dual core'. Does this sound right in terms of optimization?

Is there anyway that I can verify that it compiled an x64 version?

You need to set it to "Intel Core2" in the dropdown list and have "64-bit Processor" and "Dual Core" ticked. How can you tell if it's compiled for 64-bit? The name of the exe will be vmame.exe.

OK I was thinking Core2 was Duo line. Will do, thanks!
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: markronz on July 29, 2009, 09:17:00 am
I am trying to use this tool to compile the latest Mame 133 but am having some problems.   It seems to lock up in the middle of the compile.  I even let it run over night and it still did not finish. 

I downloaded the hi_133.diff patch, and the latest source code for mame 133.  There are no other intermediate diff patches right now either for 133.   

When I compile it, I choose to optimize for "Pentium 4 (+SSE3)", and I tick Dual Core (since I have a pentium D dual core processor), and I tick mameui.

I followed along the guide posted on the Compiler Home page.  The guide references all 126 stuff, so I just replaced 133 stuff and did the same steps.

I've tried doing it without the optimization part and that didn't help either.  I've tried the "Disable Warnings as Error" option and that does not help either.   I look at the status window of the compiler and there doesnt appear to be any errors I can see.  It just locks up in the middle is all.

Anyone have any ideas what I can do to make this work?  Let me know if you need any more info!

Thanks!



Title: Re: Mame Compiler 64 v1.17 Released!
Post by: headkaze on July 29, 2009, 10:04:14 am
You should have it set to optimize for "Intel Core2".
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: markronz on July 29, 2009, 10:16:00 am
Just have two questions...

1.  A Pentium D is considered an "Intel Core2"?

2.  Do I need to compile this on the machine I plan on using it for?   I use my own personal computer that I typically use to compile things, and it's not the computer that has the actual Pentium D in it.  Just wondering if it's ok if I use a different pc to compile or if it has to actually be my mame pc...

Thanks!
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: headkaze on July 29, 2009, 11:19:06 am
1. It seems that the Pentium D is infact the predecessor to the Intel Core 2 line of chips, but the question is what instructions sets do they use? According to Wikipedia the difference is in cache and power consumption. So without someone with more knowledge on the subject I can't say for sure if it will work or not. How about giving it a try and letting us know?

2. You need a 64-bit OS and CPU to compile a 64-bit version but as for different CPU's with the same bitness again I can't say for sure. There is such a thing as "cross-compiling" which allows you to do that but I really don't know if the compilers used in MC can do that. In my experience you can't as it compiles tools on the fly and executes them, so these tools will fail if the CPU does not support the instruction set. I do know you can compile a 32 bit version of Mame on a 64-bit OS/CPU and it works fine, but not a 64-bit version of Mame on a 32-bit OS/CPU.

Best thing to do is give it a try and share your experience with us.


Title: Re: Mame Compiler 64 v1.17 Released!
Post by: markronz on July 29, 2009, 11:51:00 am
Well, the machine I am using is 32bit and also is dual core, but it is Athlon.  My mame machine is a Pentium as I mentioned before.  So I'm not sure what that would mean.  I did give it a shot though...  I picked Intel Core 2 and ticked dual core and mameui

It seemed to get a lot further but it's been running for 16 minutes now and hasnt finished.   Here is an exerpt from the end of the compiler...

Compiling src/osd/windows/output.c...
Compiling src/osd/windows/sound.c...
Compiling src/osd/windows/video.c...
src/osd/windows/video.c:237: error: redefinition of 'osd_update_hi'
src/osd/windows/video.c:216: error: previous definition of 'osd_update_hi' was here
src/osd/windows/video.c:258: error: redefinition of 'osd_update_hi'
src/osd/windows/video.c:216: error: previous definition of 'osd_update_hi' was here
src/osd/windows/video.c:279: error: redefinition of 'osd_update_hi'
src/osd/windows/video.c:216: error: previous definition of 'osd_update_hi' was here
mingw32-make: *** [obj/winui/mame/osd/windows/video.o] Error 1
mingw32-make: *** Waiting for unfinished jobs....


Any ideas on what to do now?
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: headkaze on July 29, 2009, 12:15:51 pm
That looks more like a problem with how you've setup the files to compile not the settings in MC64. I would start from scratch and follow the instructions. If your still having problems try compiling vanilla Mame (no MameUI) as well as no patches and see if you can get that to work. Most probably just a simple mistake your making.
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: u_rebelscum on July 29, 2009, 01:24:48 pm
1. No.  "Pentium D"s are two pentium 4s on one chip.  The brands "Core", "Core 2", and "Core i7" are very different then P4s.  I blame Intel for the confusing brand names: dual core = any CPU chip with two CPU cores on it; Core 2 = a specific CPU brand that comes in single, dual and quad models.  So the setup is correct as you mentioned (http://forum.arcadecontrols.com/index.php?topic=71845.msg997173#msg997173).

2. As headkase said, to compile or run the 64bit version, you need a 64 bit OS.  But besides that, you can compile for any CPU with any CPU.  IOW, compiling a 32 bit mame to be run on a P4 from an athlon is fine, but compiling a 64 bit mame from a 32 bit OS is a no-no.
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: headkaze on July 29, 2009, 10:47:44 pm
I've confused myself with Dual Core and Core 2 before. So Pentium D is just a P4 then, so in that case I would just be careful using "Pentium 4 (+SSE3)" as you may need to select "Pentium 4 (-SSE3)" instead.
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: garnerb350 on August 06, 2009, 09:00:55 am
Headkaze...I need to pick your brain on this one...

Can your Compiler compile Misfitmame? I was talking to MKChamp asking if the "no nag/hi-score diff" would work...

MKChamp...

Sorry if this question is stupid...but I just got Misfitmame (still has the new car scent)...Can this be done also on Misfitmame?  :dunno

(I just got it yesterday...playing D2K...other games eventually)

When i first played it, i forgot all about the nag screen... :hissy:

It *should*...I've never tried it. Easy to do, though. I believe the last time misfitmame was updated was for 127...so...
1) Get the mame source for 127
2) Get the misfitmame source for 127

3) Apply misfitmame source to core mame source
4) Download the hi_127a.txt and patch away!

Let me know if it worked...

I used your compiler on my MameUI v.129...and it worked....Now I am tinkering with this misfit mame...and I feel like i am back at step one trying to figure this mess out....
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: FrizzleFried on August 18, 2009, 10:07:32 am
Welp,   went from .132u2 to 133u2 last night and got an error...something to do with "SPEAKER"... I couldn't capture the error as it was on my arcade cab not my wired PC...

I was attempting to compile a 64 bit version...

...when I backed off to .133 it compiled perfectly (with HS support).   I've not tried .133u1 yet,  but .133u2 crashed with the same error,  about 8 minutes 30-40 seconds in...

...any ideas?
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: FrizzleFried on August 19, 2009, 04:40:39 pm
Found reference to this issue at MAMEWORLD. 

http://www.mameworld.info/ubbthreads/showthreaded.php?Cat=&Number=199408&page=0&view=collapsed&sb=5&o=&fpart=1&vc=1

Title: Re: Mame Compiler 64 v1.17 Released!
Post by: headkaze on August 20, 2009, 05:29:40 am
Found reference to this issue at MAMEWORLD. 

http://www.mameworld.info/ubbthreads/showthreaded.php?Cat=&Number=199408&page=0&view=collapsed&sb=5&o=&fpart=1&vc=1

The equivalent to that is to turn on the "Disable Warnings as Error" option.
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: FrizzleFried on August 21, 2009, 11:34:49 am
Well... I waited for .133u3 to come out and now that it did,  I get a different error only 4 minutes in to the process both with DISABLE WARNINGS on and off.  I think it may be a HS.diff issue though... not 100% sure.
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: MKChamp on August 21, 2009, 02:27:49 pm
Well... I waited for .133u3 to come out and now that it did,  I get a different error only 4 minutes in to the process both with DISABLE WARNINGS on and off.  I think it may be a HS.diff issue though... not 100% sure.


Yep...grab the one for 133u3...
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: FrizzleFried on August 21, 2009, 04:00:16 pm
I can confirm the problem is with the HS.diff not the u3 release. 

I compiled with the HS.diff = crash at about 4:30 in to the compile.

I compiled without the HS.diff = finished compiling ... good to go.

I re-comppiled with the HD.diff (the latest .133 version) = crash at about 4:30 in to the compile.

At least with my rig...
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: FrizzleFried on August 21, 2009, 04:02:28 pm
Damn... I see that a new HS file was added today.  There ya go!  :)

I wish the post would show as updated today in the menu without having to look in to the post...

Title: Re: Mame Compiler 64 v1.17 Released!
Post by: Encryptor on September 21, 2009, 07:55:32 pm
I have an older version of MAME .119 and I want to recompile it. I can get the source files from the mamedev site but they don't list any updates. Any idea where I can get any U files for this version? TIA!


Encryptor
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: headkaze on September 22, 2009, 07:46:19 am
Why get the u versions? Why not just get .120? Or .121 for that matter? Anyway the point is if you want to go for .119 for some reason just get the non u version as they are just updates between .119 and .120.
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: Encryptor on September 22, 2009, 02:30:26 pm
Ok thanks.

Encryptor
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: Kman-Sweden on September 23, 2009, 07:16:40 am
I've been trying to compile a no-nag MameUIFX using this software without success.
Has anyone found a way to do it?

I noticed that the mameui.mak was called mameuifx.mak but it still didn't work after renaming.


--Edit--
Ah got it working. Didn't read close enough at MameUIFX's webpage. Excelent application.  :applaud:

Made a small HowTo for myslef so I don't have to reinvent the wheel again next time. PM me If you have problems compiling MameUIFX using this exelent app.
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: jasonbar on September 27, 2009, 01:26:04 pm
Just another  :applaud: & a bump for this thread for this fine program.  Just compiled 132 w/ the hiscore patch.

Went smoothly & worked great, even for a software klutz like me.

Thanks!
-Jason
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: Encryptor on September 29, 2009, 06:56:11 pm
I  have ver .119. I applied the diffs u1, u2, u3, u4 and hi_119u2.diff. I compiled it with Mame Compiler 64 and it seemed to be going fine until it was done and I got this error. Any ideas?

mingw32-make: *** [obj/windows/mame/mame/video/namcofl.o] Error -1073741819
Finished!
0 Hours 21 Minutes and 38 Seconds Elapsed.

Any help would be greatly appreciated.

Encryptor
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: Kman-Sweden on September 30, 2009, 01:51:14 am
I  have ver .119. I applied the diffs u1, u2, u3, u4 and hi_119u2.diff. I compiled it with Mame Compiler 64 and it seemed to be going fine until it was done and I got this error. Any ideas?

mingw32-make: *** [obj/windows/mame/mame/video/namcofl.o] Error -1073741819
Finished!
0 Hours 21 Minutes and 38 Seconds Elapsed.

Any help would be greatly appreciated.

Encryptor
If you have ver .119. with the diffs up to u4 applied, you need Hi diff to be u4 aswell.
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: MKChamp on September 30, 2009, 12:48:43 pm
Why wouldn't you use one of the stable builds (either 119 or 120)??
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: Encryptor on September 30, 2009, 04:25:36 pm
Why wouldn't you use one of the stable builds (either 119 or 120)??

After I posted my last message I tried that. I used just the .119 source and used the hi_118_119.diff file from the High Score thread and it was taking a long time so I let it run overnight and it was still not done this morning when I got up. I don't know what's wrong with it or what I'm doing wrong.

Encryptor
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: Kman-Sweden on October 05, 2009, 01:16:30 am
Still running?  :dunno  Did you click on "GO"?
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: Encryptor on October 05, 2009, 05:17:42 am
I don't know what the issue is. Maybe something in my pc is conflicting with mame compiler. Yes I clicked the GO button and it ran for over 8 hours. Then I got the latest version of mame and simply tried to apply the hi score diff file and again it ran for over 5 hours before I finally stopped it.  :dunno

Encryptor
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: jasonbar on October 11, 2009, 03:56:56 am
If you P4 is running at 1.5 GHz, then it is probably an early generation P4 and would not have SSE3 optimizations.  So you should compile it with the -SSE3 flag.


Howdy-

Well, I've "upgraded" my MAME PC from a P4 1.5GHz to a P4 1.8GHz!!! :o

(don't laugh...it was free, like the other one...)

Just a sanity check to confirm that this old P4 still probably doesn't have SSE3, so I should still use my MAME compiles optimized with -SSE3, yah?

Thanks,
-Jason
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: Kman-Sweden on October 11, 2009, 11:02:28 am
If you P4 is running at 1.5 GHz, then it is probably an early generation P4 and would not have SSE3 optimizations.  So you should compile it with the -SSE3 flag.


Howdy-

Well, I've "upgraded" my MAME PC from a P4 1.5GHz to a P4 1.8GHz!!! :o

(don't laugh...it was free, like the other one...)

Just a sanity check to confirm that this old P4 still probably doesn't have SSE3, so I should still use my MAME compiles optimized with -SSE3, yah?

Thanks,
-Jason
I'm 99,9% sure it's still not a SSE3. I have a 2,8Ghz P4 and its still a "Northwood" and does not have SSE3. It has SSE2.
Download this little app and have a look. http://www.cpuid.com/cpuz.php (http://www.cpuid.com/cpuz.php)
After you've installed it you start it up and on the first tab CPU you'll have the information (or not) after whe line Intructions:
But to save you some time... No it's still not a SSE3 processor.
Title: Re: Mame Compiler 64 v1.12 Released!
Post by: jasonbar on October 11, 2009, 11:08:53 am


Thanks!

-Jason
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: Huggybaby on October 31, 2009, 11:24:40 am
The Dual Core and Quad Core options specify the number of processes spawned during compilation, so they can really speed up the compiling process.

Question: Does using different compile options result in the exact same mame.exe? In other words they only affect how efficiently the same mame.exe is compiled?

Or, do the different options produce different mame.exe's optimized somehow for different processors and instruction sets?

Also, is there ever a reason NOT to use the Disable Warnings as Error option?

<edit> Well, after lots of compiling, it appears that the different compile options affect not only the compiling process, but also the end result. So if I compile a quad core version, the compiler makes a quad core mame, and uses four cores to do it. That's pretty clever but I wonder if they could be separated, because if I compile a single core version on my quad core machine, my four cores are not fully utilized.

Compiling Mame UI 134u3 on an Intel Core 2 Quad Q9550 2.83GHz
Settings, Time, File Size, crc32

None = 13:01  35,594,752   ccedfe67

None plus Dual Core = 4:31  35,594,752   115225d3

None plus Quad Core = 3:44  35,594,752   2e1b6b89

None plus Dual Core AND Quad Core = 4:38  35,594,752   f609c7b0

Intel Core 2 = 13:44  35,793,408   730d53f2

Intel Core 2 plus Dual Core = 4:49  35,793,408   e9e74139

Intel Core 2 plus Quad Core = 3:56  35,793,408   da1be89b

Intel Core 2 plus Dual Core AND Quad Core = 4:49  35,793,408   c2c43672

Title: Re: Mame Compiler 64 v1.17 Released!
Post by: jasonbar on November 12, 2009, 11:44:13 pm
Howdy Headkaze-

I've got a compiling but that's vexing me.

I'm compiling 133 (because 132 has some vertical racing games with the hi/lo shifter stretched to a horizontal aspect ratio).

I patched with MKChamp's hiscore patch.

Patch applies OK.

I have Pentium 4 (-SSE3) & "Disable Warnings as Error" selected.  After I hit "GO!", after 3 minutes & 1 second, it chokes.  I'll copy & paste the last several lines of text.

Got an idea of what's wrong?

Thanks,
-Jason


[Edit: I get the same error when compiling without using the hiscore patch, but 31 seconds earlier]


Linking obj/windows/mame/build/verinfo.exe...
Compiling src/version.c...
Compiling src/mame/mamedriv.c...
Compiling src/mame/drivers/albazc.c...
Compiling src/mame/drivers/albazg.c...
Compiling src/mame/drivers/rmhaihai.c...
Archiving obj/windows/mame/mame/alba.a...
Compiling src/mame/drivers/ace.c...
Compiling src/mame/drivers/clayshoo.c...
Archiving obj/windows/mame/mame/alliedl.a...
Compiling src/mame/drivers/alpha68k.c...
Compiling src/mame/video/alpha68k.c...
Compiling src/mame/drivers/champbas.c...
Compiling src/mame/video/champbas.c...
Compiling src/mame/drivers/equites.c...
Compiling src/mame/video/equites.c...
Compiling src/mame/drivers/meijinsn.c...
Compiling src/mame/drivers/shougi.c...
Archiving obj/windows/mame/mame/alpha.a...
Compiling src/mame/drivers/alg.c...
Compiling src/mame/machine/amiga.c...
Compiling src/mame/audio/amiga.c...
Compiling src/mame/video/amiga.c...
Compiling src/mame/video/amigaaga.c...
Compiling src/mame/drivers/arcadia.c...
Compiling src/mame/drivers/cubocd32.c...
Compiling src/mame/machine/cubocd32.c...
Compiling src/mame/drivers/mquake.c...
Compiling src/mame/drivers/upscope.c...
Archiving obj/windows/mame/mame/amiga.a...
Compiling src/mame/drivers/86lions.c...
Compiling src/mame/drivers/caswin.c...
Compiling src/mame/drivers/aristmk4.c...
Compiling src/mame/drivers/aristmk5.c...
Compiling src/mame/machine/archimds.c...
Archiving obj/windows/mame/mame/aristocr.a...
Compiling src/mame/drivers/atarigx2.c...
Compiling src/mame/video/atarigx2.c...
Compiling src/mame/drivers/arcadecl.c...
Compiling src/mame/video/arcadecl.c...
Compiling src/mame/drivers/asteroid.c...
Compiling src/mame/machine/asteroid.c...
Compiling src/mame/audio/asteroid.c...
Compiling src/mame/audio/llander.c...
Converting src/mame/layout/atarifb.lay...
mingw32-make: *** [obj/windows/mame/mame/layout/atarifb.lh] Error -1073741790
Finished!
0 Hours 3 Minutes and 1 Seconds Elapsed.
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: jasonbar on November 16, 2009, 01:20:16 pm
Boy, my Norton Internet Security better be doing a really good job of protecting my computer, if I'm going to have to put up with it blocking my attempts at compiling MAME...   :(

I disabled every last portion of Norton Internet Security, unplugged my laptop from the internet, & ran MAME Compiler 64.

133 w/ the hiscore patch compiled perfectly.


Thanks,
-Jason
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: speedklz on November 20, 2009, 10:20:00 pm
Where are there any plus diff`s for version .133... I would like to compile a 64bit verson of plus without the nags screens?
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: Cakemeister on December 20, 2009, 01:24:31 pm
The installation assumes that the mingw directory is on drive C. Mine is not. No big deal, because the app itself doesn't make that assumption.

The generic compiler seems to work okay, but I get a compiler error when the 64 bit processor, AMD64 optimizing, and dual core options are set.

Compiling src/osd/windows/main.c...
mingw32-make: *** [obj/windows/mame/osd/windows/verinfo.o] Error -99
mingw32-make: *** Waiting for unfinished jobs....
vconv.c
mingw32-make: *** [obj/windows/mame/osd/windows/main.o] Error -99
Finished!
0 Hours 0 Minutes and 0 Seconds Elapsed.

Title: Re: Mame Compiler 64 v1.17 Released!
Post by: Huggybaby on December 20, 2009, 03:38:16 pm
Like the main page says:
Quote
If your doing a Mame64 compile you may have to press GO! again a few times when you get an "Error -99"
You have to keep hitting the GO button until it works, I think it takes three times.
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: Garetmax on January 10, 2010, 07:21:24 pm
Hi,

This is my first time compiling and the nag screens still show.  I guess I don't really know what the nag screens are for sure.  After compiling when you load a game, is it supposed to stop at the main screen and not show any others? 

Right now, if its the first time I go in a game, a warning screen comes up at which point I have to do a left and a right.  If I go into that game again, the warning screen is gone but a game information screen comes up.  Is this normal?

I compiled the latest .136 and followed Headkazes guide with the exception of using mameui.

I applied the hiscore diff patch and the compiling went through fine although it took about 1.5 hours.

I put in the hiscore.dat and all of the compiled exe files into the mame folder and then made a subfolder hi but this doesn't seem to have worked. ???

Thanks,
Scott
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: Garetmax on January 10, 2010, 10:28:58 pm
I finally got it working. :)

I'm not sure how I fixed it but I recompiled again with HeadKazes and this time there was hiscore stuff in the mame.ini file which wasn't there before when it wasn't working.

Then I went to the command line and tested and it worked.
Then I went into Mala and it wouldn't work until I unchecked using CPWizard for the control panel viewer.
Once I did that it worked.
I definitely want to add the CPWizard back in so I need to test some more, but I'm out of time.

Scott
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: FrizzleFried on January 17, 2010, 10:00:01 am
Evidently some changes were made in compiling "tool chain" whatever that means with the .136u1 release...

Will MAME Compiler still work or will there be an update necessary?
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: Kman-Sweden on January 17, 2010, 12:14:30 pm
Probably not, but I'm guessing he'll have a new version out any day now.  ;D
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: headkaze on January 17, 2010, 06:15:34 pm
I will update this soon..
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: Yoeddy1 on January 17, 2010, 08:58:41 pm
Could somebody please email or PM me the hi_136.txt file?  It looks like the site to grab it from has been suspended.

Thanks,
yoeddy1@cableone.net
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: MKChamp on January 18, 2010, 01:53:04 am
This thread should be a sticky....obviously...it's got over 50000 views.
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: shimoda on January 20, 2010, 10:40:09 pm
I will update this soon..

Looking forward to it, tried to figure out the new tools, but somehow became confused...  Thanks for a great app HEadKaze, apparently others like it too! :applaud:
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: Jefferson on January 24, 2010, 07:18:41 pm
Thanks so much to headkaze and to this thread... I had compiled following Mr. Do's instructions, finding their mamedev linked files had changed, and thus instructions had to be... I had gotten it working though just by guessing and checking. It saved mspacman and galaga scores, but I noticed SFII would just go to black screen and quit. Same with all capcom fighters. and Burgertime. Ugh.

Then I walked thru your program instructions from scratch, and caught a snag when I pointed to a brand new empty C/mingw. Then I pointed it to the c/mingw from my failed Mr Do compile (made additions per your instructions)... and it worked! All games enabled! Looking back I learned that my Mr. Do-instructed compile was going off of .128 source (thus my .135 werent all working apparently)

The weekend wasn't a total failure! Thanks dudes!
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: Yoeddy1 on January 24, 2010, 10:12:32 pm
So this is strange.  I just compiled 0.136 and selected C2D, 64 bit, annoying intro screens and high scores.  Everything is working great with high scores now!  I played all sets of Capcom Bowling and entered high scores for each game.  I exited the games after entering the high scores.  When I re enter those games, I get a black screen, but I can hear the sound in the background.  If I delete the nvram files and cfg files for each of those games, I can enter, see and play the games again...until I enter my initials for a high score.  Then it's back to black screen on re-entry.  This doesn't happen with any other games that I have played so far.  Just Capcom Bowling.  Any ideas?
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: FrizzleFried on February 06, 2010, 10:44:11 am
Any word on an update?

I feel so naked without this app...
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: headkaze on February 06, 2010, 11:09:16 am
Any word on an update?

I feel so naked without this app...

It still compiles the latest version though doesn't it? They have added a GCC 64-bit compiler but MameCompiler uses the Microsoft 64-bit compiler. I'm pretty sure it should still work okay. I doubt there will be any difference between the performance of using the different compiler. Anyway I've been a busy lately but will look into it..
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: Eddie_Brock on February 07, 2010, 12:31:15 pm
Is it possible to request a 0.136 version of MAME without nagscreens and HiScore enabled?

I've finally got my mame working the way I liked, I tried Mame UI and MameUIFX with no success, and the thought of compiling my own version seems a bit daunting, to say the least...
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: ratsflif on February 07, 2010, 04:15:00 pm
No, it does not work with the newest mame.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: headkaze on February 08, 2010, 01:31:02 am
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 (http://www.mameworld.info/ubbthreads/showflat.php?Cat=&Number=211369))

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.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: Huggybaby on February 08, 2010, 02:19:42 am
Wow, this is really good news, thanks a million headkaze. :applaud:

<edit> Just compiled a 64 bit version. It auto-detected my quad core and compiled without any error -99's!

<edit> Well, it compiled a regular version of mame, but I had Mame UI selected...can someone else verify?
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: shimoda on February 08, 2010, 07:12:03 pm
Thanks HeadKaze!  I haven't tried it yet, but I will later and post some feedback!  Thanks again!
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: headkaze on February 08, 2010, 08:32:04 pm
<edit> Well, it compiled a regular version of mame, but I had Mame UI selected...can someone else verify?

I have no tested with MameUI yet, so I would like feedback on this too.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: Huggybaby on February 09, 2010, 02:48:34 am
Over at PD, YountMJ said:

Quote
I got the same results as you, huggybaby.  No mameui.exe to be found, only the command line version of mame64.exe...  which does indeed work, but not what I was hoping for.
Using Parameters  OSD=windows TARGETOS=win32 -j3 ARCHOPTS=-march=athlon64 PTR64=1 -f MameUI.mak
MameUI.mak:40: warning: overriding commands for target `mame64.exe'
makefile:648: warning: ignoring old commands for target `mame64.exe'

The rest of the output was pretty and green, and ran just as smoothly as when I ran it without the 'MAME UI' option enabled.

EDIT:  I'm not sure where the 'TARGETOS=win32' came from.  The '64-bit Processor' option was selected.

I took mine off Auto and specified a Core 2 just to see if I could force the issue, here are my two errors:

Using Parameters  OSD=windows TARGETOS=win32 -j5 ARCHOPTS=-march=core2 PTR64=1 -f MameUI.mak
MameUI.mak:40: warning: overriding commands for target `mame.exe'
makefile:542: warning: ignoring old commands for target `mame.exe'

I had 64 bit processor checked but I get "overriding commands for target `mame.exe'" while YountMJ gets "overriding commands for target `mame64.exe'".
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: headkaze on February 09, 2010, 03:28:45 am
I see what is going wrong here. For some reason the MAME makefile is not detecting a Windows machine (ifeq ($(OS),Windows_NT) is false) so it attempts to build an sdl version. To fix that I explicitly added OSD=windows to the build. When compiling WinUI the MameUI.mak is supposed to override MAME's default makefile by changing it to OSD=winui. So what I've done is change that again when selecting WinUI from the options.

I will upload the full package again in a minute, but in the meantime you can copy over your MameCompiler64.exe with the one attached. This should work now  :cheers:
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: Huggybaby on February 09, 2010, 04:44:36 am
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.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: headkaze on February 09, 2010, 06:52:56 am
It compiled fine for me. I would delete your Mame source and try again from the beginning.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: Huggybaby on February 09, 2010, 04:39:02 pm
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.  :dizzy:
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: u_rebelscum on February 09, 2010, 04:57:26 pm
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+....
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: Huggybaby on February 09, 2010, 04:59:08 pm
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.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: u_rebelscum on February 09, 2010, 06:51:32 pm
Agree. 

FWIW, I looked over at mameworld, and one of the bigger MameDev said that gcc 64 bit is "significantly faster" than MS compiler (http://www.mameworld.info/ubbthreads/showthreaded.php?Cat=&Number=211493&page=&view=&sb=5&o=&fpart=1&vc=1).  surprised but good to hear. 

But I'd like some hard numbers, dang it. :badmood:  ...  ::)  ...  8)
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: gargoyle67 on February 13, 2010, 06:52:35 am
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  :cry:
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: headkaze on February 13, 2010, 07:18:48 am
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  :cry:

You can Download Mame Compiler 64 1.17 from here (http://headsoft.com.au/download/mame/MC64Setup117.exe)  :cheers:
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: Necro on February 13, 2010, 11:14:54 am
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! :)
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: gargoyle67 on February 13, 2010, 04:27:12 pm
Thank you headkaze  :laugh: :applaud:
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: Huggybaby on February 13, 2010, 04:32:16 pm
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.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: headkaze on February 13, 2010, 05:58:47 pm
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 (http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx), 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.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: Huggybaby on February 13, 2010, 06:35:17 pm
Headkaze, any chance of adding a MS/GCC compile option? If it's a lot of work forget it of course.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: Necro on February 13, 2010, 07:53:14 pm
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.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: Harakiri on February 17, 2010, 07:02:59 pm
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:

(http://img694.imageshack.us/img694/1194/patchingerror.gif)

(http://img269.imageshack.us/img269/259/compileerror.gif)

</edit>


Help...  :'(
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: headkaze on February 17, 2010, 09:16:45 pm
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 (http://forum.arcadecontrols.com/index.php?topic=64298.0) 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 (http://mamedev.org/release.html) and extract to C:\MinGW\source\MameUI0136u3
4. Download the updates from here (http://mamedev.org/updates.html) (0136u1_diff, 0136u2_diff and 0136u3_diff) and extract them to C:\MinGW\patches
5. Download MameUI source from here (http://www.mameui.info/) 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.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: Harakiri on February 18, 2010, 12:17:10 am
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...  :-\
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: iAtoria on February 19, 2010, 09:26:14 am
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?
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: headkaze on February 19, 2010, 09:38:50 pm
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.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: iAtoria on February 24, 2010, 12:10:42 pm
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?
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: Huggybaby on February 24, 2010, 02:59:54 pm
Yes, it only works with 136u1 and up.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: iAtoria on February 25, 2010, 09:21:16 am
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.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: headkaze on February 25, 2010, 09:55:58 am
I need to put this in a more prominate place but you can download MC64 1.17 from here (http://headsoft.com.au/download/mame/MC64Setup117.exe). LOL @ humping my leg.. well comon then, start the humping  :laugh2:
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: brian_hoffman on February 25, 2010, 10:55:10 am
If you could make this happen I will hump your leg up and down the street.


LOL
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: iAtoria on February 25, 2010, 06:25:57 pm
 :banghead:
^--This is the closest thing to a hump emote thanks headkaze
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: smalltownguy on March 02, 2010, 10:25:37 pm
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.

Title: Re: Mame Compiler 64 v1.18 Released!
Post by: Haterot on March 04, 2010, 12:14:26 pm
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 (http://www.mameworld.info/ubbthreads/showflat.php?Cat=&Number=211369))

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?
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: headkaze on March 04, 2010, 01:13:08 pm
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 $@
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: Haterot on March 04, 2010, 01:50:32 pm
Once again HK, thanks. Worked like a charm first go through.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: Harakiri on March 05, 2010, 05:08:14 am
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.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: dasfool on March 05, 2010, 08:51:25 am
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.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: headkaze on March 05, 2010, 08:59:14 am
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.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: Harakiri on March 05, 2010, 09:37:13 am
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.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: headkaze on March 05, 2010, 10:26:08 am
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?
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: Harakiri on March 05, 2010, 11:31:15 am
I get this:

(http://img641.imageshack.us/img641/6531/mameuierror.png)

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.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: headkaze on March 05, 2010, 03:19:54 pm
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.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: Huggybaby on March 07, 2010, 10:51:22 am
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.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: 200X on March 08, 2010, 07:47:41 am
I got one error

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

But then it finished. So is that bad?
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: 200X on March 08, 2010, 08:53:19 am
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?
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: dasfool on March 09, 2010, 02:39:50 am
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.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: 200X on March 09, 2010, 02:54:23 am
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?

I compiled mine on another computer and it worked.

But when I try to start a game by double-clicking it, it crashes. If I right-click and choose play (whatever game), then it works. But through Maximus, it won't work. I have basically tried all the same settings as the old version. What could be the problem?
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: Harakiri on March 09, 2010, 03:21:38 am
I compiled MAMEUI and i was experiencing random crashes then i tried this setup:

http://forum.arcadecontrols.com/index.php?topic=84933.msg1067238#msg1067238 (http://forum.arcadecontrols.com/index.php?topic=84933.msg1067238#msg1067238)

It works flawlessly.

Title: Re: Mame Compiler 64 v1.18 Released!
Post by: raungst on March 09, 2010, 11:28:39 am
I got one error

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

But then it finished. So is that bad?

I'm having a similar issue. Though mine is:

make: *** [obj/windows/mame/mame/drivers/megadriv.o] Error 1

I'll try on a different computer tonight.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: Yoeddy1 on March 12, 2010, 01:32:02 am
This running ok with .137?  Just checking to see if anyone has used it yet with the new release.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: FrizzleFried on March 13, 2010, 11:08:48 am
I got one error

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

But then it finished. So is that bad?

I'm having a similar issue. Though mine is:

make: *** [obj/windows/mame/mame/drivers/megadriv.o] Error 1

I'll try on a different computer tonight.

I got a similar error... 18 minutes and 48 seconds in to a regular MAME 32-bit compile.

make: ***[obj/windows/mame/mame/video/cheekyms.o]Error 1

EDIT: I am trying a 64bit compile on a Core2Duo rig now (different computer)...I'll report back.

Welp,  the 64 bit compile on the Core2Duo rig compiled fine,  but the 32 bit compile on the AMD Opteron (AMD32) failed with the above error.  Same procedure executed.  Frankly,  I don't really care as I was primarily looking to upgrade the Horizontal MAME (64-bit)...


Title: Re: Mame Compiler 64 v1.18 Released!
Post by: Havok on March 15, 2010, 12:45:23 am
Just compiled Mame64 on a Core 2 Duo running Windows 7 - works fine, took 11 minutes...
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: cmoses on March 15, 2010, 04:31:36 pm
Trying to compile and got the following error

make: *** [obj/windows/mame/emu/uismall.fh] Error 1073741819

Any ideas?  Just a standard compile no options checked.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: dwight01 on March 16, 2010, 04:55:06 pm
I too am seeing similar errors and have tried compiling 0.137 using mame compiler 64 v1.18 on a Windows 7 Core i& machne and a core2duo.  The 64 bit version compiles without a hitch and works fine.  I managed to get a 32 bit version compiled once, but anytime I tried to run a game it would fail with an error about accessing memory segment FFFFFFFFFFF (a bunch of Fs).

Now when I try to compile a 32 bit version on the core2duo I get an error about PNG2DBC (thats not the right name, but its close) failing and whether I want to send the error to Microsoft.  Otherwise, on either machine, and with disabling warnings displayed as errors, I keep getting those error 1 messages.  I have also tried uninstalling and reinstalling mame compiler 64, no difference.  Finally I tried downloading the 32bit minGW package from mamedev.org/tools, but now if I try to compile it fails almost immediately with the first mkdir command.

Any thoughts?
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: bent98 on March 16, 2010, 06:06:11 pm
I have same exact problem as swight01 on with my i7 win 64 bit install with 32 bit mame compile. I am glad Im not going crazy
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: Havok on March 16, 2010, 06:41:14 pm
Has anyone tried compiling the old fashioned way? Is this a problem with the compiler software, or Mame?

(I'd do it but I'm feeling lazy since I have my 64bit goodness working fine)
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: headkaze on March 16, 2010, 09:44:04 pm
Are people compiling using the "Auto Detect" option? It's equivalent to the "ARCHOPTS=-march=native" option.

The problems people are having extend to compiling "the old fashioned way". If people searched on Google with the errors they are getting they would find threads like this (http://www.mameworld.info/ubbthreads/showflat.php?Number=211369)
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: dwight01 on March 17, 2010, 03:23:15 am
I have tried specifying "Intel core 2" as well as using "Autodetect", also tried "dual core" compile options, tried no compile options, have tried "Clean compile" and "Disable warnings with errors" with the same results. 

I have also tried installing a fresh install on a core2duo laptop that has never had MINGW or anything mame related installed on it, with the same result - for me, compiling dies around the "Archiving" phase with an error on png2bdc.exe "png2bdc.exe has encountered a problem and needs to close.  We are sorry for the inconvenience".  The last message was "Archiving obj/windows/mame/libcpu.a...", and the last compiling message (before the archiving messages) was "Compiling src/emu/cpu/tms57002/57002dsm.c..." (the stop point seems fairly consistent).

The png2bdc.exe file lives under "C:\MinGW\sources\mame0137\obj\windows\mame\build" - It's not part of the source file package, so I think that means it is created during compiling?  I have also unzipped the updated png2bdc.exe and mamecompiler64.exe (after copying to specified locations) - If I double click the updated png2bdc.exe it tells me it is not a valid win32 file (is this update only meant for 64bit OSs?) - same png2bdc.exe error unfortuantely.  If I hit "GO" again immediately (so clean compile is NOT selected", png2bdc.exe crashes almost immediately.

My compile options were "Using Parameters OSD=windows TARGETOS=win32 -j3 ARCHOPTS=-march=core2".  I have attached the entire log from the mame compiler  "Output" window to this message in case that will be helpful.  This is a 32 bit machine I am compiling on.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: headkaze on March 17, 2010, 03:39:55 am
The issue with png2bdc.exe is not a problem with the MC64 it's an issue in MAME. Hopefully they will have it sorted soon.

I thought I posted a 32-bit version of png2bdc.exe but perhaps I didn't? Try the one attached.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: bent98 on March 17, 2010, 02:11:54 pm
file is corrupt
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: Havok on March 17, 2010, 03:05:54 pm
file is corrupt

I also can't open the attached zip...
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: dwight01 on March 17, 2010, 04:10:04 pm
I had no trouble with the zip, applied it and was able to complie mame.exe - unfortunately, the exe won't run any roms.  It starts up fine and shows the list of roms, but as soon as I launch one of the roms it dies with an unable to access memory region FFFFFFFFFF error, and a dump of some register values by the looks of it.  This is also mentioned in other forums as a current symptom of the current mame 137 source.

Interestingly, the same mame.exe (compiled for 32 bit) will work fine on a 64 bit OS (on my i7), it just won't run on any 32 bit machine.

Just have to wait for a new mame source, or a new mingw-mame package.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: Encryptor on March 17, 2010, 06:23:56 pm
I'm not compiling at this time but I was able to download the zip and open it.

Encryptor
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: Havok on March 17, 2010, 08:49:58 pm
Weird - I get an expected end of archive error when attempting to open it on two different computers, and with IE\Firefox\Chrome.

(They are both Windows 7 machines however)
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: Huggybaby on March 17, 2010, 08:54:58 pm
The file downloads fine for me. Here's a mirror: http://www.mediafire.com/file/y5hemjm34td/png2bdc.zip (http://www.mediafire.com/file/y5hemjm34td/png2bdc.zip)
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: headkaze on March 17, 2010, 11:43:20 pm
Weird - I get an expected end of archive error when attempting to open it on two different computers, and with IE\Firefox\Chrome.

(They are both Windows 7 machines however)

I can't download it in Firefox either.. corrupt archive.. XP 64 machine... just tried uploading again and same problem. Wierd!
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: Havok on March 18, 2010, 12:06:44 am
The file downloads fine for me. Here's a mirror: http://www.mediafire.com/file/y5hemjm34td/png2bdc.zip (http://www.mediafire.com/file/y5hemjm34td/png2bdc.zip)

That one works for me...
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: cmoses on March 26, 2010, 01:26:08 pm
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 $@

Headkaze,

I had previously sucessfully compiled a few versions of 32 bit MAME around the time I was first setting up my cabinet.  I wanted to update and take advantage of the new versions features so I have been trying to compile a 32 bit version of 137 with Mame Compiler 64 v1.18.  I had been unsuccessful, getting various errors during the process.  I went back through the posts to reread and see if I missed anything.  I found the post above and downloaded the png2bdc file.  I was easily able to edit the build.mak file in step #2, but was not able to find the location specified in step #1.  I checked a previously compiled version and saw that the directory was there but it was not in the newly unzipped source.  I concluded that this directory 'Mamexxxx\obj\windows\mame\build' is created during the compile process.  I launched Mame Compiler, did my updates and then started the compile.  I watched for the directroy to be created and once it was I copied the png2bdc.exe file in there while the program was compiling.

The program compiled for the first time and seemd to be sucessful but when I try to run any ROMS I get the same error as Dwight01 mentioned in a post above.  I get an unable to access memory region FFFFFFFFFF error.

I am not sure that this is the proper way to do this but it worked for me.  Can you verify that this is correct or is there another way?

Thanks
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: headkaze on March 27, 2010, 09:43:03 am
Wait for the next release of MAME the 32-bit compiled version seems to have some bug.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: cmoses on March 27, 2010, 07:23:08 pm
Wait for the next release of MAME the 32-bit compiled version seems to have some bug.

Do you mean the next full version (0138) or the next update (0137U1)?  I see they have released a update for 0137.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: R0UNDEYEZ on April 02, 2010, 03:03:41 am
Quote
Do you mean the next full version (0138) or the next update (0137U1)?  I see they have released a update for 0137.

I was never able to get it to compile with headkazes compiler program for this release. (no disrespect at all headkaze, i've used it 3 times for prior releases with absolutely no problems at all)

what i did was download the source,the high score diff offered here: http://forum.arcadecontrols.com/index.php?topic=64298.0 (http://forum.arcadecontrols.com/index.php?topic=64298.0)  and got the updated toolset mentioned on the mame site when you get the source. then i followed the directions here: http://mrdo.mameworld.info/compile.html (http://mrdo.mameworld.info/compile.html)
its slightly different than the pictures because of the new tool set but essentially the same process. I can't code and the idea of compiling myself from the command line really made me nervous, but it really isnt that hard if you  follow the directions.plus it feels awesome when you finish and it works haha :)
hope that helps you out.

Title: Re: Mame Compiler 64 v1.18 Released!
Post by: cmoses on April 05, 2010, 10:11:50 am
Roundeyez,

I followed your post, got the hi score diff, got the updated toolset and the Mame updates then followed the directions on Mr Do's site.  Everything went pretty smooth until I got to the last step.  When I typed 'MakeMame' I got an error stating that it didn't recognize the command 'mingw32-make'.  I looked at the .bat file and realized that the last line needed to be edited.  The line was

mingw32-make

I edited to just

make

and it ran correctly.  I tested the compiled version and it runs fine.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: R0UNDEYEZ on April 07, 2010, 02:56:51 am
I'm glad it worked for you.  ;D
Yeah ,the command change threw me off as well, sorry I forgot to mention that.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: RetroBorg on April 09, 2010, 06:25:00 am
Other than adding hiscore support, what other things are people compiling into mame?
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: headkaze on April 19, 2010, 03:01:34 pm
Can anyone confirm if MC64 works with the latest version of MAME? Just seem to be alot of people reporting it failing and I haven't had time to test the latest version.
Title: Re: Mame Compiler 64 v1.18 Released!
Post by: atomikbohm on April 19, 2010, 04:17:38 pm
I seem to be having trouble compiling the 32 bit version of 137.  I've tried on my i7 (64bit vista) system as well as a AMD Athlon XP (32 bit Win XP) system.  The 32 bit version complied on my i7 system works just fine in my 64 bit vista but when I try to load a rom on the 32bit system it crashes right after selecting a ROM to load. 

Core I7 920
6Gb RAM
Nvidia Geforce 9600

AMD Athlon XP 2100+
768 MB RAM
Geforce FX 5500 OC

I was compiling MAME 0.137 only the hiscore Diff. No 'u' updates.
Title: Re: Mame Compiler 64 v1.19 Released!
Post by: headkaze on May 05, 2010, 04:58:08 am
Mame Compiler 64 v1.19 Released

- Added "Optimize for: None" option (should solve png2bdc.exe crash issue)

For those who were having problems compiling a 32-bit verson of MAME the official solution from MameDev is to compile with no optimization (ie. Set "Optimize for: None" in Mame Compiler).
Title: Re: Mame Compiler 64 v1.19 Released!
Post by: Huggybaby on May 05, 2010, 04:04:02 pm
Thanks headkaze.
Title: Re: Mame Compiler 64 v1.19 Released!
Post by: Yoeddy1 on May 18, 2010, 07:53:36 pm
Just compiled .138...worked great!
Title: Re: Mame Compiler 64 v1.19 Released!
Post by: Don on June 02, 2010, 09:52:11 am
EDIT: nevermind, have it working perfectly now thanks, great app!

Just one thing, when chosing what processor to optimise for, is there one i should choose for a Pentium III (996MHz)?
Title: Re: Mame Compiler 64 v1.19 Released!
Post by: lettuce on June 09, 2010, 09:03:39 am
Is this error message anything i should be worried about?:

MameUI.mak:40: warning: overriding commands for target `mameui64.exe'
makefile:684: warning: ignoring old commands for target `mameui64.exe'
Title: Re: Mame Compiler 64 v1.19 Released!
Post by: headkaze on June 09, 2010, 09:11:36 am
Is this error message anything i should be worried about?:

MameUI.mak:40: warning: overriding commands for target `mameui64.exe'
makefile:684: warning: ignoring old commands for target `mameui64.exe'

Nope. It just means it's using the MameUI makefile instead of the default one.
Title: Re: Mame Compiler 64 v1.19 Released!
Post by: jimmy2x2x on June 09, 2010, 05:20:08 pm
Im trying to compile mameui 0.138.1.0

I have followed the instructions, patched in the correct order (u1.diff then hiscore.txt)
ticked the Mame UI check box and optimize for none option
it compiles with the warnings from the last post, took 20 mins for me
the .exe is 38,626kb
it runs the gui just fine, and allows me to audit games, change default options etc
but crashes when I try to run any game

EDIT:

Changed my compile options to optimize for Intel Core2
ticked:
64 bit processor
dual core
mame ui
disable warnings as error

This compiled version seems to run fine

EDIT2:

optimize for Pentium M, Intel core
ticked:
mame ui
disable warnings as error

This version crashes on game launch

Any suggestions please?

Many thanks
Title: Re: Mame Compiler 64 v1.19 Released!
Post by: headkaze on June 10, 2010, 05:50:57 pm
If it crashes when you compile using the "Pentium M" optimization setting, then don't use it ;)
Title: Re: Mame Compiler 64 v1.19 Released!
Post by: jimmy2x2x on June 10, 2010, 10:23:35 pm
The issue was I wanted to build on my (much) faster pc, and there isn't any combination of switches that would produce a stable build suitable for a pentium class machine.

The only way to build a stable version was to compile on the target machine.

Did the job tho! Thanks ;)
Title: Re: Mame Compiler 64 v1.19 Released!
Post by: Generic Eric on June 28, 2010, 10:00:39 pm
Quote
Finished!
3 Hours 11 Minutes and 44 Seconds Elapsed.

Awesome!  I tried w/o the compiler first, but I was missing something.  I took about 5 minutes to set everything up.  What a gem!
Title: Re: Mame Compiler 64 v1.19 Released!
Post by: Flip The Switch on July 22, 2010, 08:05:44 am
Mine crashes randomly (stops responding gives me check for solution online msg) im running windows 7, is there anything else i need to put in my mameUI dir?

after it finished compiling i just put the exe and highscore.dat in my mame directory?

is there something else or have i just compiled wrong?

it worked maybe 4 or 5 times now it just crashes.
Title: Re: Mame Compiler 64 v1.19 Released!
Post by: headkaze on July 22, 2010, 08:51:48 am
Mine crashes randomly

When you compiled did you set "Optimize for" to None?
Title: Re: Mame Compiler 64 v1.19 Released!
Post by: Flip The Switch on July 22, 2010, 06:03:43 pm
Hey crazy, no i set it to autodetect, and i had mameUI ticked like in your walkthrough, is this where i went wrong?

the computer im on now is a old 3.6 gig intel but the cabinet has an even older PC which is an old pentium 4.

/edit i tried it with "otimize for" set to none, it only took 6 minutes and there wasnt a exe at the end of the process, im obviously going wrong somewhere.
Title: Re: Mame Compiler 64 v1.19 Released!
Post by: Flip The Switch on July 25, 2010, 02:34:04 am
/EDIT - all working now, thanks MKChamp for the help!
Title: Re: Mame Compiler 64 v1.19 Released!
Post by: shrunkenmaster on August 03, 2010, 02:52:04 pm
Just compiled Mame 0137 using the Mame Compiler 1.19 - compilation was successful, but I can't seem to find where it places the new executable. It's made a zipped Mame folder inside C/MinGW/source but all that's inside that is:

docs (folder)
src (folder)
makefile
whatsnew

Any pointers please, or am I just being plain stupid as usual??
Title: Re: Mame Compiler 64 v1.19 Released!
Post by: Yoeddy1 on August 05, 2010, 03:01:04 am
Just compiled .139 with Intel C2D x64, no white nag lines/warnings, and high scores with 1.19.  Worked great!
Title: Re: Mame Compiler 64 v1.19 Released!
Post by: Encryptor on August 05, 2010, 05:54:33 am
It might be a pain but did you do a search for mame.exe and see if there is another one besides the one in your mame folder?

Encryptor
Title: Re: Mame Compiler 64 v1.19 Released!
Post by: WhereEaglesDare on August 25, 2010, 09:05:14 pm
/EDIT - all working now, thanks MKChamp for the help!

What did you have to do to fix it?
Title: Re: Mame Compiler 64 v1.19 Released!
Post by: WhereEaglesDare on August 25, 2010, 10:10:35 pm
HeadKaze, thanks for the Compilier.  I need some help.

I followed the tutorial and it didn't work, but neither did just running the MinGW through commandprompt, any ideas?

Each time I start with a fresh copy of the diff files and the source... I set optimized to none and I applied the 139u1 patch first then the hi score patch. 

It ends like this:
src/osd/windows/video.c: In function 'void osd_update_hi(running_machine*, int)':
src/osd/windows/video.c:271: error: redefinition of 'void osd_update_hi(running_machine*, int)'
src/osd/windows/video.c:247: error: 'void osd_update_hi(running_machine*, int)' previously defined here
Finished!
0 Hours 55 Minutes and 28 Seconds Elapsed.
make: *** [obj/windows/mame/osd/windows/video.o] Error 1

I attached the entire log.

There are no additional files in the source folder.
Title: Re: Mame Compiler 64 v1.19 Released!
Post by: WhereEaglesDare on August 26, 2010, 07:54:53 am
Ran it again and it ran fine, but this time all i did was apply the hiscore patch, when i try to run the u update it doesnt work...  what am I doing wrong?
Title: Re: Mame Compiler 64 v1.19 Released!
Post by: Kman-Sweden on August 27, 2010, 09:05:58 am
Have a look here.... http://forum.arcadecontrols.com/index.php?topic=64298.msg1029706#msg1029706 (http://forum.arcadecontrols.com/index.php?topic=64298.msg1029706#msg1029706)
Title: Re: Mame Compiler 64 v1.19 Released!
Post by: WhereEaglesDare on August 27, 2010, 03:45:12 pm
no i read that, and I did get it working, just with the hiscore diff, it wont work though when i load the 139u1 update
Title: Re: Mame Compiler 64 v1.19 Released!
Post by: Kman-Sweden on August 28, 2010, 07:45:28 am
So do you have the hi-score diff for U1?
Title: Re: Mame Compiler 64 v1.19 Released!
Post by: XNIF on August 28, 2010, 09:47:43 am
I know this is stupid to ask but i do not understand why you should compile mame yourself? Isn't the normal compiled binaties good enough? Is there performance increase when you compile your own version?
Title: Re: Mame Compiler 64 v1.19 Released!
Post by: jimmy2x2x on August 28, 2010, 11:11:08 am
Main reasons for me are the hiscore saving and removal of nag screens (you need to apply the appropriate patch)
Title: Re: Mame Compiler 64 v1.19 Released!
Post by: WhereEaglesDare on August 28, 2010, 09:22:42 pm
So do you have the hi-score diff for U1?

Yea, got it from the hiscore thread

Ran it again over night, 2hr 15 min works great, thanks
Title: Re: Mame Compiler 64 v1.19 Released!
Post by: iano on September 19, 2010, 03:44:00 pm
Hi Ben. Tried compiling vanilla mame 0.139 with hiscore diff patch. Compile options were 'Optimize For Intel Core2' and dual core selected. Got the following error but don't know if it's a big deal.

make: *** [obj/windows/mame/emu/uismall.fh] error - 1073741819
make: *** waiting for unfinished jobs

ps. Is there any advantage in forcing directinput in the mame source code (it's for use in my arcade cab) ?

Cheers,
ian.

EDIT: My bad - haven't compiled mame since 0.135, found answer a couple of pages back. Noticed now there's just a single exe.
Title: Re: Mame Compiler 64 v1.20 Released!
Post by: headkaze on September 19, 2010, 07:06:54 pm
Mame Compiler 64 v1.20 Released

- Updated to latest MinGW

Tested and working with MAME 0.139u3 + hi_139u3.diff
Title: Re: Mame Compiler 64 v1.20 Released!
Post by: iano on September 19, 2010, 09:50:02 pm
Thanks.

 :)
Title: Re: Mame Compiler 64 v1.20 Released!
Post by: WhereEaglesDare on September 19, 2010, 10:15:53 pm
when you check the dual core box does that mean that it is optimizing the compiler for dual core or the MAME build or both...  if I compile a dual core MAME does it run just as well on a single core?
Title: Re: Mame Compiler 64 v1.20 Released!
Post by: MKChamp on September 19, 2010, 10:21:48 pm
Mame Compiler 64 v1.20 Released

- Updated to latest MinGW

Tested and working with MAME 0.139u3. Please note there is no hiscore diff patch for u3 just yet.

There is now :-)
Title: Re: Mame Compiler 64 v1.20 Released!
Post by: headkaze on September 19, 2010, 10:24:20 pm
Mame Compiler 64 v1.20 Released

- Updated to latest MinGW

Tested and working with MAME 0.139u3. Please note there is no hiscore diff patch for u3 just yet.

There is now :-)

lol I just saw that! Uploading a new version of MC64 with it included now ;)
Title: Re: Mame Compiler 64 v1.20 Released!
Post by: wxforecaster on October 03, 2010, 03:31:15 pm
I just wanted to thank headkaze for this. Did my first ever compile (both the UI and standalone mame.exe) and everything worked great on the first try.

If I had one suggestion for a future update, it would be to specify an output directory for the executable. From there, the compiler could create (if they don't exist) all the standard subfolders (roms, ini, cfg, etc....) including the elusive "Hi" directory for high score storage.

Thanks!
Evan
Title: Re: Mame Compiler 64 v1.20 Released!
Post by: Donkbaca on November 08, 2010, 12:14:17 pm
Headkaze, help!  I have tried to compile a bunch of time, trying to do MAME .0140 and MAME UI.  Followed the instructions word for word  numerous times, the compile goes without a hitch, no errors at all, but I am having 2 issues:

1) When the compile is done, it spits out MAMEUI.exe in the source folder, but when I copy and paste the .exe to my mame folder, it won't run and and it crashes.

2) When I double click on the MAMEUI while it is in the MAME folder it runs, then I go through the trouble of changing all the directories to my MAME folder and I can run a few games, but after a few minutes I get an error message and it shuts down.

Any ideas on why this is happening? 

I have downloaded everything per the website instructions, I am only applying the hi_score.diff patch for MAME 140.  I hit go, everything compiles without an error, but if I move the executable, it won't run, and if I run the executable at its current location it gets some sort of critical error and shuts down.  I have even deleted/uninstalled/redownloaded and tried several times, but the same problem keeps occurring.

If I download and run vanilla MAMEUI140, it runs fine.

Help!

, even
Title: Re: Mame Compiler 64 v1.20 Released!
Post by: headkaze on November 08, 2010, 01:21:46 pm
Are you using any optimization when compiling?

What's the error message you're getting?
Title: Re: Mame Compiler 64 v1.20 Released!
Post by: Donkbaca on November 08, 2010, 02:59:31 pm
I set it to auto optimization, I click the MAMEUI checkbox.

I am not getting getting any errors when I compile, its just when I am done, if I move the executable to my MAME directory, where i have all my roms and such in their folders, it won't start, and if I click on the MAMEUI exe in the MINGW source directory, where it outputs, it runs for a while and then crashes, a gray box pops up in windows and says something to the effect that the program has experienced some error and cannot continue and it asks me if I want to report the problem to microsoft, etc.  I will check out the error tonight and send it to you.
Title: Re: Mame Compiler 64 v1.20 Released!
Post by: WhereEaglesDare on November 08, 2010, 03:12:43 pm
try setting your optimizations to NONE.  Erase all of your source files and start over with fresh downloads and set NONE optimizations.  Itll work this time.
Title: Re: Mame Compiler 64 v1.20 Released!
Post by: headkaze on November 08, 2010, 03:17:37 pm
try setting your optimizations to NONE.  Erase all of your source files and start over with fresh downloads and set NONE optimizations.  Itll work this time.

Yup  ;)
Title: Re: Mame Compiler 64 v1.20 Released!
Post by: nismofun on December 21, 2010, 05:43:15 pm
Just tried compiling 1.40 and it ran for about 15min and popped off the following:
Quote
src/osd/windows/video.c: In function 'void osd_update_hi(running_machine*, int)':
src/osd/windows/video.c:264: error: redefinition of 'void osd_update_hi(running_machine*, int)'
src/osd/windows/video.c:240: error: 'void osd_update_hi(running_machine*, int)' previously defined here
Finished!
0 Hours 15 Minutes and 34 Seconds Elapsed.
make: *** [obj/winui/mame64/osd/windows/video.o] Error 1

Any ideas?
Title: Re: Mame Compiler 64 v1.20 Released!
Post by: headkaze on December 22, 2010, 03:49:31 am
Just tried compiling 1.40 and it ran for about 15min and popped off the following:
Quote
src/osd/windows/video.c: In function 'void osd_update_hi(running_machine*, int)':
src/osd/windows/video.c:264: error: redefinition of 'void osd_update_hi(running_machine*, int)'
src/osd/windows/video.c:240: error: 'void osd_update_hi(running_machine*, int)' previously defined here
Finished!
0 Hours 15 Minutes and 34 Seconds Elapsed.
make: *** [obj/winui/mame64/osd/windows/video.o] Error 1

Any ideas?

Delete the files and start again.
Title: Re: Mame Compiler 64 v1.20 Released!
Post by: john_abey on January 09, 2011, 02:54:32 pm
Thanks for the great program use it all the time.

I am running into a problem mame 0.141,  mame standalone is fine and works great but mameui .141 stops after
9min 27sec with this error.

src/mame/video/circusc.c: In function 'void palette_init_circusc(running_machine*, const UINT8*)':
src/mame/video/circusc.c:33: internal compiler error: Segmentation fault
Finished!
0 Hours 9 Minutes and 27 Seconds Elapsed.
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
make: *** [obj/winui/mame/mame/video/circusc.o] Error 1


I would have thought this would have been posted already, tried 3 times each time fail at same spot no optimization and clean install each time.
Title: Re: Mame Compiler 64 v1.20 Released!
Post by: headkaze on January 10, 2011, 01:35:32 am
src/mame/video/circusc.c:33: internal compiler error: Segmentation fault

You might want to try pressing GO! a few times before giving up. Sometimes pressing GO! again will continue to compile okay. If it still fails then read the following quote:

Quote from: R. Belmont
It's random, and it occurs only on XP. The 100% way to cure it is to upgrade to Vista or 7. Seriously.
Title: Re: Mame Compiler 64 v1.20 Released!
Post by: Beretta on January 20, 2011, 09:28:38 pm
couple questions

1st off kudos to headkaze for making this, i once tried to compile mame by hand and i got no where with it.. kept dying on errors.


quesiton 1. what is the effect of dual/quad check boxes? i assume this only effects the thread(s) the compiler uses because leaving them both unchecked was MUCH slower to compile.
does this have any effect on the end exe?


question 2. is there anyway to optimize for a processor other then what you're compiling on?

i ask this because i tried and failed miserably to compile a 32 bit version optimized for p4 -sse3
on my core2 quad.. the core2 has all the instructions+ what is on the p4 but it continuously died on that png2bnc.exe or something another.

i downloaded the one listed in this thread and tried replacing it but it did'nt help.. it just insta crashes when called by the compiler.

i'd go compile it on the p4 but i'd have ot install net framework and then the MC.. so.. MC is'nt very portable.

anyway i was able to get it to compile optimized for "none".. and for "core2" when compiling on the core2.. i was trying to compile mame 0.141 btw.


question 3. whats the typical performance benefit for optimizing? the plan was to build various versions of mame optimized for athlon-xp and p4's.. i have'nt been able to compile those but i did try a 64bit core2 vs none build.

my test was killer instinct run unthrottled with combo + fogore on orchids rooftop and manually observed the FPS,
but the difference if any was unnoticeable.

i then tried the -bench (@ 120) setting and came up with just 8% difference
none: 508 vs core2: 516%

next i tried burger time, bench @ 150, ran 3 times each
core2 2211-2215% vs none 2206-2208%
which is nearly identical.

am i missing something? i remember reading long ago that when compiling (optimizing) for different CPU's you had to comment out a line and change a variable in the main .c file.

is that still necessary? im trying to squeeze every ounce i can out of the cpu's im wanting to use.

PS: i just tested the 2 i compiled vs the "official" mame64 v0.141 release and btime was 2090%, which puts the my compiles about 6% faster.. although no apparent difference between the 2 them selves.


EDIT:

question 4. i just tried using MC 1.17 to compile 0.68.. it did'nt make it
was curious if any of the older versions of MC can handle < 0.106?
i could'nt find a place to download older MC versions.


EDIT2: btw i just got done testing.. 0.106 works with 1.17, then i tried 0.100 and no go.
must be because of the video changes in .106.
Title: Re: Mame Compiler 64 v1.20 Released!
Post by: Gray_Area on January 31, 2011, 03:57:02 pm
This thread should be stickied. Great app. I compiled diff 141u1 into 141, with a small custom change in the source. Smooth as silk.
Title: Re: Mame Compiler 64 v1.20 Released!
Post by: Mickelonis on March 07, 2011, 11:57:04 pm
Not working for 141...


Compiling Mame...
Using Parameters OSD=windows TARGETOS=win32 -j5 PTR64=1
mkdir.exe -p obj/windows/mame64
process_easy: DuplicateHandle(In) failed (e=6)
Finished!
0 Hours 0 Minutes and 0 Seconds Elapsed.
process_easy() failed to launch process (e=6)
mkdir.exe -p obj/windows/mame64
Counted 3 args in failed launch


EDIT!

Seems to work if I change it to optimize for 'none'

Thanks for the great tool!

Title: Re: Mame Compiler 64 v1.20 Released!
Post by: TheManuel on April 22, 2011, 07:16:09 pm
Hello.

When trying to comile MAME 0.142 with the corresponidng hiscore diff patch, I get teh following error:
make: *** [obj/windows/mame/emu/uismall.fh] Error -1073741819

Does anyone know why?
Title: Re: Mame Compiler 64 v1.20 Released!
Post by: TheManuel on April 22, 2011, 09:20:17 pm
Never mind.
Kept reading and found out that I have to disable the optimizations.
I don't recall those optimizations making much difference, anyway, when I've done comparisons in the past...
Title: Re: Mame Compiler 64 v1.20 Released!
Post by: llaffer on April 28, 2011, 11:34:15 pm
For the last few versions, I've had problems compiling the MAMEUI64.EXE using this compiler (MAME64.EXE works fine).

I'm not sure if there's an updated Makefile that's needed or something, but starting with 142u1, there hasn't been a Makefile with the UI source code.

When I compile it, I get a ton of these errors:

Code: [Select]
Linking mameui64.exe...
obj/winui/mame64/libemu.a(ldpr8210.o):ldpr8210.c:(.text+0x629): undefined reference to `I8049'
obj/winui/mame64/libemu.a(ldpr8210.o):ldpr8210.c:(.text+0x749): undefined reference to `I8748'
obj/winui/mame64/libemu.a(ldv1000.o):ldv1000.c:(.text+0x679): undefined reference to `Z80'
obj/winui/mame64/libemu.a(ldvp931.o):ldvp931.c:(.text+0x4f9): undefined reference to `I8049'
obj/winui/mame64/libemu.a(z80ctc.o):z80ctc.c:(.text+0x6a7): undefined reference to `device_config_z80daisy_interface::device_config_z80daisy_interface(machine_config const&, device_config&)'
obj/winui/mame64/libemu.a(z80ctc.o):z80ctc.c:(.text+0x807): undefined reference to `device_config_z80daisy_interface::device_config_z80daisy_interface(machine_config const&, device_config&)'
obj/winui/mame64/libemu.a(z80ctc.o):z80ctc.c:(.text+0x928): undefined reference to `device_z80daisy_interface::device_z80daisy_interface(running_machine&, device_config const&, device_t&)'
obj/winui/mame64/libemu.a(z80ctc.o):z80ctc.c:(.text+0xbf8): undefined reference to `device_z80daisy_interface::device_z80daisy_interface(running_machine&, device_config const&, device_t&)'
obj/winui/mame64/libemu.a(z80ctc.o):z80ctc.c:(.text+0x1800): undefined reference to `device_config_z80daisy_interface::device_config_z80daisy_interface(machine_config const&, device_config&)'
obj/winui/mame64/libemu.a(z80ctc.o):z80ctc.c:(.text$_ZN20z80ctc_device_configD1Ev[z80ctc_device_config::~z80ctc_device_config()]+0x86): undefined reference to `device_config_z80daisy_interface::~device_config_z80daisy_interface()'
obj/winui/mame64/libemu.a(z80ctc.o):z80ctc.c:(.text$_ZN20z80ctc_device_configD0Ev[z80ctc_device_config::~z80ctc_device_config()]+0x86): undefined reference to `device_config_z80daisy_interface::~device_config_z80daisy_interface()'
obj/winui/mame64/libemu.a(z80ctc.o):z80ctc.c:(.text$_ZN13z80ctc_deviceD0Ev[z80ctc_device::~z80ctc_device()]+0x86): undefined reference to `device_z80daisy_interface::~device_z80daisy_interface()'
obj/winui/mame64/libemu.a(z80ctc.o):z80ctc.c:(.text$_ZN13z80ctc_deviceD1Ev[z80ctc_device::~z80ctc_device()]+0x86): undefined reference to `device_z80daisy_interface::~device_z80daisy_interface()'
obj/winui/mame64/drivlist.o:drivlist.c:(.data+0x0): undefined reference to `driver_005'
obj/winui/mame64/drivlist.o:drivlist.c:(.data+0x8): undefined reference to `driver_10yard'
obj/winui/mame64/drivlist.o:drivlist.c:(.data+0x10): undefined reference to `driver_10yard85'
obj/winui/mame64/drivlist.o:drivlist.c:(.data+0x18): undefined reference to `driver_10yardj'
obj/winui/mame64/drivlist.o:drivlist.c:(.data+0x20): undefined reference to `driver_11beat'
obj/winui/mame64/drivlist.o:drivlist.c:(.data+0x28): undefined reference to `driver_18w'
obj/winui/mame64/drivlist.o:drivlist.c:(.data+0x30): undefined reference to `driver_18w2'
obj/winui/mame64/drivlist.o:drivlist.c:(.data+0x38): undefined reference to `driver_18wheelr'
obj/winui/mame64/drivlist.o:drivlist.c:(.data+0x40): undefined reference to `driver_1941'

And that goes on for a while.  After 30 seconds of seeing these errors, I stopped my compile attempt.

Has anyone been able to get a good link lately?

Thanks.
Title: Re: Mame Compiler 64 v1.20 Released!
Post by: jeustaquio on April 29, 2011, 11:26:49 am
First, thanks for the app.

I compiled the 142 version without problems.

Thanks again.


Title: Re: Mame Compiler 64 v1.20 Released!
Post by: llaffer on May 09, 2011, 10:54:30 pm
For the last few versions, I've had problems compiling the MAMEUI64.EXE using this compiler (MAME64.EXE works fine).

I'm not sure if there's an updated Makefile that's needed or something, but starting with 142u1, there hasn't been a Makefile with the UI source code.

When I compile it, I get a ton of these errors:

Code: [Select]
Linking mameui64.exe...
obj/winui/mame64/libemu.a(ldpr8210.o):ldpr8210.c:(.text+0x629): undefined reference to `I8049'
obj/winui/mame64/libemu.a(ldpr8210.o):ldpr8210.c:(.text+0x749): undefined reference to `I8748'
obj/winui/mame64/libemu.a(ldv1000.o):ldv1000.c:(.text+0x679): undefined reference to `Z80'
obj/winui/mame64/libemu.a(ldvp931.o):ldvp931.c:(.text+0x4f9): undefined reference to `I8049'
obj/winui/mame64/libemu.a(z80ctc.o):z80ctc.c:(.text+0x6a7): undefined reference to `device_config_z80daisy_interface::device_config_z80daisy_interface(machine_config const&, device_config&)'
obj/winui/mame64/libemu.a(z80ctc.o):z80ctc.c:(.text+0x807): undefined reference to `device_config_z80daisy_interface::device_config_z80daisy_interface(machine_config const&, device_config&)'
obj/winui/mame64/libemu.a(z80ctc.o):z80ctc.c:(.text+0x928): undefined reference to `device_z80daisy_interface::device_z80daisy_interface(running_machine&, device_config const&, device_t&)'
obj/winui/mame64/libemu.a(z80ctc.o):z80ctc.c:(.text+0xbf8): undefined reference to `device_z80daisy_interface::device_z80daisy_interface(running_machine&, device_config const&, device_t&)'
obj/winui/mame64/libemu.a(z80ctc.o):z80ctc.c:(.text+0x1800): undefined reference to `device_config_z80daisy_interface::device_config_z80daisy_interface(machine_config const&, device_config&)'
obj/winui/mame64/libemu.a(z80ctc.o):z80ctc.c:(.text$_ZN20z80ctc_device_configD1Ev[z80ctc_device_config::~z80ctc_device_config()]+0x86): undefined reference to `device_config_z80daisy_interface::~device_config_z80daisy_interface()'
obj/winui/mame64/libemu.a(z80ctc.o):z80ctc.c:(.text$_ZN20z80ctc_device_configD0Ev[z80ctc_device_config::~z80ctc_device_config()]+0x86): undefined reference to `device_config_z80daisy_interface::~device_config_z80daisy_interface()'
obj/winui/mame64/libemu.a(z80ctc.o):z80ctc.c:(.text$_ZN13z80ctc_deviceD0Ev[z80ctc_device::~z80ctc_device()]+0x86): undefined reference to `device_z80daisy_interface::~device_z80daisy_interface()'
obj/winui/mame64/libemu.a(z80ctc.o):z80ctc.c:(.text$_ZN13z80ctc_deviceD1Ev[z80ctc_device::~z80ctc_device()]+0x86): undefined reference to `device_z80daisy_interface::~device_z80daisy_interface()'
obj/winui/mame64/drivlist.o:drivlist.c:(.data+0x0): undefined reference to `driver_005'
obj/winui/mame64/drivlist.o:drivlist.c:(.data+0x8): undefined reference to `driver_10yard'
obj/winui/mame64/drivlist.o:drivlist.c:(.data+0x10): undefined reference to `driver_10yard85'
obj/winui/mame64/drivlist.o:drivlist.c:(.data+0x18): undefined reference to `driver_10yardj'
obj/winui/mame64/drivlist.o:drivlist.c:(.data+0x20): undefined reference to `driver_11beat'
obj/winui/mame64/drivlist.o:drivlist.c:(.data+0x28): undefined reference to `driver_18w'
obj/winui/mame64/drivlist.o:drivlist.c:(.data+0x30): undefined reference to `driver_18w2'
obj/winui/mame64/drivlist.o:drivlist.c:(.data+0x38): undefined reference to `driver_18wheelr'
obj/winui/mame64/drivlist.o:drivlist.c:(.data+0x40): undefined reference to `driver_1941'

And that goes on for a while.  After 30 seconds of seeing these errors, I stopped my compile attempt.

Has anyone been able to get a good link lately?

Thanks.

I found the solution to my problem: There is a new method to compiling UI based only on the makefile from the base code, along with adding in the UI code where it's needed and proper make arguments.  The old make file specific for UI is no longer needed.

So 1.20 of Mame Compiler 64 is currently obsolete.
Title: Re: Mame Compiler 64 v1.20 Released!
Post by: Gray_Area on May 13, 2011, 01:33:35 am
So 1.20 of Mame Compiler 64 is currently obsolete.

Seems it's obsolete in general, because I had a similar experience compiling baseline MAME.
Title: Re: Mame Compiler 64 v1.20 Released!
Post by: headkaze on May 14, 2011, 11:28:22 pm
Seems it's obsolete in general, because I had a similar experience compiling baseline MAME.

I just tried compiling Mame 142u3 and didn't have any problems.
Title: Re: Mame Compiler 64 v1.20 Released!
Post by: llaffer on May 14, 2011, 11:34:42 pm
I've had no problems with using it to compile the command-line version of MAME.  It's MAMEUI that will not compile any more with v1.20.
Title: Re: Mame Compiler 64 v1.20 Released!
Post by: headkaze on May 14, 2011, 11:51:50 pm
The old make file specific for UI is no longer needed.

I've fixed this and will upload a new version (1.21) soon.
Title: Re: Mame Compiler 64 v1.21 Released!
Post by: headkaze on May 28, 2011, 09:43:36 pm
Updated to support latest toolchain.
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: Gray_Area on May 29, 2011, 08:12:09 pm
I'm getting the following errors when patching the diffs:


diff 142u1

patch: **** Can't create file 'C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp/poa03376' : Permission denied


diff 142u2

Hunk #1 FAILED at 38


diff 142u3

patch: **** Can't create file 'C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp/poa04092' : Permission denied


diff 142u4

Hunk #1 FAILED at 414.
Hunk #2 FAILED at 475.
Hunk #3 FAILED at 530.
Hunk #4 FAILED at 577.
4 out of 4 hunks FAILED
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: jimmy2x2x on June 07, 2011, 07:57:46 pm
Hello, I am trying to compile 0.142 base version
with Mame compiler 64 v1.22
no patches applied

Im getting lots of errors!

Compiling src/osd/windows/d3d9intf.c...
src/osd/windows/d3d9intf.c: In function 'HRESULT d3d_device_set_texture_stage_state(d3d_device*, DWORD, D3DTEXTURESTAGESTATETYPE, DWORD)':
src/osd/windows/d3d9intf.c:428: error: 'D3DTSS_ADDRESSU' was not declared in this scope
Finished!
0 Hours 18 Minutes and 36 Seconds Elapsed.
src/osd/windows/d3d9intf.c:430: error: 'D3DTSS_ADDRESSV' was not declared in this scope
src/osd/windows/d3d9intf.c:432: error: 'D3DTSS_BORDERCOLOR' was not declared in this scope
src/osd/windows/d3d9intf.c:434: error: 'D3DTSS_MAGFILTER' was not declared in this scope
src/osd/windows/d3d9intf.c:436: error: 'D3DTSS_MINFILTER' was not declared in this scope
src/osd/windows/d3d9intf.c:438: error: 'D3DTSS_MIPFILTER' was not declared in this scope
src/osd/windows/d3d9intf.c:440: error: 'D3DTSS_MIPMAPLODBIAS' was not declared in this scope
src/osd/windows/d3d9intf.c:442: error: 'D3DTSS_MAXMIPLEVEL' was not declared in this scope
src/osd/windows/d3d9intf.c:444: error: 'D3DTSS_MAXANISOTROPY' was not declared in this scope
make: *** [obj/windows/mame64/osd/windows/d3d9intf.o] Error 1


Any ideas?

Thanks

EDIT: Seems like the problem isn't isolated to Mame compiler for me.

I uninstalled Mame Compiler, deleted all the source code

'easy way' compiler package from mamedevs
base source code for 0.142, no patches applied.
source is in c:\mame
set path =c:\mingw\mingw64-w64\bin
compiling using 'make' command in the source directory
tried changing the path to w32, same result.
nothing else in the path, just mingw

Always get the above compile errors...


Title: Re: Mame Compiler 64 v1.22 Released!
Post by: headkaze on June 08, 2011, 01:10:37 am
I had to press Go twice for the latest version to compile for me. Give that a try.
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: jimmy2x2x on June 08, 2011, 11:37:51 pm
Found the problem:

mingw-mame-20100102.exe (0.136u1 - 0.142u3)
mingw-mame-20110519.exe (0.142u4 - present)

To compile 0.142 stock you need the older set of tools, new set isn't backwards compatible!

Also, another strange thing I have found: the supplied PATCH program that comes with mingw will not apply the groovymame.diff, but the one included with Mame Compiler works fine. I suspect this might be related to CR / CRLF characters.

Title: Re: Mame Compiler 64 v1.22 Released!
Post by: FrizzleFried on June 22, 2011, 05:52:32 pm
Last time I compiled MAME (.136 or so from my recollection) it took me about 20-25 minutes to compile....

...I've been compiling .142u6 today... I'm up to just about an hour and a half. 

Huh?

Is that normal with the new tools that came in to play somewhat lately?

Title: Re: Mame Compiler 64 v1.22 Released!
Post by: Yoeddy1 on July 04, 2011, 01:20:49 am
Any problems with 0.143? 

Jason
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: headkaze on July 05, 2011, 10:48:07 am
Any problems with 0.143? 

Jason

Nope
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: Visitor Q on July 09, 2011, 05:22:37 pm
0.143 will not compile for me.

Compiling Mame...
Using Parameters OSD=windows TARGETOS=win32 -j3 ARCHOPTS=-march=native PTR64=1
make: *** No targets specified and no makefile found.  Stop.
Finished!
0 Hours 0 Minutes and 0 Seconds Elapsed.

^^^ I figured it out, the remote dirs are not working if you set them to a different drive other than default under MinGW if that makes sense.
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: portugese pirate on August 17, 2011, 11:00:38 pm
I need some help....Im trying to compile 131 and get this when I hit go

mingw32.make:MameUI.mak: No file or directory
mingw32.make: ***No rule to make target "MameUI.mak", stop

what am I doing wrong.....please help
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: headkaze on August 18, 2011, 06:21:48 am
The makefile for MAMEUI has changed to WinUI.mak. I updated the instructions on the website a while back so give those a read.
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: portugese pirate on August 18, 2011, 12:01:39 pm
I just checked my mamui131 folder and both the mamemake file amd winui.mak are both there.....still getting same error
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: sega_mad on August 19, 2011, 06:36:46 pm
Headkaze,

Have used your compiler before, and it's great.

Is it possible to use it for MAME 0.98

The reason I want this version is for Crusin' USA. If I overclock my CPU to 4 GHZ, it runs fine, all other version seem to run a bit slow and the sound stutters.

If it is possible, where do I go to get the Diff files to remove the Nag screens.

Cheers

Sega_mad
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: Dazz on August 19, 2011, 08:41:50 pm
Ok, something has definitely changed.  Trying to compile 143u3 and it's definitely failing.  I've never had any issues compiling and my compiling environment hasn't changed.  I'm seeing the same errors that the guys below are getting. 

Any ideas?
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: headkaze on August 20, 2011, 05:52:13 am
What error Dazz? Are you compiling MameUI?

Code: [Select]
mingw32.make:MameUI.mak: No file or directory
mingw32.make: ***No rule to make target "MameUI.mak", stop

This must be an older version of MAME because MameUI.mak is the older makefile name. I don't understand how you can have WinUI.mak with an older version? Anyway try renaming it to MameUI.mak if that's what it's looking for.
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: Donkbaca on August 20, 2011, 09:30:17 am
I tried compiling MAMEUi and had some errors. I am confused about the .mak file. I read you didn't need the Mameui.mak file, but the instructions say you do. Can you update the instructions by any chance?

Thanks!
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: Dazz on August 20, 2011, 01:11:40 pm
What error Dazz? Are you compiling MameUI?

Code: [Select]
mingw32.make:MameUI.mak: No file or directory
mingw32.make: ***No rule to make target "MameUI.mak", stop

This must be an older version of MAME because MameUI.mak is the older makefile name. I don't understand how you can have WinUI.mak with an older version? Anyway try renaming it to MameUI.mak if that's what it's looking for.

Nah, I'm just trying to compile MAME64 143u3.  I'm getting the same errors as jimmy2x2x

Compiling src/osd/windows/d3d9intf.c...
src/osd/windows/d3d9intf.c: In function 'HRESULT d3d_device_set_texture_stage_state(d3d_device*, DWORD, D3DTEXTURESTAGESTATETYPE, DWORD)':
src/osd/windows/d3d9intf.c:428: error: 'D3DTSS_ADDRESSU' was not declared in this scope
Finished!
0 Hours 18 Minutes and 36 Seconds Elapsed.
src/osd/windows/d3d9intf.c:430: error: 'D3DTSS_ADDRESSV' was not declared in this scope
src/osd/windows/d3d9intf.c:432: error: 'D3DTSS_BORDERCOLOR' was not declared in this scope
src/osd/windows/d3d9intf.c:434: error: 'D3DTSS_MAGFILTER' was not declared in this scope
src/osd/windows/d3d9intf.c:436: error: 'D3DTSS_MINFILTER' was not declared in this scope
src/osd/windows/d3d9intf.c:438: error: 'D3DTSS_MIPFILTER' was not declared in this scope
src/osd/windows/d3d9intf.c:440: error: 'D3DTSS_MIPMAPLODBIAS' was not declared in this scope
src/osd/windows/d3d9intf.c:442: error: 'D3DTSS_MAXMIPLEVEL' was not declared in this scope
src/osd/windows/d3d9intf.c:444: error: 'D3DTSS_MAXANISOTROPY' was not declared in this scope
make: *** [obj/windows/mame64/osd/windows/d3d9intf.o] Error 1

It looks like some changes to mingw-mame were made starting 142u4.
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: headkaze on August 21, 2011, 11:50:48 am
It looks like some changes to mingw-mame were made starting 142u4.

Thanks for reporting this. MC64 has been updated with the latest toolchain.
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: netman88 on September 21, 2011, 01:05:50 pm

Hi There,

Sorry for my not being able to figure it out.  But where can you get the 119u2.diff file from or do you have to build it from scratch?
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: headkaze on September 21, 2011, 07:34:38 pm
Does it have to be 119u2? Why not 119 or 120?

You can get the diff's from here (http://forum.arcadecontrols.com/index.php?topic=64298.0)
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: Chewbacca on September 29, 2011, 12:06:16 pm
Headkaze, First off i'd like to say thank you for the software! Wondering if i can get your help with the following error.

Compiling Mame64...
Using Parameters  -j3 ARCHOPTS="-march=pentium-m -msse3" MSVC_BUILD=1 PTR64=1
mingw32-make: *** create_child_process: DuplicateHandle(In) failed (e=6)
Finished!
0 Hours 0 Minutes and 0 Seconds Elapsed.
.  Stop.

tried searching the thread for a resolution and didn't see one so forgive me if i overlooked it. Thanks again.
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: Yoeddy1 on February 07, 2012, 05:50:18 pm
Just compiled 0.145.  Worked great!

Jason
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: raungst on February 21, 2012, 02:07:00 am
I'm trying to recompile MAME 0.137 using 1.17 and I get the error Chewbacca does above. I'm not sure why. I used Mame Compiler many moons ago to compile it when 0.137 was the latest. I'm hoping to apply a different set of patches this time around... Any ideas what's happening?
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: raungst on February 21, 2012, 02:44:35 am
I should add that I'm compiling with 32bit Windows 7. I'm not sure if that's the issue or not. My arcade cabinet is XP, so I can try that if it comes down to it.
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: headkaze on February 21, 2012, 03:24:30 am
Duplicate handle is usually caused by not using the custom MingGW install by Mame Compiler 64.

Anyway if you can't get it working I'll take a look at it later for you.
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: g_block247 on March 08, 2012, 08:36:46 pm
A noobish question I know, but what is (MAME Compiler) for?
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: Le Chuck on March 08, 2012, 08:41:03 pm
From wiki:

A compiler is a computer program (or set of programs) that transforms source code written in a programming language (the source language) into another computer language (the target language, often having a binary form known as object code). The most common reason for wanting to transform source code is to create an executable program.

In this case many folks want MAME to do some very specific things that it doesn't do "out of the box" so they alter the MAME source code to allow high score data, or no nag screens (two very common examples) and then put that through a compilier to get the MAME executable. 
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: milhouse on March 10, 2012, 10:30:15 am
I'm getting an error I haven't seen with .145 with Mame Compiler 64 1.23.

Compiling Mame...
Using Parameters OSD=windows TARGETOS=win32
make: *** makefile: Bad file descriptor.  Stop.
Finished!
0 Hours 0 Minutes and 0 Seconds Elapsed.

I applied 145u1, 145u2, 145u3 and hi_145u1.diff in that order bu that's the error I get...

***********NEVERMIND***********

Had to apply 145u1, hi_145u1.diff 145u2, and 145u3 in that order.
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: milhouse on March 14, 2012, 11:46:27 am
Though I thought I had it working, it seems something went wrong when I try to upgrade from .141 to .145u3 (relevant roms have also been updated FWIW).

I used 145u1, 145u2, 145u3 and hi_145u1.diff but though it works and everything loads, I have a few issues:


I've tried applying hi_145u1.diff after u1 and u3, but it doesn't seem to make a difference.

Anyone seen this before?

Title: Re: Mame Compiler 64 v1.22 Released!
Post by: Flake on April 29, 2012, 05:34:43 pm
I have no idea what I'm doing wrong....trying to compile mame .145 64 bit version with UI.

I get the following error:

Using Parameters OSD=winui TARGETOS=win32 -j3 ARCHOPTS=-march=native PTR64=1
make: *** No targets specified and no makefile found.  Stop.
Finished!
0 Hours 0 Minutes and 0 Seconds Elapsed.


Also, does anyone know where to get a 64bit version of mame .124.  The mamedev sit doesnt seem to have this?
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: Flake on April 29, 2012, 05:38:47 pm
I have no idea what I'm doing wrong....trying to compile mame .145 64 bit version with UI.

I get the following error:

Using Parameters OSD=winui TARGETOS=win32 -j3 ARCHOPTS=-march=native PTR64=1
make: *** No targets specified and no makefile found.  Stop.
Finished!
0 Hours 0 Minutes and 0 Seconds Elapsed.


Also, does anyone know where to get a 64bit version of mame .124.  The mamedev sit doesnt seem to have this?
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: Rok on May 06, 2012, 01:22:24 pm
deleted
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: Flake on May 10, 2012, 03:55:27 pm
Seriously WTF happened to this thread?  Did everyone go on vacation for a month?
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: headkaze on May 24, 2012, 03:06:14 pm
You appear to be trying to compile MameUI but it can't fine the makefile. You can only compile that version if you have copied in the MameUI files. If you follow the instructions on my website correctly you should be fine.
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: Flake on May 25, 2012, 07:59:51 am
Can you be more specific on the "mameui files" I need!  I'm pretty sure I followed directions exactly as I interpreted them.  So perhaps a bit of clarification could help?

Thanks
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: headkaze on May 25, 2012, 03:24:01 pm
I would start from the beginning and follow the instructions here (http://headsoft.com.au/index.php?category=mame&page=mc64).

It has a link to MameUI here (http://www.mameui.info/). MameUI adds a user interface to the standard MAME so you have to add that source code as per the instructions given on my website.

You don't have to add MameUI unless you need the user interface. If you're using a front end you will not need to follow the MameUI steps. In that case take the tick off "MameUI" in the "Compile Options" to prevent it from trying to compile MameUI and skip any steps that mention MAMEUI (as per the instructions).
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: Deadly on June 04, 2012, 03:45:59 pm
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.
 :dunno
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?
 
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: CZakalwe on June 07, 2012, 03:23:10 am
Nevermind :)

BTW thanks Headkaze for this

:applaud:
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: Dazz on June 12, 2012, 03:09:58 pm
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
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: DNA Dan on August 18, 2012, 10:10:02 pm
I got the same result. Are those files no longer needed? I don't even know what they are for.
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: wild_eyed on August 31, 2012, 07:48:59 pm
hi my processor is a phenom x4 9600, what would the best processor selection in MAME Compiler be for me?
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: xefned on October 13, 2012, 08:03:47 am
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!   
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: gman314 on November 15, 2012, 12:31:42 am
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. (http://)
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: headkaze on November 15, 2012, 06:03:47 pm
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. (http://)

It looks like you have tried to apply the patch twice or something. Delete the source and start again.
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: gman314 on November 17, 2012, 01:07:09 am
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.
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: gman314 on November 18, 2012, 03:33:59 pm
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.  :cheers:
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: equlizer on December 03, 2012, 08:47:04 pm
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?
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: flyguy0101 on December 07, 2012, 09:53:59 am
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
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: brihyn on December 07, 2012, 04:12:54 pm
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.
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: headkaze on December 07, 2012, 04:44:50 pm
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.

Quote
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 (http://headsoft.com.au/download/mame/MC64Setup117.exe).

I guess the fact my links don't highlight in any way is a little confusing. I should fix that.
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: brihyn on December 07, 2012, 05:06:12 pm
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!
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: bullrees on December 09, 2012, 06:51:43 pm
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.
Title: Re: Mame Compiler 64 v1.22 Released!
Post by: txjoker on December 12, 2012, 06:14:16 pm
I'm having the exact same issue -- I've cleaned out the source tree twice and repatched with the same results.
Title: Re: Mame Compiler 64 v1.24 Released!
Post by: headkaze on December 13, 2012, 03:20:39 am
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 (http://www.sendspace.com/file/xxb8j0).

Download Mame Compiler 64 v1.24 (http://headsoft.com.au/index.php?category=mame&page=mc64)
Title: Re: Mame Compiler 64 v1.24 Released!
Post by: txjoker on December 13, 2012, 12:37:03 pm
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 (http://www.sendspace.com/file/xxb8j0).

Download Mame Compiler 64 v1.24 (http://headsoft.com.au/index.php?category=mame&page=mc64)

Building now!  Thanks!
Title: Re: Mame Compiler 64 v1.24 Released!
Post by: txjoker on December 13, 2012, 05:54:54 pm
Success!  Thanks for the update!
Title: Re: Mame Compiler 64 v1.24 Released!
Post by: bullrees on December 16, 2012, 05:25:24 pm
Thanks headkaze. Works great. :notworthy:


EDIT: What does the Force Direct Input option do?
Title: Re: Mame Compiler 64 v1.24 Released!
Post by: txjoker on December 18, 2012, 02:12:31 pm
Tested successfully with Mame0147u4 (had to click "Go!" twice to get the binary).
Title: Re: Mame Compiler 64 v1.24 Released!
Post by: headkaze on December 23, 2012, 06:22:26 pm
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.
Title: Re: Mame Compiler 64 v1.24 Released!
Post by: bullrees on December 25, 2012, 03:45:28 pm
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.
Title: Re: Mame Compiler 64 v1.3
Post by: headkaze on December 26, 2012, 02:01:30 pm
Mame Compiler 64 1.3 Released
- Many new compiler options added
Title: Re: Mame Compiler 64 v1.3
Post by: griffindodd on January 08, 2013, 09:04:18 pm
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
Title: Re: Mame Compiler 64 v1.3
Post by: txjoker on January 11, 2013, 06:52:58 pm
Tested successfully with Mame 0.148 (hiscore diff and non-UI)
Title: Re: Mame Compiler 64 v1.3
Post by: Yoeddy1 on January 11, 2013, 11:28:08 pm
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
Title: Re: Mame Compiler 64 v1.3
Post by: txjoker on January 12, 2013, 09:28:04 am
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.
Title: Re: Mame Compiler 64 v1.3
Post by: Yoeddy1 on January 12, 2013, 03:49:18 pm
Txjoker, yep that did it!

Thanks my friend.

Jason
Title: Re: Mame Compiler 64 v1.3
Post by: gamepimp on February 09, 2013, 06:23:06 pm
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.
Title: Re: Mame Compiler 64 v1.3
Post by: raungst on February 09, 2013, 06:53:36 pm
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
Title: Re: Mame Compiler 64 v1.3
Post by: paracai2 on February 16, 2013, 02:24:30 pm
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.
Title: Re: Mame Compiler 64 v1.3
Post by: paracai2 on February 16, 2013, 03:26:35 pm
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.
Title: Re: Mame Compiler 64 v1.3
Post by: paracai2 on February 19, 2013, 03:44:32 am
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.
Title: Help needed to compile
Post by: shaddow76 on February 19, 2013, 07:34:04 pm
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 (http://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 (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
Title: Re: Mame Compiler 64 v1.3
Post by: syncmaster on February 20, 2013, 04:31:33 pm
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
Title: Re: Mame Compiler 64 v1.3
Post by: Harakiri on February 23, 2013, 09:49:38 am
Mame compiler is outputting this error message though everything seems to be correctly set-up.

(http://i.imm.io/X8Ej.png)

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. (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! ;)
Title: Re: Mame Compiler 64 v1.3
Post by: PiriPT on April 17, 2013, 02:52:43 pm


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
Title: Re: Mame Compiler 64 v1.3
Post by: LeedsFan on April 23, 2013, 07:05:03 am
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?
Title: Re: Mame Compiler 64 v1.3
Post by: headkaze on April 24, 2013, 02:36:47 pm
You need to download mingw-mame-20121207.exe (http://mamedev.org/downloader.php?file=tools/mingw-mame-20121207.exe)

Please read the instructions here (http://www.headsoft.com.au/?category=mame&page=mc64)
Title: Re: Mame Compiler 64 v1.3
Post by: Yoeddy1 on June 20, 2013, 01:15:38 am
Just compiled with MAME 0.149 x64.  Worked great!

Thanks,
Jason
Title: Re: Mame Compiler 64 v1.3
Post by: trickyd on October 02, 2013, 09:07:37 pm
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
Title: Re: Mame Compiler 64 v1.3
Post by: headkaze on October 03, 2013, 04:44:30 am
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.
Title: Re: Mame Compiler 64 v1.3
Post by: trickyd on October 03, 2013, 08:13:24 pm
Fantastic! No warnings or errors. Thanks very much

Can you compile UME with it


Many Many Thanks!
Title: Re: Mame Compiler 64 v1.3
Post by: headkaze on October 06, 2013, 11:34:05 pm
Fantastic! No warnings or errors. Thanks very much

Can you compile UME with it

Yes. Check the Target tab.
Title: Re: Mame Compiler 64 v1.3
Post by: Yoeddy1 on November 14, 2013, 06:17:10 pm
Just compiled with MAME 0.151 x64.  Worked great!

Thanks,
Jason
Title: Re: Mame Compiler 64 v1.3
Post by: CWorley on December 02, 2013, 06:58:46 pm
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!
Title: Re: Mame Compiler 64 v1.3
Post by: trickyd on December 21, 2013, 11:46:54 pm
Fantastic app ;)ever think of including hbmame
Title: Re: Mame Compiler 64 v1.3
Post by: trickyd on December 23, 2013, 01:27:23 am
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 (http://www.mamedev.org/tools/previous-20110519.html)
Title: Re: Mame Compiler 64 v1.3
Post by: juggle50 on March 25, 2014, 09:58:14 pm
Can anybody tell me why I'm getting this error?  Thank you so much.
Title: Re: Mame Compiler 64 v1.3
Post by: trickyd on March 28, 2014, 04:57:04 pm
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(http://) but set parameters. Was able to compile ui from command so it must be in MC64.
Title: Re: Mame Compiler 64 v1.3
Post by: Jumpstile on April 08, 2014, 04:17:18 pm
I have the same exact problem. .net Framework 4.5.1 issue perhaps? This worked fine when I was compiling .152 in December...

 - J*
Title: Re: Mame Compiler 64 v1.3
Post by: headkaze on April 30, 2014, 09:33:57 pm
Mame Compiler v1.3.1 Released
- Added fix for output in MameUI 0153+ and FASTDEBUG option
Title: Re: Mame Compiler 64 v1.3.1
Post by: Jumpstile on April 30, 2014, 11:16:04 pm
headkaze, you are awesome. It works perfectly. Thank you so much for an excellent piece of software!!

 - J*
Title: Re: Mame Compiler 64 v1.3.1
Post by: trickyd on May 05, 2014, 05:09:45 pm
Thanks for the update.
Title: Re: Mame Compiler 64 v1.3.1
Post by: Mordwaffe on May 27, 2014, 04:28:20 pm
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  :banghead:
Title: Re: Mame Compiler 64 v1.3.1
Post by: Brian B on June 03, 2014, 07:23:27 pm
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.
Title: Re: Mame Compiler 64 v1.3.1
Post by: Nuexzz on June 04, 2014, 01:13:45 am
guys leave here I attached my error. Is this normal?
Title: Re: Mame Compiler 64 v1.3.1
Post by: Yarb on June 23, 2014, 06:15:31 pm
Thanks Headkaze,

I always thought compiling MAME would be difficult but with your tool it went smooth as silk!!!
Title: Re: Mame Compiler 64 v1.3.1
Post by: withalligators on July 14, 2014, 04:11:52 pm
Trying to compile a 64 bit version of 153 and followed the instructions here (http://"http://www.headsoft.com.au/index.php?category=mame&page=mc64") 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 (http://"http://mamedev.org/release.html")
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
Title: Re: Mame Compiler 64 v1.3.1
Post by: Gatsu on July 23, 2014, 02:48:13 pm
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?

(http://i601.photobucket.com/albums/tt94/gatsugodhand/compileerror_zpsb9b815e6.jpg) (http://s601.photobucket.com/user/gatsugodhand/media/compileerror_zpsb9b815e6.jpg.html)
Title: Re: Mame Compiler 64 v1.3.1
Post by: trickyd on September 12, 2014, 09:26:17 pm
Now that there is new tools, is there going to be an update for MC64
Title: Re: Mame Compiler 64 v1.3.1
Post by: headkaze on September 12, 2014, 10:13:26 pm
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 (http://www.mamedev.org/downloader.php?file=tools/mingw-mame-20140905.exe) from http://www.mamedev.org/tools/ (http://www.mamedev.org/tools/)
Title: Re: Mame Compiler 64 v1.3.1
Post by: trickyd on September 12, 2014, 11:45:44 pm
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.
Title: Re: Mame Compiler 64 v1.3.1
Post by: smalltownguy on September 20, 2014, 09:18:34 am
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.

Title: Re: Mame Compiler 64 v1.3.1
Post by: EMDB on September 20, 2014, 04:53:07 pm
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.
Title: Re: Mame Compiler 64 v1.3.1
Post by: B2K24 on September 21, 2014, 01:25:32 pm
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.
Title: Re: Mame Compiler 64 v1.3.1
Post by: fleskebacon on September 22, 2014, 02:15:47 pm
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.
Title: Re: Mame Compiler 64 v1.3.1
Post by: trickyd on September 22, 2014, 02:27:29 pm
I always had good luck with MC64 so I'll just wait and see if it's updated before the next release.
Title: Re: Mame Compiler 64 v1.3.1
Post by: fleskebacon on September 22, 2014, 03:14:02 pm
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.
Title: Re: Mame Compiler 64 v1.3.1
Post by: B2K24 on September 23, 2014, 02:18:50 pm
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.
Title: Re: Mame Compiler 64 v1.3.1
Post by: Hituro on September 24, 2014, 06:49:52 pm
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?
Title: Re: Mame Compiler 64 v1.3.1
Post by: trickyd on September 24, 2014, 07:15:30 pm
A few posts before http://forum.arcadecontrols.com/index.php/topic,71845.msg1462905.html#msg1462905 (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.
Title: Re: Mame Compiler 64 v1.3.1
Post by: Hituro on September 24, 2014, 07:56:25 pm
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?
Title: Re: Mame Compiler 64 v1.3.1
Post by: Hituro on September 24, 2014, 09:43:16 pm
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 >.<
Title: Re: Mame Compiler 64 v1.3.1
Post by: Hituro on September 25, 2014, 04:32:42 am
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.
Title: Re: Mame Compiler 64 v1.3.1
Post by: B2K24 on October 04, 2014, 12:38:29 am
Newest tools have always worked for me since they got added.
Title: Re: Mame Compiler 64 v1.3.1
Post by: fleskebacon on October 18, 2014, 05:54:13 pm
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!
Title: Re: Mame Compiler 64 v1.3.1
Post by: Jollywest on October 18, 2014, 06:27:44 pm
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.
Title: Re: Mame Compiler 64 v1.3.1
Post by: Mordwaffe on October 22, 2014, 03:47:14 pm
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.

For what it is worth I get the same error with the new tools (20140905) and not the older (20121207).

I can however compile form the command line (not using MC64 to compile, but i did use it to apply the diff) using the new just fine after running the bat files to set the ENV.



Title: Re: Mame Compiler 64 v1.3.1
Post by: trickyd on October 22, 2014, 04:29:40 pm
I updated to the new tools when HomeBrew came out (hb won't compile with old tools). Haven't had any fails after running bat files but still miss the ease of MC64
Title: Re: Mame Compiler 64 v1.3.1
Post by: Mordwaffe on October 22, 2014, 04:50:15 pm
So what does HB (or groovy for that matter) have that regular mame does not?  I am out of the loop on these alternate builds
Title: Re: Mame Compiler 64 v1.3.1
Post by: trickyd on October 23, 2014, 03:04:00 pm
HB has all the hacks you will never see in mame.
Title: Re: Mame Compiler 64 v1.3.1
Post by: headkaze on November 12, 2014, 12:00:07 am
MAME Compiler 64 v1.3.2
- Fix for compiling MAME 0154+
Title: Re: Mame Compiler 64 v1.3.2
Post by: trickyd on November 13, 2014, 01:32:23 pm
Thanks for the update :)
Title: Re: Mame Compiler 64 v1.3.2
Post by: headkaze on November 19, 2014, 07:19:25 am
Mame Compiler 64 v2.0 Released
- UI Update, new options added, auto-download source and patches
Title: Re: Mame Compiler 64 v2.0
Post by: trickyd on December 03, 2014, 08:27:01 am
What is the difference between the source folder under the mingw folder and the mame source folder?
Title: Re: Mame Compiler 64 v2.0
Post by: tronyony on December 27, 2014, 10:35:25 am
EDIT: This seems to be what fixed my problem.  I have now compiled 137, 149, and 151 via external HDD.  I found this reading the hiscore diff thread.

Posted by B2K24: "try any other drive and don't compile on C:\ 
If you have to buy a USB flash or use external. For me trying to compile on win 7 using C:\ is always problems because some directories have lock icons even with UAC disabled and logged on Admin account."



I know this is a somewhat old thread but I just can't seem to figure this out.  I'm trying to add hi_137 to mame0137s and make it 64bit and I just can't get.  The patch, patches fine but it won't compile.  I have tried, what I believe to be, everything.  I'm running Windows 8 on a Mac via Bootcamp.  I have tried MC64 v2.0 with the newest mgwin, MC64 v1.17 with the same mgwin as well as an older mgwin (201001020), and MrDo's way.  all with random errors.  From what I've read, I need to use MC64 v1.17 and mgwin 20100102.  Am I doing something wrong or missing something?  Here is what I get with MC64 v1.17 and the newest mgwin and older mgwin:

Compiling Mame64...
Using Parameters  MSVC_BUILD=1 PTR64=1
process_begin: CreateProcess(NULL, uname -a, ...) failed.
Finished!
0 Hours 0 Minutes and 0 Seconds Elapsed.
process_begin: CreateProcess(NULL, uname -a, ...) failed.
process_begin: CreateProcess(NULL, uname -a, ...) failed.
process_begin: CreateProcess(NULL, uname -a, ...) failed.
process_begin: CreateProcess(NULL, uname -a, ...) failed.
process_begin: CreateProcess(NULL, uname -a, ...) failed.
makefile:94: *** Unable to detect TARGETOS from uname -a: .  Stop.


Thank you in advance for looking.

V/r
Tony
Title: Re: Mame Compiler 64 v2.0
Post by: ramos8414 on January 01, 2015, 07:19:39 pm
Does this work with mame 0.157?
Title: Re: Mame Compiler 64 v2.0
Post by: milhouse on January 01, 2015, 10:01:14 pm
Is anyone else having a problem with MinGW?  I downloaded the package from mame but am getting  data errors for a bunch of files in the 7-zip pacage when it tries to self-exract.
Title: Re: Mame Compiler 64 v2.0
Post by: tronyony on January 02, 2015, 01:43:02 am
Is anyone else having a problem with MinGW?  I downloaded the package from mame but am getting  data errors for a bunch of files in the 7-zip pacage when it tries to self-exract.

I didn't have issues with MinGW.  Maybe try a different web browser?


V/r
Tony
Title: Re: Mame Compiler 64 v2.0
Post by: EMDB on January 30, 2015, 11:01:57 am
Version 0.157 compiled just fine with Mame Compiler 64 2.0 + MinGW MAME 20140905 but version 0.158 doesn't...

Compiling Mame...
Using Parameters -j6 NOWERROR=1 TARGETOS=win32 TARGET=mame OSD=windows PTR64=1
mkdir -p obj/windows64
mkdir -p obj/windows64/build
mkdir -p obj/windows64/emu/audio
The syntax of the command is incorrect.
mkdir -p obj/windows64/emu/bus
The syntax of the command is incorrect.
mkdir -p obj/windows64/emu/bus/centronics
The syntax of the command is incorrect.
mkdir -p obj/windows64/emu/bus/generic
The syntax of the command is incorrect.
make: [obj/windows64] Error 1 (ignored)
mkdir -p obj/windows64/emu/bus/isa
The syntax of the command is incorrect.
make: [obj/windows64/build] Error 1 (ignored)
mkdir -p obj/windows64/emu/bus/neogeo
The syntax of the command is incorrect.
make: [obj/windows64/emu/audio] Error 1 (ignored)
mkdir -p obj/windows64/emu/bus/rs232
The syntax of the command is incorrect.
mkdir -p obj/windows64/emu/bus/scsi
make: [obj/windows64/emu/bus] Error 1 (ignored)
The syntax of the command is incorrect.
mkdir -p obj/windows64/emu/bus/vectrex
make: [obj/windows64/emu/bus/centronics] Error 1 (ignored)
The syntax of the command is incorrect.
make: [obj/windows64/emu/bus/generic] Error 1 (ignored)

...

make: [obj/windows64/osd/windows] Error 1 (ignored)
make: [obj/windows64/tools] Error 1 (ignored)
Assembler messages:
Fatal error: can't create obj/windows64/build/makedep.o: No such file or directory
Assembler messages:
Fatal error: can't create obj/windows64/lib/util/astring.o: No such file or directory
Assembler messages:
Fatal error: can't create obj/windows64/lib/util/corealloc.o: No such file or directory
Assembler messages:
Fatal error: can't create obj/windows64/lib/util/corefile.o: No such file or directory
src/lib/util/corealloc.c:384:1: fatal error: error writing to -: Invalid argument
 }
 ^
compilation terminated.
Assembler messages:
Fatal error: can't create obj/windows64/lib/util/unicode.o: No such file or directory
make: *** [obj/windows64/lib/util/corealloc.o] Error 1
make: *** Waiting for unfinished jobs....
src/lib/util/unicode.c:345:1: fatal error: error writing to -: No error
 }
 ^
compilation terminated.
src/lib/util/astring.c:483:1: fatal error: error writing to -: No error
 }
 ^
compilation terminated.
src/build/makedep.c:463:1: fatal error: error writing to -: Invalid argument
 }
 ^
compilation terminated.
make: *** [obj/windows64/build/makedep.o] Error 1
make: *** [obj/windows64/lib/util/astring.o] Error 1
make: *** [obj/windows64/lib/util/unicode.o] Error 1
src/lib/util/corefile.c:1052:1: fatal error: error writing to -: No error
 }
 ^
compilation terminated.
make: *** [obj/windows64/lib/util/corefile.o] Error 1
Assembler messages:
Fatal error: can't create obj/windows64/osd/windows/vconv.o: No such file or directory
make: *** [obj/windows64/osd/windows/vconv.o] Error 1
Finished!
0 Hours 0 Minutes and 2 Seconds Elapsed.
Title: Re: Mame Compiler 64 v2.0
Post by: headkaze on January 31, 2015, 03:00:23 am
Please download Mame Compiler 64 2.0.1 for the 0.158+ fix
Title: Re: Mame Compiler 64 v2.0
Post by: EMDB on January 31, 2015, 04:40:31 am
Please download Mame Compiler 64 2.0.1 for the 0.158+ fix
Thanks. Works like a charm again  :applaud:
Title: Re: Mame Compiler 64 v2.0.1
Post by: otsep on February 28, 2015, 01:58:50 pm
I'm seeing this error when trying to compile 158(WinUI) using 2.0.1.

Windows 7 Pro 64-bit

The src was freshly downloaded before compiling.

Code: [Select]
Compiling src/osd/windows/d3d9intf.c...
Compiling src/osd/windows/drawd3d.c...
Compiling src/osd/windows/drawdd.c...
Compiling src/osd/windows/d3dhlsl.c...
make: *** No rule to make target `obj/winui64/osd/windows/drawbgfx.o', needed by `obj/winui64/libosd.a'.  Stop.
make: *** Waiting for unfinished jobs....
Compiling src/osd/windows/drawgdi.c...
Finished!
0 Hours 7 Minutes and 12 Seconds Elapsed.

Regular MAME 158 compiles fine.
Title: Re: Mame Compiler 64 v2.0.1
Post by: otsep on February 28, 2015, 04:57:28 pm
I noticed that MAMEui is now 159.  Could this be the cause?
Title: Re: Mame Compiler 64 v2.0.1
Post by: otsep on March 03, 2015, 01:39:08 am
?
Title: Re: Mame Compiler 64 v2.0.1
Post by: headkaze on March 03, 2015, 07:34:52 am
I noticed that MAMEui is now 159.  Could this be the cause?

Yes the MameUI file does not include a version number to identify it so it doesn't always match the official Mame version in MC64's file list. I have updated the file list so you can download it and try again.
Title: Re: Mame Compiler 64 v2.0.1
Post by: otsep on March 03, 2015, 10:04:43 am

Yes the MameUI file does not include a version number to identify it so it doesn't always match the official Mame version in MC64's file list. I have updated the file list so you can download it and try again.

Thanks headkaze. That took care of it.


Sent from my iPhone using Tapatalk
Title: Re: Mame Compiler 64 v2.0.1
Post by: machyavel on March 09, 2015, 07:35:25 pm
Hello and thanks a lot for mame compiler 64. I used it many times but now I'm facing an issue with 2.0.1, trying to compile mame159 with groovy patch.

If possible, please have a look at the log file attached. Error messages start line 2741 :
In file included from z:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/../../../../x86_64-w64-mingw32/include/winnt.h:1446:0

Any clue on how to fix this?
Thanks in advance


EDIT: I upgraded MINGW and it works now.
Title: Re: Mame Compiler 64 v2.0.1
Post by: Jumpstile on March 25, 2015, 09:23:12 am
Can someone give me instructions on how to set up the new version of MinGW (the latest version from the GIT) with this compiling software? I can't seem to get it working for some reason... A quick step by step would be helpful, I'm sure, for many here and on the net.

Thank you!!

- J*
Title: Re: Mame Compiler 64 v2.0.1
Post by: what2be on March 26, 2015, 03:30:48 am
I second that suggestion! (and Jumpstile, I just sent you a PM on Hyperspin as well asking this very question)
Title: Re: Mame Compiler 64 v2.0.1
Post by: headkaze on March 26, 2015, 03:56:25 am
I just tested Mame 0.160 with the MinGW version you can download directly from MC64 and it works fine. So I would just use that. I may update to the newer version in the near future.
Title: Re: Mame Compiler 64 v2.0.1
Post by: bobmoo79 on April 08, 2015, 03:04:20 pm
Deleted.
Title: Re: Mame Compiler 64 v2.0.1
Post by: gamepimp on April 23, 2015, 08:28:49 pm
Just downloaded MAME 0.160 source, 0.160 hi score patch, MC 2.0.1, and the MinGW from MC site. Applied the patch without any issues. Started compiling and it looked like things were going well. But after about 8 minutes, the compiling completed with the error messages listed below: 

Finished!
0 Hours 9 Minutes and 54 Seconds Elapsed.
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/../../../../x86_64-w64-mingw32/include/intrin.h:950:5: error: conflicts with new declaration with 'C' linkage
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/include/emmintrin.h:819:1: error: previous declaration of 'long long int _mm_cvtsd_si64x(__m128d)' with 'C++' linkage
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/../../../../x86_64-w64-mingw32/include/intrin.h:951:5: error: conflicts with new declaration with 'C' linkage
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/include/emmintrin.h:869:1: error: previous declaration of '__m128d _mm_cvtsi64x_sd(__m128d, long long int)' with 'C++' linkage
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/../../../../x86_64-w64-mingw32/include/intrin.h:952:5: error: conflicts with new declaration with 'C' linkage
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/include/xmmintrin.h:595:1: error: previous declaration of '__m128 _mm_cvtsi64x_ss(__m128, long long int)' with 'C++' linkage
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/../../../../x86_64-w64-mingw32/include/intrin.h:953:5: error: conflicts with new declaration with 'C' linkage
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/include/xmmintrin.h:505:1: error: previous declaration of 'long long int _mm_cvtss_si64x(__m128)' with 'C++' linkage
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/../../../../x86_64-w64-mingw32/include/intrin.h:954:5: error: conflicts with new declaration with 'C' linkage
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/include/emmintrin.h:841:1: error: previous declaration of 'long long int _mm_cvttsd_si64x(__m128d)' with 'C++' linkage
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/../../../../x86_64-w64-mingw32/include/intrin.h:955:5: error: conflicts with new declaration with 'C' linkage
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/include/xmmintrin.h:550:1: error: previous declaration of 'long long int _mm_cvttss_si64x(__m128)' with 'C++' linkage
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/../../../../x86_64-w64-mingw32/include/intrin.h:956:5: error: conflicts with new declaration with 'C' linkage
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/include/emmintrin.h:1467:1: error: previous declaration of '__m128i _mm_cvtsi64x_si128(long long int)' with 'C++' linkage
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/../../../../x86_64-w64-mingw32/include/intrin.h:957:5: error: conflicts with new declaration with 'C' linkage
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/include/emmintrin.h:221:1: error: previous declaration of 'long long int _mm_cvtsi128_si64x(__m128i)' with 'C++' linkage
c:\mingw\mingw64-w64\bin\../lib/gcc/x86_64-w64-mingw32/4.6.3/../../../../x86_64-w64-mingw32/include/intrin.h:958:5: error: conflicts with new declaration with 'C' linkage
make: *** [obj/windows64/osd/modules/debugger/debugwin.o] Error 1


Any thoughts on what might be going wrong here? Certainly looks like there's an issue with MinGW. But I believe the version of MinGW from the MC site is supposed to work fine with 0.160. I have Windows 7 Pro 64 bit with an i5 processor. I've included a pic of the build options I had selected. Any help is greatly appreciated!

Title: Re: Mame Compiler 64 v2.0.1
Post by: syncmaster on April 30, 2015, 08:44:13 am
Hello
the compile tools have changed once again, so the best way is to wait MC64 to be updated
which is surely on the way with the MAME 0.161 release out
Title: Re: Mame Compiler 64 v2.0.1
Post by: gamepimp on April 30, 2015, 10:54:51 am
Sounds good. I will just hang tight until the next release. Thx!
Title: Re: Mame Compiler 64 v2.0.1
Post by: Jumpstile on May 01, 2015, 05:08:17 pm
Haven't been able to compile MAME .161 with the old tools. Hope a fix is in the works for the compiler! Thanks a ton, Headkaze!

 - J*
Title: Re: Mame Compiler 64 v2.0.1
Post by: Yoeddy1 on May 01, 2015, 07:41:57 pm
Yes, please update asap.  We appreciate the work with this as it makes compiling so easy!

Jason
Title: Re: Mame Compiler 64 v2.0.1
Post by: Jonny G on May 02, 2015, 11:18:37 am
Not able to compile with latest mingw either but also, hi scores don't seem to be working in .160 or .161. I just reverted to .153 and all was fine. Checked my mame.ini and all patches were enabled and hi score directory set correctly. Anyone else getting this?

EDIT - scratch that. Somehow my hiscore.dat had gotten deleted.
Title: Re: Mame Compiler 64 v2.0.1
Post by: headkaze on May 02, 2015, 02:59:31 pm
I'm currently updating MC64 to support Mame 0161 and the new build tools.
Title: Re: Mame Compiler 64 v2.0.1
Post by: Yoeddy1 on May 03, 2015, 09:12:59 pm
It looks like an update has been made, but has the process changed?  I'm not sure where I'm going wrong.  Do I need to update compiler tools?  When I download the MAME source, diff file, and compiler tools, I then try to apply the patch, but it errors out. 

Thoughts?

Jason
Title: Re: Mame Compiler 64 v2.0.1
Post by: Yoeddy1 on May 03, 2015, 10:55:15 pm
Nevermind...I figured it out.  I was trying to apply the patch before the compiling tools were done unzipping.

Thanks,
Jason
Title: Re: Mame Compiler 64 v2.0.1
Post by: headkaze on May 04, 2015, 01:22:27 am
Nevermind...I figured it out.  I was trying to apply the patch before the compiling tools were done unzipping.

Thanks,
Jason

Yeah there are a few issues that need sorting out which is why there has been no official announcement yet.
Title: Re: Mame Compiler 64 v2.0.1
Post by: Yoeddy1 on May 04, 2015, 01:41:55 am
Nevermind...I figured it out.  I was trying to apply the patch before the compiling tools were done unzipping.

Thanks,
Jason

Yeah there are a few issues that need sorting out which is why there has been no official announcement yet.

Ok, thanks.  I did get MAME 0.161 to compile and have it working with your latest version.  If there's another version coming, I'll test it as well.

Thanks,
Jason
Title: Re: Mame Compiler 64 v2.0.1
Post by: Jumpstile on May 04, 2015, 12:04:11 pm
Boy, it takes much longer to compile with the new tools and MAME Compiler 2.161... well over an hour to compile on an i5 processor... Used to take me 30-45 mins tops.


Nevermind... Problem with AntiVirus. Thanks for the updates and bugfixes, headkaze!

 - J*
Title: Re: Mame Compiler 64 v2.0.1
Post by: headkaze on May 04, 2015, 12:22:49 pm
Ok, thanks.  I did get MAME 0.161 to compile and have it working with your latest version.  If there's another version coming, I'll test it as well.

There is a new upload but still nothing official. It should now wait for the extraction to finish before allowing you to exit the download.

I believe there is a problem if you download Mame and MameUI source at the same time and try a MameUI compile. I believe it's because the downloader currently doesn't wait for the previous download to finish zip extraction before going onto the next.

Boy, it takes much longer to compile with the new tools and MAME Compiler 2.161... well over an hour to compile on an i5 processor... Used to take me 30-45 mins tops.

For some reason the "-j" parameter is not working. It specifies the number of parallel jobs to run. If anyone has any idea why or how we can solve this please let me know.

EDIT: I just noticed your edit. I believe there is still a problem with this switch not working. I only see two make processes running when I specified 8 parallel jobs. Can anyone confirm?
Title: Re: Mame Compiler 64 v2.0.1
Post by: Jumpstile on May 04, 2015, 03:42:46 pm
When I specify 6 parallel jobs, I get 3 MAKE processes.

I was also wondering - can you add a HBMAME target? I can't compile HBMAME with MAME Compiler as of now. Thanks!

 - J*
Title: Re: Mame Compiler 64 v2.0.1
Post by: Santo8742 on May 07, 2015, 12:05:26 am
I'm having all kinds of errors trying to compile. Trying to compile version 0161 with hiscore. Keep getting the attached error. When I try to compile from command line I get the error "python is not available in path". Any ideas on what is causing this and how to fix it?

Title: Re: Mame Compiler 64 v2.0.1
Post by: headkaze on May 07, 2015, 01:59:12 am
I'm having all kinds of errors trying to compile. Trying to compile version 0161 with hiscore. Keep getting the attached error. When I try to compile from command line I get the error "python is not available in path". Any ideas on what is causing this and how to fix it?

The latest Mame Compiler 64 requires the new build tools installed. So you will need to go to downloads tab and download them.
Title: Re: Mame Compiler 64 v2.0.1
Post by: CapnBry on May 07, 2015, 05:31:02 pm
For some reason the "-j" parameter is not working. It specifies the number of parallel jobs to run. If anyone has any idea why or how we can solve this please let me know.

EDIT: I just noticed your edit. I believe there is still a problem with this switch not working. I only see two make processes running when I specified 8 parallel jobs. Can anyone confirm?
Yeah I noticed this too, the -j option isn't working at the top level. I see that MameCompiler64 launches make which launches multiple makes, but only one g++ instance at a time. I edited the mame makefile and modified MAKEPARAMS:
Code: [Select]
MAKEPARAMS := -R -j4

It works regardless of the make command line. It does not look like you can set this from the main make command because it doesn't override it, it just sets it. Other options don't appear to be working either because I don't have "Include symbols" checked yet the final executable definitely has symbols in it.
Title: Re: Mame Compiler 64 v2.0.1
Post by: abispac on May 07, 2015, 10:44:17 pm
im trying to compile mame .138 but the mame compiler 64 v1.17 wont do the job,and i read that   1.18 will work, but cant find a download for it, can anyone help share it?
Title: Re: Mame Compiler 64 v2.0.1
Post by: headkaze on May 08, 2015, 06:11:36 am
I edited the mame makefile and modified MAKEPARAMS

Thanks for the info. When I get a moment I'll update MC64 to use this method.

im trying to compile mame .138 but the mame compiler 64 v1.17 wont do the job,and i read that   1.18 will work, but cant find a download for it, can anyone help share it?

Check out the "Older Versions of MAME" section at the Mame Compiler 64 homepage (http://headsoft.com.au/index.php?category=mame&page=mc64)
Title: Re: Mame Compiler 64 v2.0.1
Post by: headkaze on May 08, 2015, 07:35:02 am
Okay MC64 has been updated to support multiple jobs again. Compile time for me went from over an hour to 20 minutes  :cheers:

There is still no official update as there are still a few minor issues left to resolve but for the most part it should be fine to download and start using it to compile Mame 0161+

Note 1. You must download the latest Build Tools to compile again (from the Download tab in MC64). Your MinGW folder structure will now be 'buildtools' with 'src' and 'patch' sub-folders. Also there is a new "Update Build Tools" button which will grab the latest build tools from Git (this will only work after you do the initial "Build Tools" download).

Note 2. If you download Mame and MameUI source at the same time then do a compile you may get an "undefined reference" error when you target a compile for WinUI. If this happens download the MameUI source again then put a tick next to "Clean Compile" and try again.
Title: Re: Mame Compiler 64 v2.0.1
Post by: abispac on May 08, 2015, 11:03:15 am
Check out the "Older Versions of MAME" section at the Mame Compiler 64 homepage (http://headsoft.com.au/index.php?category=mame&page=mc64)
I did, i got the source for mame .138, i downloaded mame compiler64 v1.17, and went i get all together,i get
"make: *** windows32_openpipe(): DuplicateHandle(In) failed (e=6)" right away.
ive tried "You need to download mingw-mame-20121207.exe" as you suggestion on a similar problem , i tried some other mingw version but no succes, i read that v1.18 would do the job but cant seem to find a download for your previews versions.
Title: Re: Mame Compiler 64 v2.0.1
Post by: Leachdude on May 19, 2015, 11:13:00 am
Need help please.  I have read the thread and still can not figure out why I get this message when applying the hi_161.txt patch.

Compiling Mame...
Using Parameters PYTHON_AVAILABLE=python SHELLTYPE=msdos -j6 NOWERROR=1 TARGETOS=windows TARGET=mame OSD=windows PTR64=1
Running 'setup-Qt.bat'
Running 'env.bat'
Running 'init.bat'
Error Compiling Mame.
CompileMame(): The system cannot find the file specified


My directory structure is buildtools with patch and src folders.


What am I missing?   I have tried everything I can think of.
Title: Re: Mame Compiler 64 v2.0.1
Post by: Yoeddy1 on May 29, 2015, 04:29:24 am
So will this work with 0.162?  Sounds like there a lot of changes.

Jason
Title: Re: Mame Compiler 64 v2.0.1
Post by: Jumpstile on May 29, 2015, 08:51:21 am
Haven't had any success building .162 yet with MAME Compiler 2.0.161.

 - J*
Title: Re: Mame Compiler 64 v2.0.1
Post by: headkaze on May 29, 2015, 07:06:02 pm
Haven't had any success building .162 yet with MAME Compiler 2.0.161.
I didn't have a problem compiling 0162.
Title: Re: Mame Compiler 64 v2.0.1
Post by: Yoeddy1 on May 30, 2015, 03:48:20 am
How did you pull down 0.162?  I run it and it's still pulling down 0.161 stuff.

Thanks,
Jason
Title: Re: Mame Compiler 64 v2.0.1
Post by: headkaze on May 30, 2015, 06:06:51 am
How did you pull down 0.162?  I run it and it's still pulling down 0.161 stuff.

As soon as MKChamp updates the hiscore diff I'll update the downloads.
Title: Re: Mame Compiler 64 v2.0.1
Post by: Jumpstile on May 30, 2015, 03:39:23 pm
The program does not work if you are trying to compile an arcade only version of MAME. The proper subtarget should be arcade, not MAME for this. Can you add the proper alternate subtargets please?

Compiling src/mess/drivers/vii.c...
Compiling src/mess/drivers/wicat.c...
Compiling src/mess/drivers/xor100.c...
Compiling src/mess/drivers/xavix.c...
Compiling src/mess/drivers/zorba.c...
Archiving libskeleton.a...
Compiling src/mame/mame.c...
Compiling src/version.c...
Building driver list...
Importing drivers from '../../../../../src/mame/arcade.lst'
Compiling generated/mame/mame/drivlist.c...
Importing drivers from '../../../../../src/mame/mess.lst'
13859 drivers found
make[2]: *** No rule to make target `../../../../generated/resource/arcadevers.rc', needed by `../../../../mingw-gcc/obj/x64/Release/mameui.res'.  Stop.
make[1]: Leaving directory `E:/MAMESrc/build/projects/winui/mame/gmake-mingw64-gcc'
Finished!
0 Hours 32 Minutes and 23 Seconds Elapsed.
make[1]: *** [mame] Error 2
make: *** [windows_x64] Error 2

 - J*
Title: Re: Mame Compiler 64 v2.0.1
Post by: Yoeddy1 on May 30, 2015, 05:01:55 pm
Looks like the 0.162 diff file is up now.  Looks like MC64Setup.exe still contains 0.161. Hopefully the targets are updated soon.

Thanks,
Jason
Title: Re: Mame Compiler 64 v2.0.1
Post by: Jdurg on May 31, 2015, 02:41:56 am
Looking forward to an update.  Got a new laptop for the first time in eight years, so I can't wait to play with the new HLSL options.
Title: Re: Mame Compiler 64 v2.0.1
Post by: headkaze on June 01, 2015, 05:13:16 am
MC64 2.0.162 Released
- Support for "arcade" and "mess" sub targets
Title: Re: Mame Compiler 64 v2.0.1
Post by: Yoeddy1 on June 01, 2015, 04:56:43 pm
Anybody else hanging up on UnZip 'buildtools.7z' Done?  I can't get an active "OK" button. 
Title: Re: Mame Compiler 64 v2.0.1
Post by: Jumpstile on June 01, 2015, 04:58:07 pm
I haven't had to do that. Compiling MAME and MESS as subtargets now works great. Thanks!


 - J*
Title: Re: Mame Compiler 64 v2.0.1
Post by: Yoeddy1 on June 01, 2015, 06:36:12 pm
So I'm trying this on another PC and am getting the same thing.  What in the world is going on?

I've used this for every release since it came out way back when.

I downloaded and ran MC64setup.exe.

All paths look correct for everything. 

I go to the Download tab and put a checkbox by MAME0162 Source, HiScore diff patch, and Build Tools.

I go to the build options tab and select Auto for optimization, and the subtarget as Arcade.

I go back to the Download tab and click the Download Selected button.

It pulls everything down, but once it gets to the following screen it hangs forever and won't move past Unzip build tools.  (see screenshot).

Is it actually doing something?  My HDD light isn't flickering.  Clicking cancel won't do anything and the OK button is always grayed out.  Is there another process that I'm supposed to run?  I don't even get the point where I can click go to compile or apply the diff patch.

Anything would be appreciated.

Thanks,
Jason
Title: Re: Mame Compiler 64 v2.0.1
Post by: Yoeddy1 on June 01, 2015, 10:00:38 pm
Looking at the links in the updated version, I see:

http://mamedev.org/downloader.php?file=releases/mame0162s.exe (http://mamedev.org/downloader.php?file=releases/mame0162s.exe)

This ends in a 404.

Shouldn't it be:

http://mamedev.org/downloader.php?file=mame0162/mame0162s.exe (http://mamedev.org/downloader.php?file=mame0162/mame0162s.exe)

Thanks,
Jason
Title: Re: Mame Compiler 64 v2.0.1
Post by: Yoeddy1 on June 01, 2015, 10:28:54 pm
Yeah, the MAME source is what's locking it up.  If you select the MAME 0162 source by itself and try to download it, that's what's locking everything up.

Sent you a PM headkaze.

Thanks,
Jason
Title: Re: Mame Compiler 64 v2.0.1
Post by: headkaze on June 02, 2015, 01:34:12 am
Thanks Jason, I've updated it.
Title: Re: Mame Compiler 64 v2.0.1
Post by: Yoeddy1 on June 02, 2015, 01:40:19 am
You're welcome.  Thank you!  :)

Jason
Title: Re: Mame Compiler 64 v2.0.1
Post by: EMDB on June 02, 2015, 03:28:47 am
Why is the file size of the MAME executable increased that much from 0.161 to 0.162? And what exactly are the 'tiny', 'arcade' and default builds compared to the old MAME / MESS ones?
Title: Re: Mame Compiler 64 v2.0.1
Post by: headkaze on June 02, 2015, 12:55:44 pm
Why is the file size of the MAME executable increased that much from 0.161 to 0.162? And what exactly are the 'tiny', 'arcade' and default builds compared to the old MAME / MESS ones?

As per the whatsnew_0162.txt (http://www.mamedev.org/releases/whatsnew_0162.txt)

Quote
As of 0.162 the MAME and MESS projects have been combined into a single emulator.
Quote
-MAME now represents full build, for building MESS drivers only use
 make SUBTARGET=mess, for building only Arcades
 drivers only use: make SUBTARGET=arcade [Miodrag Milanovic]
Title: Re: Mame Compiler 64 v2.0.162
Post by: EMDB on June 02, 2015, 03:10:58 pm
Thanks. I expected something like that but the Arcade version is still WAY bigger than the previous version (121 MB against 89 MB)  :dizzy:
Title: Re: Mame Compiler 64 v2.0.162
Post by: Yoeddy1 on June 02, 2015, 06:28:45 pm
Headkaze, it's working great on my end now.  Just finished compiling 0.162 (arcade sub-target).

One bit of feedback for the next release...

The high score patch points to a .diff file by default.  What gets downloaded is a .txt file.  I always have to manually browse to and select the .txt file, otherwise the patching process fails.  A user may not know to do that.

Thanks,
Jason
Title: Re: Mame Compiler 64 v2.0.162
Post by: MydknyteStyrm on June 03, 2015, 09:01:24 pm
Thanks for a great program! I am having a bit of trouble though. I can download and get the system to compile Mame 0162, but it hasnt finished yet. Right now its been over five hours, and all four of my cores are at 100%, making the computer slow to a crawl. I have a i5-4670k and I am trying to compile a 32bit version of Mame 0162 on Windows 7 Ultimate 64bit. The reason I want to go with 32 is because my Aimtraks dont seem to work in 64 bit Mame.

The question I have is, what would be the optimal settings on my Build Options tab for my system? What should the SubTarget be? I had the Optimize=AutoDetect, and left everything unchecked except for No Warnings as Errors. Should the Optimize Level be at 0? Any insight would be greatly appreciated. Thanks!
Title: Mame Compiler 64 v2.0.162
Post by: Jumpstile on June 03, 2015, 09:08:36 pm
Thanks for a great program! I am having a bit of trouble though. I can download and get the system to compile Mame 0162, but it hasnt finished yet. Right now its been over five hours, and all four of my cores are at 100%, making the computer slow to a crawl. I have a i5-4670k and I am trying to compile a 32bit version of Mame 0162 on Windows 7 Ultimate 64bit. The reason I want to go with 32 is because my Aimtraks dont seem to work in 64 bit Mame.

The question I have is, what would be the optimal settings on my Build Options tab for my system? What should the SubTarget be? I had the Optimize=AutoDetect, and left everything unchecked except for No Warnings as Errors. Should the Optimize Level be at 0? Any insight would be greatly appreciated. Thanks!

Try disabling your AV and try it.

 - J*
Title: Re: Mame Compiler 64 v2.0.162
Post by: MydknyteStyrm on June 04, 2015, 11:15:14 am
That did the trick. Thanks so much!


Sent from my iPhone using Tapatalk
Title: Re: Mame Compiler 64 v2.0.162
Post by: Jumpstile on June 04, 2015, 11:16:31 am
Cool. Same exact thing happened to me. What AV do you use?


 - J*
Title: Re: Mame Compiler 64 v2.0.162
Post by: MydknyteStyrm on June 04, 2015, 11:17:01 am
I have Norton installed


Sent from my iPhone using Tapatalk
Title: Re: Mame Compiler 64 v2.0.162
Post by: Jumpstile on June 04, 2015, 11:19:05 am
Interesting. I use Webroot. Headkaze, is this an issue you have run across? I can't compile anything with my AV turned on using MAME Compiler. Turning it off isn't a big deal, but just curious. Thanks again!!


 - J*
Title: Re: Mame Compiler 64 v2.0.162
Post by: jaquer on June 20, 2015, 12:39:02 pm
Hey all.

I'm getting an error trying to get 0.158 to compile. I'm getting errors about linking PortMidi. Am I supposed to compile that separately?

I installed the buildtools first, using the install.exe from mamedev.org/tools. I've tried using the 0.158 source from git (checked out the mame0158 tag) and from mame0158s.zip. I've tried the compile with and without the hi_158 diff.

I'm running W7 Ultimate 64 bit, trying to build a 32bit target for an XP machine. All MC build options are set to off, except "No Warnings as Errors".

I'm targeting this build because this is the romset I have access to.

Any help is greatly appreciated.

Code: [Select]
Linking mame...
obj/windows/libosd.a(portmidi.o):portmidi.c:(.text+0x89): undefined reference to `Pm_GetDefaultInputDeviceID'
Finished!
1 Hours 23 Minutes and 44 Seconds Elapsed.
obj/windows/libosd.a(portmidi.o):portmidi.c:(.text+0xe9): undefined reference to `Pm_GetDefaultOutputDeviceID'
obj/windows/libosd.a(portmidi.o):portmidi.c:(.text+0x1b4): undefined reference to `Pm_GetDefaultInputDeviceID'
obj/windows/libosd.a(portmidi.o):portmidi.c:(.text+0x2b4): undefined reference to `Pm_GetDefaultOutputDeviceID'
obj/windows/libportmidi.a(portmidi.o):portmidi.c:(.text+0xfe): undefined reference to `pm_alloc'
obj/windows/libportmidi.a(portmidi.o):portmidi.c:(.text+0x1ec): undefined reference to `pm_init'
obj/windows/libportmidi.a(portmidi.o):portmidi.c:(.text+0x2a5): undefined reference to `pm_init'
obj/windows/libportmidi.a(portmidi.o):portmidi.c:(.text+0x302): undefined reference to `pm_init'
obj/windows/libportmidi.a(portmidi.o):portmidi.c:(.text+0x4e5): undefined reference to `pm_init'
obj/windows/libportmidi.a(portmidi.o):portmidi.c:(.text+0x514): undefined reference to `pm_term'
obj/windows/libportmidi.a(portmidi.o):portmidi.c:(.text+0xf74): undefined reference to `pm_alloc'
obj/windows/libportmidi.a(portmidi.o):portmidi.c:(.text+0x107b): undefined reference to `pm_free'
obj/windows/libportmidi.a(portmidi.o):portmidi.c:(.text+0x1096): undefined reference to `pm_free'
obj/windows/libportmidi.a(portmidi.o):portmidi.c:(.text+0x1114): undefined reference to `pm_alloc'
obj/windows/libportmidi.a(portmidi.o):portmidi.c:(.text+0x11f1): undefined reference to `Pt_Started'
obj/windows/libportmidi.a(portmidi.o):portmidi.c:(.text+0x11fc): undefined reference to `Pt_Time'
obj/windows/libportmidi.a(portmidi.o):portmidi.c:(.text+0x1221): undefined reference to `pm_free'
obj/windows/libportmidi.a(portmidi.o):portmidi.c:(.text+0x1248): undefined reference to `Pt_Start'
obj/windows/libportmidi.a(portmidi.o):portmidi.c:(.text+0x1342): undefined reference to `pm_free'
D:/games/MAME/buildtools/vendor/mingw32/bin/../lib/gcc/i686-w64-mingw32/4.9.2/../../../../i686-w64-mingw32/bin/ld.exe: obj/windows/libportmidi.a(portmidi.o): bad reloc address 0x0 in section `.data'
collect2.exe: error: ld returned 1 exit status
make: *** [mame] Error 1

Edit: Got it working. The error had to do with the 32-bit cross-compile. I edited env.bat to force using MinGW32 and I was able to link the executable.
Title: Re: Mame Compiler 64 v2.0.162
Post by: roknrol on June 21, 2015, 12:34:50 pm
Trying to download MinGW from MC site results in a 404 at GitHub. Same when trying directly from mamedev.org. Was able to find the mingw-mame-20121207.exe at mameworld.info, though.

Should be good, right? Trying to compile .151 if that makes a difference.
Title: Re: Mame Compiler 64 v2.0.162
Post by: Robbbert on June 25, 2015, 10:31:58 pm
Thanks. I expected something like that but the Arcade version is still WAY bigger than the previous version (121 MB against 89 MB)  :dizzy:

You need to strip out the symbols.

Add the option STRIP_SYMBOLS=1 on your make line.
Title: Re: Mame Compiler 64 v2.0.162
Post by: headkaze on June 26, 2015, 06:23:55 pm
Mame Compiler 64 v2.0.163 Released (http://headsoft.com.au/index.php?category=mame&page=mc64)
- Added support for STRIP_SYMBOLS

This option is on by default as it will reduce the MAME binary substantially (ie. 118 MB vs 167 MB for a vanilla 64-bit build)
Title: Re: Mame Compiler 64 v2.0.163
Post by: Yoeddy1 on July 01, 2015, 01:28:42 am
Worked fantastic with 0.163!  Thanks headkaze!

Jason
Title: Re: Mame Compiler 64 v2.0.163
Post by: Pitou on July 08, 2015, 01:44:25 pm
Hello,

Does anyone know the difference between the Arcade and Tiny options in the compiler?

Also, is it possible to compile without the small embedded menu in mame?

Thank you.

Pitou!
Title: Re: Mame Compiler 64 v2.0.163
Post by: delt31 on July 18, 2015, 11:48:51 am
....actually I"m making some progress......
Title: Re: Mame Compiler 64 v2.0.163
Post by: dmckean on July 20, 2015, 04:17:17 pm
Is there an archive of previous releases of Mame Compiler 64? I'm trying to compile version 1.44 but I'm having trouble.
Title: Re: Mame Compiler 64 v2.0.163
Post by: Yoeddy1 on July 30, 2015, 10:02:54 am
MAME 0.164 is out.  Are the config files up to date yet or are they still at 0.163?

Thanks,
Jason
Title: Re: Mame Compiler 64 v2.0.163
Post by: headkaze on July 31, 2015, 01:03:47 am
MAME 0.164 is out.  Are the config files up to date yet or are they still at 0.163?

It's updated now.
Title: Re: Mame Compiler 64 v2.0.163
Post by: Yoeddy1 on July 31, 2015, 07:43:06 pm
Just finished up a 0.164 compile. Worked great!

Thanks,
Jason
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: 8BitMonk on August 17, 2015, 01:50:19 am
I've been trying to compile a no-nag MameUIFX using this software without success.
Has anyone found a way to do it?

I noticed that the mameui.mak was called mameuifx.mak but it still didn't work after renaming.


--Edit--
Ah got it working. Didn't read close enough at MameUIFX's webpage. Excelent application.  :applaud:

Made a small HowTo for myslef so I don't have to reinvent the wheel again next time. PM me If you have problems compiling MameUIFX using this exelent app.

Can someone help me out with instructions for compiling mameuifx with Mame Compiler. PM'd Kman but haven't heard back.
Title: Re: Mame Compiler 64 v2.0.163
Post by: EvilNuff on August 26, 2015, 07:45:29 pm
It looks like the actual application needs to be updated for 165?  I see no way to update the mame source URL or am I missing something?  Thanks.

Edit: Nevermind, I can update the path to source in the general tab.  Oops. :)
Title: Re: Mame Compiler 64 v2.0.163
Post by: headkaze on August 27, 2015, 05:05:19 am
It looks like the actual application needs to be updated for 165?  I see no way to update the mame source URL or am I missing something?  Thanks.

Edit: Nevermind, I can update the path to source in the general tab.  Oops. :)

You can download the latest by clicking Downloads->Download File List.
Title: Re: Mame Compiler 64 v2.0.163
Post by: EvilNuff on August 27, 2015, 08:26:50 am
Thanks, appreciate the reply.  And thank you for the tool, it is fantastic!
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: 8BitMonk on August 27, 2015, 09:49:29 am
I've been trying to compile a no-nag MameUIFX using this software without success.
Has anyone found a way to do it?

I noticed that the mameui.mak was called mameuifx.mak but it still didn't work after renaming.


--Edit--
Ah got it working. Didn't read close enough at MameUIFX's webpage. Excelent application.  :applaud:

Made a small HowTo for myslef so I don't have to reinvent the wheel again next time. PM me If you have problems compiling MameUIFX using this exelent app.

Can someone help me out with instructions for compiling mameuifx with Mame Compiler. PM'd Kman but haven't heard back.

Bump on this question, anyone else compiled mameuifx with Mame Compiler 64? Heard back from K-man but he couldn't remember how he did it. PM'd Headkaze as well with no response.
Title: Re: Mame Compiler 64 v2.0.163
Post by: Yoeddy1 on August 27, 2015, 02:37:57 pm
Is it normal for buildtools.7z to take over 5 hours to extract everything.  I'm still waiting for it.  It never took this long in the past.

Thanks,
Jason
Title: Re: Mame Compiler 64 v2.0.163
Post by: headkaze on August 27, 2015, 09:08:13 pm
Is it normal for buildtools.7z to take over 5 hours to extract everything.  I'm still waiting for it.  It never took this long in the past.

This must be caused by the output. I've turned it off for the buildtool.7z extraction. Please update MC64.
Title: Re: Mame Compiler 64 v2.0.163
Post by: Yoeddy1 on August 27, 2015, 09:10:51 pm
Is it normal for buildtools.7z to take over 5 hours to extract everything.  I'm still waiting for it.  It never took this long in the past.

This must be caused by the output. I've turned it off for the buildtool.7z extraction. Please update MC64.

Will do next time.  It finally finished and the compile of 0.165 worked fantastic!  Thanks as always!

Jason
Title: Re: Mame Compiler 64 v2.0.163
Post by: peterson65 on August 28, 2015, 08:00:38 pm
so is compiling mamui possibly anymore? can seen to do it on newest mame
Title: Re: Mame Compiler 64 v2.0.163
Post by: headkaze on August 28, 2015, 10:28:23 pm
so is compiling mamui possibly anymore? can seen to do it on newest mame

Yes it's easy to do in MC64. Just follow the instructions in the help tab.
Title: Re: Mame Compiler 64 v2.0.163
Post by: EvilNuff on August 30, 2015, 11:19:40 am
I only get errors with the WinUI option selected.  I just assumed I was doing something wrong.

Edit to add details:
Compiling src/emu/video.c...
Archiving libcapcom.a...
../../../../../src/emu/video.c:535:6: error: redefinition of 'void video_manager::frame_update_hi(bool)'
 void video_manager::frame_update_hi(bool debug)
      ^
../../../../../src/emu/video.c:475:6: note: 'void video_manager::frame_update_hi(bool)' previously defined here
 void video_manager::frame_update_hi(bool debug)
      ^
../../../../../src/osd/windows/video.c:238:6: error: redefinition of 'void windows_osd_interface::update_hi(bool)'
 void windows_osd_interface::update_hi(bool skip_redraw)
      ^
../../../../../src/osd/windows/video.c:211:6: note: 'virtual void windows_osd_interface::update_hi(bool)' previously defined here
 void windows_osd_interface::update_hi(bool skip_redraw)
      ^
make[2]: *** [../../../../mingw-gcc/obj/x64/Release/osd_winui/src/osd/windows/video.o] Error 1
make[1]: *** [osd_winui] Error 2
make[1]: *** Waiting for unfinished jobs....
make[2]: *** [../../../../mingw-gcc/obj/x64/Release/src/emu/video.o] Error 1
make[1]: *** [emu] Error 2
make[1]: Leaving directory `D:/Mame/buildtools/src/Mame0165/build/projects/winui/mame/gmake-mingw64-gcc'
make: *** [windows_x64] Error 2
Finished!
0 Hours 2 Minutes and 22 Seconds Elapsed.
Title: Re: Mame Compiler 64 v2.0.163
Post by: peterson65 on August 30, 2015, 11:24:40 am
i just tried again to compile winui and i get make ***[windows_x64]error 2
Title: Re: Mame Compiler 64 v2.0.163
Post by: headkaze on August 30, 2015, 09:16:00 pm
It looks like the MameUI team have moved the source to GitHub.

In MC64 go to the Downloads tab and select "Download File List" and then it should prompt to update, update it and then follow the MameUI compile instructions.

The MameUI source download now contains the entire source required to compile so you no longer need to download vanilla Mame first.
Title: Re: Mame Compiler 64 v1.17 Released!
Post by: 8BitMonk on September 03, 2015, 03:57:26 pm
I've been trying to compile a no-nag MameUIFX using this software without success.
Has anyone found a way to do it?

I noticed that the mameui.mak was called mameuifx.mak but it still didn't work after renaming.


--Edit--
Ah got it working. Didn't read close enough at MameUIFX's webpage. Excelent application.  :applaud:

Made a small HowTo for myslef so I don't have to reinvent the wheel again next time. PM me If you have problems compiling MameUIFX using this exelent app.

Can someone help me out with instructions for compiling mameuifx with Mame Compiler. PM'd Kman but haven't heard back.

Bump on this question, anyone else compiled mameuifx with Mame Compiler 64? Heard back from K-man but he couldn't remember how he did it. PM'd Headkaze as well with no response.

I was able to get mameuifx with no-nag diff applied to compile in MC64. Mameuifx already has cheats and hi-score support built in so no need for those.

Here are the steps I followed:

After the build completes mameuifx seems to work fully with nags removed an no apparent errors though I've only tested 10 or so games.

Hopefully that helps anyone else looking to compile mameuifx with MC64.
Title: Re: Mame Compiler 64 v2.0.165
Post by: retrometro on September 07, 2015, 02:05:54 am
Hi, I'm trying to simply compile a 0.161 windows exe with the high score patch.  I'm able to compile a working 64bit mame exe but the hi_161.txt patch isn't working for some reason  See the screenshot.  What should I look for?  thanks

(http://i.imgur.com/G3z3yhZ.jpg)
Title: Re: Mame Compiler 64 v2.0.165
Post by: Robbbert on September 12, 2015, 08:44:48 pm
Quote
It looks like the MameUI team have moved the source to GitHub.

In MC64 go to the Downloads tab and select "Download File List" and then it should prompt to update, update it and then follow the MameUI compile instructions.

The MameUI source download now contains the entire source required to compile so you no longer need to download vanilla Mame first.

There's been a lot of improvements to MAMEUI over the past few months, so you should always get the source from Github. One thing to note is that Github is kept up to date (or nearly so) with MAME, so you'll get the latest in-progress source rather than how it was at the last official release.
Title: Re: Mame Compiler 64 v2.0.165
Post by: brucelee00 on September 14, 2015, 09:45:01 pm
Not sure if this is the right area to post/ ask this and or if this is taboo, but anyone know where to get the other .diff patches other then then no nag provided here. I used to get all the others that were kept up to date on systempixel.fr but looks like the developer  is stopping support on them. Thanks for the help.
Title: Re: Mame Compiler 64 v2.0.165
Post by: oldhag270 on September 30, 2015, 11:07:38 am
MAME 0.166 was just released today.
Title: Re: Mame Compiler 64 v2.0.165
Post by: Yoeddy1 on October 02, 2015, 12:00:50 pm
Hi Headkaze,

Any eta when the tool will be updated for 0.166?

Thanks,
Jason
Title: Re: Mame Compiler 64 v2.0.165
Post by: headkaze on October 03, 2015, 02:56:46 am
Any eta when the tool will be updated for 0.166?

It's updated  :cheers:

Note that the version number of MC64 will not necessarily correspond with the MAME version. You will need to download the file list again and it should have all the MAME 0.166 files listed.
Title: Re: Mame Compiler 64 v2.0.165
Post by: newoski on October 29, 2015, 12:42:18 pm
Any eta when the tool will be updated for 0.166?

It's updated  :cheers:

Note that the version number of MC64 will not necessarily correspond with the MAME version. You will need to download the file list again and it should have all the MAME 0.166 files listed.

How about 167?  ;D
Title: Re: Mame Compiler 64 v2.0.165
Post by: Yoeddy1 on November 02, 2015, 10:49:47 pm
Headkaze, has this been updated to 0.167 yet?

Thanks,
Jason
Title: Re: Mame Compiler 64 v2.0.165
Post by: headkaze on November 03, 2015, 06:39:56 am
Headkaze, has this been updated to 0.167 yet?

Yes it has. You can always just check by clicking the Downloads tab then "Download File List". If it's new you should see the updated MAME version in the list.
Title: Re: Mame Compiler 64 v2.0.165
Post by: Yoeddy1 on November 03, 2015, 09:33:29 pm
Headkaze, has this been updated to 0.167 yet?

Yes it has. You can always just check by clicking the Downloads tab then "Download File List". If it's new you should see the updated MAME version in the list.

Worked great! 

Thanks,
Jason
Title: Re: Mame Compiler 64 v2.0.165
Post by: newoski on November 15, 2015, 09:21:11 am
I'm running into major errors trying to compile 160. Is the current software backwards compatible with 160?

Sent from my HTC6535LVW using Tapatalk

Title: Re: Mame Compiler 64 v2.0.165
Post by: Yoeddy1 on January 02, 2016, 10:24:30 am
Hi Headkaze,

Any ETA for MAME 0.169 support?

Thanks,
Jason
Title: Re: Mame Compiler 64 v2.0.165
Post by: RTyper56 on January 02, 2016, 12:23:33 pm
i think the download link for the build tools is dead.
Tried following the link that's in the compiler in a browser, and page cannot be found
Title: Re: Mame Compiler 64 v2.0.165
Post by: quakebo on January 02, 2016, 06:05:35 pm
I am trying to compile 0.167 but get this error
Mame Compiler 64 Applying Diff Patch... Error Applying Patch. PatchDiff(): The system cannot find the file specified  so how do I fix it
Title: Re: Mame Compiler 64 v2.0.165
Post by: headkaze on January 03, 2016, 03:26:54 am
I've updated Mame Compiler 64 to support the new build tools.

If you already have previous build tools installed, please delete the folder, and download the latest from MC.

We are currently on MAME 168 but I will update to the new version once MKChamp releases a 169 diff.

I have not had a lot of time to test this but please let me know of any issues.
Title: Re: Mame Compiler 64 v2.0.168
Post by: quakebo on January 03, 2016, 06:26:38 am
I downloaded the new build tools and tried to apply hi_167.txt but still get Applying Diff Patch... Error Applying Patch. PatchDiff(): The system cannot find the file specified.
Title: Re: Mame Compiler 64 v2.0.168
Post by: quakebo on January 03, 2016, 03:45:47 pm
I downloaded a mame 0.167 all ready done which works but does not save high scores but it should so why is that.
Title: Re: Mame Compiler 64 v2.0.168
Post by: Yoeddy1 on January 03, 2016, 04:04:21 pm
Headkaze,

Check out the following thread:

http://forum.arcadecontrols.com/index.php/topic,64298.1000.html (http://forum.arcadecontrols.com/index.php/topic,64298.1000.html)

It looks like GroovyMAME has the 0.169 file.  I pulled it down from GoogleDrive, zipped it up, and attached it here.

Does this give you what you need?

Thanks,
Jason
Title: Re: Mame Compiler 64 v2.0.168
Post by: Yoeddy1 on January 05, 2016, 01:51:39 am
Looks like MKChamp uploaded the 0.169.diff file.

Thanks,
Jason
Title: Re: Mame Compiler 64 v2.0.168
Post by: FalcoZX on January 05, 2016, 02:24:02 am
Great piece of software. I'm having an issue with the compiled emulator. Whenever I would launch it, I receive this message:

"The program can't start because libwinpthread-1.dll is missing from your computer. Try reinstalling the program to fix this problem."

I don't understand why I'm receiving this message. It looks like the dll is indeed in the build tools directory. Any idea or guidance?
Title: Re: Mame Compiler 64 v2.0.168
Post by: BDC009 on January 05, 2016, 02:40:33 am
I'm trying to compile mame 0.169 with the hiscore patch but I keep getting error:

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

When applying the patch. All paths seem correct. MinGW, mame source and the hiscore patch were downloaded by Mame Compiler 64. I'm not sure what I'm doing wrong.

I figured I'd go ahead and do a test build without the patch and I get the following: http://pastebin.com/RBuuiT1i (http://pastebin.com/RBuuiT1i)

Any insight on what may be causing this is much appreciated.
Title: Re: Mame Compiler 64 v2.0.168
Post by: EMDB on January 05, 2016, 02:52:51 am
V0.169 does not build for me with the new build tooling. V0.168 does...

Title: Re: Mame Compiler 64 v2.0.168
Post by: headkaze on January 05, 2016, 03:47:30 am
Mame Compiler 64 v2.0.169 released

NOTE: You need to uninstall the previous version of Mame Compiler and delete your old build tools folder. Then download the new build tools from MC64.
Title: Re: Mame Compiler 64 v2.0.169
Post by: newoski on January 05, 2016, 06:56:57 am
Can the latest release build 0.160?
Title: Re: Mame Compiler 64 v2.0.169
Post by: EMDB on January 05, 2016, 12:06:56 pm
Old version uninstalled. Build folder deleted. Installed MC64. Downloaded source code and build tools. Not working:
Title: Re: Mame Compiler 64 v2.0.169
Post by: yungism on January 05, 2016, 01:00:00 pm
This is the error I got after trying to compile on version 0.169

I see that the build tools on mamedev has been updated to 01/04/2016, and the build tools downloaded by mc64 compiler is 01/03/2016. That may be why.

Code: [Select]
Compiling Mame...
Using Parameters PYTHON_AVAILABLE=python SHELLTYPE=msdos -j12 ARCHOPTS=-march=native NOWERROR=1 TARGETOS=windows TARGET=mame OSD=windows PTR64=1 DONT_USE_NETWORK=1 STRIP_SYMBOLS=1
/usr/bin/sh: head: command not found
/usr/bin/sh: grep: command not found
/usr/bin/sh: sed: command not found
/usr/bin/sh: head: command not found
GCC  detected
make[1]: Entering directory `C:/buildtools/src/Mame0169/3rdparty/genie/build/gmake.windows'
Converting src/mame/layout/24cdjuke.lay...
Creating obj/Release/src/host
Converting src/mame/layout/18w.lay...
os_chdir.c
os_getcwd.c
os_ticks.c
Creating ../../bin/windows
os_copyfile.c
os_stat.c
Creating obj/Release
premake_main.c
os_uuid.c
Converting src/mame/layout/280zzzap.lay...
Converting src/mame/layout/4004clk.lay...
Converting src/mame/layout/30test.lay...
Converting src/mame/layout/abaseb.lay...
os_isfile.c
Creating obj/Release/src/host/lua-5.3.0/src
Converting src/mame/layout/abc1600.lay...
Unable to open output file 'build/generated/mame/layout/18w.lh'
Converting src/mame/layout/3bagflnz.lay...
make: *** [build/generated/mame/layout/18w.lh] Error -1
Converting src/mame/layout/3bagflvt.lay...
make: *** Waiting for unfinished jobs....
Unable to open output file 'build/generated/mame/layout/4004clk.lh'
make: *** [build/generated/mame/layout/4004clk.lh] Error -1
Unable to open output file 'build/generated/mame/layout/280zzzap.lh'
Unable to open output file 'build/generated/mame/layout/30test.lh'
make: *** [build/generated/mame/layout/280zzzap.lh] Error -1
make: *** [build/generated/mame/layout/30test.lh] Error -1
Converting src/mame/layout/ace.lay...
Unable to open output file 'build/generated/mame/layout/3bagflnz.lh'
make: *** [build/generated/mame/layout/3bagflnz.lh] Error -1
Unable to open output file 'build/generated/mame/layout/3bagflvt.lh'
Unable to open output file 'build/generated/mame/layout/24cdjuke.lh'
make: *** [build/generated/mame/layout/3bagflvt.lh] Error -1
make: *** [build/generated/mame/layout/24cdjuke.lh] Error -1
Unable to open output file 'build/generated/mame/layout/abaseb.lh'
Unable to open output file 'build/generated/mame/layout/abc1600.lh'
make: *** [build/generated/mame/layout/abaseb.lh] Error -1
make: *** [build/generated/mame/layout/abc1600.lh] Error -1
../../src/host/os_ticks.c:41:1: fatal error: opening dependency file obj/Release/src/host/os_ticks.d: No such file or directory
 }
 ^
compilation terminated.
../../src/host/os_getcwd.c:32:1: fatal error: opening dependency file obj/Release/src/host/os_getcwd.d: No such file or directory
 }
 ^
compilation terminated.
../../src/host/os_stat.c:46:1: fatal error: opening dependency file obj/Release/src/host/os_stat.d: No such file or directory
 }
 ^
compilation terminated.
../../src/host/os_copyfile.c:34:1: fatal error: opening dependency file obj/Release/src/host/os_copyfile.d: No such file or directory
 }
string_endswith.c
 ^
scripts.c
compilation terminated.
make[1]: *** [obj/Release/src/host/os_getcwd.o] Error 1
make[1]: *** Waiting for unfinished jobs....
string_hash.c
Unable to open output file 'build/generated/mame/layout/ace.lh'
make[1]: *** [obj/Release/src/host/os_copyfile.o] Error 1
../../src/host/premake_main.c:29:1: fatal error: opening dependency file obj/Release/src/host/premake_main.d: No such file or directory
 }
 ^
compilation terminated.
make: *** [build/generated/mame/layout/ace.lh] Error -1
make[1]: *** [obj/Release/src/host/os_ticks.o] Error 1
make[1]: *** [obj/Release/src/host/os_stat.o] Error 1
make[1]: *** [obj/Release/src/host/premake_main.o] Error 1
../../src/host/os_uuid.c:79:1: fatal error: opening dependency file obj/Release/src/host/os_uuid.d: No such file or directory
 }
 ^
compilation terminated.
../../src/host/os_chdir.c:32:1: fatal error: opening dependency file obj/Release/src/host/os_chdir.d: No such file or directory
 }
 ^
compilation terminated.
make[1]: *** [obj/Release/src/host/os_chdir.o] Error 1
../../src/host/scripts.c:359:1: fatal error: opening dependency file obj/Release/src/host/scripts.d: No such file or directory
 };
 ^
compilation terminated.
make[1]: *** [obj/Release/src/host/os_uuid.o] Error 1
../../src/host/os_isfile.c:30:1: fatal error: opening dependency file obj/Release/src/host/os_isfile.d: No such file or directory
 }
 ^
compilation terminated.
make[1]: *** [obj/Release/src/host/scripts.o] Error 1
make[1]: *** [obj/Release/src/host/os_isfile.o] Error 1
../../src/host/string_hash.c:35:1: fatal error: opening dependency file obj/Release/src/host/string_hash.d: No such file or directory
 }
 ^
compilation terminated.
make[1]: *** [obj/Release/src/host/string_hash.o] Error 1
../../src/host/string_endswith.c:28:1: fatal error: opening dependency file obj/Release/src/host/string_endswith.d: No such file or directory
 }
 ^
compilation terminated.
make[1]: Leaving directory `C:/buildtools/src/Mame0169/3rdparty/genie/build/gmake.windows'
make[1]: *** [obj/Release/src/host/string_endswith.o] Error 1
make: *** [3rdparty/genie/bin/windows/genie.exe] Error 2
Finished!
0 Hours 0 Minutes and 2 Seconds Elapsed.
Title: Re: Mame Compiler 64 v2.0.169
Post by: Yoeddy1 on January 05, 2016, 02:10:29 pm
I get a .Net runtime error at the end of the download/extraction process.

Thanks,
Jason
Title: Re: Mame Compiler 64 v2.0.169
Post by: BDC009 on January 05, 2016, 08:38:30 pm
I'm still getting the error messages when attempting to apply the hiscore patch or just when attempting to compile mame 0.169. Screenshots are attached and full console output is here: http://pastebin.com/RBuuiT1i (http://pastebin.com/RBuuiT1i)

Anybody encounter anything like this?
Title: Re: Mame Compiler 64 v2.0.168
Post by: FalcoZX on January 05, 2016, 10:30:57 pm
Great piece of software. I'm having an issue with the compiled emulator. Whenever I would launch it, I receive this message:

"The program can't start because libwinpthread-1.dll is missing from your computer. Try reinstalling the program to fix this problem."

I don't understand why I'm receiving this message. It looks like the dll is indeed in the build tools directory. Any idea or guidance?

Anyone run into this issue before that can offer some assistance? I've tried recompiling so many times with no luck and I can't seem to find an answer on Google.

I'm still getting the error messages when attempting to apply the hiscore patch or just when attempting to compile mame 0.169. Screenshots are attached and full console output is here: http://pastebin.com/RBuuiT1i (http://pastebin.com/RBuuiT1i)

Anybody encounter anything like this?

Try clicking the update build tools button under the downloads tab.
Title: Re: Mame Compiler 64 v2.0.169
Post by: BDC009 on January 05, 2016, 11:15:01 pm
Quote
Try clicking the update build tools button under the downloads tab.

I tried that, same issue. I also tried a clean install by uninstalling mame compiler 64, and deleting mingw, mame source, and hiscore patch then reinstalled mame 64 got the build tools, source and hiscore patch from the downloads section of mame compiler 64. Same errors, no change.

Title: Re: Mame Compiler 64 v2.0.169
Post by: Yoeddy1 on January 06, 2016, 01:17:58 am
I'm getting the same issues as mentioned in the previous posts.  Uninstall goes well, but when deleting the buildtools folder, I couldn't delete everything because there were 2 NUL files in the path.  Luckily I googled and found a way to delete those files via cmd prompt.

Thanks,
Jason
Title: Re: Mame Compiler 64 v2.0.169
Post by: headkaze on January 06, 2016, 04:43:12 am
Can you guys try updating Mame Compiler again. There have been a few odd issues I've had to resolve with the new build tools.
Title: Re: Mame Compiler 64 v2.0.169
Post by: EMDB on January 06, 2016, 05:43:59 am
Can you guys try updating Mame Compiler again. There have been a few odd issues I've had to resolve with the new build tools.
Just did. Working fine again. Thanks  :applaud:
Title: Re: Mame Compiler 64 v2.0.169
Post by: EMDB on January 06, 2016, 06:10:25 am
Can you guys try updating Mame Compiler again. There have been a few odd issues I've had to resolve with the new build tools.
Just did. Working fine again. Thanks  :applaud:
Although... It builds but it does not run. It complains about missing libwinpthread-1.dll. (should be statically linked I guess)  :o

(Adding 64 bits version of libwinpthread-1.dll to the MAME folder works but I like to have MAME run natively without external dependencies)
Title: Re: Mame Compiler 64 v2.0.169
Post by: headkaze on January 06, 2016, 08:44:59 am
It complains about missing libwinpthread-1.dll. (should be statically linked I guess)  :o

Please try another update and then put a tick next to "Clean Compile" before you compile. Let me know how you go.
Title: Re: Mame Compiler 64 v2.0.169
Post by: BDC009 on January 06, 2016, 10:46:52 am
Quote
Can you guys try updating Mame Compiler again. There have been a few odd issues I've had to resolve with the new build tools.

I updated Mame Compiler and build tools and then tried it again with the clean compile option. Applying the Hiscore patch went through fine and compiling MAME gets a lot further but now I get:

Code: [Select]
GCC version 4.9 or later needed
make: *** [build/projects/windows/mame/gmake-mingw64-gcc/Makefile] Error -1
make: *** Waiting for unfinished jobs....

Running gcc --version in mingw\mingw32\bin and mingw\mingw64\bin shows version 5.3.0 so I'm not sure why its giving an error that 4.9 or later is needed.

Thanks for the update!
Title: Re: Mame Compiler 64 v2.0.169
Post by: EMDB on January 06, 2016, 11:17:35 am
It complains about missing libwinpthread-1.dll. (should be statically linked I guess)  :o

Please try another update and then put a tick next to "Clean Compile" before you compile. Let me know how you go.
Perfect! No more dependency on libwinpthread-1.dll  :applaud:
Title: Re: Mame Compiler 64 v2.0.169
Post by: Yoeddy1 on January 06, 2016, 02:52:47 pm
Just completed it and everything ran perfect.  I checked "Clean compile."

Thanks,
Jason
Title: Re: Mame Compiler 64 v2.0.169
Post by: BDC009 on January 06, 2016, 03:54:00 pm
Well I installed it on another pc and everything compiled fine. I couldn't find any other gcc.exe files on the original pc so I still have no idea why it was giving an error that it was an old version. Thanks for your help.
Title: Re: Mame Compiler 64 v2.0.169
Post by: FalcoZX on January 07, 2016, 03:55:25 am
Running the compiler now with "clean compile" checked. So far it looks like it's running without any issues. Crossing my fingers.

Title: Re: Mame Compiler 64 v2.0.169
Post by: Yoeddy1 on January 07, 2016, 11:50:08 am
Just a suggestion...

If "Clean compile" needs to be checked in order for the process to work, shouldn't it be checked by default?

Thanks,
Jason
Title: Re: Mame Compiler 64 v2.0.169
Post by: dannybrear on January 07, 2016, 05:44:59 pm
Hi,

First post so hope this is in the appropriate place! I've managed to get my cab built and running from searching browsing these forums but I really want hi-score support.

I decided to try the compiler and the latest version of mame, run the patch that ended in the .txt then compiled which took 7 hours on my laptop. A quick test of Puckman and it doesn't seem to be saving hi-scores. I've also added hi folder and hiscore.dat into the mame folder.

Is there anything obvious I'm doing wrong ? As it takes so long to compile i can't play around as much with it as I have to get the rest of the setup working. Maybe I should try a older version as I'm only playing the classics!

On a plus note excellent work on the compiler the compiled mame does run so I've learnt something new!

Cheers

Danny

Sent from my XT1068 using Tapatalk

Title: Re: Mame Compiler 64 v2.0.169
Post by: headkaze on January 07, 2016, 11:24:44 pm
If "Clean compile" needs to be checked in order for the process to work, shouldn't it be checked by default?

That was only a suggestion for EMDB since he'd already attempted a compile. What "Clean Compile" does is delete all previous compiled objects so it will start a fresh compile. In most cases you will not need to use it.
Title: Re: Mame Compiler 64 v2.0.169
Post by: FalcoZX on January 07, 2016, 11:39:22 pm
I just wanted to follow up my post from yesterday. I was able to compile and run mame successfully with no issues after checking "clean compile". Thank you so much for this amazing piece of software headkaze.  :applaud:

Edit: It seems that the "No Warnings as Errors" option didn't work with the mame I compiled. Weird. I'm not sure what's going on. I didn't receive any errors or anything like that. Is there supposed to be a setting somewhere to turn this option on?

Edit 2: Never mind, works as expected :)
Title: Re: Mame Compiler 64 v2.0.169
Post by: bearzilla333 on January 16, 2016, 08:03:14 pm
Anyone help me? I have compiled MAME like 5x times, I get no errors, but that dam nagscreen/whitebox, and the highscore is not working for me, am I missing something on the "build options tab"? I have used this program  before with no problem, not sure what I am doing wrong.


***Figured it out, got it to work, works good for me, I brainfarted the exact samething I did in the past, changing that dam file to Diff, I feel like an idiot, but I got it to work  :)
Title: Re: Mame Compiler 64 v2.0.169
Post by: bobmoo79 on January 18, 2016, 10:27:12 am
Hi there,

I tried to compile mame0.169 with the nonag/hiscore diff over the weekend and it didn't work. There were no errors but the nag screens still appear and the hiscore doesn't save. Sounds like it could be the same issue you're having.

I'm sorry perhaps I'm having a slow day today but I couldn't tell what your resolution was from your post. Seems a bit ambiguous to me.....


Do you mean you changed the 'txt' extension to 'diff' and that caused your problem?

Or that you left it as 'txt' when you should have renamed it?

If somebody could clarify that would be appreciated.


Many thanks!

Edit: I pointed the compiler at the txt file and it worked fine.
Incidentally when trying to use the diff downloaded by the compiler it appeared to be blank (file size was 0kb). Is that an error/bug??? It happened work two different installations on two different machines.
Title: Re: Mame Compiler 64 v2.0.169
Post by: Flyer on January 19, 2016, 09:41:17 am
Hopefully this doesn't offend anyone with an RTFM response but I see no "M" for anything on headsoft.

I have successfully followed the directions on their site and compiled MAMEUI64 169 version with headkaze's compiler but nothing happens when I run it :/

I tried putting it in place of the downloaded 169 EXE on my machine but when I run it nothing launches.  I saw some direction about making a "HI" folder and copying the hiscore dat and did all that but still nothing.

What am I missing?

Thanks!
Title: Re: Mame Compiler 64 v2.0.169
Post by: bobmoo79 on January 20, 2016, 06:29:49 am
Hmm, I don't think you're missing much. This could be related to the comment I edited into my post last night.

The diff file downloaded through the compiler is actually empty - 0kb - and so doesn't work. I found that when using that diff MAME would load with just a black screen.

Try downloading the diff from the link below and then point the compiler to that. Make sure you click 'apply patch' before you click 'go'.

https://forum.arcadecontrols.com/index.php/topic,64298.0.html



Let us know if this solves your problem...
Title: Re: Mame Compiler 64 v2.0.169
Post by: headkaze on January 20, 2016, 07:29:53 am
The diff file downloaded through the compiler is actually empty - 0kb - and so doesn't work.

Please do an MC64 update. I've hopefully fixed this issue.
Title: Re: Mame Compiler 64 v2.0.169
Post by: bobmoo79 on January 20, 2016, 08:58:02 am
I  just updated and it now correctly downloads the diff. Thanks.


Flyer if you update MC64 now you can just use the diff downloaded through the software - no need to use the one from the link I provided.
Title: Re: Mame Compiler 64 v2.0.169
Post by: artyfarty on January 20, 2016, 09:21:22 am
Is there an update to get the 01/04/2016 build tools? I tried performing the update suggested on mamedev:

"In case you have version from 2016-01-03, just do : git pull in root of your tools to update
scripts, and then check if file usr\bin\sh.exe.old exist, if so rename it to usr\bin\sh.exe
Start your environment and enjoy. "

But this gives me an "aborted" error, although the usr\bin\sh.exe.old did exist, so I renamed it.

Thanks,

Martin
Title: Re: Mame Compiler 64 v2.0.169
Post by: Flyer on January 20, 2016, 01:08:22 pm
So here is another issue that I found while using the compiler.  If I tell it to download mame source, the patch and the built tools at the same time I get the attached image error.

I have run the update but the version number never changed.

This is the error:
(http://i645.photobucket.com/albums/uu175/SparkyDClown/MyBCS/Random/mame64%20error_zpstqr6zdk7.png)
Title: Re: Mame Compiler 64 v2.0.169
Post by: Flyer on January 20, 2016, 05:13:02 pm
Dang, I just cant win.  This machine has nothing on it.  Fresh Win 10 install compiler this is the ONLY thing installed.   I flushed everything on it to do with the compiler and buildtools dir and started over.  Everything downloads and decompresses if I choose each download 1 at a time however....
 
Now I get this:  make: *** [windows_x64] Error 2  after it runs for 23 minutes on an i7 latest Gen processor with 8GB ram and a hybrid drive.
Title: Re: Mame Compiler 64 v2.0.169
Post by: EMDB on January 27, 2016, 02:46:10 pm
MAME 0.170 does not build with MAME Compiler 64 V2.0.169:

Deleting Build Folder...
Compiling Mame...
Using Parameters PYTHON_AVAILABLE=python SHELLTYPE=msdos -j6 NOWERROR=1 TARGETOS=windows TARGET=mame SUBTARGET=arcade OSD=windows PTR64=1 STRIP_SYMBOLS=1
GCC 5.3.0 detected
make: *** No rule to make target `build/generated/mame/layout/', needed by `build/generated/mame/layout/24cdjuke.lh'.  Stop.
make: *** Waiting for unfinished jobs....
Finished!
0 Hours 0 Minutes and 0 Seconds Elapsed.
Title: Re: Mame Compiler 64 v2.0.169
Post by: headkaze on January 28, 2016, 01:29:47 am
MAME 0.170 does not build with MAME Compiler 64 V2.0.169:

Make sure you have the latest build tools by selecting "Update Build Tools" under the "Downloads" tab.

If you get the "No rule to make target" error, just press the "GO!" button again, and it should continue and successfully compile.
Title: Re: Mame Compiler 64 v2.0.169
Post by: EMDB on January 28, 2016, 11:18:21 am
...If you get the "No rule to make target" error, just press the "GO!" button again, and it should continue and successfully compile.
Thanks. Trying again did the trick although I never ever had to do that before  ???
Title: Re: Mame Compiler 64 v2.0.169
Post by: Yoeddy1 on February 16, 2016, 01:06:03 am
I can't for the life of me figure this out.  I have updated the compiling tools, tried this on 2 pcs and it won't work with 170.  I get all of the errors listed above.  I checked clean compile like with 169.  Nothing works.  Any ideas?

Headkaze, is there an updated version available?

Jason
Title: Re: Mame Compiler 64 v2.0.169
Post by: ArrogANT on February 16, 2016, 04:25:26 pm
Hi Headkaze,

Thank you for you work with the app, but I am also getting errors when compiling Mame 0.170. I receive the following error:

../../../../../src/osd/windows/video.cpp:233:6: error: redefinition of 'void windows_osd_interface::update_hi(bool)'
 void windows_osd_interface::update_hi(bool skip_redraw)
      ^
../../../../../src/osd/windows/video.cpp:206:6: note: 'virtual void windows_osd_interface::update_hi(bool)' previously defined here
 void windows_osd_interface::update_hi(bool skip_redraw)
      ^
../../../../../src/osd/windows/video.cpp:260:6: error: redefinition of 'void windows_osd_interface::update_hi(bool)'
 void windows_osd_interface::update_hi(bool skip_redraw)
      ^
../../../../../src/osd/windows/video.cpp:206:6: note: 'virtual void windows_osd_interface::update_hi(bool)' previously defined here
 void windows_osd_interface::update_hi(bool skip_redraw)
      ^
make[2]: *** [../../../../mingw-gcc/obj/x64/Release/osd_windows/src/osd/windows/video.o] Error 1
make[1]: *** [osd_windows] Error 2
make[1]: *** Waiting for unfinished jobs....

I have downloaded the build tools and Mame source multiple times, but it seems to fail.

This is on a newly built PC with hardly anything installed on it.

Thanks!
Title: Re: Mame Compiler 64 v2.0.169
Post by: Yoeddy1 on February 16, 2016, 07:24:12 pm
Yeah, one of my tests was on a Win10 x64 new image.  Something has to be wrong.  Usually this software is smooth and easy sailing. 

Thanks,
Jason
Title: Re: Mame Compiler 64 v2.0.169
Post by: ArrogANT on February 17, 2016, 09:20:44 am
I hope so, because I remember compiling Mame from Mr Do's walk-through being a lot harder than what Headkaze has made this!  ;D
Title: Re: Mame Compiler 64 v2.0.169
Post by: KingViper on February 18, 2016, 02:06:03 pm
I also could not compile Mame 0.170. I'm running Windows 10 x64. I did not however have issues compiling Mame 0.168.
Title: Re: Mame Compiler 64 v2.0.169
Post by: Yoeddy1 on February 23, 2016, 02:48:10 am
Any updates Headkaze?

Thanks,
Jason
Title: Re: Mame Compiler 64 v2.0.169
Post by: headkaze on February 23, 2016, 06:14:14 pm
Any updates Headkaze?

I successfully compiled 0.170 + hiscore patch in MC64 a while back.

Did you read this post (http://forum.arcadecontrols.com/index.php/topic,71845.msg1557724.html#msg1557724)? If you're receiving an error message what is it?
Title: Re: Mame Compiler 64 v2.0.169
Post by: Yoeddy1 on February 24, 2016, 04:00:41 am
Any updates Headkaze?

I successfully compiled 0.170 + hiscore patch in MC64 a while back.

Did you read this post (http://forum.arcadecontrols.com/index.php/topic,71845.msg1557724.html#msg1557724)? If you're receiving an error message what is it?

I did.  Still couldn't get it to work.  It looks like MAME 0.171 just released tonight so I guess I'll skip 0.170 and hope that 0.171 works out better.

Thanks,
Jason
Title: Re: Mame Compiler 64 v2.0.169
Post by: Jumpstile on February 24, 2016, 07:25:08 am
I was able to compile .170 with no issues.


 - J*
Title: Re: Mame Compiler 64 v2.0.169
Post by: Yoeddy1 on February 25, 2016, 01:43:12 am
I wonder what the difference could be.  Even on a new Win 10 x64 laptop I ran into all kinds of problems.  I wonder if some of us are enabling/disabling certain options in the compiler that lead to some of us having problems. 

Is this still the current flow for instructions as per the website?

How to compile Mame with the Hiscore patch:

1.Click the Downloads tab
2.If this is your first time running Mame Compiler put a tick next to Build Tools
3.Put a tick next to Mame Source and the Hiscore Diff Patch
4.Click the Download Selected button and wait for the files to finish downloading and extracting
5.Click the Diff Patch tab
6.Click the magnifying glass icon to browse and select the Hiscore diff patch (Eg. hi_163.txt)
7.Click the Apply Patch button to apply the Hiscore diff patch
8.Click the GO! button to compile


Jason
Title: Re: Mame Compiler 64 v2.0.169
Post by: trickyd on February 25, 2016, 04:04:21 pm
I compiled 170 with no problems but 171 is erroring right from the start
Title: Re: Mame Compiler 64 v2.0.169
Post by: headkaze on February 25, 2016, 08:31:56 pm
Everyone please try Mame Compiler 64 v2.0.171
Title: Re: Mame Compiler 64 v2.0.171
Post by: Yoeddy1 on February 25, 2016, 11:55:28 pm
I had a .NET error come up during the extraction process.  I clicked continue.

Will update.

Thanks,
Jason
Title: Re: Mame Compiler 64 v2.0.171
Post by: Yoeddy1 on February 26, 2016, 02:32:20 am
After clicking Continue on the .NET error screen, the download and extraction process continues, but the OK button never goes active...stays grayed out.  I waited for an hour and it never changed.  Is the 0.171 diff file updated in this build?  Mine still shows 0.170.  Same behavior as previous version for the most part.  I uninstalled the compiler, deleted the source folder, Windows temp folder contents, rebooted.  Started clean.  Same issues.  Haven't even been able to click "Go" yet to compile.

Thanks,
Jason
Title: Re: Mame Compiler 64 v2.0.171
Post by: Richardgregory on February 26, 2016, 10:35:46 pm
How can I get the hiscore function to work?  I downloaded a copy of the hiscore.dat file and placed it in the "hi" directory, but it's not saving the high scores.   I also compiled a UI version and I don't see the "Enable Hiscore Support" under miscellaneous menu item.

Anyone can help?
Title: Re: Mame Compiler 64 v2.0.171
Post by: ArrogANT on February 27, 2016, 05:12:54 am
Tried compiling on a different drive. It ran for about 35 mins and then I got the following error:

make[2]: *** [../../../../mingw-gcc/bin/x64/Release/mame_mame/libmatic.a] Error 1
make[1]: *** [matic] Error 2
make[1]: *** Waiting for unfinished jobs....
Title: Re: Mame Compiler 64 v2.0.171
Post by: Richardgregory on February 27, 2016, 06:55:24 pm
I'm giving up on this tool.  I'm getting inconsistent errors and tried everything.....doesn't seem to make any sense why.  Tried re installing, re downloading, recompiling...etc.  No go...
Title: Re: Mame Compiler 64 v2.0.171
Post by: Yoeddy1 on February 27, 2016, 07:06:55 pm
I wouldn't give up yet.  This tool has worked smooth as butter with past releases.  Not sure why so many problems have surfaced all of a sudden, but hopefully Headkaze will get them figured out.  It's so easy to compile MAME using this tool and it would be a shame if it went away.

Thanks,
Jason
Title: Re: Mame Compiler 64 v2.0.171
Post by: headkaze on February 27, 2016, 08:33:20 pm
Is the 0.171 diff file updated in this build?  Mine still shows 0.170.

Not until MKChamp releases a 171 patch. I only include MKChamp releases in MC64. Right now the 170 patch does not work with 171. Apparently there is an updated version in the GroovyMAME (http://forum.arcadecontrols.com/index.php/topic,135823.0.html) thread you can download in the meantime.
Title: Re: Mame Compiler 64 v2.0.171
Post by: Richardgregory on February 27, 2016, 10:17:59 pm
FINALLY!  Got it to work.....after a few runs.  What I did was had to re download the files, checkmarked on Clean Compile, and recompiled.  Also downloaded the 0171 hi score diff and it works.  Now trying to see if I can get the UI to work  as well, but running into the same problems, but will redownload files and try the same sequence that I did to get the regular compile to work.

Title: Re: Mame Compiler 64 v2.0.171
Post by: Yoeddy1 on February 27, 2016, 10:55:05 pm
Could you post the EXACT steps and sequence that you used to get it to work?  I will try to replicate.

Thanks,
Jason
Title: Re: Mame Compiler 64 v2.0.171
Post by: headkaze on February 28, 2016, 12:01:58 am
Okay let's start from the beginning...

1. Delete your "buildtools" folder
2. Click the "Downloads" tab and click "Download File List"
3. Click "Update Mame Compiler" to make sure you have the latest version
4. Put a tick next to:
   ✓ Mame 0171 Source
   ✓ Hiscore Diff Patch (for now you can skip this because a patch for 0171 is not available yet)
   ✓ Build Tools
5. Click "Download Selected"
6. Wait patiently for the download, extraction and file copy to finish. If MC64 stops responding just wait. If the OK button is greyed out it hasn't finished yet.
7. At this point you would usually apply the "Hiscore Diff Patch" but we will skip this step for now
8. Click the GO! button*

* NOTE: If it fails try pressing the GO! button again (I had to twice)
Title: Re: Mame Compiler 64 v2.0.171
Post by: ArrogANT on February 28, 2016, 11:46:46 am
Thank Headkaze!

Everything looks like it is working!
Title: Re: Mame Compiler 64 v2.0.171
Post by: WindDrake on February 28, 2016, 06:32:50 pm
Not working for me. About half way through the build tools extraction, I get a .Net error. If I hit continue, MC64 will sit on 100% file progress once everything is extracted, with OK greyed out.
Title: Re: Mame Compiler 64 v2.0.171
Post by: Richardgregory on February 28, 2016, 06:47:15 pm
I can't really recall exactly, but what I do recall   having to redownloaded the 0171 package and pressing the GO button.    If it fails, press the GO again.  If it failed, I recall re downloading the 0171 package, and pressing Go again.   I had to do that a few times, and it finally finished and compiled properly.  It's weird I know, but it worked for me.   

Could you post the EXACT steps and sequence that you used to get it to work?  I will try to replicate.

Thanks,
Jason
Title: Re: Mame Compiler 64 v2.0.171
Post by: headkaze on February 28, 2016, 06:57:43 pm
Not working for me. About half way through the build tools extraction, I get a .Net error. If I hit continue, MC64 will sit on 100% file progress once everything is extracted, with OK greyed out.

Can you please post the .NET error?
Title: Re: Mame Compiler 64 v2.0.171
Post by: Yoeddy1 on February 28, 2016, 07:22:40 pm
Not working for me. About half way through the build tools extraction, I get a .Net error. If I hit continue, MC64 will sit on 100% file progress once everything is extracted, with OK greyed out.

Can you please post the .NET error?

Here's mine.  Basically the same activity as above with the OK button staying grayed out.

Jason
Title: Re: Mame Compiler 64 v2.0.171
Post by: ArrogANT on February 29, 2016, 06:05:33 am
The only things that I did differently was to download and extract the build tools myself. I also used the 171 patch from the GroovyMAME thread.
Title: Re: Mame Compiler 64 v2.0.171
Post by: EMDB on February 29, 2016, 02:19:40 pm
Not working for me. About half way through the build tools extraction, I get a .Net error. If I hit continue, MC64 will sit on 100% file progress once everything is extracted, with OK greyed out.

Can you please post the .NET error?

Here's mine.  Basically the same activity as above with the OK button staying grayed out.

Jason
Same here...
Title: Re: Mame Compiler 64 v2.0.171
Post by: headkaze on February 29, 2016, 07:37:38 pm
Here's mine.  Basically the same activity as above with the OK button staying grayed out.

According to the error a file is locked because it is in use by another process. Try rebooting your PC.
Title: Re: Mame Compiler 64 v2.0.171
Post by: Yoeddy1 on February 29, 2016, 11:36:07 pm
Here's mine.  Basically the same activity as above with the OK button staying grayed out.

According to the error a file is locked because it is in use by another process. Try rebooting your PC.

When?  This PC/MAME cab is rebooted every day.  I've done it several times after uninstalling and reinstalling this software as part of the troubleshooting process.  This also happened on a clean Windows 10 64-bit machine.

Jason
Title: Re: Mame Compiler 64 v2.0.171
Post by: Yoeddy1 on March 01, 2016, 12:18:15 am
I noticed that the MAMECompiler64 folder within that path is not removed by the uninstaller and contains almost 4Gb of data.  I'm blowing that folder and it's contents away as part of the uninstall and cleanup process to see if it makes a difference.

Jason
Title: Re: Mame Compiler 64 v2.0.171
Post by: Yoeddy1 on March 01, 2016, 12:24:52 am
Now this .NET error was thrown during the extraction process.

Jason
Title: Re: Mame Compiler 64 v2.0.171
Post by: Yoeddy1 on March 02, 2016, 01:05:04 am
Still having the same problem.  Ok button never goes active to start the compile process.

Jason
Title: Re: Mame Compiler 64 v2.0.171
Post by: ArrogANT on March 03, 2016, 06:39:19 am
Jason,

Have you tried downloading the files and extracting them yourself?
Title: Re: Mame Compiler 64 v2.0.171
Post by: Yoeddy1 on March 04, 2016, 01:38:22 am
I haven't.  Not sure where to go from here.  I'm close to just downloading the complied 0.171 64-bit/no nag screen/high score version from Hyperspin.   I just can't get this to work for some reason.

Jason
Title: Re: Mame Compiler 64 v2.0.171
Post by: Yoeddy1 on March 08, 2016, 09:11:41 pm
So I noticed that the 0.171 diff was updated.  Any updates to the tool or are we flying as-is?

Jason
Title: Re: Mame Compiler 64 v2.0.171
Post by: Richardgregory on March 09, 2016, 06:50:16 am
That's what I end up doing.....it works like a charm!  Not sure what the advantage is doing the compile way in this case.  And besides, the one from hyperspin has the no nag screen but if you were to compile your own, it will have the nag screen, so..


I haven't.  Not sure where to go from here.  I'm close to just downloading the complied 0.171 64-bit/no nag screen/high score version from Hyperspin.   I just can't get this to work for some reason.

Jason
Title: Re: Mame Compiler 64 v2.0.171
Post by: EMDB on March 30, 2016, 06:04:09 am
MAME 0.172 is just released. I couldn't get 0.171 working with MC64. Hopefully 0.172 will be supported again. I will try this afternoon and report the results here...
Title: Re: Mame Compiler 64 v2.0.171
Post by: Jumpstile on March 30, 2016, 06:38:49 am
I had no problems at all compiling .171, including a no-nag version. I'll try .172 this weekend.


 - J*
Title: Re: Mame Compiler 64 v2.0.171
Post by: EMDB on March 30, 2016, 07:16:33 am
I had no problems at all compiling .171, including a no-nag version. I'll try .172 this weekend.


 - J*
you mean with MC64?
Title: Re: Mame Compiler 64 v2.0.171
Post by: Jumpstile on March 30, 2016, 07:21:04 am
Yes, of course. The key was to delete the old compiling tools completely and then let MC64 reinstall the latest version. Like headkaze said, you need to start the compile, let it stop, and then do it again and it will compile just fine. Works perfectly.


 - J*
Title: Re: Mame Compiler 64 v2.0.171
Post by: EMDB on March 30, 2016, 08:01:54 am
Yes, of course. The key was to delete the old compiling tools completely and then let MC64 reinstall the latest version. Like headkaze said, you need to start the compile, let it stop, and then do it again and it will compile just fine. Works perfectly.


 - J*
not for me (and a lot of others reading the comments)
Title: Re: Mame Compiler 64 v2.0.171
Post by: Jumpstile on March 30, 2016, 08:31:38 am
Don't know why, sorry. Like I said, it does work fine here. I'm sure you guys are doing something incorrectly... Sorry I can't be of more assistance...


 - J*
Title: Re: Mame Compiler 64 v2.0.171
Post by: EMDB on March 30, 2016, 04:46:16 pm
No luck again. Used MC64 V2.0.171. Again deleted the build tools, downloaded the latest build tools from within MC64 and tried to build (Clean Compile):

Compiling Mame...
Using Parameters PYTHON_AVAILABLE=python SHELLTYPE=msdos -j6 NOWERROR=1 TARGETOS=windows TARGET=mame SUBTARGET=arcade OSD=windows PTR64=1 STRIP_SYMBOLS=1
GCC  detected
Converting src/mame/layout/18w.lay...
Converting src/mame/layout/24cdjuke.lay...
Converting src/mame/layout/280zzzap.lay...
GCC version 4.9 or later needed
make: *** [build/projects/windows/mamearcade/gmake-mingw64-gcc/Makefile] Error -1
make: *** Waiting for unfinished jobs....
Converting src/mame/layout/30test.lay...
Finished!
0 Hours 0 Minutes and 1 Seconds Elapsed.

Hitting GO! again did not fix it:

Compiling Mame...
Using Parameters PYTHON_AVAILABLE=python SHELLTYPE=msdos -j6 NOWERROR=1 TARGETOS=windows TARGET=mame SUBTARGET=arcade OSD=windows PTR64=1 STRIP_SYMBOLS=1
GCC  detected
Converting src/mame/layout/ace.lay...
GCC version 4.9 or later needed
Converting src/mame/layout/aces1.lay...
Converting src/mame/layout/acrnsys1.lay...
make: *** [build/projects/windows/mamearcade/gmake-mingw64-gcc/Makefile] Error -1
make: *** Waiting for unfinished jobs....
Converting src/mame/layout/aim65.lay...
Converting src/mame/layout/aim65_40.lay...
Finished!
0 Hours 0 Minutes and 1 Seconds Elapsed.

 :hissy: :hissy: :hissy:

Title: Re: Mame Compiler 64 v2.0.171
Post by: lowlytech on March 30, 2016, 08:12:57 pm
Do you think the GCC needs updated? My message area states mine is GCC 5.3.0. and mine does not state "GCC version 4.9 or later needed" anywhere in the logs.  Maybe make a new folder name for the install of the buildtools?  I don't know anything about writing code, but I am on win7x64 and MC 2.0.171 complies the latest .172 source with the nonag/hiscore + defender 8 way diff patches.
Title: Re: Mame Compiler 64 v2.0.171
Post by: headkaze on March 31, 2016, 12:47:29 am
No luck again. Used MC64 V2.0.171. Again deleted the build tools, downloaded the latest build tools from within MC64 and tried to build (Clean Compile):

I noticed your output says "GCC detected" when it should say "GCC 5.3.0 detected". This is caused by an annoying permissions issue. The only way that appeared to solve this was to remove granting admin rights in the setup application.

So unless you get the message "GCC 5.3.0 detected" it will not work.

When you select "Update Mame Compiler" in the Downloads tab it should download and run MC64Setup.exe which should remove the registry key that makes MC64 run as admin. If this doesn't work then the "fix" is obviously not as robust as I had hoped.
Title: Re: Mame Compiler 64 v2.0.171
Post by: EMDB on March 31, 2016, 11:23:49 am
No luck again. Used MC64 V2.0.171. Again deleted the build tools, downloaded the latest build tools from within MC64 and tried to build (Clean Compile):

I noticed your output says "GCC detected" when it should say "GCC 5.3.0 detected". This is caused by an annoying permissions issue. The only way that appeared to solve this was to remove granting admin rights in the setup application.

So unless you get the message "GCC 5.3.0 detected" it will not work.

When you select "Update Mame Compiler" in the Downloads tab it should download and run MC64Setup.exe which should remove the registry key that makes MC64 run as admin. If this doesn't work then the "fix" is obviously not as robust as I had hoped.
Thanks for your reply. I used "Update Mame Compiler". It did not fix the issue. Still "GCC detected" is shown. Can I manually remove the registry key?
Title: Re: Mame Compiler 64 v2.0.171
Post by: headkaze on March 31, 2016, 06:06:12 pm
Thanks for your reply. I used "Update Mame Compiler". It did not fix the issue. Still "GCC detected" is shown. Can I manually remove the registry key?

I can replicate the issue on my Windows 10 machine. Looking into it now.

EDIT: Please try another "Update Mame Compiler"
Title: Re: Mame Compiler 64 v2.0.171
Post by: EMDB on April 01, 2016, 01:03:40 am
Thanks for your reply. I used "Update Mame Compiler". It did not fix the issue. Still "GCC detected" is shown. Can I manually remove the registry key?

I can replicate the issue on my Windows 10 machine. Looking into it now.

EDIT: Please try another "Update Mame Compiler"
FIXED  :applaud: :applaud: :applaud:
Title: Re: Mame Compiler 64 v2.0.171
Post by: JeremyX on April 05, 2016, 03:17:04 pm
This isn't working with MAME .172, do we have to wait for an update or am I doing something wrong?

I get:
make: *** [windows_x86] Error 2
Title: Re: Mame Compiler 64 v2.0.171
Post by: Yoeddy1 on April 06, 2016, 10:06:18 am
I wonder if there is a common problem here.  For those having problems (including me), is it because we're choosing the "Arcade" type of compile?  You know...that area within the tool that let's you select "Tiny", "Arcade", etc.  I'm not in front of it right now.  I think "Arcade" is not selected by default.  Maybe there is an issue choosing "Arcade" instead of the default setting.

Thanks,
Jason
Title: Re: Mame Compiler 64 v2.0.171
Post by: EMDB on April 06, 2016, 01:28:10 pm
I wonder if there is a common problem here.  For those having problems (including me), is it because we're choosing the "Arcade" type of compile?  You know...that area within the tool that let's you select "Tiny", "Arcade", etc.  I'm not in front of it right now.  I think "Arcade" is not selected by default.  Maybe there is an issue choosing "Arcade" instead of the default setting.

Thanks,
Jason
After the March 31 update MC64 works fine for me building MAME 0.172 in Arcade. Make sure you update MC64 from within MC64...
Title: Re: Mame Compiler 64 v2.0.171
Post by: JeremyX on April 06, 2016, 07:43:54 pm
What options did you choose? I only did 64 bit, no warnings, and direct input.
Title: Re: Mame Compiler 64 v2.0.171
Post by: MiahXGaming on April 07, 2016, 09:09:00 pm
Neat tool.
Title: Re: Mame Compiler 64 v2.0.171
Post by: Jumpstile on April 07, 2016, 09:14:29 pm
That happens for me as well but i can compile MAME with no problems.


 - J*
Title: Re: Mame Compiler 64 v2.0.171
Post by: JeremyX on April 08, 2016, 06:30:29 pm
Ok, I got it to work and I think I know what the problem was. If you look at all the posts from MKChamp on this page, he changed the 172 patch a couple times due to errors: http://forum.arcadecontrols.com/index.php/topic,64298.1040.html (http://forum.arcadecontrols.com/index.php/topic,64298.1040.html)

So I might have downloaded it before that. Anyhow, I just deleted everything and started over and it worked.
Title: Re: Mame Compiler 64 v2.0.171
Post by: Sorn on April 15, 2016, 11:52:05 am
...edit....got it compiled.
Title: Re: Mame Compiler 64 v2.0.171
Post by: Sorn on April 15, 2016, 08:11:17 pm
edit 2....got it compiled.
Title: Re: Mame Compiler 64 v2.0.171
Post by: Sorn on April 17, 2016, 08:38:55 pm
Could someone help with compiling 0172? Im getting the following errors. I was able to compile 0171 successfully on this same setup.

Compiling src/devices/cpu/h8/h8_intc.cpp...
../../../../../src/emu/video.cpp:586:6: error: redefinition of 'void video_manager::frame_update_hi(bool)'
 void video_manager::frame_update_hi(bool debug)
      ^
../../../../../src/emu/video.cpp:525:6: note: 'void video_manager::frame_update_hi(bool)' previously defined here
 void video_manager::frame_update_hi(bool debug)
      ^
Compiling src/mame/machine/igs036crypt.cpp...
Compiling src/mame/machine/kaneko_toybox.cpp...
Compiling src/mame/drivers/ms32.cpp...
Compiling src/mame/video/offtwall.cpp...
make[2]: *** [../../../../mingw-gcc/obj/x64/Release/src/emu/video.o] Error 1
make[1]: *** [emu] Error 2
make[1]: *** Waiting for unfinished jobs....

Compiling src/mame/audio/hyprolyb.cpp...
../../../../../src/osd/windows/video.cpp:234:6: error: redefinition of 'void windows_osd_interface::update_hi(bool)'
 void windows_osd_interface::update_hi(bool skip_redraw)
      ^
../../../../../src/osd/windows/video.cpp:205:6: note: 'virtual void windows_osd_interface::update_hi(bool)' previously defined here
 void windows_osd_interface::update_hi(bool skip_redraw)
      ^
Compiling src/mame/video/hyperspt.cpp...
make[2]: *** [../../../../mingw-gcc/obj/x64/Release/osd_windows/src/osd/windows/video.o] Error 1
Compiling src/mame/drivers/poolshrk.cpp...
make[1]: *** [osd_windows] Error 2


And why is it everytime I check mark clean compile I get this?

GCC 5.3.0 detected
make: *** No rule to make target `build/generated/mame/layout/', needed by `build/generated/mame/layout/18w.lh'.  Stop.
make: *** Waiting for unfinished jobs....


EDIT - Was finally able to get it to compile. I started fresh (again), downloaded compiler tools and hit update. Then I extracted the 0172 source to the fresh mame source directory, checkmarked clean compile, hit go, got the above 18w.lh error, then hit go again (it unchecks clean compile after you hit go the first time, so I left it unchecked otherwise it keeps throwing that same 18w.lh error), and then it was able to compile.

Found a bug and was able to submit to mametesters :)
Title: Re: Mame Compiler 64 v2.0.171
Post by: dragon_sa on April 24, 2016, 02:36:38 am
Hi...Im running a win7 64bit i7 system with 16g ram
Im having a lot of difficulty trying to apply the ShowCP155.diff patch, I keep getting the following error

Quote
Applying Diff Patch...
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- old\emu\machine.c   2014-03-11 16:55:00.000000000 +0000
|+++ src\emu\machine.c   2014-06-06 21:38:27.421797900 +0100
--------------------------
Finished!
0 Hours 0 Minutes and 0 Seconds Elapsed.
File to patch:

I have downloaded 171 and 172 and had same issue with both versions.
The only other patch I applied is hi_172.diff which applied without error.

I am assuming they are the only 2 patches you need to apply these days
Title: Re: Mame Compiler 64 v2.0.171
Post by: dragon_sa on April 25, 2016, 08:57:05 am
Quote
Applying Diff Patch...
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- old\emu\machine.c   2014-03-11 16:55:00.000000000 +0000
|+++ src\emu\machine.c   2014-06-06 21:38:27.421797900 +0100
--------------------------
Finished!
0 Hours 0 Minutes and 0 Seconds Elapsed.
File to patch:

I worked out the problem with the patch...the following filenames have changed on the following lines when patching 171 or 172

Change line 1 & 2
Code: [Select]
--- old\emu\machine.c 2014-03-11 16:55:00.000000000 +0000
+++ src\emu\machine.c 2014-06-06 21:38:27.421797900 +0100
to
Code: [Select]
--- old\emu\machine.cpp 2014-03-11 16:55:00.000000000 +0000
+++ src\emu\machine.cpp 2014-06-06 21:38:27.421797900 +0100

Change lines 77 & 78
Code: [Select]
--- old\emu\render.c 2014-04-07 08:04:20.000000000 +0100
+++ src\emu\render.c 2014-06-06 21:39:14.734504000 +0100
to
Code: [Select]
--- old\emu\render.cpp 2014-04-07 08:04:20.000000000 +0100
+++ src\emu\render.cpp 2014-06-06 21:39:14.734504000 +0100

Change lines 88 & 89
Code: [Select]
--- old\emu\ui\selgame.c 2014-04-07 08:04:20.000000000 +0100
+++ src\emu\ui\selgame.c 2014-06-06 21:39:38.663872700 +0100
to
Code: [Select]
--- old\emu\ui\selgame.cpp 2014-04-07 08:04:20.000000000 +0100
+++ src\emu\ui\selgame.cpp 2014-06-06 21:39:38.663872700 +0100

Replace your mame 171 or 172 folder with fresh source files and apply all your patches
Title: Re: Mame Compiler 64 v2.0.171
Post by: JeremyX on May 05, 2016, 12:24:08 pm
173 &174 compiled fine for me.
Title: Re: Mame Compiler 64 v2.0.171
Post by: vettetek on July 10, 2016, 01:05:49 pm
So - is this program still being updated? Ive had some successful compiles with it in the past but It doesn't seem to be updated past .173 and Id like to compile .175.
Anyone have a compiled 64 bit version of .175 with highscore and without nag/info?
Title: Re: Mame Compiler 64 v2.0.171
Post by: Jumpstile on July 10, 2016, 07:16:30 pm
Did you try? This is a compiler. It doesn't necessarily need to be updated with every MAME release - only if something is broken.


 - J*
Title: Re: Mame Compiler 64 v2.0.171
Post by: brucelee00 on July 14, 2016, 10:43:40 pm
Is Hi Score built-in to the new Mame release now ? or does it still have to be  compiled manually either way I am getting errors when trying to apply the hi_175.txt listed here forum.arcadecontrols.com/index.php/topic=64298.msg1580774#msg1580774 date=1468548706 anyone have any insight ?
Title: Re: Mame Compiler 64 v2.0.171
Post by: GadgetFreak on August 02, 2016, 11:50:18 am
I have just downloaded Mame Compiler 64 V2.0.173.
I on windows 10 64bit and had issues with the program locking up after decompressing any of the downloads.
So I manually used the links and then decompressed the 3 archives to the buildtools root folder on my C drive.
I am trying to build MameUI but it makes no difference if I try the OSD as windows. I am a dev but mostly do bits in VS2015 on the PC for ease but mainly do microcontroller stuff these days.
Anyway, it always fails the first time after ticking clean build, but the second GO results in the build makefiles being generated.
But the first compile fails... Here is a portion of the log window:-

Generating ../build/projects/windows/mame/gmake-mingw64-gcc/zvt.make...
Generating ../build/projects/windows/mame/gmake-mingw64-gcc/skeleton.make...
Generating ../build/projects/windows/mame/gmake-mingw64-gcc/mame.make...
Done.
make[1]: Entering directory `C:/buildtools/src/Mame0173/build/projects/windows/mame/gmake-mingw64-gcc'
Precompiling src/emu/emu.h...
In file included from ../../../../../src/emu/emu.h:41:0:
../../../../../src/emu/hash.h:82:12: error: 'sha1_t' has not been declared
  bool sha1(sha1_t &result) const { result = m_sha1; return m_has_sha1; }
            ^
../../../../../src/emu/hash.h:83:16: error: 'sha1_t' has not been declared
  void add_sha1(sha1_t sha1) { m_has_sha1 = true; m_sha1 = sha1; }
                ^
../../../../../src/emu/hash.h:104:2: error: 'crc32_t' does not name a type
  crc32_t                 m_crc32;
  ^
<<<<<<<<<<<<<<<< Removed some of the errors here to reduce post size >>>>>>>>>>>>>>>>>>>>>>>>>>>>
make[2]: *** [../../../../mingw-gcc/obj/x64/Release/emu.h.gch] Error 1
make[1]: Leaving directory `C:/buildtools/src/Mame0173/build/projects/windows/mame/gmake-mingw64-gcc'
Finished!
0 Hours 0 Minutes and 49 Seconds Elapsed.
make[1]: *** [precompile] Error 2

Have I just made a path mistake?
Has anybody else hit this problem?
Title: Re: Mame Compiler 64 v2.0.171
Post by: newoski on August 02, 2016, 05:19:33 pm
I'm trying to compile 176, but everything I apply the hiscore diff, patch.exe crashes. Do I need to wait for an update to MameCompiler?
Title: Re: Mame Compiler 64 v2.0.176
Post by: headkaze on August 05, 2016, 02:25:00 am
Mame Compiler 64 v2.0.176 Released
- Added support for EOL Conversion and Prefix Strip options for patching
Title: Re: Mame Compiler 64 v2.0.176
Post by: acvieluf on November 30, 2016, 09:03:07 pm
Hi headkaze,

Great program!  I'm just beginning to try compiling out, and was wondering if there were some basic instructions on the method of compiling older versions?  I have perused this thread some, but it's a lot, so i'm not sure if its buried here?  I'm not asking you to have to type everything out or anything, but is there a link you can point me to?

Thanks again.  And thanks for making this free, on behalf of those of us that would be too intimidated to spend the money on something we have no clue about. Its both terrifying and exciting to take on something like this that's not at all in my wheelhouse.

 :cheers:
Title: Re: Mame Compiler 64 v2.0.176
Post by: headkaze on February 25, 2017, 07:20:21 am
MAME Compiler has been updated to use GCC 6.3.0. Please update MAME Compiler along with your Compile Tools.

1. Select the Downloads tab
2. Select the "Update MAME Compiler" button
3. Select the "Download File List" button
4. Put a tick next to "Build Tools" and select the "Download Selected" button
5. Please wait until the download, extraction and copy finishes
6. Compile MAME again
Title: Re: Mame Compiler 64 v2.0.176
Post by: eric.gilmore.750 on May 14, 2017, 10:35:18 pm
Hi everyone. I'm new to mame an I was wondering can this program compile mame 0.185 ? I have the 0.185 non merged set plus chds. I want to add no nag an high score support?


Sent from my SM-N920T using Tapatalk

Title: Re: Mame Compiler 64 v2.0.176
Post by: smalltownguy on May 26, 2017, 10:59:46 am
Anyone successfully compile MAME 183 with this? I'm having trouble.

EDIT: Nevermind, I figured it out. I was trying to compile version 183 with the hiscore diff from 178. Once I manually downloaded the source for 178 and used that, it compiled just fine.
Title: Re: Mame Compiler 64 v2.0.176
Post by: Malandro on August 16, 2017, 02:48:34 pm
I'm having trouble compiling MAME 0.188 with the new driver for Thunder Hoop 2 which was promoted to working status thanks to David Haywood and Kevin Eshbach.

I've downloaded mame source code from the official website, replaced the old "thoop2.cpp" file with the new one ticked some options in MC64 and got the following error message (see attachment image). I know i'm missing something obvious i just can't figure out what...

Title: Re: Mame Compiler 64 v2.0.176
Post by: EMDB on April 14, 2018, 04:26:22 am
When I try to compile  MAME 0.196 with the no-nag patch (http://mamestuff.lowtrucks.net/MKChamp/ (http://mamestuff.lowtrucks.net/MKChamp/)) using the latest Mame Compiler (V2.0.176) I get a lot of warnings during the build. The build finishes though and a new version om MAME is created. It even seems to work but I'm in doubt about the warnings. It looks like 2 warnings about deprecated stuff repeating in all kind of drivers:

(http://www.emdb.eu/mame-error.jpg)
Title: Re: Mame Compiler 64 v2.0.176
Post by: Robbbert on April 23, 2018, 08:14:56 pm
Don't worry about that "deprecated" stuff... ignore it. There's going to be even more of it for 0.197
Title: Re: Mame Compiler 64 v2.0.176
Post by: Jakobud on April 29, 2018, 08:10:06 pm
Is Mame Compiler 64 still supported? I just installed v2.0.177 and when I goto the Download Tab, the list is empty. I click "Download File List" and I get an Exception:

https://prnt.sc/jbrz6o


Code: [Select]
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NotSupportedException: The requested security protocol is not supported.
   at System.Net.ServicePointManager.set_SecurityProtocol(SecurityProtocolType value)
   at MAMECompiler64.FileDownloader..ctor(Boolean supportsProgress)
   at MAMECompiler64.frmDownload.DownloadFile()
   at System.Windows.Forms.Form.OnLoad(EventArgs e)
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.WmShowWindow(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
MAMECompiler64
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files%20(x86)/MAME%20Compiler%2064/MAMECompiler64.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5485 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.


Title: Re: Mame Compiler 64 v2.0.176
Post by: EMDB on May 07, 2018, 10:15:49 am
Is Mame Compiler 64 still supported? I just installed v2.0.177 and when I goto the Download Tab, the list is empty. I click "Download File List" and I get an Exception:
The latest (V2.0.197) works fine for me. List is downloaded with the latest (0.197) source code.