Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Raspberry Pi Build please #5

Open
sionisaac opened this issue Jun 7, 2022 · 7 comments · Fixed by libretro/libretro-super#1665
Open

Raspberry Pi Build please #5

sionisaac opened this issue Jun 7, 2022 · 7 comments · Fixed by libretro/libretro-super#1665

Comments

@sionisaac
Copy link

Can this core be built for Raspberry Pi specifically retropie? I keep checking the nightly section but still now core updates for armhf.

@emptyinside666
Copy link

Same. Since argument "-m32" is disabled it keeps throwing a PTR64 flag error eventhough I set PTR64 ?= 0 at the top of the Makefile.libretro. This works amazing on my PC but getting Mess to run CDI on RPi4 is frustating to say the least.

@sionisaac
Copy link
Author

I've got mame and mess working on my raspberry pi 400 and pi zero 2. I can run CDI games with mame and advanced mess. Having a standalone core would make setup less tedious.

@zach-morris
Copy link
Owner

I think this is out my league. Looking at other cores, I don't see any specific recipes for armhf that I can copy. This issue probably belongs in https://github.com/libretro/libretro-super

zach-morris added a commit to zach-morris/libretro-super that referenced this issue Aug 3, 2022
Add same_cdi to armhf.  Note that I have not tested this as I don't know how.  However I've just copied the recipe for mame to same_cdi, they use pretty much the same makefile so it should in theory work.
Fixes zach-morris/same_cdi#5
@sionisaac
Copy link
Author

This sounds promising. Can you link to rpi compatible core if and when it goes live.

@zoltanvb
Copy link

zoltanvb commented Aug 6, 2022

Disclaimer: I am no libretro infrastructure maintainer, just someone who has spent some effort recently around this topic.

The armhf (and armv7-neon-hf) nightly builds are now not operational, images in there are close to 2 years old and new ones are not being built. So it won't appear there.
The nightly builds are not controlled by the recipes any more, instead by the .gitlab-ci.yml files, but there are no suitable rules for armhf (or aarch64) to add. at least not yet. So the best bet is still manual compilation.

@sionisaac
Copy link
Author

Can anyone give instructions on how to build this core on a rpi 3 or 4?

@zach-morris
Copy link
Owner

zach-morris commented Aug 16, 2022

I was able to compile on an RPi2 (32 bit, I unfortunately dont have a 3 or 4 so couldn't test 64 bit), using these instructions as a guide. 64 bit should be pretty much the same though. I have no idea how well this will actually run.

Requirements:

  • Typical build stuff like make, gcc, git, etc
  • Python > 3.5. I used:
>>python --version
Python 3.7.3
  • Increase your swapfile size on the RPi, since compiling this requires RAM that the RPi doesn't have. Use the instructions at the link above. Reboot after the change.

Steps:

  1. Build and install SDL2 first, using these instructions, or the helpful script from here. After install you should be able to:
>>sdl2-config --version
2.0.15
  1. Get the same_cdi code:
cd ~/Documents/code (or wherever you want to put the source)
git clone https://github.com/libretro/same_cdi.git
cd same_cdi
  1. Make (warning, this takes a looooong time, i just let it go overnight):
make -f Makefile.libretro PTR64=0

Thats it. If you wanted to do this for 64bit Raspian, the steps would be the same, except:

make -f Makefile.libretro PTR64=1

Attached is the 32 bit armhf compiled version.
same_cdi_libretro.zip

I would think this might be easier to request be added to Retropie or whatever flavor you're using, since they've probably got some cross-compiling build system already setup to handle this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants