@mitu Thanks! Definitely gives me something to work with. I will try with something that was easier to build and would have a higher level of interest for Retropie users such as Astromenace or Valyria Tear.

Just to confirm I had email confirmation that the change was merged into master, so post-update I tested again anyway and all works fine. Thanks for sorting this so quickly. Cheers

It has nothing to do with the modules, there's something related to the kernel files copied by rpi-update which breaks the compilation - see https://github.com/raspberrypi/firmware/issues/1364.

personally, if i was doing this i would make a fork in github with my changes, and then edit the retropie build script to point at it, then compile it through retropie - update via source. eg https://github.com/RetroPie/RetroPie-Setup/blob/master/scriptmodules/emulators/mupen64plus.sh#L32 if i made a change to the master branch of my fork of mupen64plus-core, i would this line to 'dankcushions core' note that when you edit retropie scripts the script updater will complain when you come to update it.

@mth75 The patches added by the RetroPie install script work only with the branch/version specified in the script. If you'd like to get the latest dev version, you should also remove the .diff being applied.

@mitu Thank you, works!

@dixeflatline I think you could compile it for armv8a. How much memory does the switch have? You might be able to compile it on the switch.

@littlehui said in emulationstation can not lauche: lima driver only support opengl es. Is this the problem? No, actually is the other way around - Emulationstation needs OpenGL ES for your system to work, but it relies on SDL2 to offer that. If your SDL2 library is not compiled with OpenGL ES support, then it won't work. The RetroPie-Setup script takes care of compiling or installing such SDL2 version (for Raspberry PI at least), I'm not sure your system provided SDL2 library has GL ES support and - also important - accelerated GLES support from the Lima driver.

@mitu Thank you very much for the reply!! The bad thing is that I do not know how to write code ... and I'm not sure where I should write the commit (eaac037a9e331e8b26a77239d8dd96b76f86515e) and with what syntax ... Please, if it is not too much trouble, if I could write the line that I should include in the ir-picodrive.sh and in what position, I compile and see if it works !!! many thanks!!!

Sorry, I thought I did. But that was in another post. That said, compiling on a threadripper 2990WX with -J80 is almost hilarious. :-)

@mitu That just gives me a segmentation fault. If it's too much trouble then I'll just try asking the person that compiled lr-mess successfully and hope that he can share it. The reason I wanted to try is because the person said he could succesfully run neogeo cd chd games. If latest mame can also do this now, I wonder how much work would it be to backport it for the mame2003-plus guys.

Nevermind i figured it out. The guide dosen't it make it noob clear that after you have built your own version you still have to actually move the binary to the appropriate folder but as i said in the end i figured it out :)

@mitu Oh I'm aware it's just a front end, I've tried doing RetroPie for my brother in law as a Christmas gift (which I got working easily enough). And I didn't think to try Github's instructions, I guess I just assumed the main page would work. Tired and ready for bed. Thanks, I'll give it a shot later.

@BuZz Thanks for your help I got it working, I replaced the /opt/retropie/supplementary/emulationstation/emulationstation file with the one that I compiled myself. I hope this post can help someone in the future :)

@madmodder123 I changed the vector images of buttons to symbolic (playstation). I converted them from a raster to a vector in an inscape. In this thread, @jacobfk20 helped me with the compilation, and everything worked.

@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.

@mitu the emulated chroot is created via RetroPie-Setup. See admin/image module. It's created from raspbian lite image, so it's identical to a real install which is good for catching problems and dependency issues. It's used for building the images too which uses qemu again on a pc.