MAME Compiler 64 v2.0.197

[headkaze]

https://www.baker76.com/mame-compiler-64

[MKChamp]

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.

[headkaze]

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?

[MKChamp]

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.

[headkaze]

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!

[headkaze]

Minor update

[edge]

Thanks, headkaze, for the app.  Will try it out this week.

[Neilyboy]

very cool app headkaze!! this is very much appreciated.

Neil

[mcfreak]

Very nice. 

[MKChamp]

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.

[Encryptor]

When using the program should you do the 119u1 & 119u2 patches before or after applying the high diff no nag patch?


Encryptor

[loadman]

 

[headkaze]

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

[headkaze]

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.

[Encryptor]

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

Thank you!

Encryptor

[TheBrokentoken]

Great, great tool.  Many thanks for putting this together.

Is your site down right now?  I cannot get either of the files downloaded.  Thanks.

[headkaze]

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.

[gonzo90017]

How old?

[headkaze]

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.

[headkaze]

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+

[TeutonicDarkness]

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

[SGT]

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.

[TeutonicDarkness]

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.

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

[SGT]

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?

[TeutonicDarkness]

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

[Lakersfan]

Thanks for this app! It was fun compiling manually, but this sure makes things easier and quicker. 

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

[headkaze]

Thanks for this app! It was fun compiling manually, but this sure makes things easier and quicker. 

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.

[Lakersfan]

Thanks for the reply, headkaze. I used it for a compile of .120 and it worked perfectly! 

[topher0002]

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?

[headkaze]

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.

[rooter]

Any chance this works with the 64bit version of Mame?  If not, will it in the future?

[headkaze]

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.

[bent98]

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.

[MKChamp]

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

[bent98]

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

[headkaze]

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

[bent98]

haha. Will it cause a problem though?

[MKChamp]

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??)

[headkaze]

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

[bent98]

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.