Repository navigation
Fix Nix build: point qmake at qttools' lrelease binary - #73
Conversation
qmake's qtPrepareTool() macro hardcodes tool lookups (like lrelease) to qtbase's own store output at mkspecs-generation time. On nixpkgs, lrelease lives in kdePackages.qttools instead, which is a separate derivation, so the build failed with "No such file or directory" once CONFIG += lrelease was introduced. Pass QT_TOOL.lrelease.binary explicitly on the qmake command line to point at the real binary.
|
I don't know much about .nix ecosystem but this seems to create hard dependency on KDE framework, is the .nix always combined only with KDE and nothing else? |
Do you mean the nativeBuildInputs = with pkgs.kdePackages; [ qmake qttools wrapQtAppsHook ];
buildInputs = with pkgs.kdePackages; [ qtbase ];which is shorthand for nativeBuildInputs = [ pkgs.kdePackages.qmake pkgs.kdePackages.qttools pkgs.kdePackages.wrapQtAppsHook ];
buildInputs = [ pkgs.kdePackages.qtbase ];So |
|
now I get it, I am not familiar with nix at all (that entire nix file was added into repo by someone else), from that diff alone this wasn't obvious |
qmake's qtPrepareTool() macro hardcodes tool lookups (like lrelease) to qtbase's own store output at mkspecs-generation time. On nixpkgs, lrelease lives in kdePackages.qttools instead, which is a separate derivation, so the build failed with "No such file or directory" once CONFIG += lrelease was introduced. Pass QT_TOOL.lrelease.binary explicitly on the qmake command line to point at the real binary.
This was broken by #71