245 replies to this topic

[iano]

headkaze, on Oct 7 2007, 12:13 PM, said:

Yep those should be perfectly fine. I tested compiling Mame 109 and I didn't get any warnings but I didn't apply any of the diff's. I'm pretty sure those warnings are from the diff's.

Those are just warnings not errors so it should be fine. The "Disable WError" really just disables the warnings that stop compiling. This is because were using a newer version of GCC.

Thanks.

[hansolo77]

I'm gonna try and do this. I've done everything according to your instructions in the first message. However, I'm holding off right now on finish until I get an answer for this question:

Do I need to apply the hi_119u2.diff patch to the 119u2 patch before patching up to 119u3? Or should I continue and patch to 119u3 then apply the hi_119u2 patch? It doesn't seem clear to me because in my eyes, applying an older patch to a newer version shouldn't work.

I just wanted to know for sure which patch I should do next.

[Brian Hoffman]

Do this.
Download mame 119 source
Download the U1-U3 patches

Do this

1. Apply hi_119diff (included in installer)
2. Apply 119u1.diff (from mamedev)
3. Apply 119u2.diff (from mamedev)
4. Apply 119u3.diff (from mamedev)
5. Compile

[hansolo77]

Are you sure about that Brian? HK said to apply the u-diffs first, then the hiscore.

headkaze, on Sep 29 2007, 02:41 PM, said:

Mame Compiler v0.3 - HeadKaze
==============================================
### Applying Patches ###

To apply them do in this order:

1. Apply xxxu1.diff
2. Apply xxxu2.diff
3. Apply xxxu3.diff
4. Apply hi_xxx.diff
5. Compile

Now I'm really confused!

[Brian Hoffman]

hansolo77, on Oct 9 2007, 10:17 PM, said:

Are you sure about that Brian? HK said to apply the u-diffs first, then the hiscore.
Now I'm really confused!

100% sure my friend.
download 119 soucre.
Patch using the supplied 119_hi.diff ( I also included it here)
Then patch the u1-u3 official.



Basiclly your downloading 119 non updated.. Then your removing the nags and adding hiscore for the same version.
then your updating to the newer version.

If you were to use the 119u2_hi.diff then you would need to be on U2 before applying the patch. Then you would need to update to U3..

I find the first way less confusing.

Attached Files

•  hi_119.zip   5.6K   4 downloads

[hansolo77]

OK great. Then I'm glad I stopped. I almost patched up to u3 then go back and patch the hi. Thanks a lot!

[Brian Hoffman]

hansolo77, on Oct 9 2007, 11:18 PM, said:

OK great. Then I'm glad I stopped. I almost patched up to u3 then go back and patch the hi. Thanks a lot!

I del the whole SRC folder and re extract it from the ZIP from MAMEDEV. Just because you stop the compile doesnt mean it undoes your changes. Its really not too bad.. let us know how it works for ya

[hansolo77]

