RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login

    Feature Request: Provide pre-compiled deb binaries for ARM64

    Scheduled Pinned Locked Moved Ideas and Development
    featurerequestdebpackagesarm64
    4 Posts 3 Posters 1.4k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • L
      libredeb
      last edited by

      Hello team,

      First of all, thank you for your incredible work on this project.

      I'm writing to respectfully request the addition of pre-compiled deb binaries for the ARM64 architecture.

      Currently, the primary method for installing on ARM64 devices, such as the Raspberry Pi Zero 2W, is by compiling from source. This process is resource-intensive and can be problematic on hardware with limited capabilities. For instance, the Raspberry Pi Zero 2W often freezes during compilation due to high CPU and RAM usage, making the installation process challenging and sometimes impossible.

      The availability of pre-compiled .deb binaries for ARM64 would make the project much more accessible and user-friendly for a growing community of users. This would allow for a fast and straightforward setup without the need for a toolchain or a lengthy compilation process.

      My primary use case is to run lightweight emulators for systems like SNES and Megadrive on a Raspberry Pi Zero 2W. For this purpose, a straightforward installation method is crucial.

      Providing pre-compiled .deb packages would not only solve the installation problem for users with similar hardware but would also significantly broaden the project's user base in the growing ARM64 ecosystem.

      Thank you for your time and for considering this request.

      B 1 Reply Last reply Reply Quote 0
      • B
        barbudreadmon @libredeb
        last edited by barbudreadmon

        @libredeb said in Feature Request: Provide pre-compiled deb binaries for ARM64:

        For instance, the Raspberry Pi Zero 2W often freezes during compilation due to high CPU and RAM usage

        There is a bigger problem then : your device is faulty and/or you are overclocking it too much.

        It has been a long time since i booted my retropie, was the "install from binaries" choice removed ? Not that i'd ever recommend using that since binaries are outdated most of the time.

        FBNeo developer - github - forum

        mituM 1 Reply Last reply Reply Quote 0
        • mituM
          mitu Global Moderator @barbudreadmon
          last edited by mitu

          @barbudreadmon said in Feature Request: Provide pre-compiled deb binaries for ARM64:

          It has been a long time since i booted my retropie, was the "install from binaries" choice removed ? Not that i'd ever recommend using that since binaries are outdated most of the time.

          It was not removed, but they're produced for certain releases, platform combos of RaspiOS and RPI models. We do not have 64bit binaries for Bookworm - I think for any PI model. For a Pi Zero 2W, I would recommend using the 32bit RaspiOS release and not the 64bit version.

          L 1 Reply Last reply Reply Quote 0
          • L
            libredeb @mitu
            last edited by

            Thank you both for the quick replies and for sharing your perspectives.

            @mitu, your point about the 32-bit OS performing better on the Raspberry Pi Zero 2W is well-taken, and I completely agree with that for its current state. However, that wasn't quite the core of my request. It leads me to a broader question: what is the reasoning for recommending a 32-bit OS in an era where the tech world is steadily moving away from it?

            My primary goal is to make things more accessible for the average user. For someone just getting into the Raspberry Pi world to build their own projects, having ready-to-use .deb packages is a much more welcoming experience than facing a complex compilation process.

            This has led me to think about a potential middle ground. Lately, the best approach I've found for creating reproducible builds is using Dockerfiles (a.k.a. Containerfiles). Although I haven't yet managed to create a fully functional build of EmulationStation this way, it seems like a very promising path.

            Perhaps we could collaborate on creating and maintaining container-based build files? This could automate the process for everyone and serve as a solid foundation for generating reliable binaries in the future. I believe this could be a great step forward for the project and its community.

            Thanks again for the discussion and for your incredible work.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post

            Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

            Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.