2 ms·
Hi HN, I started developing an experimental project with the goal of running macOS CLI binaries natively on Linux ARM machines. As of now, we have working proto
by vlad_kalinkin 4mo ago
Hi HN,
I started developing an experimental project with the goal of running macOS CLI binaries natively on Linux ARM machines.
As of now, we have working prototypes for:
- 7-Zip: Passes multi-threaded compression tests on an 8k-file tree. Currently ~5.2x slower than native Linux execution, but I already mapped out a clear optimization plan to cut this gap down.
- curl: Over 200 commands and options successfully pass our automated Docker test script.
- Xcode Tools Git: Basic version control commands (init, add, commit) are up and running, though 100% stability is not yet guaranteed.
I would be highly grateful for your constructive criticism, architectural ideas, and feedback!
Thank you!
- StilesCrisis 4mo agoI assume you eventually plan to target binaries that don't already exist on Linux? Where do you think you'll start?
- vlad_kalinkin 4mo agoWell, of course, most of all I would like to achieve full-fledged support for Xcode Tools (including building iOS applications) and the macOS version of Homebrew. But, of course, there is still a lot of work ahead to get to this point. Thank you!
- iwontberude 4mo agoAnd it’s an endlessly moving target, look at how many apps break every major release (and use it to justify regular, expensive paid upgrades)
- vlad_kalinkin 4mo agoThat's true. But if we can achieve support for the current stable version, it will be much easier to add new features later or rework the ones that were replaced (unless Apple changes everything on purpose :)
- frumplestlatz 4mo agoHistorically, I’d say that the chances of this being successful are exceptionally low given how large the ABI surface is — and it will wildly change out from underneath you on a near yearly cadence. Perhaps LLMs change that calculation. I really couldn’t say.
- RossBencina 4mo agoI'm curious: how large is it really? As I understand it, Kakehashi is targeting command line programs, especially Xcode-tools. How much non-POSIX/Mach/BSD interface do Mac command line programs use? How much of that is not already open source. How much of that changes yearly? The only thing that comes to mind is process security for codesign and notarization but I'm just guessing.
- StilesCrisis 4mo agoThe Xcode Tools are written by Apple to run on Macs; they have no reason to avoid internal APIs, and when dealing with App Store-related concerns, they probably do use them heavily.
- dmix 4mo agoEven React Native tools used by tons of companies struggle to keep up with Xcode build tool changes on mac itself.
- ethin 4mo agoI would look at osxcross[0] if you haven't looked into it already. It can at least do the "build stuff targeting macos" part (well, relatively speaking). Swift support kinda breaks down, unfortunately, and actually getting it set up is a bit of a hassle. but it does work. [0]: https://github.com/tpoechtrager/osxcross https://github.com/tpoechtrager/osxcross
- account42 4mo agoWould be nice to have a "sanity check the resulting binary" tool though like you can use Wine for Windows builds.
- imoverclocked 4mo agoDo you plan on supporting different target versions and implementing similar restrictions to those targets? eg: older macOS had a writable /usr/ while newer does not without manual effort. Also, do you plan on having similar cli tools available with similar features ported (maybe from the available Darwin sources?) eg: can I run a /bin/bash script that expects a macOS environment? Will it get "Darwin" from "uname -o"
- nullsanity 4mo ago[dead]