qtwebengine: replace targetPlatform with hostPlatform#267292
Conversation
stdenv.targetPlatform really shouldn't be used by software that doesn't generate or manipulate binaries. I did a mass-replacement in #267229 and it affected eval for only two packages; one of them is qt6-qtwebengine, but it is affected only on Darwin. So I am breaking this out into a separate PR.
|
I bet the difference on darwin is coming from nixpkgs/pkgs/os-specific/darwin/apple-sdk-11.0/default.nix Lines 66 to 69 in 7206143 which overrides And this is presumably per the upstream platform support being macOS 11, 12, 13 but nothing older. So, while this change seems logically correct (qtWebEngine isn't a cross-compiler and should use Either that or qtwebengine should just be literally coding CMAKE_OSX_DEPLOYMENT_TARGET=11.0 (the minimum per upstream's requirements), and not trying to make different binaries per host revision. greping nixpkgs for CMAKE_OSX_DEPLOYMENT_TARGET seems to find that more often, and it would make for fewer distinct builds... |
|
Also seems like nixpkgs/pkgs/development/libraries/qt-6/default.nix Lines 28 to 31 in 91ac57c https://nixos.org/manual/nixpkgs/unstable/#sec-darwin says
So it seems like this perhaps should be using the whole I don't have any |
Yes, and this has actually been reported in #238993 (comment). So for now
Yes, once again. A modern approach would be |
Description of changes
stdenv.targetPlatformreally shouldn't be used by software that doesn't generate or manipulate binaries.I did a mass-replacement in #267229 and it affected eval for only two packages; one of them is qt6-qtwebengine, but it is affected only on Darwin. So I am breaking this out into a separate PR.
Things done
nix.conf? (See Nix manual)sandbox = relaxedsandbox = truenix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/)