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

  

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

0 Members and 1 Guest are viewing this topic.

Flip The Switch

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 61
  • Last login:July 02, 2012, 02:33:48 am
  • I grew extra fingers for gaming....
Re: Mame Compiler 64 v1.19 Released!
« Reply #480 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.
« Last Edit: July 22, 2010, 08:16:15 am by Flip The Switch »
:picsMy first cab - Plutos rebuild:pics

headkaze

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 2943
  • Last login:August 14, 2023, 02:00:48 am
  • 0x2b|~0x2b?
Re: Mame Compiler 64 v1.19 Released!
« Reply #481 on: July 22, 2010, 08:51:48 am »
Mine crashes randomly

When you compiled did you set "Optimize for" to None?

Flip The Switch

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 61
  • Last login:July 02, 2012, 02:33:48 am
  • I grew extra fingers for gaming....
Re: Mame Compiler 64 v1.19 Released!
« Reply #482 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.
« Last Edit: July 22, 2010, 07:51:37 pm by Flip The Switch »
:picsMy first cab - Plutos rebuild:pics

Flip The Switch

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 61
  • Last login:July 02, 2012, 02:33:48 am
  • I grew extra fingers for gaming....
Re: Mame Compiler 64 v1.19 Released!
« Reply #483 on: July 25, 2010, 02:34:04 am »
/EDIT - all working now, thanks MKChamp for the help!
« Last Edit: July 25, 2010, 07:08:16 am by Flip The Switch »
:picsMy first cab - Plutos rebuild:pics

shrunkenmaster

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 636
  • Last login:July 24, 2022, 10:17:33 am
Re: Mame Compiler 64 v1.19 Released!
« Reply #484 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??

Yoeddy1

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 112
  • Last login:September 15, 2022, 12:40:23 am
Re: Mame Compiler 64 v1.19 Released!
« Reply #485 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!

Encryptor

  • Trade Count: (+34)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1287
  • Last login:December 21, 2023, 08:01:18 pm
Re: Mame Compiler 64 v1.19 Released!
« Reply #486 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

WhereEaglesDare

  • Trade Count: (+4)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1536
  • Last login:March 24, 2014, 08:47:08 pm
  • Shut Off All The Compactors on the Detention Level
    • My HomePage
Re: Mame Compiler 64 v1.19 Released!
« Reply #487 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?

WhereEaglesDare

  • Trade Count: (+4)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1536
  • Last login:March 24, 2014, 08:47:08 pm
  • Shut Off All The Compactors on the Detention Level
    • My HomePage
Re: Mame Compiler 64 v1.19 Released!
« Reply #488 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.

WhereEaglesDare

  • Trade Count: (+4)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1536
  • Last login:March 24, 2014, 08:47:08 pm
  • Shut Off All The Compactors on the Detention Level
    • My HomePage
Re: Mame Compiler 64 v1.19 Released!
« Reply #489 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?

Kman-Sweden

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 526
  • Last login:October 23, 2015, 07:29:00 am
  • Up the Irons!
Re: Mame Compiler 64 v1.19 Released!
« Reply #490 on: August 27, 2010, 09:05:58 am »

WhereEaglesDare

  • Trade Count: (+4)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1536
  • Last login:March 24, 2014, 08:47:08 pm
  • Shut Off All The Compactors on the Detention Level
    • My HomePage
Re: Mame Compiler 64 v1.19 Released!
« Reply #491 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

Kman-Sweden

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 526
  • Last login:October 23, 2015, 07:29:00 am
  • Up the Irons!
Re: Mame Compiler 64 v1.19 Released!
« Reply #492 on: August 28, 2010, 07:45:28 am »
So do you have the hi-score diff for U1?

XNIF

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 133
  • Last login:January 18, 2017, 04:40:32 pm
Re: Mame Compiler 64 v1.19 Released!
« Reply #493 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?

jimmy2x2x

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1216
  • Last login:December 19, 2018, 01:29:48 am
Re: Mame Compiler 64 v1.19 Released!
« Reply #494 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)

WhereEaglesDare

  • Trade Count: (+4)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1536
  • Last login:March 24, 2014, 08:47:08 pm
  • Shut Off All The Compactors on the Detention Level
    • My HomePage
Re: Mame Compiler 64 v1.19 Released!
« Reply #495 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
« Last Edit: August 29, 2010, 07:48:05 am by WhereEaglesDare »

iano

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 53
  • Last login:June 15, 2011, 03:39:11 pm
Re: Mame Compiler 64 v1.19 Released!
« Reply #496 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.
« Last Edit: September 19, 2010, 06:27:15 pm by iano »

headkaze

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 2943
  • Last login:August 14, 2023, 02:00:48 am
  • 0x2b|~0x2b?
Re: Mame Compiler 64 v1.20 Released!
« Reply #497 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
« Last Edit: September 19, 2010, 10:23:39 pm by headkaze »

iano

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 53
  • Last login:June 15, 2011, 03:39:11 pm
Re: Mame Compiler 64 v1.20 Released!
« Reply #498 on: September 19, 2010, 09:50:02 pm »
Thanks.

 :)

