-
-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to run it on MacOS #126
Comments
My CPU is inter. |
Are you sure you downloaded the correct file? Can you start a terminal and type |
seems like github recently updated their action runners to m1 images by default. Good catch! |
should now be the correct intel binary again in the latest prerelease |
❯ file lan-mouse-macos-intel |
But still not work: ❯ ./lan-mouse-macos-intel2 --port 54243 (:18959): Gdk-CRITICAL **: 10:57:14.843: _gdk_macos_surface_update_fullscreen_state: assertion 'GDK_IS_MACOS_SURFACE (self)' failed (:18959): Gdk-CRITICAL **: 10:57:24.538: _gdk_macos_surface_update_fullscreen_state: assertion 'GDK_IS_MACOS_SURFACE (self)' failed (:18959): Gtk-WARNING **: 10:57:24.552: Broken accounting of active state for widget 0x7fddb278afc0(GtkBox) (:18959): Gtk-WARNING **: 10:57:24.552: Broken accounting of active state for widget 0x7fddb278a5b0(GtkBox) (:18959): Gtk-WARNING **: 10:57:24.552: Broken accounting of active state for widget 0x7fddb278a430(AdwComboRow) |
What dou you mean exactly? Does the window show up? |
On Macos cargo also fails (lib adwaita installed via brew):
|
This seems like an issue with your rust setup. Could you try updating / reinstalling rust and llvm? |
@joaomcarlos I just tested it again on a fresh VM and it works for me. You appear to have llvm 18.1.4 locally installed which might be the cause but I can not say for sure. |
I have executed this:
brew install libadwaita
and download the release "lan-mouse-macos-intel"
I chmod u+x on lan-mouse-macos-intel, when run it in terminal, I got "zsh: bad CPU type in executable: /Users/aaron/Desktop/lan-mouse-macos-intel"
The text was updated successfully, but these errors were encountered: