Xargon/RetroDECK
1
0
Fork 0
mirror of https://github.com/RetroDECK/RetroDECK.git synced 2025-01-31 12:35:39 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

WIKI: Img fixes

Browse source
This commit is contained in:
Lazorne 2023-12-07 19:00:50 +01:00
parent 61d538de1a
commit 5aea4a2c62
1 changed files with 9 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
wiki-rtd/docs/wiki_general/supported-devices.md
View file

@ -3,15 +3,18 @@
RetroDECK currently supports two systems:
- Steam Deck
- The Linux Desktop
- Linux Desktop
## Steam Deck LCD/OLED
Supported from the beginning. RetroDECK is tailored to the Steam Deck.
### Other SteamOS devices
SteamOS the operative system will always be supported but as of today there are no other officialy released devices with SteamOS other the Valve's Steam Deck lineup.
## Linux Desktop
It is working, but the user experience might not be that great it as we want it to be just yet.
You will also need to manually configure the input to match your desktop and might need to tweak more settings. If you want to try it make sure that your distribution has flatpak support (else you will need to install it).
@ -27,10 +30,11 @@ ARM devices are not supported currently. ES-DE does support the ARM emulators bu
It would be a major undertaking but maybe one day in the far off future it could be possible. But it would need to be a different experience as the emulators, other underlying systems would not be the same and would need to be rewritten.
### Will you support Android?
We believe that is not really possible to bundle and preconfigure external emulators on Android unfortunately.
No, we believe that is not really possible to bundle and preconfigure emulators on Android unfortunately as of now.
### Will you support other distribution methods usch as Snap or AppImage?
It's not in our roadmap yet as now the entire buildsystem is based on the flatpak-build that builds the software via flatpak manifest.
In the past we evaluated to migrate to **Buildstream** (or similar) to build in multiple output format, but the team is not large enough to migrate and maintain other distribution methods, so we prefer to focus our effort on Flatpak only.
If someone wishes to take charge of this we are open to discuss it.
It's not in our roadmap yet as now the entire buildsystem is based on the flatpak-build that builds the software via the flatpak manifest.
In the past we evaluated to migrate to **Buildstream** (or similar solutions) and build on to multiple output formats.
But the team is not large enough to migrate and maintain other distribution methods, so we prefer to focus our effort on Flatpak only.
If someone with knowlage and the passion wishes to help us with this we are open to discuss it at least.