WhereEaglesDare

  • Trade Count: (+4)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1536
  • Last login:March 24, 2014, 08:47:08 pm
  • Shut Off All The Compactors on the Detention Level
    • My HomePage
Re: Mame Compiler 64 v1.20 Released!
« Reply #499 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?

MKChamp

  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 502
  • Last login:February 07, 2024, 02:45:53 pm
  • Stil around.
Re: Mame Compiler 64 v1.20 Released!
« Reply #500 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 :-)

headkaze

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 2943
  • Last login:August 14, 2023, 02:00:48 am
  • 0x2b|~0x2b?
Re: Mame Compiler 64 v1.20 Released!
« Reply #501 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 ;)

wxforecaster

  • Trade Count: (+2)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 105
  • Last login:February 28, 2019, 01:19:24 pm
Re: Mame Compiler 64 v1.20 Released!
« Reply #502 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

Donkbaca

  • Our reptillian overlords would be pleased
  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 2648
  • Last login:May 09, 2012, 06:28:10 pm
    • Slim built MAME/Xbox cab
Re: Mame Compiler 64 v1.20 Released!
« Reply #503 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

headkaze

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 2943
  • Last login:August 14, 2023, 02:00:48 am
  • 0x2b|~0x2b?
Re: Mame Compiler 64 v1.20 Released!
« Reply #504 on: November 08, 2010, 01:21:46 pm »
Are you using any optimization when compiling?

What's the error message you're getting?

Donkbaca

  • Our reptillian overlords would be pleased
  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 2648
  • Last login:May 09, 2012, 06:28:10 pm
    • Slim built MAME/Xbox cab
Re: Mame Compiler 64 v1.20 Released!
« Reply #505 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.

WhereEaglesDare

  • Trade Count: (+4)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 1536
  • Last login:March 24, 2014, 08:47:08 pm
  • Shut Off All The Compactors on the Detention Level
    • My HomePage
Re: Mame Compiler 64 v1.20 Released!
« Reply #506 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.

headkaze

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 2943
  • Last login:August 14, 2023, 02:00:48 am
  • 0x2b|~0x2b?
Re: Mame Compiler 64 v1.20 Released!
« Reply #507 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  ;)

nismofun

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 4
  • Last login:January 07, 2011, 10:55:16 am
Re: Mame Compiler 64 v1.20 Released!
« Reply #508 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?

headkaze

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 2943
  • Last login:August 14, 2023, 02:00:48 am
  • 0x2b|~0x2b?
Re: Mame Compiler 64 v1.20 Released!
« Reply #509 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.

john_abey

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 38
  • Last login:September 07, 2011, 03:51:12 pm
Re: Mame Compiler 64 v1.20 Released!
« Reply #510 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.

headkaze

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 2943
  • Last login:August 14, 2023, 02:00:48 am
  • 0x2b|~0x2b?
Re: Mame Compiler 64 v1.20 Released!
« Reply #511 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.

Beretta

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 798
  • Last login:December 20, 2021, 02:11:30 pm
Re: Mame Compiler 64 v1.20 Released!
« Reply #512 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.
« Last Edit: January 21, 2011, 12:18:15 am by Beretta »
Anyone got change for a dollar?
PLEASE HELP NEED Fastmame .70 and .9* releases

Gray_Area

  • -Banned-
  • Trade Count: (+1)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 3363
  • Last login:June 23, 2013, 06:52:30 pm
  • -Banned-
Re: Mame Compiler 64 v1.20 Released!
« Reply #513 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.
-Banned-

Mickelonis

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 40
  • Last login:November 24, 2017, 06:23:25 pm
Re: Mame Compiler 64 v1.20 Released!
« Reply #514 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!

« Last Edit: March 08, 2011, 12:39:07 am by Mickelonis »

TheManuel

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 805
  • Last login:August 07, 2020, 10:15:48 am
  • On and off hobbyist
Re: Mame Compiler 64 v1.20 Released!
« Reply #515 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?
"The Manuel"

TheManuel

  • Trade Count: (0)
  • Full Member
  • ***
  • Offline Offline
  • Posts: 805
  • Last login:August 07, 2020, 10:15:48 am
  • On and off hobbyist
Re: Mame Compiler 64 v1.20 Released!
« Reply #516 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...
"The Manuel"

llaffer

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 7
  • Last login:November 24, 2011, 11:09:40 am
Re: Mame Compiler 64 v1.20 Released!
« Reply #517 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.

jeustaquio

  • Trade Count: (0)
  • Newbie
  • *
  • Offline Offline
  • Posts: 1
  • Last login:October 09, 2011, 04:26:27 pm
Re: Mame Compiler 64 v1.20 Released!
« Reply #518 on: April 29, 2011, 11:26:49 am »
First, thanks for the app.

I compiled the 142 version without problems.

Thanks again.


« Last Edit: May 01, 2011, 09:02:27 am by jeustaquio »

llaffer

  • Trade Count: (0)
  • Jr. Member
  • **
  • Offline Offline
  • Posts: 7
  • Last login:November 24, 2011, 11:09:40 am
Re: Mame Compiler 64 v1.20 Released!
« Reply #519 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.