LibreELEC Switch support

  • I know that the devs had issues with the way I did stuff in lakka tree. I was hoping that a working proof of concept build my help. Please respond with a list of code fixes you would like to see, and I will start porting the changes into libreelec clean without lakka specific stuff.

    What works:

    Pretty much everything I have tested, excepting updater, as I can't add builds to the update path.

    What doesn't work:

    There was an issue with nvv4l2 decoder with the South Park addon. This addon no longer works at all, so I am not looking to fix at this time, though I do have some ideas why it didn't work, I have no broken path to test the theory, or potential fixes at this time. If and when the addon starts working again, or I get a report of another addon failing in a similar way, I will look into fixing it.

    Here is my latest build: https://nightly.builds.lakka.tv/members/gavin/…420-247d2dc.tar

    For full feature support enable_upfs = 1 to hekate in file. This enable permissions in storage dir, which is needed for add-ons that try to set permissions on downloaded background executables. Also needed for systemd units in storage dir. System will run without this option, but you might hit permission issues.

  • Honestly no idea what you're talking about /shrug

    LE doesn't mind if Lakka things are discussed occasionally, but LE has zero Switch support (and isn't looking to change that) so it's not really on-topic for here. Perhaps better to discuss in Lakka/Retroarch forums?

  • Honestly no idea what you're talking about /shrug

    LE doesn't mind if Lakka things are discussed occasionally, but LE has zero Switch support (and isn't looking to change that) so it's not really on-topic for here. Perhaps better to discuss in Lakka/Retroarch forums?

    This isnt lakka, lakka is based on libreelec tree. Basically libreelec with lakka changes dumped on top. I ported switch stuff to lakka. But since libreelec is also still in the tree, firing the build is literally changing the DISTRO variable. The real question I have is why a perfectly working build candidate for a commonly owned platform isn't something you would want to support? That is the part I don't understand? The work is basically done already, and would help other distro devs that base their work off of your trees to easily add support to their builds as well.