Author Topic: MAME Compiler 64 v2.0.197 (Read 366027 times)

Gray_Area · « **Reply #520 on:** May 13, 2011, 01:33:35 am »

Quote from: llaffer on May 09, 2011, 10:54:30 pm

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.

headkaze · « **Reply #521 on:** May 14, 2011, 11:28:22 pm »

Quote from: Gray_Area on May 13, 2011, 01:33:35 am

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.

llaffer · « **Reply #522 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.

headkaze · « **Reply #523 on:** May 14, 2011, 11:51:50 pm »

Quote from: llaffer on May 09, 2011, 10:54:30 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.

headkaze · « **Reply #524 on:** May 28, 2011, 09:43:36 pm »

Updated to support latest toolchain.

Gray_Area · « **Reply #525 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

jimmy2x2x · « **Reply #526 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...

headkaze · « **Reply #527 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.

jimmy2x2x · « **Reply #528 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.

FrizzleFried · « **Reply #529 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?

Yoeddy1 · « **Reply #530 on:** July 04, 2011, 01:20:49 am »

Any problems with 0.143?

Jason

headkaze · « **Reply #531 on:** July 05, 2011, 10:48:07 am »

Quote from: Yoeddy1 on July 04, 2011, 01:20:49 am

Any problems with 0.143?

Jason

Nope

Visitor Q · « **Reply #532 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.

portugese pirate · « **Reply #533 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

headkaze · « **Reply #534 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.

portugese pirate · « **Reply #535 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

sega_mad · « **Reply #536 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

Dazz · « **Reply #537 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?

headkaze · « **Reply #538 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.

Donkbaca · « **Reply #539 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!

Dazz · « **Reply #540 on:** August 20, 2011, 01:11:40 pm »

Quote from: 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.

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.

headkaze · « **Reply #541 on:** August 21, 2011, 11:50:48 am »

Quote from: Dazz on August 20, 2011, 01:11:40 pm

It looks like some changes to mingw-mame were made starting 142u4.

Thanks for reporting this. MC64 has been updated with the latest toolchain.

netman88 · « **Reply #542 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?

headkaze · « **Reply #543 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

Chewbacca · « **Reply #544 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.

Yoeddy1 · « **Reply #545 on:** February 07, 2012, 05:50:18 pm »

Just compiled 0.145. Worked great!

Jason

raungst · « **Reply #546 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?

raungst · « **Reply #547 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.

headkaze · « **Reply #548 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.

g_block247 · « **Reply #549 on:** March 08, 2012, 08:36:46 pm »

A noobish question I know, but what is (MAME Compiler) for?

Le Chuck · « **Reply #550 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.

milhouse · « **Reply #551 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.

milhouse · « **Reply #552 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 now get an exit prompt when I try to exit Mame (Are you sure you want to quit? Press ''UI Select'' (default: Enter) to quit. Press ''UI Cancel'' (default: Esc) to return to emulation). Looks like its from emu/ui.c.
My old hi scores are gone for certain games (Robotron, Q-Bert) but remain for others (Ms. Pac-Man, Pac-Man).
My old controlled config files, at least for qbert, don't work.

I've tried applying hi_145u1.diff after u1 and u3, but it doesn't seem to make a difference.

Anyone seen this before?

Flake · « **Reply #553 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?

Flake · « **Reply #554 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?

Rok · « **Reply #555 on:** May 06, 2012, 01:22:24 pm »

deleted

Flake · « **Reply #556 on:** May 10, 2012, 03:55:27 pm »

Seriously WTF happened to this thread? Did everyone go on vacation for a month?

headkaze · « **Reply #557 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.

Flake · « **Reply #558 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

headkaze · « **Reply #559 on:** May 25, 2012, 03:24:01 pm »

I would start from the beginning and follow the instructions here.

It has a link to MameUI here. 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).


Main	Restorations	Software	Audio/Jukebox/MP3	Everything Else	Buy/Sell/Trade
Project Announcements	Monitor/Video	GroovyMAME	Merit/JVL Touchscreen	Meet Up	Retail Vendors
Driving & Racing	Woodworking	Software Support Forums	Consoles	Project Arcade	Reviews
Automated Projects	Artwork	Frontend Support Forums	Pinball	Forum Discussion	Old Boards
Raspberry Pi & Dev Board	controls.dat	Linux	Miscellaneous Arcade	Wiki Discussion	Old Archives
Lightguns	Arcade1Up	Try the site in https mode		Site News


Unread posts \| New Replies \| Recent posts \| Rules \| Chatroom \| Wiki \| File Repository \| RSS \| Submit news