!rGlCMuXgAhgEpdvJUz:nixos.org

NixOS KDE

190 Members
54 Servers

Load older messages


SenderMessageTime
29 Sep 2025
@outfoxxed:outfoxxed.meoutfoxxedI was going to follow up on this with a pr removing propagation if possible05:47:54
@outfoxxed:outfoxxed.meoutfoxxedfor now I figure cross working is better than cross not working05:48:10
@outfoxxed:outfoxxed.meoutfoxxedqt also likes to special case things on CMAKE_CROSSBUILD (or a similar name) which is not helpful05:49:39
@outfoxxed:outfoxxed.meoutfoxxedI made the assumption that nix users cross building would prefer the package be as close as possible to a native build05:49:57
@outfoxxed:outfoxxed.meoutfoxxedthey seem to assume an embedded target and dont build half the tools05:50:16
@outfoxxed:outfoxxed.meoutfoxxedand the one probably most relevant to kde, or 90% of qt packages in nixpkgs is that pyside still doesn't work05:53:44
@k900:0upti.meK900We could skip pyside on cross05:54:33
@k900:0upti.meK900At least for now05:54:51
@outfoxxed:outfoxxed.meoutfoxxedI tried skipping it and most of qt failed to build expecting shiboken605:55:23
@outfoxxed:outfoxxed.meoutfoxxed*most of kde05:55:28
@outfoxxed:outfoxxed.meoutfoxxedpackages in the core dep tree for most important kde things at least05:55:47
@outfoxxed:outfoxxed.meoutfoxxedI don't know if theres a cmake flag to get around that, didn't check05:55:58
@k900:0upti.meK900There is05:56:01
@k900:0upti.meK900It's what we're setting when hasPythonWhatever but backwards05:56:16
@outfoxxed:outfoxxed.meoutfoxxedprobably a good idea for now then. I tried to get shiboken working as well but the stdenv was fucked somehow in cross05:56:40
@outfoxxed:outfoxxed.meoutfoxxed(after fixing the wrong things being in buildinputs/nativebuildinputs)05:56:55
4 Oct 2025
@aidalgol:tchncs.de@aidalgol:tchncs.de left the room.00:51:27
5 Oct 2025
@marie:marie.cologneMarie does KDE upstream know about the issue that apps start up really slow when $XDG_DATA_DIRS has so many entries? 15:57:11
@k900:0upti.meK900 Very roughly, yes, but also I don't think there's going to be a solution any time soon 16:22:42
@k900:0upti.meK900 Because this is not something Qt will normally run into 16:23:00
@k900:0upti.meK900 And you'd have to do some kind of special case optimization for this stuff 16:23:09
@marie:marie.cologneMarieAnd we can't do anything about it from our side?16:27:24
@k900:0upti.meK900One thing we could do is try and reduce the number of things that end up in XDG_DATA_DIRS16:27:54
@k900:0upti.meK900Some of that was already done in 25.11 but there's potentially more16:28:03
@k900:0upti.meK900 Honestly I'm personally not very interested in hyperoptimizing this because on fast enough storage it kinda becomes a non-issue 16:28:49
@k900:0upti.meK900Like yes we are still slower but it's not a relevant amount of slower16:29:10
@marie:marie.cologneMarieit's very noticeable to me tbh16:29:37
@sandro:supersandro.deSandro 🐧Isn't that the main source that every KDE application takes like 3 seconds to open?16:31:50
@sandro:supersandro.deSandro 🐧eg: first time starting krunner takes a good amount of time16:32:06
@k900:0upti.meK900 I have no idea where you're getting 3 seconds tbh 16:32:26

Show newer messages


Back to Room ListRoom Version: 9