351ELEC VS source-to-image

The files are posted here: https://github.com/351ELEC/351ELEC/releases/tag/20211122

351elec and arkos are still actively updated. Whenever an emulator is discovered that is capable of running on these devices they add it. There just simply isn't very many stand alone emulators because it's difficult to configure them to run on these devices.

The stock OS is very buggy. Switch to JELOS or 351ELEC instead.

Oh, sorry, did not try that yet. But I am interested and found this on how to place it in ports and this which makes it seem a little difficult to make it work. Hope this helps anyway.

First of all, you should REALLY look into installing a custom firmware. The one it comes with is terrible (both for UI and actual game performance). But also the SD card it ships with WILL corrupt. My suggestion would be to buy a sandisk 64GB card and install the 351ELEC software. Russel from RetroGameCorps on Youtube has tutorials, it's pretty easy even if you've never done it before.

https://github.com/351ELEC/351ELEC/releases https://github.com/christianhaitian/arkos/releases

build implies creating a flashable image from source code. Reference https://github.com/351ELEC/351ELEC for build instructions. Since the build instructions are made for Ubuntu 20.04, you may have troubles getting it functional.

You can try and use s2i (source to image) - https://github.com/openshift/source-to-image You deploy container to your cluster that produce another image

Surprised to see it supports source-to-image (S2I). If you're using S2I, you're likely using OpenShift where your development pipeline is figured out for you. You wouldn't be using Shipwright on that platform.

If that's not an option, I unfortunately don't know how to compile source code into an IMG file from github, but I have a feeling that there's quite a few people who are knowledgeable in these matters lurking around this subreddit. The only thing I found was this: https://github.com/openshift/source-to-image but I have no idea how or where exactly to execute the code outlined in the readme below. Looks promising though.

Source-To-Image (S2I) is a toolkit for building images directly from source code without Dockerfile. This tool works well for simple, expected scenarios and workflows but quickly becomes annoying and clumsy if you need little too much customization or if your project doesn't have the expected layout. You might consider using S2I if you are not very confident with Docker yet or if you build your images on OpenShift cluster, as builds with S2I are a built-in feature.