| 11 May 2025 |
 carlossless | * No additional logs with SDL_DEBUG=1, I guess the app doesn't respect it | 07:49:26 |
| carlossless | I'll try a debug build | 07:49:39 |
 K900 | Do other SDL applications work? | 07:54:54 |
| carlossless | Well I just confirmed that switching back to SDL2_classic makes it work again. So it's definitely SDL that's the issue here | 07:58:50 |
| carlossless | need to look up what uses SDL2 and has darwin as one of the supported platforms | 08:00:57 |
| carlossless | K900: just tried bzflag - same issue | 08:06:41 |
| carlossless | hm, blobwars does work though | 08:10:03 |
| carlossless | Redacted or Malformed Event | 08:13:57 |
| carlossless | Here's the SDL_CreateWindow calls for all three apps:
bzflag - https://github.com/BZFlag-Dev/bzflag/blob/f6f647cdc1bc4921bf8e58c8ec6e8b518f9e818c/src/platform/SDL2Window.cxx#L264-L272
q2pro - https://github.com/skullernet/q2pro/blob/aba81ef8bc277e9a4e11733a449a29d07ea28c7a/src/unix/video/sdl.c#L258-L259
blobwars - https://github.com/perpendicular-dimensions/blobwars/blob/1622ca7486227c8993dab2657837de51f09bad94/src/init.cpp#L272 | 08:15:10 |
| carlossless | I'm going to guess it's probably the opengl option that makes the difference here | 08:16:10 |
| K900 | I wonder if it's failing to load libGL for some reason | 08:21:45 |
| carlossless | Seems like the correct env var for logging is SDL_LOGGING, but even though setting SDL_LOGGING="*=trace" produces more output, there's no info on why it couldn't create a new window | 08:31:55 |
| carlossless | hm, the previous version which works for me was already linked against sdl2-compat, the only difference between the two links is the patch bump 2.32.52 -> 2.32.54 | 08:44:31 |
| K900 | We do have 2.32.56 in staging-next | 08:46:06 |
| K900 | You might want to try that | 08:46:08 |
| carlossless | hm, no 2.32.52 still fails | 08:56:25 |
| carlossless | although I took the last commit before the 54 upgrade, seems like there were some things changes that could've affected darwin | 09:02:56 |
| carlossless | ah no, that's wrong, I failed in my process, the commit before the 54 wasn't broken. Still confirming all of this though | 09:24:31 |
| carlossless | welp, apparently I need to rebuild everything under the sun just to get that version to build now... | 11:28:29 |
| carlossless | okay, it built, and apparently it wasn't that... building and running it from f64a287 works just fine... | 13:22:40 |
| carlossless | can't easily try 2.32.56 there's other failures in staging-next | 14:49:03 |
| carlossless | I can confirm though that at f64a287d96ad7783e10f17b2c703078ea3ba0346 everything was still working, so it's not any changes to sdl-compat or sdl3 directly | 15:08:24 |
| K900 | Well I guess you'll have to bisect nixpkgs | 15:09:01 |
|  nick joined the room. | 19:30:57 |
| 12 May 2025 |
| carlossless | ugh, bisecting this is such a pain. Unrelated build failures plaguing every other step... And I am really wishing for a --no-check option on nix-build | 07:56:24 |
|  TobiNary joined the room. | 11:07:45 |
 Jaoreir | Hi everyone. Has anyone else tried to run the unity editor on nixos? I'm experiencing an issue where the editor couldn't find its default fonts to do IMGUI rendering.
It spams the error "Unable to find a font file with the specified Family Name [LegacyRuntime] and Style [Regular].
UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&) (at /home/bokken/build/output/unity/unity/Modules/IMGUI/GUIUtility.cs:219)" over and over.
I tried to symlink my fonts directory to /usr/share/fonts but it doesn't help. :( | 13:01:10 |
|  @fxomt:pub.solar joined the room. | 18:18:37 |
 aidalgol | Something like that I would run via steam-run or a custom FHS environment wrapper. | 19:29:22 |
| 13 May 2025 |
|  energi joined the room. | 22:44:16 |
