-
-
Notifications
You must be signed in to change notification settings - Fork 577
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
arm64 #641
Comments
Hi there! |
I have compiled aw-server-rust and aw-watcher-window-wayland for my Librem 5 Linux phone and have also tried it on a PinePhone, so at least it partially works. The issue I think is rather to know which platforms are worth supporting ARM for, as it means more maintenance. It's also a question about which platforms our CI works well with (GitHub Actions). |
imo, Linux, for sure. Then definitely Darwin since Silicons will be gradually more and more popular and widespread. Additionally, it's likely that more manufacturers will decide to put arm64's into their laptops because of its many upsides |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
With Asahi linux bringing linux to ARM, we are at an inflection point for ARM64 adoption. It's going to be increasingly important for software to work on ARM64 hardware. |
Exactly this! +1 |
Any progress on this? It should work for Apple Silicon Macs. I compiled it on my Mac and it's good for use so far. |
Can't make progress on this until someone figures out how to build arm64
builds on GitHub CI (which only offers x86 machines).
This is low-priority for me as it seems the current build works just fine,
and getting arm64 to build *feels* like it'll be a lot of work (unless you
already know how to, unlike me).
…On Wed, Oct 19, 2022, 23:26 Changyu Gao ***@***.***> wrote:
Any progress on this? It should work for Apple Silicon Macs. I compiled it
on my Mac and it's good for use so far.
—
Reply to this email directly, view it on GitHub
<#641 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKXDOSWYKP4VNUOISVCNFTWEBRRRANCNFSM5ARRQDQA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Haven't tested it yet but found this info actions/runner-images#2187 (comment) |
Arrived here after checking out the website, deciding to install, then realising there is no arm64 macOS build. Which languages are used here? Cross-compiling Rust is very easy ( |
@jbg Cross-compiling Rust to ARM64 is easy, so that's not a big issue. While running python on ARM64 is easy, using pyinstaller to bundle everything is not as easy. It seems like pyinstaller has gotten decent ARM64 the past few years, but since GitHub Actions don't support macOS ARM runners we also need to be able to cross-compile ARM64 with pyinstaller which I'm sure is a bit more tricky. An option to cross-compiling would be to build in a virtualized ARM64 environment which @yeradis mentioned which might work. Feel free to dig further, the short answer is really that no one has given this an attempt. |
It seems https://cirrus-ci.org/pricing/ indicates free service for public open source projects. I am willing to sponsor whoever implements the Apple Silicon build of ActivityWatch. ActivityWatch is a killer app and it would be great to have it available natively, given it runs in the background. |
+1 for aarch64 (using Fedora Asahi). |
+1 for aarch64 (on mobian) |
It seems Github has Apple Silicon runners in beta. That should make it possible to build for Apple Silicon for sure, not sure if that means it would also work for Fedora Asahi or other arm builds though... Would it be possible to use the Apple Silicon beta runner? Would that mean the workflow/build has to be adjusted? |
You can test it from https://copr.fedorainfracloud.org/coprs/wojnilowicz/activitywatch/ |
Are there any sticking points today? |
are you planning on releasing arm64 builds? would be very useful since that's where computers are headed (at least laptops) and some don't have anything else available
Issue
same as above
The text was updated successfully, but these errors were encountered: