!rGlCMuXgAhgEpdvJUz:nixos.org

NixOS KDE

206 Members
57 Servers

Load older messages


SenderMessageTime
25 Sep 2025
@k900:0upti.meK900 ⚡️It fixes the media player applet QML crash06:42:03
27 Sep 2025
@amadaluzia:tchncs.deamadaluzia[tde] changed their profile picture.12:15:00
29 Sep 2025
@k900:0upti.meK900 ⚡️ @outfoxxed gave a very quick look to the Qt6 PR 05:35:25
@k900:0upti.meK900 ⚡️ @outfoxxed gave a very quick look to the Qt6 cross PR 05:35:33
@k900:0upti.meK900 ⚡️I think the core idea makes sense05:35:52
@k900:0upti.meK900 ⚡️I think there's a dumb typo in there05:35:52
@outfoxxed:outfoxxed.meoutfoxxedah where?05:36:05
@k900:0upti.meK900 ⚡️Commented05:36:12
@outfoxxed:outfoxxed.meoutfoxxeddid you submit the review, not showing up for me05:36:31
@k900:0upti.meK900 ⚡️ Can't promise much more due to gestures at current events 05:36:42
@k900:0upti.meK900 ⚡️Ah great github ate it I think05:37:38
@k900:0upti.meK900 ⚡️ Anyway there's both __nix_qtbase_check and __nix_check_qtbase and I think those should be one thing? 05:37:53
@k900:0upti.meK900 ⚡️Though I might be missing something and it is just a case of really questionable naming lol05:38:13
@outfoxxed:outfoxxed.meoutfoxxedone of those is _cross i think05:38:45
@outfoxxed:outfoxxed.meoutfoxxednot _check05:38:47
@outfoxxed:outfoxxed.meoutfoxxedsec05:38:50
@k900:0upti.meK900 ⚡️No, they are both _check05:39:02
@outfoxxed:outfoxxed.meoutfoxxedyep thats a typo05:39:30
@outfoxxed:outfoxxed.meoutfoxxedwere supposed to be the same thing05:39:37
@outfoxxed:outfoxxed.meoutfoxxedI guess I'm building qt again today05:40:02
@k900:0upti.meK900 ⚡️Also I think I now have the context to explain what I was saying before about nativeBuildInputs05:40:28
@k900:0upti.meK900 ⚡️My idea was to instead of doing what you did and propagating host tools everywhere05:40:41
@k900:0upti.meK900 ⚡️To build a special "cross Qt" for (build -> target)05:41:09
@k900:0upti.meK900 ⚡️So we have tools for build and libraries for target in the same package05:41:19
@k900:0upti.meK900 ⚡️And then we just use those everywhere05:41:24
@k900:0upti.meK900 ⚡️Which works without cmake patching but does lead to funni in Canadian use cases but no one does that anyway05:42:02
@outfoxxed:outfoxxed.meoutfoxxedI'm not sure what the advantage of that would be but I think that is an officially supported mode of operation05:42:10
@outfoxxed:outfoxxed.meoutfoxxedhonestly I'm not sure why I had to patch the cmake for this, it should work with a host build in one folder05:42:38
@k900:0upti.meK900 ⚡️ That is the officially supported mode of operation 05:42:39
@k900:0upti.meK900 ⚡️That's mostly the advantage yes05:42:39

Show newer messages


Back to Room ListRoom Version: 9