GM 0.147u3

[Jonny G]

Hi Calamity.

Is the 0.147u3 diff good to go for windows? It's been ages since I touched my MAME install and I think i'm a bit rusty. Is the process to use the 0.147 source, then apply the regular u1, u2, u3 diffs, hiscore, then your GM u3 diff?

Thanksyous.

[Ansa89]

Is the 0.147u3 diff good to go for windows?

Do you mean groovymame 0.014 applied to mame 0.147u3?
In that case, I think yes.

Is the process to use the 0.147 source, then apply the regular u1, u2, u3 diffs, hiscore, then your GM u3 diff?

Yes.

[Jonny G]

By good to go I meant there was a load of problems with 0.147 building properly. Gonna wait for confirmation from Calamity that this one is cool.

Thanks for the reminder on the compiling. Just needed to see it in front of me for it to make sense again.

[Ansa89]

I compiled groovymame-0.147u3 without problems, and Calamity (some time ago) said that the new patch will be windows compliant.
So I think you also can compile it.

[Jonny G]

Cool. What did you use to compile? I was using mamecompiler64 with the default environment it installs, rather than the new one from mamedev.

[Calamity]

Hi Jonny G,

Yeah once the code compiled for me (both 32/64-bit) without a single warning,  I created the diff out of it, so if you apply it as mentioned above you should have no issues.

As a note I used the new compiling tools downloaded directly from the mamedev site. It should be just the same with the updated MAME Compiler64.

[Ansa89]

I used the new compiling tools downloaded directly from the mamedev site.

Me too.

[Jonny G]

As a note I used the new compiling tools downloaded directly from the mamedev site. It should be just the same with the updated MAME Compiler64.

Is there a new MC64? I can only find V1.23

[Calamity]

Is there a new MC64? I can only find V1.23

No idea, just make sure the compiling pack is up to date.

[Jonny G]

I've got the new dev tools from here http://mamedev.org/tools/. Removed the original mingw 64 & 32 directories from c:\mingw and replaced them with the two I downloaded.

0147 source is unpacked to c:\mingw\source.

Upon applying the first u1 update i get the following (see attached log) something tells me its not going to compile correctly. Any ideas?

Thanks!

[Ansa89]

Which command did you use?
Starting with fresh sources, try with

Code: [Select]

patch --binary -E -p0 -i path\to\patch.diff

[Jonny G]

I'm using Headkaze's mamecompiler 64. No idea how to compile manually but have managed to compile myself the last 10 or so mame versions with it.

Just tried again with a fresh download of source and same. Feeling like a noob.

[Calamity]

I've been using MAME Compiler for years, but this time due to the new tool chain I wanted to minimize risks and just followed the instructions here:

http://mamedev.org/updates.html

I worked perfect for me.

[Jonny G]

Cheers guys. I'll give that a whirl.

[dgame]

Johnny G,

I got those same errors when applying the patches.

The errors seem to relate to the console/computer emulation (MESS) stuff.

It still compiles with Headkaze's Mame Compiler 64 v1.23 and works, at least the MAME games do.

[Jonny G]

Johnny G,

I got those same errors when applying the patches.

The errors seem to relate to the console/computer emulation (MESS) stuff.

It still compiles with Headkaze's Mame Compiler 64 v1.23 and works, at least the MAME games do.

Thanks for that, I thought it might just be MESS related, but didn't want to get it installed in my cab and update my roms to 147 only to find out it didnt work properly.

[Jonny G]

Well, manual compile works, but it's spat out a MAME64.exe which I presume isn't going to work on my 32bit XP install. Do you know how to specify compiling a 32bit version?

[dgame]

Open up a command-line window. First, ensure that the appropriate mingw/bin directory is part of your search path. Do that by typing:

set path=mingw\mingw64-w32\bin (32-bit)
set path=mingw\mingw64-w64\bin (64-bit)

http://mamedev.org/tools/

or try
> make PTR64=0

[Jonny G]

aaaah i see what I've done now. I set both of those, but obviously setting 64 overwrote 32. Duh. Not one of my brighter days today.

[dgame]

Did you figure out how to switch between Mame and Mame64?

The "set path=" command specifies the version of the compiler to use and not the type of Mame executable to build.

I suppose the compiler defaults to building the version to support the current OS version.

However, Headkaze's Mame Compiler is able to produce both 32 bit and 64 bit on my 32 bit system so it should be possible from the command line.

I am trying to build 64 bit Mame on 32 bit Windows OS.

Using  "make PTR64=1" Starts to build a Mame64 but it fails.

Anyway, this is not a big deal as I can just compile Mame on the 64 bit OS it will run on.

I am just curious as to how to force it to build one type or the other.

[Calamity]

Using  "make PTR64=1" Starts to build a Mame64 but it fails.

Anyway, this is not a big deal as I can just compile Mame on the 64 bit OS it will run on.

I am just curious as to how to force it to build one type or the other.

I was never able to get that working. The problem, I think, is that the compilation process involves creating some binaries that are launched by the makefile, but this binaries are created with the same settings as MAME so they can't run under 32 bits and the compilation fails.

[Jonny G]

Thanks for the help guys. Looks like I'm back up to date with GroovyMame. Don't suppose anyone knows how to add Cave support back in do they?

