| 18 Apr 2026 |
 Randy Eckenrode | … is Rubberband broken with libc++ 21? | 01:17:24 |
| Randy Eckenrode | Yes. https://github.com/breakfastquay/rubberband/pull/126 | 01:29:25 |
| Randy Eckenrode | https://github.com/NixOS/nixpkgs/pull/511070 makes GNU libiconv the default on Darwin. I keep tripping over autoreconfHook causing breakage …. | 03:32:56 |
|  @lain:glasgow.social left the room. | 04:32:43 |
 viraptor | In reply to @reckenrode:matrix.org
I would just patch that stuff out. Swift Build already requires a ton of patching due assuming FHS. It's all going in the right direction. There are a few changes in xcbuild, ibtool and others, but... I'm confident things will work in the end. swbuild itself is behaving well. | 07:33:46 |
| viraptor | * It's all going in the right direction. There are a few changes in xcbuild, ibtool and others, but... I'm confident things will work in the end. swbuild itself is behaving well.
(There's at least 2 utilities to shim/rewrite to make it work. Currently dealing with derq) | 09:05:52 |
 WeetHet | I wish that making vulkan loader use mesa didn’t feel as hacky. I know that it uses moltenvk only in one place and using override { moltenvk = mesa; } works but it feels wrong
Gtk4 doesn’t use vulkan on macOS for now due to the visual artifacts with moltenvk which aren’t present with mesa
| 11:18:13 |
| Randy Eckenrode | Can’t apps that need Mesa set the environment variable to point at the KosmicKrisp ICD? | 11:19:23 |
 K900 | This makes no sense anyway | 11:19:59 |
| K900 | It should not be linking moltenvk at all | 11:20:08 |
| K900 | It should be linking vulkan-loader | 11:20:12 |
| WeetHet | https://github.com/NixOS/nixpkgs/blob/a9503707cb403de2b9a974c27d89031c73b84455/pkgs/by-name/vu/vulkan-loader/package.nix#L52 | 11:20:41 |
| K900 | Yeah that's a hack | 11:21:00 |
| K900 | If GTK links vulkan-loader you can set the environment variables | 11:21:14 |
| K900 | And point it at kosmickrisp | 11:21:16 |
| Randy Eckenrode | That’s a default path, isn’t it? | 11:21:19 |
| K900 | If GTK links moltenvk directly, that's a problem | 11:21:22 |
| WeetHet | Oh I didn’t know about that | 11:21:34 |
| WeetHet | Yeah it links vulkan loader | 11:21:50 |
| K900 | VK_ICD_FILENAME=/nix/store/... should work | 11:21:52 |
| Randy Eckenrode | Or VK_DRIVER_FILES I think. | 11:22:30 |
| WeetHet | More stuff to add to the gtk app wrapper hook ig | 11:23:19 |
| K900 | https://github.com/KhronosGroup/Vulkan-Loader/blob/main/docs/LoaderDriverInterface.md | 11:23:28 |
| K900 | I will defer to the Darwin team on that | 11:23:41 |
| K900 | But I don't think this is a good idea | 11:23:49 |
| K900 | Unless there are obvious immediate issues with the GL code path | 11:24:02 |
| K900 | I think we should follow upstream here | 11:24:05 |
| K900 | Instead of trying to force an experimental Vulkan renderer on an experimental Vulkan driver | 11:24:21 |
| Randy Eckenrode | If MoltenVK doesn’t work, there may not be a better option. However, KosmicKrisp is not supported on Intel hardware. | 11:24:36 |
| WeetHet | It’s still used as default even if vulkan is available | 11:24:41 |