Yeah, I actually had a bit of trouble but I came out on top eventually! What I tried to do first, was just compile what diff's I had done... to see if it would even work. It came out ok, but I didn't really like the fact that it compiled everything into the "Mame Compiler\MAME" folder, where I also had the source files. I didn't remember which ones were new, and which ones were source. So, I deleted everything in that folder, and created a new subfolder called "!SOURCE". I figured that would be obvious enough for me to know which folders are new, and which were source. I re-extracted the 119 source to the new folder, and proceeded with patching. For some reason, the compiler didn't like the source in a nested subfolder like I had it. It gave me a whole bunch of RED ERROR txt in the readout. I tried to uninstall the compilre, but one of the files were locked and wouldn't allow me to delete it. I shrugged it off anyway, and reinstalled again. This time, it gave me an error that a file already existed, and when I tried to overwrite it, it gave me permission errors. I decided to ignore that too. Another attempt at compiing and it completed. However, the compiled version was now in the "!SOURCE" folder as well! UGH! Then I noticed it didn't actually create the executable. Something very wrong here. I tried another uninstall, had the same file come up protected an undeleteable. I tried manually deleting it, still no go. Then I tried to adjust the permissions of the file so I could grant myself delete permission. That wouldn't even happen. It came back on the permissions tab saying I didn't have permission to edit the permission settings of that file! WHAT GIVES!?! Is that file now permanetly locked on my computer? LOL! I ended up doing a complete shutdown. Had dinner. Came back and cold booted. Manually deleted the file, and it worked! I then reinstalled the compiler and put the source in the MAME subfolder as originally stated. I also opened a NotePad and wrote down the names of the 4 things in that folder so I would know which ones NOT to copy to my MAME drive. Then I began to apply the patches once more. Here's how I did it:
hi_119.diff
119u1.diff
119u2.diff
hi_119u2.diff
11i9u3.diff
Then for compiling, I selected "Pentium M/Dual Core" from the drop down, and checked the Dual Core box. I wasn't sure about the other options, like force direct input, debug, clean version, etc. So I just left those blank. The compile took about 8 minutes for me. I brushed my teeth while I waited. Then I copied over the new files to my MAME drive, in it's own \MAME\ folder. I erased everything I had so far in that folder because I have my roms and extras and chd's backed up on another drive. I wanted to make sure nothing from previous MAMEs would interfere. The I launched the program. "mamepm.exe -cc" I don't know why it's mamePM, but oh well. It created my config file. Then I copied over my roms to the ROMS folder. Then I launched the command-line (this is a first for me, I've always used MAME32 with the GUI). It came up instantly with the little in game menu box, displaying a list of games randomy. If you start typing letters, it displays the games that match. Every letter further shrinks the list of games found. I tried to play a game, and although it ran fine, I couldn't get the controls to work. I have a gamepad I'll eventually use (in reality, I'll eventually be using a real joystick control panel), but right now I just wanted keyboard functionality. I already know 5 coins and 1 starts. But nothing else happened. I hit TAB for the menu and could move the bar with my cursor keys, but now I can't go into the Input options. It's like the "Press enter to select option" [ENTER] key is remapped some how. Any ideas?

Oh, and yes. I was successful in compiling MAME (yes!) and getting GameEx to work with it (yes!) and able to launch games via GameEx (YES!).

-----------------------
:::::::::EDIT:::::::: Nevermind, I figured it out!
-----------------------

[jthompson]

hansolo77, on Oct 9 2007, 08:25 PM, said:

The I launched the program. "mamepm.exe -cc" I don't know why it's mamePM, but oh well. It created my config file.

Mamepm for mame compiled for pentium M, mameat for mame compiled for athlon etc. Just rename it to mame if you like.

[Brian Hoffman]

HK,

Im having a issue compiling mame .120 using the compilier... I gives me a libemu.a error...

I can compile using the mingw32 from mamedev... The only reason I bring this up is I know your version is special because of the output...

Have you tried this new version?

[headkaze]

Brian Hoffman, on Oct 17 2007, 11:56 AM, said:

HK,

Im having a issue compiling mame .120 using the compilier... I gives me a libemu.a error...

I can compile using the mingw32 from mamedev... The only reason I bring this up is I know your version is special because of the output...

Have you tried this new version?

I'm trying it now...

[headkaze]

I get the same error. Here is what I found...

- My compiled version of mingw32-make.exe is causing the problem
- If I download the official source for MinGW make and compile it even with _no_ changes it wont work either
- My compiled version of make is 204 KB, the official make binary is 162 KB (both are version 3.81). Only the official make binary seems to compile Mame 0120 successfully.

So in conclusion it seems, the problem is my custom make file, but it's not the changes I've made but the _way_ I've compiled it. I've tried both Visual C 98 and Visual C 2003 and they both compile a make that won't work. Remember this is with or without the necessary changes to make output work in Mame Compiler. Very strange.

So to fix this we really need to find out how the official MinGW make file is compiled so we can compile it in the same way. Unfortunately I have no idea how to find this out.

I'm really busy trying to get LCD Plugin v2 out the door so I can't waste any more time on this, but maybe you or MKChamp can figure this one out. PM me if you need the source code changes necessary to get make output in Mame Compiler.

Here is the source for MinGW make:

http://mamedev.org/t...81-src-2.tar.gz

And here is the official MinGW make binary:

http://mamedev.org/t...e-3.81-2.tar.gz

[Nologic]

hmm I thought most things compiled for mame where with GCC...which build...I don't know.

[headkaze]

Nologic, on Oct 18 2007, 02:47 AM, said:

hmm I thought most things compiled for mame where with GCC...which build...I don't know.

Your probably right. Although I also tried doing this..

1. Downloaded http://mamedev.org/t...81-src-2.tar.gz
2. Downloaded MSYS
3. Put make-3.81 folder into C:\msys\1.0\home\HeadKaze
4. Run msys.bat

$ cd make-3.81
$ configure
$ make

5. Copy make.exe to C:\MinGW\bin\mingw32-make.exe
6. Compile Mame 0120

Result:

mingw32-make.exe: *** No rule to make target `obj/windows/mamep4/emu/machine/rp5h01.o', needed by `obj/windows/mamep4/libemu.a'.  Stop.

Same result as using Visual Studio 98 and 2003

[iano]

headkaze, on Oct 17 2007, 06:06 PM, said:

Your probably right. Although I also tried doing this..

1. Downloaded http://mamedev.org/t...81-src-2.tar.gz
2. Downloaded MSYS
3. Put make-3.81 folder into C:\msys\1.0\home\HeadKaze
4. Run msys.bat

$ cd make-3.81
$ configure
$ make

5. Copy make.exe to C:\MinGW\bin\mingw32-make.exe
6. Compile Mame 0120

Result:

mingw32-make.exe: *** No rule to make target `obj/windows/mamep4/emu/machine/rp5h01.o', needed by `obj/windows/mamep4/libemu.a'.  Stop.

Same result as using Visual Studio 98 and 2003

Do you think this may be done intentionally ? The timing seems funny after the 'patch episode'.

[Brian Hoffman]

iano, on Oct 17 2007, 10:37 PM, said:

Do you think this may be done intentionally ? The timing seems funny after the 'patch episode'.

No this wasnt....

Aaron Giles told me that the patch was ok... just not condoned.
2 reasons... 1) I didn't include the source. 2) It removes the screens that make mame make sure users are a) aware that some roms may not work correctly. Make sure its useres are aware they need to legally own the PCB or the dumped rom they have.