[dgame]

I found about the Cave SH3 games from another thread on here.

If you Google you can find pre-built binaries, roms, and such. But no GroovyMAME SH3 goodness.

I had a hard time finding the source code files (cavesh3.c and csh3blit.c) and the ones I did find did not work with GM 147u3 patched source.

There is a mame 147u1 cave sh3 driver diff file floating around that creates the missing cavesh3.c and csh3blit.c files and correctly patches the mame.lst file but it misses on the src/mame/mame.mak patches and does not compile.

BUT if you apply the diff patch and reference the diff file's last entry to manually add the two missing lines to the src/mame/mame.mak in your GM patched source code it will compile and run.

EDIT: There is a cavesh3_147u3.diff file floating around that works without modification. Apply this patch last. See: http://forum.arcadecontrols.com/index.php?topic=129890.0

Those bullet hell games are crazy.

[desh_thiere]

Hi, I am sorry to dig up an old thread, this is my first post here. I am looking at compiling GroovyMame 0147u3 with Cave SH3 support. This is the first time I have ever compiled a version of MAME and I have run into a few issues. I downloaded the latest mingw environment + the 147 source (I know 148 is out now, but I made sure I grabbed 147). I then followed this basic guide to compiling. http://mrdo.mameworld.info/compile.php

I applied the u1, u2 and u3 updates with no errors, however, when I went to apply the groovymame 0147u3 diff, I encountered this error.


C:\mamesrc1>patchmame 0147u3_groovymame_014

C:\mamesrc1>set path=c:\mingw\mingw64-w64\bin

C:\mamesrc1>patch -p0 -E  0<0147u3_groovymame_014.diff
patching file src/emu/clifront.c
patching file src/emu/drivers/empty.c
patching file src/emu/emu.h
patching file src/emu/emu.mak
patching file src/emu/emuopts.c
patching file src/emu/emuopts.h
patching file src/emu/hiscore.c
Hunk #1 FAILED at 305.
1 out of 1 hunk FAILED -- saving rejects to file src/emu/hiscore.c.re
patching file src/emu/machine.c
patching file src/emu/machine.h
patching file src/emu/render.c
patching file src/emu/switchres/modeline.c
patching file src/emu/switchres/monitor.c
patching file src/emu/switchres/switchres.c
patching file src/emu/switchres/switchres.h
patching file src/emu/switchres/util.c
patching file src/emu/ui.c
patching file src/emu/video.c
patching file src/emu/video.h
patching file src/mame/drivers/galaxian.c
patching file src/mame/includes/galaxian.h
patching file src/osd/sdl/osdsdl.h
patching file src/osd/sdl/sdl.mak
patching file src/osd/sdl/sdlmain.c
patching file src/osd/sdl/switchres.c
patching file src/osd/sdl/video.c
patching file src/osd/sdl/video.h
patching file src/osd/sdl/window.c
patching file src/osd/sdl/window.h
patching file src/osd/windows/drawd3d.c
patching file src/osd/windows/drawdd.c
patching file src/osd/windows/pstrip.c
patching file src/osd/windows/pstrip.h
patching file src/osd/windows/switchres.c
patching file src/osd/windows/video.c
patching file src/osd/windows/video.h
patching file src/osd/windows/window.c
patching file src/osd/windows/windows.mak
patching file src/osd/windows/winmain.c
patching file src/osd/windows/winmain.h

Would anyone be able to help me out with what I am doing wrong? I want to add the SH3 compatibility according dgame's last post also. However, I need to first get Groovymame 147u3 to compile properly. Something appears to be going wrong with the hiscore part? I am not sure...

Thanks very much for anyone who is able to assist. This is my first time doing this, and expected something to go wrong

[Calamity]

Hi desh_thiere,

You didn't apply the MKChamp's hiscore diff, you need to add it before the GM patch:

MAME's source -> u1 diff-> u2 diff->u3 diff-> MKChamp's diff-> GM diff

[desh_thiere]

Hi Calamity, thanks for the super fast reply.

I did actually apply a file called 147_hi, I forgot to put that in my original post. So I applied the u1, u2 and u3 patches and then the 147_hi.diff. That is the error I got after applying those files and then trying to apply the groovymame 147u3 diff.

Is there another hiscore file I need to be applying? I grabbed the hiscore file from here. http://forum.arcadecontrols.com/index.php?topic=64298.0

Thanks very much for your help.

[Calamity]

Maybe he changed the diff afterwards, try the one here.

[desh_thiere]

That worked beautifully! Thanks a lot Calamity. Now all I need to do is figure out how to add in the SH3 support and I will have my perfect new MAME build.

If anyone on the boards can help me with figuring out how to do this: As stated previously by dgame. It would be excellent.

"There is a mame 147u1 cave sh3 driver diff file floating around that creates the missing cavesh3.c and csh3blit.c files and correctly patches the mame.lst file but it misses on the src/mame/mame.mak patches and does not compile.

BUT if you apply the diff patch and reference the diff file's last entry to manually add the two missing lines to the src/mame/mame.mak in your GM patched source code it will compile and run."

I do not really know what he means by adding the reference to the diff file, this stuff is rather new to me.

Thanks for all the help!