• Cyclohexane@lemmy.mlM
      link
      fedilink
      arrow-up
      6
      arrow-down
      1
      ·
      11 months ago

      I use a self hosted binhost so that I only compile on one of my devices, share with the rest. Works flawlessly.

      • zagaberoo@beehaw.org
        link
        fedilink
        arrow-up
        2
        ·
        11 months ago

        Sounds like an awesome setup. I can’t quite let go of my illusory -march=native benefits lol.

        • Cyclohexane@lemmy.mlM
          link
          fedilink
          arrow-up
          2
          ·
          11 months ago

          I’m sure there are small benefits, but the benefits of the binhost are much cooler to me

          • zagaberoo@beehaw.org
            link
            fedilink
            arrow-up
            1
            ·
            11 months ago

            Was it much of a pain to set up? I was hemming and hawing about distcc recently, but binhost sounds potentially better.

            • Cyclohexane@lemmy.mlM
              link
              fedilink
              arrow-up
              2
              ·
              11 months ago

              Are your systems the same architecture and similar profiles? If so, then yes. It’s just a matter of enabling it and running the quickpkg command.

              Otherwise, it’s a bit harder. You’ll be using cross compiler (if different architecture) and a chroot. You’ll have to setup the host to compile for the target systems whenever you do updates. The initial compile will take a while since it’ll compile basically everything.