compiling takes long???

jonnykesh

@alturis It's usually best to quit out of ES when compiling anything from source. Just so it isn't running in the background and using resources.
However Mame2016 does take a very, very long time to compile. I have a decent enough fibre connection and it took me over 3 hours iirc. But it's not really about how quickly it can be downloaded obviously, it's how quick the Pi can build it.
And the Pi is a very low powered device.

Just as an edit, I always update from the command line and not from within ES.
Just run cd RetroPie-Setup && sudo ./retropie_setup.shfrom the terminal.

gomisensei

@alturis said in compiling takes long???:

Running on a Pi3 here and experiencing similar issues. I am currently trying to install Mame2016 from sources and its been going for a couple hours already I think. (not sure I didnt look at the time when I started it) I have installed other things from source and it has never taken anywhere near this long.

Running top from putty and there are only really 2 processes taking up any significant amount of CPU and thats 2 instances of cclplus.

I was doing this from emulationstation -> RPSetup so wondering if I should have fully quit emulationstation first. But I dont see it showing up in the top list either.

MAME is the toughest, you need lots of memory, and current to your power supply. You will first need to go do "raspi-config" from Retropie menu, or from command prompt. In advanced settings of raspi-config, memory split is probably 256, lower it to 16 temporarily, and you should have enough ram for compile (don't forget to reboot, you may need to exit emulationstation and enter "cd RetroPie-Setup && sudo ./retropie_setup.sh" at the command prompt) . The power problem requires a power block or source that can put out at least 2A, or 2000 mA. Don't forget to run raspi-config again and set your memory split back to where it was before after your install completes.

dankcushions

yeah, consider that mame is essentially an emulator for 100s of systems, when, for example, a snes9x is an emulator of one. the mame source code is HUGE, and the pi is an incredibly weak computer.

even ancient mame2003 takes about 40 minutes to compile.

jonnykesh

@dankcushions
We need a

MAME IS DIFFERENT

tag.

Alturis

Ill keep that in mind the next time. It finished up finally.

jonnykesh

It's finished, cool. There's not a lot that will actually run on it. It's too resource intensive for a Pi.
MAME, later mames at least do not give a shit about stuff playing on a Pi.
They are all about high-end PC emulation these days as far as I can see. In fact they look down their noses at people who use Pis and RetroArch in general.

herb_fargus

@jonnykesh said in compiling takes long???:

They are all about high-end PC emulation these days

Not so much high end PC emulation so much as accuracy of emulation which as a side effect requires heftier PC's.

jonnykesh

@herb_fargus I think we re saying the same thing, just in different ways.
I have seen the MAME and Emulationsub-reddits.
They are not fans of this project and MAMEHaze hates RetroArch (and this project by default).

gomisensei

@jonnykesh said in compiling takes long???:

@herb_fargus I think we re saying the same thing, just in different ways.
I have seen the MAME and Emulationsub-reddits.
They are not fans of this project and MAMEHaze hates RetroArch (and this project by default).

That's because retroarch (and this project) are about playing the games, which is morally ambiguous at best, and despite best efforts, piracy at worst.

jonnykesh

@gomisensei I'll make no judgement against the "MAME Project". I respect their intention and their end goal.

Now, saying that. The attitude of some of the people involved...
Hmmm, I thought, naively, that we all cared about the same thing. No. Not at all.