New generic image is out:
New generic image is out:
I've dropped the builds without Kodi to avoid confusion. I've no outstanding issues with Wayland, so I declare that the future is here 
Everything except Kodi (GBM/GLES) and PCSX2 (OpenGL/Xwayland) is now running natively.
Can you test now? 
Should be in the "quit" submenu, I think the logic that built the option was faulty indeed. Try the latest images, except for RPi2 which I haven't updated yet. I will build it with vc4 driver and Wayland in time.
There's two types of builds, the ones in the root folder and then one in the kodifolder. Guess what the one in the kodi folder boots to
You can also change this after installation through modifying /storage/.config/frontend.conf. Wayland the next gen X "replacement".
Seems my gdrive went full when uploading, try again now.
For that price you could consider the Odroid H2, which is x86_64. It will beat the crap out of any ARM based SBC on the market and even run Dolphin well. Intel's Linux support has gotten very good these days and the Mesa Iris/anv drivers are excellent.
Or take the step up to for example an Intel NUC7i3. You might even be able to find it used for cheap.
I had an RX Vega for a short while, I think this was all I did to get it working:
If I'm not mistaken, you should be able to download the file to /storage/.config/udev.rules.d and it should override the system one.
Also, you might have better luck with my Wayland image which runs Kodi on GBM/KMS (no Xorg).
The Wayland image has Kodi (start from Emulationstation menu). Just uploaded a new image, try it out.
You should probably detail how you are compiling Qt, as it's not in the LibreELEC tree. If it's compiled statically, then you won't find anything in .install_pkg as static libraries do not need to be in the image they are compiled directly into your application.
Note that Qt plugins (i.e. QPA/eglfs) can't be loaded dynamically if you have built a static library.
New Wayland image out:
Once your package is built, there should be a .install_pkg in the source directory, check that. Perhaps there is something wrong with your makeinstall_target routine?
Kodi "Leia" 18.4+ (some commits after 18.4).
It's based on master from some time ago, with some upgraded components. There are of course some relatively major differences at this point, mainline runs on X11 while I've moved to GBM. It shouldn't matter much with regards to compatibility though, if that's what you are thinking about. Their plan is to ditch X11 and move to GBM anyways AFAIK, not that it matters much (except perhaps GL/GLES addons, not sure how they behave). Hard to say though, as I don't use Kodi much and community seems dead these days. I mostly hack on this to improve my HTPC gaming functionality and WAF.
It's an environment variable. I set it in the systemd service that I run ES from, don't know how it's launched in this addon.
You need to set LANG=en_US.UTF-8 when launching Emulationstation, I believe that should fix the runtime error.
New Wayland image out:
Get it here (AMD / Intel only!)
Should be easy to fire it up in a container to see how well it runs. I'll test a bit when I have some time although not at the top of my list. I don't expect Wine to be good for running an emulator.
I was thinking about it, do you have any experience with it? Says on their site intel has bugs but lots have happened in mesa lately might give it a shot. I suppose the nuc8 should handle it power wise, at least some games.
EDIT: Doh, it uses Wine.... Doable, but I think it could be a lot of work, also I'm not convinced how well it will run.
Some really cool progress on my Wayland builds, see demo here:
EDIT:
(sound is out of sync and video is off sometimes but this is just due to the recording tool I guess, because it runs great)
EDIT2: Turns out it was just due to software encoding being heavy. Enabled vaapi in ffmpeg and it's all good, will make a new video later.
Haven't added NVIDIA as I don't have any hardware to test, but should be possible through EGLStreams. This isn't included though. I'm quite pleased with the results, Wayland is running smoothly. I did have the odd crash here and there, but I'd say it's ready for day to day use.
Advantages with Wayland/Sway:
New image available here.
Others said it couldn't be done...
I also support the XU4, which is my main motivation for implementing Wayland support (no matter what this delusional idiot may think) as there's currently no way to switch modes on the fly without X11. Sway takes care of that nicely, although I haven't gotten it running on that yet because libmali is broken and soon(ish) is to be replaced by panfrost. Also X.org development has stalled to nearly a halt the last years and everybody is moving to Wayland, so might as well start getting things in shape. My tree will let you choose between them at build time, I am not here advocating one over the other the wayland builds are simply test beds for my current work. I am simply sick of this guy constantly spreading p0ison, so came to drop my two cents on what he's been saying.
