Home Page Forums MAME MAME Raspberry pie mame

Is raspberry pie mame available? Is it the Linux version does it just detect the arm processor and gpu?
Are there any development tools for mame? I would like to be able to grab sprite and background graphics and disassemble the code please
Here's a video of plusd hacker it let's you look at graphics in the ram of a sinclair zx spectrum - speaking of which does the sam coupe support allow atom lite and trinity ethernet and 1mb -4mb external ram she runs codecat 2 4 times zx spectrum speed see snaper disks velesoft website....

I'm regularly building MAME for a subset of drivers for Raspberry Pi (the TI-99 family). Do you want to build it on your Pi? Then you should have 4 GiB of RAM (better 8 GiB) and at least a Pi 4. Maybe you can take this as a guideline for your build: https://www.ninermame.org/setup/building/raspibuild

There are pi compiles of mame updated on a regular basis there: https://stickfreaks.com/mame/

You’re better off cross-compiling on a Linux PC, see the stuff here: https://github.com/danmons/mame_raspberrypi_cross_compile

As for the Sam Coupe: The Atom IDE interface (not Atom Lite) and external RAM is supported. The Trinity ethernet interface isn't.

If you don't want to cross-compile then a mac with apple-silicon cpu (m1,m2 etc) can do the job too.
Just install a linux distribution in VMware or UTM and compile it in there.

You might find this interesting too :
https://retropie.org.uk/forum/topic...-for-lr-mess-lr-mame-and-mame-standalone

Anything facilitating the hacked-up RetroArch cores won’t do you any favours here.

For curiosity, I just compiled the latest MAME (complete) on a Raspi5 with 8 GiB RAM; took 10004 secs with 4 jobs (gcc). Normally, I run the compile for a small selection of drivers (less than 2000 secs).

By the way, just if someone cares, after building on Raspberry Pi OS, I find lots of "*.a" files in the source tree, instead of in the build subtree.

Last time that I looked into the makefiles, it seemed to me as if there is an issue with setting up the build subtree; in particular there are only "build/generated" and "build/projects", but no "build/<platform>" (like build/linux_gcc).