| 19 May 2025 |
 K900 | Honestly I still want to kill off target at some point | 13:35:32 |
 emily | why not? in most cases we handle it correctly | 13:35:39 |
| K900 | I forgot why it blows up the platform offset logic but it does | 13:36:44 |
| K900 | Honestly that whole thing is the primary reason I really want to kill target | 13:37:09 |
| emily | well that's dumb | 13:37:09 |
| K900 | Having just two platform offsets and having them saturate makes things SO much easier | 13:37:22 |
| emily | targetPlatform is bad, but I thought we were at least getting value out of it | 13:37:21 |
| K900 | To reason about | 13:37:26 |
| emily | GCC and wrappers should just take a target argument. | 13:37:47 |
| emily | it's rough when you need to build libraries for target though | 13:37:58 |
| K900 | Yeah, that's what I was thinking as well | 13:38:00 |
| K900 | Anything that's explicitly-targeted can just require specifying a target | 13:38:21 |
| K900 | Actually that also blows up Canadian cross | 13:38:38 |
| emily | yes, but pkgsTarget* gets hard | 13:38:37 |
| emily | it's rare though | 13:38:44 |
| K900 | Because there is no pkgsOnBuildForTarget | 13:38:46 |
| K900 | Technically pkgsTarget does not get hard in that setup, it just becomes normal cross | 13:39:35 |
| emily | uh. hm | 13:39:36 |
| K900 | Which does require another nixpkgs | 13:39:40 |
| K900 | But that's fine probably? | 13:39:47 |
| emily | isn't that just pkgsTargetTarget | 13:40:39 |
| emily | or pkgsTargetWhatever because the Whatever never matters in that case | 13:40:47 |
| emily | (if the target of your target-platform package matters you are living in sin) | 13:40:55 |
| K900 | It does if you're doing Canadian cross | 13:41:06 |
| emily | no | 13:41:17 |
| emily | at the time it matters it is the host-platform package's target | 13:41:25 |
| emily | the target of a target-platform package would be like… the GCC build wants to bundle a JIT library so that the built GCC can link it into target-platform executables, and that JIT library itself wants to target some other target | 13:42:09 |
| emily | that's when pkgsTargetHost vs. pkgsTargetTarget vs. whatever would matter I think. thankfully those don't exist | 13:42:32 |
| emily | but doesn't pkgsTargetTarget build on the build platform? | 13:42:40 |
| emily | maybe not. wow Nixpkgs sucks. wow splicing sucks | 13:42:48 |
