[solved][noob] raspberrypi 4 - compile from source - raspbian

RetroArch Linux devices
#1

guys, I have setup my mum with retroarch on her raspberrypi 4 running raspbian

i followed (mainly) this guide guide on github

which is where i ended after searching on the raspberrypi site raspberrypi forum

retroarch is fine with only one minor glitch: i have no audio i tried setting the device as per the output from aplay -L (both in the GUI and editing retroarch.cfg) but i cannot get any audio at all (i know the audio is fine since it works in other applications…)

at this point im thinking that i might have messed up the ./configure part of the compilation i am not sure 100% of the cflags that i used (i know… very silly…) so i have some questions, mainly because it is the first time i compile something important from source:

  1. is there any command that i can run to find out what settings i used for compilation? so that i can backtrack my steps… i believe this might be my configs:
CFLAGS="-mfpu=neon" ./configure --enable-alsa --enable-udev --enable-neon --disable-videocore --disable-opengl1

  1. if i disintall retroarch, re-run the compilation in the same folder but with a different set of configs and re-install, should i expect that i will have to run though the initial setup of retroarch or the existing settings will be kept ? (i will make a copy anyway :wink: i am trying to learn from my mistakes… )

  2. following the guide i installed retroarch 1.7.7, this is mainly because it is the latest i could find when i started this project. Maybe installing 1.8.4 would help, i can try to do that, does anyone has any recommendation/suggestion to share?

thanks a lot M

#2

running ‘retroarch --features’ won’t tell you what configure flags you used, but it will tell you which drivers/functions are available.

If you keep your ~/.config/retroarch directory intact, it should be fine. Most things live in your retroarch.cfg.

I would suggest trying the snap package, which has ARM binaries available.

#3

@ huntertk, thanks for the feedback

“retroarch --features” gives me the following

i understand very little but the usual suspects seem there: i see alsa, oss, pulse

is it possible i have messed it up somewhere else?..but maybe not with the cflags…

thanks a lot

Features:
  LibretroDB:
		LibretroDB support: yes
  Command:
		Command interface support: yes
  Network Command:
		Network Command interface support: yes
  SDL:
		SDL input/audio/video drivers: no
  SDL2:
		SDL2 input/audio/video drivers: yes
  X11:
		X11 input/video drivers: yes
  wayland:
		Wayland input/video drivers: yes
  Threads:
		Threading support: yes
  Vulkan:
		Vulkan video driver: no
  Metal:
		Metal video driver: no
  OpenGL:
		OpenGL   video driver support: yes
  OpenGL ES:
		OpenGLES video driver support: no
  XVideo:
		Video driver: yes
  UDEV:
		UDEV/EVDEV input driver support: yes
  EGL:
		Video context driver: yes
  KMS:
		Video context driver: no
  OpenVG:
		Video context driver: no
  CoreAudio:
		Audio driver: no
  CoreAudioV3:
		Audio driver: no
  ALSA:
		Audio driver: yes
  OSS:
		Audio driver: yes
  Jack:
		Audio driver: no
  RSound:
		Audio driver: no
  RoarAudio:
		Audio driver: no
  PulseAudio:
		Audio driver: yes
  DirectSound:
		Audio driver: no
  WASAPI:
		Audio driver: no
  XAudio2:
		Audio driver: no
  OpenAL:
		Audio driver: no
  OpenSL:
		Audio driver: no
  7zip:
		7zip extraction support: yes
  zlib:
		.zip extraction support: yes
  External:
		External filter and plugin support: yes
  Cg:
		Fragment/vertex shader driver: no
  GLSL:
		Fragment/vertex shader driver: yes
  HLSL:
		Fragment/vertex shader driver: yes
  SDL_image:
		SDL_image image loading: no
  rpng:
		PNG image loading/encoding: yes
  rjpeg:
		JPEG image loading: yes
  Dynamic:
		Dynamic run-time loading of libretro library: yes
  FFmpeg:
		On-the-fly recording of gameplay with libavcodec: no
  FreeType:
		TTF font rendering driver: yes
  CoreText:
		TTF font rendering driver (for OSX and/or iOS): no
  Netplay:
		Peer-to-peer netplay: yes
  Python:
		Script support in shaders: no
  Libusb:
		Libusb support: yes
  Cocoa:
		Cocoa UI companion support (for OSX and/or iOS): no
  Qt:
		Qt UI companion support: no
  Video4Linux2:
		Camera driver: no
#4

i probably made some typo, i edited again the retroarch.cfg adding the info from aplay -L and now we have sound sound is a bit crackly, but i guess it can be configured and optimised…i will look for some optimisation…

i know it sounds silly, but i wanted to say thanks and mark this as solved

thank you all M

1 Like