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...
> I am not sure what the best way to proceed is, since $out should be
> $GUIX_ENVIRONMENT,
> but $GUIX_ENVIRONMENT isn't known when we build qtbase. What I think
> needs to happen
> for QtHaveModule to work is we need to generate a qt.conf file when a
> guix environment is
> creat
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 q
changed.
The error messages come from
qtwebkit-opensource-src-5.6.1/Tools/qmake/mkspecs/features/features.prf:
qtHaveModule(quick): WEBKIT_CONFIG += have_qtquick
else: CONFIGURE_WARNINGS += "QtQuick module not found, QML APIs will not be
built"
...
# HTML5 Media Support for b
