| 16 Sep 2025 |
 sterni | or rather the callPackage implementation | 09:49:59 |
 bglgwyng | Yes. I realized that after I tried to fix the issue. | 09:54:08 |
| bglgwyng | I think that callCabal2Nix result would better expose expr of itself as an attribute. | 09:54:40 |
| bglgwyng | When expr is exposed, functionArgs expr might give us enough information | 09:55:17 |
| bglgwyng | * When expr is exposed, functionArgs expr might give us enough information to correct the behavior | 09:55:30 |
| sterni | I mean that's “just” another target, but true. Support for targets that relate to IOGs business are probably going to be more fleshed out (Android, iOS, Windows, …). I think Windows has been worked again in Nixpkgs recently, though.
The big thing is probably that they have an qemu based iserv setup for TH in cross. | 10:01:08 |
| sterni | We should probably eventually look into that again… | 10:01:24 |
| bglgwyng | I hoped callCabal2Nix is enough to do my stuffs, but it turns out not. I realized that I need more control over arguments passed to cabl2nix expression. | 10:23:40 |
