Once again, I've revised the build instructions for SDLMAME on Mac OS X.

As always, if you spot any glaring errors/omissions/outright lies, please let me know.

Also, if anyone would be interested in reposting this on their site. please let me know that as well...

----------

Building SDLMAME for Mac OS X - A Guide

Welcome to the world of SDLMAME. If you've built SDLMAME for Mac OS X in the past, you'll notice that since version 0.136u1, the build procedures have changed.

If you're new to building (compiling) SDLMAME on Mac OS X, with any luck, you'll find it's not as difficult as you might think.

Either way, Don't Panic! This guide will (hopefully) get you up and running in fairly short order.

Let's get started...

Step 0 - Preliminary Steps - (These need be done only once, with the occasional periodic updates) -

0a) Run Software Update
Your Operating System, and supporting files should be updated prior to compiling SDLMAME (and should be kept up to date regardless) The minimum supported OS for SDLMAME under Mac OS X is 10.4.x (Tiger).

0b) Install/Update Xcode
Xcode is a free developer environment from Apple, and although it will be used to compile SDLMAME, you will not be required to learn how to run it.
It will need to be installed prior to compiling SDLMAME. As of this writing (2/10) the current version of Xcode is 3.1.x (for Mac OS X 10.5.x (Leopard)), and 3.2.x (for Mac OS X 10.6.x (Snow Leopard)), The minimum supported version of Xcode is 2.5 (for Mac OS X 10.4.x (Tiger)).
Xcode is free from Apple, either as part of your original install discs (or retail copy of OS X) or as a free download from http://developer.apple.com/
(Note - Software Update *Does Not* update Xcode, so it's a good idea to check Apple's developer site periodically for updates.)

0c) Install/Update SDL
Simple DirectMedia Layer (SDL) is a cross-platform multimedia library designed to provide low level access to audio, keyboard, mouse, joystick, 3D hardware via OpenGL, and 2D video framebuffer. It is used by MPEG playback software, emulators, and many popular games, including the award winning Linux port of "Civilization: Call To Power."
Go to http://www.libsdl.org/ , and click the "SDL 1.2" download link in the sidebar, then scroll down to "Mac OS X" under "Runtime Libraries". Download the "SDL-1.2.15.dmg" disk image and open it.
Click 'Macintosh HD' (or whatever your Mac's hard disk is named) in the left pane of a Finder window, then open the Library folder and drag the SDL.framework folder from the SDL disk image into the 'Frameworks' folder.

Step 0 Recap -
- Run Software Update
- Install/Update Xcode
- Install/Update SDL

=====

Step 1 - Gather files

1a) Create folder for build files
While not an absolute necessity, keeping various SDLMAME project files in a separate folder will help to avoid confusion while building. For purposes of this exercise, the folder will be called 'MAME Parts'

1b) Get 'Endings' script
Go to http://rbelmont.mameworld.info/?p=527 and download the 'Endings' file (endings.zip). Place this file in the 'MAME Parts' folder.

1c) Get Baseline MAME source
Go to http://mamedev.org/release.html and download the MAME source file (in zip format). Place this file in the 'MAME Parts' folder.

1d) Get update patch files
Go to http://mamedev.org/updates.html and download any of the diff files you do not already have. Place these files in the 'MAME Parts' folder

1e) Unzip, and place files
Go to the 'MAME Parts' folder. Unzip all the files you downloaded. Do not throw away the original zip files, as you may need them again in the future during the development cycle.
Place the endings file, and all patch files into the MAME Source folder.

Step 1 Recap -
- Create folder for build files
- Get 'Endings' script
- Get Baseline MAME source
- Get update patch files
- Unzip, and place files

=====

Step 2 - Prepare for building

2a) Launch Terminal, and set path
Open the Terminal (Applications->Utilities->Terminal). Type 'cd ' (that's cd, and a space), and drag the MAME Source folder to the Terminal window. Hit 'Return'. This sets the path for the subsequent commands.

2b) Run 'Endings'
Type the following line into the Terminal window (or copy and paste, if you prefer) -