To combat the *PATCH* future mame builds maybe digitaly signed.
You need an offical binary to compare the patched binary.. In order to create the patch file.

Tho this may never happen... Things have calmed down about this now

MAME 120 introduces a few changes to the way it works.

If anything Id think they would change the code for the disclaimers... Rather than use a new compiling method...
Or go with the signed binary..

Oh well
The Diff for 119 no nags DOES WORK for 120.

[headkaze]

We need someone who knows more about MinGW and linux, and knows how that official make binary is compiled. If we find them I can give them to modifications to it so they can compile it. Perhaps it's compiled on a linux machine? I still get a different size binary using MSYS to the official one.

[Nologic]

hmm why linux? Shouldn't the i686-pc-cygwin build work fine after if preceded by Cygwin first? Tho frankly I'm talking out of my ass for the most part.

[iano]

Brian Hoffman, on Oct 18 2007, 12:13 AM, said:

No this wasnt....

Aaron Giles told me that the patch was ok... just not condoned.
2 reasons... 1) I didn't include the source. 2) It removes the screens that make mame make sure users are a) aware that some roms may not work correctly. Make sure its useres are aware they need to legally own the PCB or the dumped rom they have.

To combat the *PATCH* future mame builds maybe digitaly signed.
You need an offical binary to compare the patched binary.. In order to create the patch file.

Tho this may never happen... Things have calmed down about this now

MAME 120 introduces a few changes to the way it works.

If anything Id think they would change the code for the disclaimers... Rather than use a new compiling method...
Or go with the signed binary..

Oh well
The Diff for 119 no nags DOES WORK for 120.

Sorry Folks. Didn't mean to start speculation or piss anyone off. Just thought it was a funny coincidence that's all.

[Brian Hoffman]

iano, on Oct 18 2007, 12:32 AM, said:

Sorry Folks. Didn't mean to start speculation or piss anyone off. Just thought it was a funny coincidence that's all.

Who's pissed?.....

I just wanted to clear the air so there is no confusion....

It did create quite a rukus didnt it...