My Qt 5.14.1 build fails on qtquick3dutils

bunjee207

Greetings trolls and Qt enthuisasts,

I'm trying to build Qt with the following:

./configure -release \
            -xplatform linux-arm-gnueabi-g++ \
            -opensource \
            -confirm-license \
            -nomake examples \
            -skip qttools \
            -skip qt3d \
            -skip qtquick3d \
            -skip qtwebengine \
            -skip qtdoc \
            -no-opengl \
            -verbose

For some reason I get the following:

/builds/3rd-party/qt5-arm/qt-everywhere-src-5.14.1/qtbase/bin/qmake -install qinstall /builds/3rd-party/qt5-arm/qt-everywhere-src-5.14.1/qtquick3d/src/utils/qtquick3dutilsglobal_p.h /builds/3rd-party/qt5-arm/qt-everywhere-src-5.14.1/../install/usr/local/Qt-5.14.1/include/QtQuick3DUtils/5.14.1/QtQuick3DUtils/private/qtquick3dutilsglobal_p.h
/builds/3rd-party/qt5-arm/qt-everywhere-src-5.14.1/qtbase/bin/qmake -install qinstall /builds/3rd-party/qt5-arm/qt-everywhere-src-5.14.1/qtquick3d/mkspecs/modules-inst/qt_lib_quick3dutils.pri /builds/3rd-party/qt5-arm/qt-everywhere-src-5.14.1/../install/usr/local/Qt-5.14.1/mkspecs/modules/qt_lib_quick3dutils.pri
/builds/3rd-party/qt5-arm/qt-everywhere-src-5.14.1/qtbase/bin/qmake -install qinstall /builds/3rd-party/qt5-arm/qt-everywhere-src-5.14.1/qtquick3d/mkspecs/modules-inst/qt_lib_quick3dutils_private.pri /builds/3rd-party/qt5-arm/qt-everywhere-src-5.14.1/../install/usr/local/Qt-5.14.1/mkspecs/modules/qt_lib_quick3dutils_private.pri
/builds/3rd-party/qt5-arm/qt-everywhere-src-5.14.1/qtbase/bin/qmake -install qinstall /builds/3rd-party/qt5-arm/qt-everywhere-src-5.14.1/qtquick3d/lib/cmake/Qt5Quick3DUtils/Qt5Quick3DUtilsConfig.cmake /builds/3rd-party/qt5-arm/qt-everywhere-src-5.14.1/../install/usr/local/Qt-5.14.1/lib/cmake/Qt5Quick3DUtils/Qt5Quick3DUtilsConfig.cmake
/builds/3rd-party/qt5-arm/qt-everywhere-src-5.14.1/qtbase/bin/qmake -install qinstall /builds/3rd-party/qt5-arm/qt-everywhere-src-5.14.1/qtquick3d/lib/cmake/Qt5Quick3DUtils/Qt5Quick3DUtilsConfigVersion.cmake /builds/3rd-party/qt5-arm/qt-everywhere-src-5.14.1/../install/usr/local/Qt-5.14.1/lib/cmake/Qt5Quick3DUtils/Qt5Quick3DUtilsConfigVersion.cmake
make[3]: Leaving directory '/builds/3rd-party/qt5-arm/qt-everywhere-src-5.14.1/qtquick3d/src/utils'
cd render/ && ( test -e Makefile || /builds/3rd-party/qt5-arm/qt-everywhere-src-5.14.1/qtbase/bin/qmake -o Makefile /builds/3rd-party/qt5-arm/qt-everywhere-src-5.14.1/qtquick3d/src/render/render.pro ) && make -f Makefile install
Project ERROR: Unknown module(s) in QT: openglextensions
Makefile:119: recipe for target 'sub-render-install_subtargets-ordered' failed
make[2]: *** [sub-render-install_subtargets-ordered] Error 3
make[2]: Leaving directory '/builds/3rd-party/qt5-arm/qt-everywhere-src-5.14.1/qtquick3d/src'
make[1]: *** [sub-src-install_subtargets] Error 2
Makefile:61: recipe for target 'sub-src-install_subtargets' failed
make[1]: Leaving directory '/builds/3rd-party/qt5-arm/qt-everywhere-src-5.14.1/qtquick3d'
make: *** [module-qtquick3d-install_subtargets] Error 2
Makefile:374: recipe for target 'module-qtquick3d-install_subtargets' failed

Which bothers me on two sides, first I'm building with no-opengl and second I'm skipping the qtquick3d module. Am I missing something there ?

Thanks a lot.

SGaist

Hi,

I would go another way. Start by building qtbase and then you can build the other modules you need one after the other.

bunjee207

@SGaist, I could try that.

But I'm building Qt 5.12.1 just fine with that script and I would very much like to solve that qtquick3d module issue.

I'm building for a Xilinx Zynq embedded platformn so I have a little bit of a constraint regarding OpenGL.

SGaist

I understand that.

AFAICT, the module is new with Qt 5.14 so you might be in a case that is not yet handled for it.

Two things I would do:

Check the bug report system to see if there's something related to it (building it with OpenGL disabled). It might still be possible because of the Qt Quick 2D renderer but I don't know.
Delete the qtquick3d folder so you don't even have to skip it and it won't be processed at all. This is still a workaround but at least you should be safe from that issue.