./endings

Hit return. Wait for the prompt (This may take a while, and it may appear that nothing is happening... Be patient).

2c) Patch files
This is the variable part of the process, as each 'u' update patch needs to be applied in order to the source.

Type the following into the Terminal window -

patch -p0 <xxxxxxxx (that's [patch], [space], -p[zero], [space], <[diff file name])

Where 'xxxxxxxx' equals the name of the diff file you wish to apply. Hit Return, and wait for the prompt.

Repeat for each diff file in order (u1, u2, u3, etc.)

2d) Check the SDLMAME forums for last minute changes
Before proceeding to the next step, check for any last minute changes/fixex/modifications at the SDLMAME forum at http://www.bannister.org/forums/

Step 2 Recap -
- Launch Terminal, and set path
- Run 'Endings'
- Patch files
- Check the SDLMAME forums for last minute changes

=====

Step 3 - Build

3a) Build
Type the following into the Terminal window -

make

-OR-

make -j3 (for dual core processors)

-OR-

make -j5 (for quad core processors)


Hit Return. SDLMAME will auto detect your CPU type (PPC or Intel), and your system type (32 bit or 64 bit), and build accordingly.

3b) Build Tools
As an option, you can build the optional tools that accompany SDLMAME (chdman, and the like) by typing the following into the Terminal window -

make tools

Hit return.

3c) Enjoy!
Congratulations! You've successfully built SDLMAME on Mac OS X!
You may want to rename the Source folder to reflect the version of SDLMAME you just built.
Attach your favorite front end application, and have fun!

Step 3 Recap -
- Build
- Build Tools
- Enjoy!

=====

Future Builds

Provided no modifications were made to the source prior to building, the next patch may simply be applied to the previous build, and the application built again (you can skip step 2b).

If, however, modifications were made to the source prior to building, it is advisable to start with fresh copies of the source, and all the diff files in order (the latest diff file will usually contain fixes for the previous versions).
If you kept the files from steps 1b, c, and,d, just proceed from step 1d.

=====

Troubleshooting FAQ

- I'm told I need to edit a file in Xcode. How do I do this?
Locate the file to be modified, and double click it. Xcode will open the file.
Chances are good that you were told what line of the code to modify. Under the 'Edit' menu, select 'Go to Line...'. Enter the line number, and click the 'Select' button. Make your modification(s), Save the change(s), and quit Xcode.

- I got an error while building. What do I do?
Check the SDLMAME forums at http://www.bannister.org/forums/ to see if this is a known problem, and if there is a fix available. If not, post a question, and someone will try to help you.
You may also want to try starting over at step 1, especially if you were patching an existing build.

- I got an error while patching the source. What do I do?
Start over from step 1, especially if you're patching an existing build. if you continue to have problems, you may be able to get help at the SDLMAME forums at http://www.bannister.org/forums/

- I had to make a modification of some sort prior to building. Will I have to make this modification again in the next version?
No. However, you may need to start over again with the original source, and latest diff files.

- Is there an easier way to do all this?
If you prefer not to build yourself, prebuilt versions of SDLMAME for Mac OS X are available for download at http://sdlmame.parodius.com/

- I've successfully built SDLMAME in Mac OS X... Now what?
That's a whole 'nother document...

Thanks. I'll sticky this

BTW, r0ni's still making canned Mac Universal binaries, so if you really would rather not compile, go here.

Unfortunately Tiger users are left out there and still have to roll their own..

Just curious RB, do you know why r0ni includes the endings script with his binaries??
I was thinking of making my 136u2 I just compiled the other day for 10.4 available somewhere or other.. Do I need to give folks the endings script too for whatever reason??

