kando-menu / kando

🥧 The Cross-Platform Pie Menu.
https://ko-fi.com/post/Kando-1-0-0-released-G2G5Z1DOS
Other
2.7k stars 79 forks source link

Macos cannot be used #312

Closed gsyyds closed 8 months ago

gsyyds commented 8 months ago
image
Schneegans commented 8 months ago

Hi there! Thanks for the report. Is this the arm64 built on an Apple Chip?

As I do not have such hardware at hand, I cannot test this. But if you have some developer experience, we could try to make this work together! Would it be possible for you to build Kando from source following the instructions in the README?

Salzman-Software commented 8 months ago

Screenshot 2024-01-14 at 01 39 43 Screenshot 2024-01-14 at 01 39 58 Same issue as OP; using arm64 build. Interestingly enough, the regular Intel x64 version DOES work on M1 through Rosetta. This leads me to believe that it is an issue with the precompiled arm64 binary and not the m1 processor.

niieani commented 8 months ago

Can confirm! The arm64 build doesn't work on macOS M1. Looks like the included node_modules dependencies are compiled for amd64, instead of for arm64.

Schneegans commented 8 months ago

I am not sure if there is a way to properly cross-compile native node modules from an Intel Mac to a M1 Mac. Instead, I now tried building the binaries on one of GitHub's large macOS runners which run on actual M1 hardware as far as I know.

This costs some money, but it could be the most robust solution. Can anyone of you test whether the binaries in this test release work on M1?

alex-emery commented 8 months ago

just gave this test release a go and it now launches

Schneegans commented 8 months ago

Thanks for the feedback! I just "rebranded" the test to v0.4.1.

kgantchev commented 8 months ago

@Schneegans Hi, I'm the CEO and co-founder of FlyCI. You can also try the FlyCI's M1 and M2 runners which are on average about 2x faster and 2x cheaper than GitHub's runners. We offer a free tier of 500 mins/month on the M1 runner. If you're looking for more performance, then definitely try our xlarge M1 and M2 runners.

Easily replace your M1 runners:

jobs:
 ci:
-    runs-on: macos-latest
+    runs-on: flyci-macos-large-latest-m1
   steps:
   - name: 👀 Checkout repo
     uses: actions/checkout@v4

Exclusive M2 runners:

jobs:
  ci:
-    runs-on: macos-latest
+    runs-on: flyci-macos-large-latest-m2
    steps:
      - name: 👀 Checkout repo
        uses: actions/checkout@v4

We'll be very happy to have you on board.

Schneegans commented 8 months ago

@kgantchev Thanks for the pointer, I'll check this out!

kgantchev commented 8 months ago

@Schneegans I cloned your repo and made a PR that uses FlyCI's MacOS runners. The results are fantastic!

For comparison, your standard MacOS PR workflow runs in about 3 min 8 seconds, while the same MacOS PR workflow runs in 51 seconds using FlyCI's M1 runner.

Here is Kando's MacOS PR workflow on GitHub MacOS runner:

image

Here is Kando's MacOS PR workflow on FlyCI's MacOS M1 runner:

image

If this is something you find helpful, we can make the PR contribution to your repo. :)