| 16 Jun 2025 |
 emily | like I realize that's enough of a project that it can't block a version bump | 05:28:45 |
| emily | but enough things expect build platform tools that standardizing a way to make that work with buildInputs would help a lot IMO | 05:29:24 |
 K900 | Yeeeeeeeeah | 05:32:32 |
| K900 | I think I am going to just slap things into nativeBuildInputs for now | 05:32:42 |
| K900 | As much as I hate it | 05:33:18 |
| emily | what kind of tools do things even expect anyway? | 05:33:19 |
| emily | Qt's whole build situation has always confused me. | 05:33:29 |
| emily | so much preprocessing stuff | 05:33:35 |
| K900 | It's not even tools really, it's just some cmake nonsense | 05:33:37 |
| K900 | There's LAYERS | 05:33:42 |
| emily | well it's about finding binaries right? | 05:33:46 |
| emily | or no? | 05:33:50 |
| K900 | Not quite | 05:34:15 |
| K900 | It's not really finding specific things | 05:34:29 |
| K900 | It's finding "Qt" | 05:34:32 |
| K900 | Whatever that means | 05:34:37 |
| K900 | If you want to dig into it, give me another like hour | 05:37:38 |
| K900 | So I can add all the nativeBuildInputs everywhere | 05:37:50 |
| K900 | And then I can push it and you can see what happens if you take those out | 05:37:58 |
| K900 | OK I no longer understand anything | 08:30:43 |
| K900 | Some Qt packages are fine being in buildInputs | 08:30:50 |
| K900 | Some only get found from nativeBuildInputs | 08:30:58 |
| K900 | e.g. qtmultimedia wants to be in nativeBuildInputs, but qtsvg is fine being in buildInputs | 08:31:21 |
| K900 | Neither contains a single executable | 08:31:27 |
| K900 | angelfish only builds when qtwebengine is in both | 08:34:41 |
| emily | anything obviously different about the CMake logic searching for them? | 09:08:32 |
| K900 | No idea | 09:24:20 |
| K900 | I have not looked yet | 09:24:22 |
| K900 | I am still bashing my head against getting it all to even build again | 09:24:30 |
| K900 | Down to only a few packages though | 09:24:46 |
