!rGlCMuXgAhgEpdvJUz:nixos.org

NixOS KDE

204 Members
56 Servers

Load older messages


SenderMessageTime
13 Jun 2025
@k900:0upti.meK900I'm trying to batch that with Frameworks 6.1515:54:33
@k900:0upti.meK900And Frameworks 6.15 is being annoying15:54:38
@k900:0upti.meK900They added qdoc to a lot of places15:54:50
@k900:0upti.meK900OK I think I'm about to just give up on strictDeps on this19:00:55
@k900:0upti.meK900It just doesn't work with cmake19:01:04
@k900:0upti.meK900We can kinda pretend it works for a while19:01:34
@k900:0upti.meK900But it just doesn't and I hate cmake19:01:42
@emilazy:matrix.orgemily is our CMake patch to fix strictDeps not working? 19:06:41
@k900:0upti.meK900Not all the way19:08:32
@k900:0upti.meK900It helps but it doesn't fully solve the problem19:08:53
@k900:0upti.meK900And the problem is that cmake is a giant blob of global state that is entirely shared between build and host19:09:07
@emilazy:matrix.orgemilythey do at least have variables that are meant to distinguish the two19:17:19
@emilazy:matrix.orgemilythey might not be good at it though19:17:21
@k900:0upti.meK900 The fundamental mismatch here is that in the cmake/qt world, you're supposed to build an entire Qt package as cross 19:20:55
@k900:0upti.meK900And then its crossness is encoded into the output19:21:04
@k900:0upti.meK900Like, it will just make build tools and host libraries and encode that knowledge into its cmake files19:21:20
@k900:0upti.meK900And when we try and give it what it thinks are two distinct Qts, one host and one build, it explodes19:21:41
@emilazy:matrix.orgemilywhy would we give it two?19:22:12
@k900:0upti.meK900Because one is nativeBuildInputs and the other is buildInputs19:22:23
@emilazy:matrix.orgemily it's okay for a cross-built package to contain buildPlatform tools 19:22:31
@emilazy:matrix.orgemily we handle some *-configs like that 19:22:39
@k900:0upti.meK900Because we want it to use the host tools19:22:40
@qyliss:fairydust.spaceAlyssa RossThis sounds like it should just be in nativeBuildInputs19:23:06
@k900:0upti.meK900I guess technically the strictDeps-ly-correct way of doing this would be to shove everything into buildInputs19:23:06
@qyliss:fairydust.spaceAlyssa RossSame deal as with a compilerr19:23:10
@k900:0upti.meK900And pretend nativeBuildInputs don't exist19:23:12
@qyliss:fairydust.spaceAlyssa Ross * 19:23:14
@k900:0upti.meK900Actually yes the opposite19:23:25
@qyliss:fairydust.spaceAlyssa RossNo, the opposite19:23:27
@k900:0upti.meK900Because it doesn't search for binaries in buildInputs19:23:38

Show newer messages


Back to Room ListRoom Version: 9