-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Add support for aarch64e (Apple Silicon) #3238
Comments
Build kitty from source and you will get native binaries. As for |
I'm trying to build from the provided nix-shell - maybe that's a bad idea in this case?
Still no cigarr: Is it nix-shell that messes it up for me? I'd guess so:
I really do not want to bloat my machine with globals like python and stuff though. |
I think your version of nixpkgs also needs to also be built for Apple Silicon. Are other binaries you installed via nixpkgs built for Apple Silicon? Try executing |
NixOS/nixpkgs#95903 may also contain useful information but I haven't read most of it. |
@Luflosi Yeah, the problem is nix. The instructions you linked are the ones I've used and they're based on Rosetta2. I've tried to read that nixpgs thread but its too much and all mixed up,. So I guess my only option is to actually install all the compile deps into my mac globally. But I think I'll just wait instead for either Nix or Kitty instead. |
I'm having issues trying to install kitty on a virtual machine (Parrot OS) on an Apple Silicon device |
Is your feature request related to a problem? Please describe.
Kitty does not run natively on Apple Silicon machines. Kitty has to be executed in the translation environment
rosetta2
which makes kitty slower than need be. It also causes all the programs kitty launches to be the x86_64 variants rather than native aarch64e.Describe the solution you'd like
Add support for
aarch64e
in the form of a universal ("fat") binary in the macOS release. Or, provide an alternate version that can be downloaded independently if the bloat of a universal binary is undesirable.Describe alternatives you've considered
The alternative is not supporting the M1 processor, which is not really an option for macOS software moving forward.
The text was updated successfully, but these errors were encountered: