David Craven writes:
> Hi
>
>>> Hi, I just sent a patch to add 'QMAKEPATH' as search-path, which should
>>> fix this issue.
>
>> Thank you! Yes this fixes the issue and is a lot cleaner than what I
>> came up with...
>
> I sent a couple of patches to the mailing list that will require the
> qt an
Hi
>> Hi, I just sent a patch to add 'QMAKEPATH' as search-path, which should
>> fix this issue.
> Thank you! Yes this fixes the issue and is a lot cleaner than what I
> came up with...
I sent a couple of patches to the mailing list that will require the
qt and kde packages to be rebuilt (like t
> Hi, I just sent a patch to add 'QMAKEPATH' as search-path, which should
> fix this issue.
Thank you! Yes this fixes the issue and is a lot cleaner than what I
came up with...
David Craven writes:
> [...]
>
>> cat >"$out/bin/qt.conf" <> [Paths]
>> Prefix = $out
>> Plugins = lib/qt5/plugins
>> Imports = lib/qt5/imports
>> Qml2Imports = lib/qt5/qml
>> Documentation = share/doc/qt5
>> EOF
>
> I am not sure what the best way to proceed is, since $out should be
> $GUIX_ENVI
Hi Andreas,
> This makes me think that "qtHaveModule" does not work; and I wonder whether
> in our other Qt modules that have Qt modules as input, these are actually
> detected correctly. Well, I tried qtsensors, and did not notice this problem.
Trying to package the missing qt modules I came to
