Appimage builds

[piplup55]

this should in in theory work but i'm unsure, and i'm sure this could be improved

[qurious-pixel]

not absolutely necessary to create an AppRun, if this is all you are doing. But it can stay in case you want to add more functionality in the future.

otherwise ln -s AppDir/usr/bin/Ryujinx.sh AppDir/AppRun

[piplup55]

i think it should stay just in case more functionality wants to be added down the road

[qurious-pixel]

PR will fail until PR #31 is merged or you make the formatting and whitespace fixes.
Then your PR should build an AppImage.

And you have to set the path to upload the artifact as PR/Release build.

[qurious-pixel]

The packaging looks good now.

Forgot to add earlier, the log files/folder needs to be directed out of the publish folder, now located in AppDir/usr/bin, because it will cause a segfault due to trying to write to a read-only location.

The project this is based on used a flag for Flatpak, which had the same issue.
Should set the Flatpak channel flag, or use custom code to create logs in XDG_DATA_HOME folder.

RYUJINX_TARGET_RELEASE_CHANNEL_OWNER: flathub

[github-actions]

Download the artifacts for this pull request:

• ryujinx-Release-1.2.0+79d337f-linux_arm64
• ryujinx-Release-1.2.0+79d337f-linux_arm64-AppImage
• ryujinx-Release-1.2.0+79d337f-linux_x64
• ryujinx-Release-1.2.0+79d337f-linux_x64-AppImage
• ryujinx-Release-1.2.0+79d337f-macos_universal
• ryujinx-Release-1.2.0+79d337f-win_x64

GUI-less (SDL2)

• sdl2-ryujinx-headless-Release-1.2.0+79d337f-linux_arm64
• sdl2-ryujinx-headless-Release-1.2.0+79d337f-linux_x64
• sdl2-ryujinx-headless-Release-1.2.0+79d337f-macos_universal
• sdl2-ryujinx-headless-Release-1.2.0+79d337f-win_x64

Only for Developers

• ryujinx-Debug-1.2.0+79d337f-linux_arm64
• ryujinx-Debug-1.2.0+79d337f-linux_arm64-AppImage
• sdl2-ryujinx-headless-Debug-1.2.0+79d337f-linux_arm64
• ryujinx-Debug-1.2.0+79d337f-linux_x64
• ryujinx-Debug-1.2.0+79d337f-linux_x64-AppImage
• sdl2-ryujinx-headless-Debug-1.2.0+79d337f-linux_x64
• ryujinx-Debug-1.2.0+79d337f-macos_universal
• sdl2-ryujinx-headless-Debug-1.2.0+79d337f-macos_universal
• ryujinx-Debug-1.2.0+79d337f-win_x64
• sdl2-ryujinx-headless-Debug-1.2.0+79d337f-win_x64

[piplup55]

The project this is based on used a flag for Flatpak, which had the same issue. Should set the Flatpak channel flag, or use custom code to create logs in XDG_DATA_HOME folder.

this shouldn't be needed as it should default to $HOME/.config/Ryujinx

[regginator]

@qurious-pixel This infra was from myself & @Samueru-sama's changes in ryujinx-mirror. There ended up being issues with just symlinking stuff for appimagetool, resulting in non-local AppImage builds simply not working due to invalid symlinks. (Why appimageool doesn't just follow symlinks like normal I have no clue) I'm unsure if AppRun really is necessary, so I'd just leave everything as-is from ryujinx-mirror.

[qurious-pixel]

The appimage works for me including creating the logs folder in $HOME/.config/Ryujinx.
The AppRun as designed accomodates running the extracted image, while appimagetool will create a relative symlink to binary if none is provided.

The zsync file doesn't need to be included in the zip, and should probably be uploaded as an artifact when published as a release. (to use with AppImageUpdate)

@regginator linuxdeploy is more robust at following symlinks, but I have used both tools for different goals.