Nix Cross Compiling | 579 Members | |
| 126 Servers |
| Sender | Message | Time |
|---|---|---|
| 3 Apr 2026 | ||
| 16:33:07 | ||
| also curious, since i got almost all supported platforms xmtp platforms (android, musl, native linux/macos) cross-compiling, what it would take to get iOS cross compile working again in NixOS. as far as I understand it, iphone/ios cross compile has been broken for some time now, but i have a morbid curiosity to maybe pursue getting that working in nix. are there resources for how the current darwin compile to work, and does anyone have an estimate or gut feel on how much actual work there is to get an iphone compile working? Right now xmtp uses a really hacky way to compile to iphone via impurity/xcode that can be improved with compose xcodeenv, but i'm thinking of what it would take to get the official working iphone64 crossSystem working again | 19:44:11 | |
| * also curious, since i got almost all supported platforms xmtp platforms (android, musl, native linux/macos) cross-compiling, what it would take to get iOS cross compile working again in NixOS. as far as I understand it, iphone/ios cross compile has been broken for some time now, but i have a morbid curiosity about the iphone64 cross compile. are there resources for how the current darwin compile to work, and does anyone have an estimate or gut feel on how much actual work there is to get an iphone compile working? Right now xmtp uses a really hacky way to compile to iphone via impurity/xcode that can be improved with compose xcodeenv, but i'm thinking of what it would take to get the official working iphone64 crossSystem working again | 19:44:38 | |
| * also curious, since i got almost all supported platforms xmtp platforms (android, musl, native linux/macos) cross-compiling, what it would take to get iOS cross compile working again in NixOS. as far as I understand it, iphone/ios cross compile has been broken for some time now, but i have a morbid curiosity about the iphone64 cross compile. does anyone have an estimate or gut feel on how much actual work there is to get an iphone compile working? Right now xmtp uses a really hacky way to compile to iphone via impurity/xcode that can be improved with compose xcodeenv, but i'm thinking of what it would take to get the official working iphone64 crossSystem working again | 19:44:48 | |
| * also curious, since i got almost all supported platforms xmtp platforms (android, musl, native linux/macos) cross-compiling, what it would take to get iOS cross compile working again in NixOS. as far as I understand it, iphone/ios cross compile has been broken for some time now, but i have a morbid curiosity about the iphone64 cross compile. does anyone have an estimate or gut feel on how much actual work there is to get an iphone compile working? Right now xmtp uses a really hacky way to compile to iphone via impurity/xcode that can be improved with compose xcodeenv, but i'm thinking of what it would take to get the official working iphone64 crossSystem working again. if i ever have some free time i'd love to pursue getting that into nixpkgs | 19:45:20 | |
| * also curious, since i got almost all the supported systems by xmtp sdks (android, musl, native linux/macos) cross-compiling, what it would take to get iOS cross compile working again in NixOS. as far as I understand it, iphone/ios cross compile has been broken for some time now, but i have a morbid curiosity about the iphone64 cross compile. does anyone have an estimate or gut feel on how much actual work there is to get an iphone compile working? Right now xmtp uses a really hacky way to compile to iphone via impurity/xcode that can be improved with compose xcodeenv, but i'm thinking of what it would take to get the official working iphone64 crossSystem working again. if i ever have some free time i'd love to pursue getting that into nixpkgs | 19:45:59 | |
| * also curious, since i got almost all the supported systems by xmtp sdks (android, musl, native linux/macos) cross-compiling, what it would take to get iOS cross compile working again in NixOS. as far as I understand it, iphone/ios cross compile has been broken for some time now, but i have a morbid curiosity about the iphone64 cross compile. does anyone have an estimate or gut feel on how much actual work there is to get an iphone compile working? Right now xmtp uses a really hacky way to compile to iphone via impurity/xcode that can be improved with compose xcodeenv, but i'm thinking of what it would take to get the official working iphone64 crossSystem working again. if i ever have some free time i'd love to pursue getting that into nixpkgs After a quick trial it seems an iphone cross fails while building rt-compiler | 19:48:25 | |
In reply to @insipx:matrix.orgI almost got around to that rabbit hole in a previous life/job. There wasn't much consensus on how much one should build with nix vs apple toolchain. | 21:25:19 | |
| IIRC step 1 was to package the ios sdk like the macos one is or something | 21:25:45 | |
| haskell.nix offers iOS cross by compiling natively on apple silicon then messing with the mach header | 21:26:57 | |
| interesting, i'll probably take a stab at at least the first step. at least for my own project i'm crafting a custom ios stdenv based on xcode and it feels similar to what the nix darwin is doing for darwin builds already | 21:28:47 | |
| * interesting, i'll probably take a stab at at least the first step. at least for my own project i'm crafting a custom ios stdenv based on xcode and it feels similar to what the nix darwin is doing for darwin builds already but i could be totally wrong | 21:28:56 | |
| 21:35:37 | |
*
where did those discussions take place previously? is there a github issue/pr/discussion of relevance | 21:35:43 | |
| nix on macos room couple years ago I think | 22:54:45 | |
| there is https://nixos.org/manual/nixpkgs/stable/#ios but I think it's bitrotted into oblivion | 22:55:43 | |
| it was a lot less than two years ago :D | 23:03:54 | |
but yes, making apple-sdk support iOS would be the thing to do there | 23:04:09 | |
| App Store requires you to use Apple's toolchain nominally | 23:04:17 | |
| but it'd be a lot less painful to support our toolchain | 23:04:26 | |
| oh interesting. by "your toolchain" do you mean something that is not xcodeenv or the impure xcode symlinks nix is creating ? So something like a nix stdenv clang/llvm? | 23:57:30 | |
| * oh interesting. by "our toolchain" do you mean something that is not xcodeenv or the impure xcode symlinks nix is creating ? So something like a nix stdenv clang/llvm? | 23:57:38 | |
| 4 Apr 2026 | ||
| yes | 00:17:16 | |
| iOS should be "just another triple" for cross compilation for the most part. though I think actually getting the SDK is going to be slightly annoying since it can't be downloaded from the software update command line tools like we do for the macOS one I guess. but you can just pull the source out of our Xcode package that requires you to manually inject it into the store or w/e | 00:18:26 | |
| when you start caring about the letter of App Store requirements is when it gets tricky | 00:18:40 | |
The apple-sdk package would have to be modified to source frameworks from Xcode because iOS stuff isn’t included in the SDK we use. | 01:09:19 | |
| (Source them for iOS.) | 01:10:10 | |
| I assume “our toolchain” as in the upstream LLVM we build. It can be tricky because if we are ahead of Apple’s LLVM fork, symbols from upstream LLVM can be flagged as from a beta Xcode release and get your app rejected. (This is less risky due to using the system libc++, but it could possibly happen due to something like compiler-rt I guess.) | 01:11:56 | |
| Redacted or Malformed Event | 01:16:39 | |
| 5 Apr 2026 | ||
| 01:18:05 | ||