 | Nix Cross Compiling | 577 Members |
| 125 Servers |
| Nix Cross Compiling | 577 Members |
| 125 Servers |
| Sender | Message | Time |
|---|---|---|
| 2 Apr 2026 | ||
 insipx | * hey everyone! What are the chances of getting this in? https://github.com/NixOS/nixpkgs/pull/505820 don't want it to get lost in the ocean of PRs. happy to modify if its missing anything :) | 16:13:14 |
 alexfmpe | huh does that rely on rosetta 2? because it's getting retired next year IIUC | 16:54:23 |
| insipx | I guess it does, since it's explicitly using x86_64 | 17:33:34 |
| insipx | i was unaware of this discontinuation, that sucks | 17:35:47 |
| insipx | * i was unaware of this discontinuation, that sucks. it's going to be difficult for developers that want to build for both android and ios specifically unless apple decides to continue a subset of rosetta support just for that which is probably doubtful | 17:36:17 |
| insipx | actually i'm wrong, the NDK for x86_64 ships with a Universal binary, which natively support silicon and x86_64, https://github.com/android/ndk/issues/1299 so it is not using rosetta | 17:37:57 |
| insipx | * ~i was unaware of this discontinuation, that sucks. it's going to be difficult for developers that want to build for both android and ios specifically unless apple decides to continue a subset of rosetta support just for that which is probably doubtful~ | 17:38:14 |
| insipx | * I was unaware of this discontinuation, that sucks. it's going to be difficult for developers that want to build for both android and ios specifically unless apple decides to continue a subset of rosetta support just for that which is probably doubtful | 17:38:29 |
| insipx | * actually i'm wrong, the NDK for x86_64 ships with a Universal 2 binary, which natively support silicon and x86_64, https://github.com/android/ndk/issues/1299 so it is not using rosetta | 17:40:22 |
| insipx | * actually i'm wrong, the NDK for x86_64 ships with a Universal 2 binary, which natively supports silicon and x86_64, https://github.com/android/ndk/issues/1299 so it is not using rosetta | 17:41:00 |
| insipx | * | 17:51:33 |
| insipx | * | 17:51:42 |
| alexfmpe | Then is it really double = "darwin-x86_64"; ? | 21:37:09 |
| 3 Apr 2026 | ||
| insipx | Download Screen Recording 2026-04-03 at 9.19.56 AM.mov | 13:21:11 |
| insipx | yeah it's counterintuitive, and maybe android should change that to darwin-universal, but that x86_64 directory houses the universal binaries for both x86 and arm64. if you download the official ndk on m1 that's the only directory shipped with it | 13:21:47 |
| insipx | * yeah it's counterintuitive, and maybe android should change that to darwin-universal, but that x86_64 directory houses the universal binaries for both x86 and arm64. if you download the official ndk on m1 that's the only directory shipped with it. also this piece of doc that shows the folders per system: https://developer.android.com/ndk/guides/other_build_systems | 13:22:16 |
| insipx | * yeah it's counterintuitive, and maybe android should change that to darwin-universal, but that x86_64 directory houses the universal binaries for both x86 and arm64. if you download the official ndk on silicon that's the only directory shipped with it. also this piece of doc that shows the folders per system: https://developer.android.com/ndk/guides/other_build_systems | 13:23:07 |
| insipx | * yeah it's counterintuitive, and maybe android should change that to darwin-universal, but that x86_64 directory houses the universal binaries for both x86 and arm64 (they're the same binary). if you download the official ndk on silicon that's the only directory shipped with it. also this piece of doc that shows the folders per system: https://developer.android.com/ndk/guides/other_build_systems | 13:26:51 |
| insipx | * yeah it's counterintuitive, and maybe android should change that to (the video i uploaded above seems unviewable on linux, but it just shows all the toolchain directories of the officially downloaded ndk on macos silicon, which is just darwin-x86_64). | 13:31:21 |
| insipx | * yeah it's counterintuitive, and maybe android should change that to darwin-universal, but that x86_64 directory houses the universal binaries for both x86 and arm64 (they're the same binary). if you download the official ndk on silicon that's the only directory shipped with it. also this piece of doc that shows the folders per system: https://developer.android.com/ndk/guides/other_build_systems | 13:31:42 |
| insipx | Redacted or Malformed Event | 13:37:14 |
| insipx |  Download Screenshot 2026-04-03 at 9.38.08 AM.png | 13:38:16 |
 A2 changed their profile picture. | 16:33:07 | |
| insipx | 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 |
| insipx | * 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 |
| insipx | * 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 |
| insipx | * 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 |
| insipx | * 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 |
| insipx | * 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 |
| alexfmpe | 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 |