diff options
| author | Adam Joseph <adam@westernsemico.com> | 2023-03-08 23:52:17 -0800 |
|---|---|---|
| committer | Adam Joseph <adam@westernsemico.com> | 2023-03-09 03:37:08 -0800 |
| commit | fa9659e0defbdab1693e708a8063403f826f931c (patch) | |
| tree | 68aeaafcc2abb254f2cab6313d316edc3499d7bd /pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch | |
| parent | cdd98d390043c5bf8ac1d1e45eaed767349fbdec (diff) | |
qt-5/hooks/fix-qt-builtin-paths.sh: do not hardcode output paths
The fix-qt-builtin-paths.sh script replaces several strings in *.pr*
files with output names; for example
```
$$[QT_HOST_BINS] is replaced by $dev
```
This causes problems when cross-compiling: the `mkspecs/qconfig.pri`
in the `$dev` output of `qtbase` will have output names *of qtbase*
hardwired into it. Since `qmake` is part of the `qtbase` package,
it will pick up these hardcoded paths when compiling the other
modules.
As a result, the `installPhase` of `qtdeclarative` (and other
modules) will attempt to copy their results into the
already-registered store path for `qtbase`. This will fail, because
Nix prevents writes to a storepath after it has been registered.
Fortunately the `.pri` files understand environment variable
substitution: you can write `$$NIX_OUTPUT_DEV` to tell `qmake` that
it should use the value of the `NIX_OUTPUT_DEV` environment variable
*at `qmake`-run-time* (rather than at `qmake`-build-time).
Diffstat (limited to 'pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch')
0 files changed, 0 insertions, 0 deletions
