| 6 Sep 2024 |
 K900 | Currently the answer is "you can't" | 13:42:10 |
| K900 | It needs some pretty invasive surgery | 13:42:20 |
| K900 | Definitely qtwebengine | 13:43:11 |
| K900 | The rest should be fixable with some, uh, less invasive surgery potentially | 13:43:22 |
 Kamilla 'ova | okay , without qtwe, at least... does anyone have any ideas about qtwayland? | 13:50:29 |
| Kamilla 'ova | * okay, without qtwe, at least... does anyone have any ideas about qtwayland? | 13:50:33 |
| K900 | You'd have to go in and fix it, basically | 13:51:25 |
| K900 | cmake cross is fundamentally Very Weird | 13:51:30 |
| K900 | Qt should conceptually cross-compile but they have a weird somewhat custom process for it | 13:52:28 |
| K900 | And at least at some point in the past qtwayland just did not cross-compile at all | 13:52:53 |
| K900 | I'm not sure if they've fixed that | 13:52:56 |
| Kamilla 'ova | In reply to @k900:0upti.me
You'd have to go in and fix it, basically well, I'm basically trying to do this, but my progress has stopped at building buildPackages.qtquick3d (first monospaced block of my message above) | 13:54:18 |
| K900 | Go in and fix it as in figure out what's going wrong and why and then fix it | 13:54:51 |
| K900 | If we knew a way to fix that we would have done that already | 13:55:14 |
| Kamilla 'ova | In reply to @k900:0upti.me
I'm not sure if they've fixed that I think, yes, because it somehow works on yocto | 13:55:18 |
| K900 | (we as in Qt maintainers) | 13:55:18 |
|  vramp joined the room. | 17:50:17 |
| vramp | I am struggling with using the cross compilation nixpkgs in a nix shell for development. When I use the package for my architecture (x86 64 linux), my build tool (zig) sees the system libraries and headers. When I switch my shell to use the cross compiliation packages (aarch64 multiplatform), I have to explicitly find the store paths in my NIX_LDFLAGS and NIX_CFLAGS_COMPILE and add them, but then I can cross compile fine. Is there maybe some Arch-dependent path/env var convention of GCC that zig lacks? Is there an example of how to get the lib and header store paths in my shell.nix (like, to set them to environment variables) so that I can pass them to my build tool? | 18:07:15 |
| K900 | Our GCC is wrapped specifically to find things correctly | 18:07:41 |
| K900 | Your presumably-external zig probably isn't | 18:07:53 |
| vramp | ah, i am using an external zig binary at the moment, i can try with a zig from nixpkgs to see if there is some magic that someone has added to that recipe | 18:10:04 |
 Curid | is there some ultra-pure option that masks system libs? | 18:41:16 |
| K900 | What system libs? | 18:43:07 |
| Curid | Everything in /usr/that isn't provided by the shell | 18:59:23 |
| Curid | * Everything in /usr/that isn't provided by the nix-shell | 18:59:33 |
| K900 | Oh, on non-NixOS? No, not really | 19:00:16 |
| Curid | Maybe it'd enter a chroot and only symlink the nix-shell files | 19:00:26 |
| K900 | But you could do --ignore-environment to at least remove things from PATH | 19:00:27 |
 Artturin | nix in fakechroot maybe 🤔 | 19:41:47 |
| Artturin | There's a way to enter the build sandbox but I can't remember what the program is | 19:45:52 |
