RetroArch for SailfishOS 4.5

Applications
#1

I’ve backported RetroArch for SailfishOS 4.5
It is available at: Release release-20240113173734 · smokku/RetroArch · GitHub

First thing to do after installation is to go to:
Online updater / Update assets
It will download assets required to properly render the User Interface.
Then update the basic information files. The rest is not necessary (but recommended).
Then the Emulation core download should work.

The cores are extracted from Lakka-RPi3.aarch64-4.3.
Unfortunately SailfishOS has very old GCC 8 with old libstdc++ library incompatible with cores using C++, so I removed these.

In order to be able to play using touch screen, you need to enable controller overlay.
Download overlays using online updater.
Go to: Settings / User interface / On Screen Display / Screen Overlay
Enable overlay and select an overlay from gamepads/ directory.

I tried configuring the Assistant button to open the core menu (default binding F1), but failed to do so.
It should be possible when using udev keyboard driver according to Xperia 10 III support - #173 by remote

Warning:
DO NOT CLOSE THE EMULATOR USING TOUCH GESTURE / CLOSE ICON!
Always use the “Close RetroArch” menu item.
Closing the app using gesture will keep the emulator in background and eat your battery.

Known issues:

  • app stays in background
  • sometimes crashes when reinitializing Wayland window (I probably messed up something when restoring wl_shell support)
  • landscape mode - This is not supported by RetroArch. RetroArch assumes the OS does the screen rotation (either on the system framebuffer or XRandr)

RetroArch-UserInterface
RetroArch-UserInterface686×1600 103 KB
RetroArch-CastlevaniaX
RetroArch-CastlevaniaX686×1600 204 KB
RetroArch-Tekken3
RetroArch-Tekken3686×1600 70.7 KB

27 Likes
Sailfish Community News, 18th January - Community Event
#2

Much appreciated thanks :+1:
EDIT: updating the database makes the app crashes on 10 III :frowning:

#3

There is some issue with the way Wayland surface is re-created and it crashes.
Just re-run and it will be working fine.

#4

I’m trying to setup an automated build via OBS, but I have difficulty configuring the build to use pkg/sailfishos/retroarch-sailfishos.spec as the SPEC file. By default OBS expects it in SPEC directory.

https://build.sailfishos.org/package/show/home:smoku/retroarch

Does anyone know how to configure it?

#5

Is there BT gamepad support?

#6

BT gamepad should work if it is a BT-HID device.
These should work when you switch to udev input driver.

#7

Is it possible for this app to have a more SFOS looking UI?

#8

You can go to Settings » Drivers » Menu and change some settings.

#9

The spec file must be in the rpm subdirectory if you are using a tar_git service file.

#10

Oh well… I guess I will then build and release it manually.

#11

Can’t you just move the spec?

Another way would be to have a “packaging repository” with this structure:

retroarch-packaging/
    .git
    .gitmodules
    upstream/
    rpm/retrarch.spec

where the “upstream” dir is a git submodule pointing to your fork. You then give this repo’s URL to the _service file.

(note that with this structure, you need an rpm setup line like this: %setup -q -n %{name}-%{version}/upstream so that the OBS builder can find the right source tree.

1 Like
#12

One question: if I build a core .so myself, where on the system should I install it so your package will find it?

Background is: I have a native build for dosbox_pure but haven’t been able to test it.

I was thinking about using /usr/share/retroarch/cores/ would that be ok?

#13

Would you consider to publish this native build?

#14

Sure. you can monitor this space:

https://build.sailfishos.org/project/show/home:nephros:devel:games:retroarch

But none of the stuff is currently tested. I haven’t even installed the build results, focussing on packaging at the moment…

Once it’s done I can either push to Chum, or create some kind of “release” repo on OBS.

4 Likes
#15

Good, I’ll be looking for it, be sure :wink:
Retroarch is a nice new app to test and enjoy

1 Like
#16

if I build a core .so myself, where on the system should I install it so your package will find it?

Cores are being downloaded to .config/retroarch/cores.

You will also need corresponding .info file.
(But these should be automatically downloaded by the online updater.)

#17

Thanks. that is a problem for packages though, as they MUST NOT install into user dirs (home).

Is it possible to configure more than one core search path?

#18

The package does not install to user dirs.
The app itself (the built-in updater) downloads to user dirs, which are configured as accessible for storage.

#19

No, yes I understand that.

But if I (or anyone) builds a core, and makes an rpm package from them, that rpm can’t install to home.

Instead, I’d choose something like /usr/lib/retroarch/cores or so.

Question is, can your retroarch be told to look in both locations, the one in home and the /usr/lib one?

#20

You can change the location of cores: Directory Configuration - Libretro Docs

If you point it to a read-only directory, the updater will not be able to download cores though.

There is a workaround I think.
Your package can copy/link the core to user-dir in a post-install script.