-
AuthorPosts
-
I manually added the snes9x-next core (https://github.com/libretro/snes9x-next), and then compared it to all the options that are currently offered in RetroPie (experimental and otherwise) and overall I liked it best. Can it be officially added to RetroPie?
The sound in snes9x-next is far more accurate than the other options. The only one that even comes close is catsfc.
(disclaimer: snes9x-next probably wouldn’t run well on the RPi 1, but it runs fine on the RPi 2)
That’s great! can you share please your .so file? thanks
[quote=89231]That’s great! can you share please your .so file? thanks[/quote]
It’s really easy to build yourself. Just do:
export CFLAGS=”-mcpu=cortex-a7 -mfpu=neon-vfpv4″
git clone https://github.com/libretro/snes9x-next.git
cd snes9x-next
make -f Makefile.libretro platform=”armv neon hardfloat” -j4Anonymous
Inactive02/26/2015 at 18:40Post count: 94Are the cores that work with RPi the same as that for Android devices? if so nightly builds can be found here….
Anonymous
Inactive02/26/2015 at 19:29Post count: 94[quote=89294]It’s really easy to build yourself. Just do:
export CFLAGS=”-mcpu=cortex-a7 -mfpu=neon-vfpv4″
git clone https://github.com/libretro/snes9x-next.git
cd snes9x-next
make -f Makefile.libretro platform=”armv neon hardfloat” -j4
[/quote]You do this on the RPi itself then?
Is it the same command for all emulators you want to compile just changing out the url for github?
So if i wanted to add FCEUMM emulator i would use the command…
export CFLAGS=”-mcpu=cortex-a7 -mfpu=neon-vfpv4″
git clone https://github.com/libretro/libretro-fceumm.git
cd FCEUMM
make -f Makefile.libretro platform=”armv neon hardfloat” -j4would that work?
[quote=89309]
<div class=”d4p-bbt-quote-title”>cacophony555 wrote:</div>
<div class=”d4p-bbt-quote-title”>vintagamer wrote:</div>
That’s great! can you share please your .so file? thanksIt’s really easy to build yourself. Just do:
export CFLAGS=”-mcpu=cortex-a7 -mfpu=neon-vfpv4″
git clone https://github.com/libretro/snes9x-next.git
cd snes9x-next
make -f Makefile.libretro platform=”armv neon hardfloat” -j4You do this on the RPi itself then?
Is it the same command for all emulators you want to compile just changing out the url for github?
So if i wanted to add FCEUMM emulator i would use the command…
export CFLAGS=”-mcpu=cortex-a7 -mfpu=neon-vfpv4″
git clone https://github.com/libretro/libretro-fceumm.git
cd FCEUMM
make -f Makefile.libretro platform=”armv neon hardfloat” -j4would that work?
[/quote]Yes, on the pi itself.
The fceumm core is already installed by default (it’s the default nes emulator too if I recall) though nestopia seems to be a bit better IMO.
The above may or may not work for other cores depending on the Makefile of the core you’re trying to bulid. It should be pretty similar though. Some cores don’t build with the “-j4” option, some use a Makefile instead of Makefile.libretro, for example.
Anonymous
Inactive02/26/2015 at 19:37Post count: 94[quote=89311]The above may or may not work for other cores depending on the Makefile of the core you’re trying to bulid. It should be pretty similar though. Some cores don’t build with the “-j4″ option, some use a Makefile instead of Makefile.libretro, for example.
[/quote]How would you know if it uses “-j4” or a Makefile??
Also the FCEUMM is an updated version of that found in Retropie, in this case would it just overwrite the old version?
Anonymous
Inactive02/26/2015 at 20:20Post count: 94Hmm just tried to complie snes9x-next and its seemed to of hanged at…
src/seta.c:678:174 warning: cat to pointer from interger of different size [-Wint-to-pointer-cast]
any ideas?
EDIT: Ok its finished now, just took a long time to complie.
Where is snes9x-next supposed to be placed?, /home/pi/RetroPie-Setup/scriptmodules/emulators ? As i cant see it there. How do i get it to show up in EmulationStation?
[quote=89216]I manually added the snes9x-next core (https://github.com/libretro/snes9x-next), and then compared it to all the options that are currently offered in RetroPie (experimental and otherwise) and overall I liked it best. Can it be officially added to RetroPie?
[/quote]Please create an “enhancement” issue in the RetroPie-Setup repository here.
[quote=89294]
<div class=”d4p-bbt-quote-title”>vintagamer wrote:</div>
That’s great! can you share please your .so file? thanksIt’s really easy to build yourself. Just do:
export CFLAGS=”-mcpu=cortex-a7 -mfpu=neon-vfpv4″
git clone https://github.com/libretro/snes9x-next.git
cd snes9x-next
make -f Makefile.libretro platform=”armv neon hardfloat” -j4
[/quote]Please forgive me, but how would a complete linux noob do this? I can get around the os, but have never compiled anything before.
I really want to play SNES on my Pi, and pisnes just will not work with my PS3 controller and have noticed a few roms don’t play well.
Edit: I should be more specific.. the line [quote]export CFLAGS=”-mcpu=cortex-a7 -mfpu=neon-vfpv4″[/quote] is what I have no idea what to do with.
Thanks, I managed to compile it and manually added to my retropie setup. I’m using a RPi1 so it’s half the speed (around 28-30 fps + choppy audio). As you stated it’s better to use it on a RPi2, snes9x-next it’s one of the most compatible/good performance snes emulators, I still use it on my Wii.
[quote=89345]
<div class=”d4p-bbt-quote-title”>cacophony555 wrote:</div>
I manually added the snes9x-next core (https://github.com/libretro/snes9x-next), and then compared it to all the options that are currently offered in RetroPie (experimental and otherwise) and overall I liked it best. Can it be officially added to RetroPie?Please create an “enhancement” issue in the RetroPie-Setup repository here.
[/quote]Thanks I just added it:
https://github.com/retropie/RetroPie-Setup/issues/695[quote=89322]Hmm just tried to complie snes9x-next and its seemed to of hanged at…
src/seta.c:678:174 warning: cat to pointer from interger of different size [-Wint-to-pointer-cast]
any ideas?
EDIT: Ok its finished now, just took a long time to complie.
Where is snes9x-next supposed to be placed?, /home/pi/RetroPie-Setup/scriptmodules/emulators ? As i cant see it there. How do i get it to show up in EmulationStation?
[/quote]It doesn’t matter where you put the generated .so file as long as you point to the correct location in the es_systems.cfg file. Just find the part that refers to the location of your current snes core (.eg pocketsnes_libretro.so) and replace it with the location of your new core.
Ok, so I think I figured it out somewhat, but why am I getting segmentation faults every time I try to run it after compiling?
[quote=89394]Ok, so I think I figured it out somewhat, but why am I getting segmentation faults every time I try to run it after compiling?[/quote]
You’re using a RPi 2, right? If not then instructions above definitely wouldn’t work.
The 4 lines I gave above are exactly what you need to type to generate the .so file. If trying to use the generated .so is causing a segfault on your RPi 2 then I’m not sure what to suggest.
[quote=89398]
You’re using a RPi 2, right? If not then instructions above definitely wouldn’t work.The 4 lines I gave above are exactly what you need to type to generate the .so file. If trying to use the generated .so is causing a segfault on your RPi 2 then I’m not sure what to suggest.
[/quote]Yep, Rpi2, even using just make by itself without any of your added code ends up with a seg fault.. also a massive list of errors when trying to make.
It’s hard to tell in your code, but those are “quotes” right.. cause they copy/paste weirdly..
[quote=89399]
<div class=”d4p-bbt-quote-title”>cacophony555 wrote:</div>
You’re using a RPi 2, right? If not then instructions above definitely wouldn’t work.The 4 lines I gave above are exactly what you need to type to generate the .so file. If trying to use the generated .so is causing a segfault on your RPi 2 then I’m not sure what to suggest.
Yep, Rpi2, even using just make by itself without any of your added code ends up with a seg fault.. also a massive list of errors when trying to make.
It’s hard to tell in your code, but those are “quotes” right.. cause they copy/paste weirdly..
[/quote]Yeah they’re just normal quote marks. Strange. I would think if there were actual errors you wouldn’t get the generated .so file. Maybe you’re not pointed at the right file?
This is what I get, copy/paste exactly what you wrote, just fixing the quotes. Takes about 8 minutes to finish, then seg faults when I try to run it through emulationstation.
Am I just missing some kind of packages? Using the SD image of RetroPie as instal.
[quote=89405]http://pastebin.com/kg9Hk4WS[/quote]
[quote=89405]
http://pastebin.com/kg9Hk4WSThis is what I get, copy/paste exactly what you wrote, just fixing the quotes. Takes about 8 minutes to finish, then seg faults when I try to run it through emulationstation.
Am I just missing some kind of packages? Using the SD image of RetroPie as instal.
[/quote]Your pastebin helps a lot :)
It looks like it failed to build due to permission issues (despite your sudo). I would try the same commands in your home directory where you definitely have write permissions and you shouldn’t need to use sudo. Then assuming it completes without error use sudo to copy the file to the directory that has the other libretro cores and make sure to point at it properly in es_systems.cfgThis is the key part of the errors:
Assembler messages:
Fatal error: can’t create src/sa1.o: Permission deniedWhen the assembler process was spawned it probably didn’t inherit your sudo.
-
AuthorPosts
- The forum ‘Everything else related to the RetroPie Project’ is closed to new topics and replies.