> > > I'd still consider it one of the biggest threats we've seen to proper emulation > in > > a > > > long time. > > > > The problem is nobody from the MAME Dev Team gonna release a MAME Android. Others > > still building their ports in a shitty way. You guys can come up one better than > > those shitty ones out there. There is no reason not to finish the source up for the > > MAME Android. The source is there. But not finish. > > > > Don't want to continue working on it? That fine with me. Just gonna use the shitty > > ones for now. (Not pointing at you Haze. The ones that was working on that source.) > > > It isn't for lack of desire - it is lack of qualified people and development of some > sort of usable touchscreen interface that is phone/tablet based that will get things > done. You can run MAME fine, people can and do compile for Android every release, but > it would require you to have some sort of external keyboard/controller in order to > use well which isn't an idea setup for an mobile device. > > Until MAME can find something that does the job and is within licensing restrictions > - it won't be an officially distributed platform. > > These views are mine alone and may or may not reflect official views of MAMEDEV.
You are right about that. But I did compile MAME Android with the older tools. MAME Android wouldn't load up. I tried all of those. I tried the newer tools and it missing some stuff for the compiling. Unless I need to download the missing parts for the newer tools. I been told not to run the pacman commands on the newer tools. That might be why the compiling won't work right. I never again mess with the compiling after that.
Index 
Flat 
Re: Mess with the RetroArch + MAME 0.187 last night.
Reply
Slamming the MAME 0.188 released at theiir face.