Tiger's not supported by SDL 1.2.14 so it's no longer officially supported by SDLMAME either. (We won't actively try to break it of course).

No idea why r0ni includes the "endings" script, probably an oversight.

Did I miss something in the SDL documentation?

As far as I can tell, the minimum System requirement for SDL 1.2.14 is still 10.4.x (Tiger)

Perchance did you mean to say that SDL 1.2.14 is not supported by 10.3.x (Panther)?

Ive been compiling Exult with 1.2.14 since it came out and havent run into any trouble yet. Although its got some bugs of its own that wreak havoc when you play Exult in full screen but other then that no problem..

From what I saw on the SDL list, Tiger is missing an API they needed so it's possible with a sufficiently smart ld.so that not all SDL apps will trigger the fatal death on Tiger.

Guess its time to start looking for a used Intel Mac or G5 hehe.
I had Leopard on it up until last summer but it was just too much of a dog so I went back.
Logic Pro went from being able to play a 20 track song to crawling with 10 tracks so it had to go hehe...

Although with that said, u3 compiled fine yesterday. Crossing my fingers all is still well! Hopefully I can keep up for awhile. MAME OS X was always a fave but I like actually staying current with things hehehe..

I do try to do what I can for PowerPCs - Run and Gun has proper graphics on 'em in u3 (should be fast enough for PS3 peeps like billb too).

actually, on my macbook pro with Snow Leopard, MAME builds 32-bit even if the OS supports 64-bit apps. hence, I had to add PTR64=1. is this expected? or is the identification process at fault (and if this is the case, can I help to fix it?)

Means you're running a 32-bit kernel. OS X is weird in that it can run 64-bit apps on a 32-bit kernel in some cases. The autodetect on Macs only builds 64 bit if you boot the system 64-bit.

according to this article

http://www.macworld.com/article/142379/2009/08/snow_leopard_64_bit.html

Snow Leopard is fully capable of running 64bit apps, but the OS uses a 32bit kernel because current hw does not need a 64bit kernel. part of it might as well be true, but I don't currently really care: the important part is the full 64bit capability. hence, I will be able to play n64 at 50% of speed with no frameskip :P

back to the autodetect point, there is no problem if I have to add a PTR64=1, but I would suggest to update the original instructions with a paragraph about Snow Leopard 32bit users because the speed gain with a 64bit compile might be appreciated

The real bottom line is that unless you're running a rare handcrafted 3rd party kernel driver for something and/or don't have a Core 2 Duo CPU, you should just reboot with 6-4 held down or whatever the appropriate magic is and then the autodetect will kick in fine.

I will not change the instructions. Always ending up with a safe working executable is my first priority, especially for Mac users.

The autodetect could determine if there is a 64-bit EFI installed:

http://www.ihackintosh.com/2009/08/snow-leopard-106-and-64-bit-what-you-need-to-know/

But it's not a big issue... although that link could be useful for anyone that wants to always boot into a 64-bit kernel.

I do? That's definitely a oversight, I have a script I use to build them and package them up, I prob need to do some work on it still, as I haven't changed it since sdlmame merged into baseline. I'll take a look at it.

And I can't support Tiger as I no longer have a PPC Mac. I don't think there is a legit Intel 10.4 disk out there, I could be wrong though.

I'm new to the MAC and still testing out. Are these instructions still valid for XCode 4?

Is there a chance to achieve the same using GCC et al.?

XCode seems awfully big and I would like to keep the clutter down, don't need all the iOS developer stuff and such.

The instructions are still valid, yes.

XCode includes "GCC et al" - it's the easiest way to get it on the Mac. It's equivalent to installing the "development" package group on Linux distros.

Thanks, I'll see how it goes.

I was wondering about the XCode tools since it's 4GB and includes SDK, iOS emulators, etc. But I guess it's the best to go with the standard tools.

You can skip the iOS stuff when you install XCode.

Hey guys long time no see.. Just last week I replaced my ancient dinosaur dual G4 with a dual core G5 to keep my music up and running..

Just getting ready to build a new SDLMAME 142u2 (last one I have was 0.139 and it doesnt work on my G5 after copying over) and have a question about the cpu types..

Now I know it will correctly detect PPC and whatnot, but since my machine is a dual-core and not a regular old dual cpu Mac like before can I (or do I even need to) use the 'make -j3' command or is this an Intel only switch??

-j3 is all purpose - it gets you faster builds on anything with dual cores or dual CPUs or whatever.

Well it built fine and MAME+Gui is working again but now..

I just set all my paths up in M+GUI, and told it to Audit all my roms and its giving me this error:

"While parsing /Volumes/Storage/MAME/ini/mame.ini:
Illegal integer value for numprocessors: "auto"; reverting to auto"

Is this possibly related to the -j3 flag?? I was about to go rebuild it again just using plain old make but figured I would ask first..

Gotta love the G5 compared to my G4.. The initial build of the game list took a couple of minutes if even that. On my old dual 1.6 G4 I would get up and go run errands while waiting for it to finish that first process haha.

it's not related to -j3. try to remove the numprocessors line from mame.ini.

Somehow it just started working right the other day hehe.
Ran my audit, and then found out Im missing like 7gb of ROMs (which is due to PinMAME roms becoming part of the new 'standard' MAME set)..

I ran into some errors compiling 0.142u3 so for now, Im back at just 0.142 until I can get my rom set properly rebuilt.. It hasnt been updated since 0.138 so Ive missed a bunch of changes since last summer..

Would you mind listing what the errors you're having with u3 are?

Ill have to rebuild it again, I shouldve wrote it down but just cleaned out my dev folder and went back to 0.142 so I could play catch up with my rom sets.
Ill see if I can get a moment to do it this afternoon.
After a hard drive freeze up a couple weeks ago, I just picked up a spindle of DVD-R's so Im wasting my weekend backing up all 500GB of crap on it (my MAME Roms included) before it dies again hehehe..

Ok just got around to it.. Now that were up to u4 I still went ahead and tried to run u3 just for the sake of doing it..

u3 stops with this error:

typeinfo for driver_device_config<driver_device>in sega.a(segamsys.o)
ld: symbol(s) not found
collect2: ld returned 1 exit status
make: *** [mame] Error 1


After that I did a make clean, and patched u4.
Now u4 is ending with this error:

Compiling src/mame/drivers/suprloco.c...
Compiling src/mame/video/suprloco.c...
cc1plus: warnings being treated as errors
src/mame/video/stvvdp2.c: In function ‘void saturn_vdp2_regs_w(address_space*, offs_t, UINT32, UINT32)’:
src/mame/video/stvvdp2.c:5491: warning: ‘vert_res’ may be used uninitialized in this function
src/mame/video/stvvdp2.c:5491: warning: ‘horz_res’ may be used uninitialized in this function
make: *** [obj/sdl/mame/mame/video/stvvdp2.o] Error 1
make: *** Waiting for unfinished jobs....

Everything up to and including u2 worked just perfect.. So it looks like Im at baseline 0.142 til I can figure it out hehe..

Ok that covered that error..
Got a little farther and hit this:


Compiling src/emu/cpu/i386/i386.c...
cc1plus: warnings being treated as errors
src/emu/cpu/i86/instr286.c: In function ‘void i80286_switch_task(i80286_state*, UINT16, int)’:
src/emu/cpu/i86/instr286.c:215: warning: statement has no effect
src/emu/cpu/i86/instr286.c:216: warning: statement has no effect
src/emu/cpu/i86/instr286.c:225: warning: statement has no effect
src/emu/cpu/i86/instr286.c:274: warning: statement has no effect
src/emu/cpu/i86/instr286.c:275: warning: statement has no effect
src/emu/cpu/i86/instr286.c:281: warning: statement has no effect
src/emu/cpu/i86/instr286.c: In function ‘void i80286_0fpre(i80286_state*)’:
src/emu/cpu/i86/instr286.c:508: warning: statement has no effect
src/emu/cpu/i86/instr286.c:528: warning: statement has no effect
make: *** [obj/sdl/mame/emu/cpu/i86/i286.o] Error 1
make: *** Waiting for unfinished jobs....

I'm a newbie to using Terminal and building, so I have likely made a complete boneheaded mistake. I followed the build instructions for SDLMAME on Mac OS X but I get an error of sdlvideo_init: initialization failed! This happens with the MAME Tunes and MamePGUI front ends.

I had used MAME Tunes with SDLMAME0130-x86 before, but didn't like the faint vector lines on games like Asteroids. I didn't use Terminal to build that one, but I'm wondering if there is some file left over from that usage that is causing the error that I'm having now?

iMac 24" 2.8 GHz Intel Core 2 Duo, 4GB SDRAM, NVIDIA GeForce 8800

What version of OS X? "sdlvideo_init: initialization failed!" is currently a known incompatibility with 10.7 Lion in full-screen mode. You can play in windowed mode while we wait for the SDL guys to cough up a fix.

I'm running Lion, so I guess that's the reason for the problem.

What is windowed mode?

Many thanks for the reply.

It's the opposite of full-screen mode, that is it will use a window as its display surface (including window decorations). Start MAME with the option "-window" (or set "window 1" in mame.ini).

The default is "-nowindow" which means full-screen (or "window 0" in mame.ini).

I see. But don't forget that I'm a complete newbie at this. Is there a thread on how to run MAME from Terminal like that?

"Start MAME with the option "-window" (or set "window 1" in mame.ini)" <-- I wouldn't know where to begin with this. I'm used to MacMAME and MAME OS X. I did manage to get MAME_Tunes going with SDLMAME 0130, which I'm presuming was already "built" since I didn't use Terminal, but the vector line games were very dim on the screen.

I appreciate your help and patience. I was 15 when PacMan hit the arcades, and it was glorious

Well, that's a bit off-topic now... I suggest you open a new thread (instead of using this sticky one which is meant for build instructions on Mac OS X).

Anyway, the -window option is just a command line argument. You were able to start MAME before (on the command line, I suppose), so just add -window on the command line .

If you want to use a front-end instead, well, there are some alternatives... besides MAME_Tunes and others there's QMC2 (the one I wrote) for instance.

I appreciate the advice and heads-up on QM2. I will try to search for newbie threads instead of being off-topic on this one. I wouldn't know where to start to launch MAME from Terminal.

You can do it in MacMAMEinfoX - go to Preferences, then click "Options" button, select the "Video 2" tab, and then choose between "Full Screen" and "Windowed" with the radio buttons.

0.143u8 seems to have a problem (at least) on Mac OS X.



is this known?, 0.143u7 compiled cleanly.

The thread that was on top of this forum until you posted here contains a workaround for that issue. Please read before writing next time.

Thanks and sorry, I usually do, just didn't realize that specific thread was discussing the same problem I had.

It seems this hasn't been fixed yet, right?, tried with last full release (0.145)

I upgraded to lion a couple of weeks ago and was still using a mame binary compiled under snow leopard, and with this binary I don't get this error when I execute it in lion. So it doesn't seem to be lion or the source code by themselves, but how it's compiled under lion. Am I right about this?, is it a problem with the newest Xcode?

ok I'm stuck on step 3 when I type "make -j3" it tells me command not found. what am I doing wrong? where should terminal be? mame source folder?

francisohs: Fullscreen on Lion needs the new SDL 1.2.15. Go to http://www.libsdl.org/ and install the new package.

dasaint80: That error indicates you haven't installed Xcode.

On OSX Lion I had to install Xcode and then from inside Xcode install the additional "Command line tools" package (Preferences -> Downloads) to get things working for me.

Ahh, didn't know that was separate now. I'll update the instructions.