Nix on macOS | 1183 Members | |
| “There are still many issues with the Darwin platform but most of it is quite usable.” — http://yves.gnu-darwin.org | 194 Servers |
| Sender | Message | Time |
|---|---|---|
| 22 Jan 2026 | ||
| but it requires compilation of shaders | 11:32:10 | |
| Signing with a developer cert isn’t really supported. | 11:40:59 | |
| Disable pre-compilation or compile them offline and vendor the resulting files. | 11:41:39 | |
| 15:02:09 | ||
| 23 Jan 2026 | ||
My current thinking on handling the stdlib is to make Swift first look for an environment variable NIX_STDLIB_RUNTIME_${swift_tuple} then fall back to looking by path. However, I need to dig into the Swift code to make sure that is possible. If so, it would allow for multiple, target-dependent stdlibs to Just Work™. | 01:11:17 | |
* My current thinking on handling the stdlib is to make Swift first look for an environment variable NIX_SWIFT_STDLIB_RUNTIME_${swift_tuple} then fall back to looking by path. However, I need to dig into the Swift code to make sure that is possible. If so, it would allow for multiple, target-dependent stdlibs to Just Work™. | 01:11:37 | |
Note: No NIX_SWIFT_STDLIB_RUNTIME_FOR_BUILD or FOR_TARGET stuff. The tuple will be a platform property that the stdlib’s hook will use to set the variable. | 01:12:13 | |
That should allow me to avoid wrappers and allow the same swiftc to support multiple -target platforms. | 01:12:37 | |
| It would be nice if we can set those up like the SDK, but I’m skeptical, and it doesn’t work right for Darwin due to having multiple SDKs (the Swift stdlib and the standard, Apple one). | 01:13:18 | |
* My current thinking on handling the stdlib is to make Swift first look for an environment variable NIX_SWIFT_STDLIB_RUNTIME_${swift_triple} then fall back to looking by path. However, I need to dig into the Swift code to make sure that is possible. If so, it would allow for multiple, target-dependent stdlibs to Just Work™. | 01:51:34 | |
| I am going to explore SDKs though. There is some neat stuff with toolchains, but will it work? | 01:51:46 | |
For some reason, swift build is only using the linker in my toolset configuration. | 03:11:23 | |
| That’s not very helpful. | 03:11:35 | |
| like link them into zig cache? | 03:12:46 | |
No idea for Zig. https://github.com/NixOS/nixpkgs/blob/b494a615768aac2f4b0e2839fd23ec02236368fa/pkgs/tools/security/pinentry/mac.nix is an example of a package that does it for .nib files with xcbuild to avoid depending on ibtool. I assume something could be done similarly for Zig. | 03:19:22 | |
| After messing with it for a bit, I don’t think Swift SDKs are going to do what we need. Swift doesn’t pick up the toolchain stuff from it. We’d have to merge the Swift stdlib and Darwin SDK to make it work on Darwin. It also seems to get funny ideas about triples and deployment targets. | 03:44:31 | |
| 17:42:13 | ||
| Heads-up: with the latest staging merge into
| 18:26:21 | |
| 18:47:01 | ||
| 24 Jan 2026 | ||
| 14:06:38 | ||
| 25 Jan 2026 | ||
| 07:00:06 | ||
| 07:00:25 | ||
| 21:01:06 | ||
| 26 Jan 2026 | ||
| swift-5.10.1 no longer compiling for me on pinning [1] https://github.com/NixOS/nixpkgs/issues/483584#issuecomment-3796732786 | 09:08:25 | |
| yeah it kind of looks like that's what's happening | 09:52:54 | |
| the include chain goes through gcc, sdk and then back again | 09:55:32 | |
| 09:55:48 | |
| these top-level lib/ come bundled with gnu hello for whatever reason and then it does a tour gnu -> gcc -> sdk -> gnu | 10:01:47 | |
| what fresh hell is this
| 10:02:45 | |
| tempted to file this under "gnu hello's problem" | 10:03:14 | |