| 24 Nov 2025 |
 K900 | I wonder if it makes sense to have two builds of Mesa | 11:26:10 |
| K900 | One that is just GLX | 11:26:13 |
| K900 | And one that is just VK | 11:26:16 |
| K900 | And eventually GLX just dies | 11:26:21 |
| K900 | There's already like, double digit consumers of it I think | 11:27:36 |
| K900 | 
Download image.png | 11:28:38 |
| K900 | Hold on | 11:28:39 |
| K900 | Where did everything go lol | 11:28:43 |
 niklaskorz | so keep mesa as the build-all package and kosmickrisp (or mesa-kosmickrisp) as the bare minimum package for Vulkan on darwin packages? | 11:28:47 |
| niklaskorz | * so keep mesa as the build-all package and kosmickrisp (or mesa-kosmickrisp) as the bare minimum dependency for Vulkan on darwin packages? | 11:29:37 |
| K900 | So there's three packages there that aren't libraries | 11:29:42 |
| K900 | That's magic-vlsi, spacenav-cube-example and unixbench | 11:29:54 |
| K900 | And technically X itself but whatever | 11:29:59 |
| K900 | Should we just break those | 11:30:08 |
| K900 | I feel like we should just break those | 11:30:12 |
| niklaskorz | "spacenav-cube-example" does not sound it hasy many dependants | 11:30:18 |
| niklaskorz | * "spacenav-cube-example" does not sound it has many users | 11:30:24 |
| K900 | Also looking closer magic-vlsi and spacenav-cube-example pull mesa_glu when they should probably pull libGLU | 11:30:32 |
| K900 | Which may or may not fix them | 11:30:37 |
| K900 | And unixbench is lol | 11:30:40 |
| niklaskorz | that also raises the question if we should build gallium by default at all, because that contains just software renderers as of now | 11:32:13 |
| niklaskorz | * that also raises the question if we should build gallium by default on darwin at all, because that contains just software renderers as of now | 11:32:19 |
| K900 | I think it's absolutely reasonable to just break those three things and never worry about GLX on Darwin | 11:32:47 |
 Randy Eckenrode | It’s enabled because dropping GLX is a breaking change. Not sure why they are linking X11 libs, but there is an open issue about xquartz and Vulkan support. | 11:32:57 |
| niklaskorz | I'm generally fine with either option, having kosmickrisp be its own package name that builds just kosmickrisp and nothing else might make it easier to consuming packages to find | 11:34:15 |
| niklaskorz | (i.e. just mesa with galliumDrivers = [ ]; and eglPlatforms = [ "macos" ]; | 11:34:43 |
| niklaskorz | * (i.e. just mesa with galliumDrivers = [ ]; and eglPlatforms = [ "macos" ];) | 11:34:44 |
| Randy Eckenrode | Consuming packages should never be using it directly. They should be using vulkan-loader. | 11:34:52 |
| niklaskorz | right, and vulkan-loader has no need for gallium | 11:35:10 |
| K900 | "Gallium" is the wrong term here FWIW | 11:35:33 |
