Building qt 5.9.7 on CentOS 7 completes but qtsvg seems to be missing

yryu4526

Could you explain a bit further, what do you mean by "installed in your custom build"? Two messages up I pasted the qt section of the build profile for the other app.

yryu4526

Just for "fun" I removed the svg reference in the qt section of the build profile for the third-party app and I could begin building it. However, it failed late in the build process when it tried to access qtsvg.

I have to believe there is something wrong with the setup since the qtsvg modules are not picked up. Might there be some bug in qt 5.9.7 itself that does not make qtsvg available? Or some setup configuration I have missed since although it builds, it does not seem to be available later...

Is there any way I can test this hypothesis outside my third-party app?

SGaist

@yryu4526 said in Building qt 5.9.7 on CentOS 7 completes but qtsvg seems to be missing:

Could you explain a bit further, what do you mean by "installed in your custom build"? Two messages up I pasted the qt section of the build profile for the other app.

Take a look into the folder that was populated after you called "make install". Do you find anything related to QtSvg ?

yryu4526

That would be, I believe, /usr/local/Qt-5.9.7/lib and it does contain libQt5Svg.so.5.9.7.

SGaist

Ok, do you have the same issue if you create a small dummy project using that module ?

yryu4526

I do not know, I do not have the skills to create a new project. I asked earlier if there are any test programs in qt that I can use to check the status post-compilation?

mrjj

@yryu4526
Hi
You can just use Creator and the menu File->"New File Or project"
and then
alt text

then add
QT += svg
in the pro file and see if that compiles.

just in case you dont have creator.
here is default project created with thw wizard
https://www.dropbox.com/s/vvz5s4yhka68uui/justDefualt.zip?dl=0

yryu4526

I downloaded the file into a new directory, ran "qmake -r justDefualt.pro" and got the following output:
Info: creating stash file /root/test/.qmake.stash
Project ERROR: Unknown module(s) in QT: svg

Note that I am running as root in a docker container, not on the main machine itself.

SGaist

And the qmake is from your self compiled Qt ?

yryu4526

Correct, it's located in /root/qt5-build/qtbase/bin. I am wondering, since I am doing this in a docker container, there might be some configuration issue?

This is the output after running the first ./configure command (../qt5/configure -opensource -prefix /usr/lib64 -nomake examples -skip qtquick1 | tee -a /qt-build.txt)
:
Configure summary:

Build type: linux-g++ (x86_64, CPU features: mmx sse sse2)
Configuration: use_gold_linker sse2 sse3 ssse3 sse4_1 sse4_2 avx avx2 avx512f avx512bw avx512cd avx512dq avx512er avx512ifma avx512pf avx512vbmi avx512vl compile_examples enable_new_dtags f16c largefile precompile_header shared rpath release c++11 c++14 c++1z concurrent dbus reduce_exports reduce_relocations stl
Build options:
Mode ................................... release
Optimize release build for size ........ no
Building shared libraries .............. yes
Using C++ standard ..................... C++1z
Using ccache ........................... no
Using gold linker ...................... yes
Using new DTAGS ........................ yes
Using precompiled headers .............. yes
Using LTCG ............................. no
Target compiler supports:
SSE .................................. SSE2 SSE3 SSSE3 SSE4.1 SSE4.2
AVX .................................. AVX AVX2 F16C
AVX512 ............................... F ER CD PF DQ BW VL IFMA VBMI
Build parts ............................ libs tools
Qt modules and options:
Qt Concurrent .......................... yes
Qt D-Bus ............................... yes
Qt D-Bus directly linked to libdbus .... yes
Qt Gui ................................. yes
Qt Network ............................. yes
Qt Sql ................................. yes
Qt Testlib ............................. yes
Qt Widgets ............................. yes
Qt Xml ................................. yes
Support enabled for:
Using pkg-config ....................... yes
QML debugging .......................... yes
udev ................................... no
Using system zlib ...................... yes
Qt Core:
DoubleConversion ....................... yes
Using system DoubleConversion ........ no
GLib ................................... yes
iconv .................................. no
ICU .................................... yes
Logging backends:
journald ............................. no
syslog ............................... no
slog2 ................................ no
Using system PCRE2 ..................... no
Qt Network:
getaddrinfo() .......................... yes
getifaddrs() ........................... yes
IPv6 ifname ............................ yes
libproxy ............................... no
OpenSSL ................................ yes
Qt directly linked to OpenSSL ........ no
SCTP ................................... no
Use system proxies ..................... yes
Qt Gui:
Accessibility .......................... yes
FreeType ............................... yes
Using system FreeType ................ yes
HarfBuzz ............................... yes
Using system HarfBuzz ................ yes
Fontconfig ............................. yes
Image formats:
GIF .................................. yes
ICO .................................. yes
JPEG ................................. yes
Using system libjpeg ............... no
PNG .................................. yes
Using system libpng ................ yes
EGL .................................... no
OpenVG ................................. no
OpenGL:
Desktop OpenGL ....................... yes
OpenGL ES 2.0 ........................ no
OpenGL ES 3.0 ........................ no
OpenGL ES 3.1 ........................ no
Session Management ..................... yes
Features used by QPA backends:
evdev .................................. yes
libinput ............................... no
INTEGRITY HID .......................... no
mtdev .................................. no
tslib .................................. no
xkbcommon-evdev ........................ yes
QPA backends:
DirectFB ............................... no
EGLFS .................................. no
LinuxFB ................................ yes
VNC .................................... yes
Mir client ............................. no
X11:
Using system-provided XCB libraries .. yes
EGL on X11 ........................... no
Xinput2 .............................. yes
XCB XKB .............................. yes
XLib ................................. yes
XCB render ........................... yes
XCB GLX .............................. yes
XCB Xlib ............................. yes
Using system-provided xkbcommon ...... yes
Qt Widgets:
GTK+ ................................... no
Styles ................................. Fusion Windows
Qt PrintSupport:
CUPS ................................... yes
Qt Sql:
DB2 (IBM) .............................. no
InterBase .............................. no
MySql .................................. no
OCI (Oracle) ........................... no
ODBC ................................... no
PostgreSQL ............................. yes
SQLite2 ................................ no
SQLite ................................. yes
Using system provided SQLite ......... no
TDS (Sybase) ........................... no
Qt SerialBus:
Socket CAN ............................. yes
Socket CAN FD .......................... yes
QtXmlPatterns:
XML schema support ..................... yes
Qt QML:
QML interpreter ........................ yes
QML network support .................... yes
Qt Quick:
Direct3D 12 ............................ no
AnimatedImage item ..................... yes
Canvas item ............................ yes
Support for Qt Quick Designer .......... yes
Flipable item .......................... yes
GridView item .......................... yes
ListView item .......................... yes
Path support ........................... yes
PathView item .......................... yes
Positioner items ....................... yes
ShaderEffect item ...................... yes
Sprite item ............................ yes
Qt Gamepad:
SDL2 ................................... no
Qt 3D:
Assimp ................................. yes
System Assimp .......................... no
Output Qt3D Job traces ................. no
Output Qt3D GL traces .................. no
Qt 3D GeometryLoaders:
Autodesk FBX ........................... no
Qt Wayland Client ........................ no
Qt Wayland Compositor .................... no
Qt Bluetooth:
BlueZ .................................. no
BlueZ Low Energy ....................... no
Linux Crypto API ....................... no
Qt Sensors:
sensorfw ............................... no
Qt Quick Controls 2:
Styles ................................. Default Material Universal
Qt Quick Templates 2:
Hover support .......................... yes
Multi-touch support .................... yes
Qt Positioning:
Gypsy GPS Daemon ....................... no
WinRT Geolocation API .................. no
Qt Location:
Geoservice plugins:
OpenStreetMap ........................ yes
HERE ................................. yes
Esri ................................. yes
Mapbox ............................... yes
MapboxGL ............................. yes
Itemsoverlay ......................... yes
Qt Multimedia:
ALSA ................................... yes
GStreamer 1.0 .......................... no
GStreamer 0.10 ......................... no
Video for Linux ........................ yes
OpenAL ................................. no
PulseAudio ............................. yes
Resource Policy (libresourceqt5) ....... no
Windows Audio Services ................. no
DirectShow ............................. no
Windows Media Foundation ............... no
Qt WebEngine:
Embedded build ......................... no
Pepper Plugins ......................... yes
Printing and PDF ....................... yes
Proprietary Codecs ..................... no
Spellchecker ........................... yes
WebRTC ................................. yes
Using system ninja ..................... no
ALSA ................................... yes
PulseAudio ............................. yes
System libraries:
re2 .................................. no
ICU .................................. no
libwebp and libwebpdemux ............. no
Opus ................................. no
ffmpeg ............................... no

Note: Also available for Linux: linux-clang linux-icc

Note: Dropped compiler flags '-pthread' when detecting library 'glib'.

Note: No wayland-egl support detected. Cross-toolkit compatibility disabled.

Qt is now configured for building. Just run 'gmake'.
Once everything is built, you must run 'gmake install'.
Qt will be installed into '/usr/lib64'.

Is there something above that does /not/ look correct?

SGaist

Did you call make install ?
You can also skip building the tests.

I find it strange that QtSvg is not listed. Did you parse them tests logs to see if anything has failed for it ?

Did you try to manually build it after the rest was built ?

yryu4526

Yes, I called make install and I did try building it manually - I already posted that previously.

But should svg have been listed in the configuration summary I posted?? It seems odd other qt components are listed but since I am not very knowledgeable I do not know if this means anything.

SGaist

What about the test logs ?

yryu4526

I have to look for them but my impression so far is that qtsvg is build but for some reason not picked up by qmake for the third-party app, nor for the test app given to me. Can I check this some way?

SGaist

All the modules should have the same structure once installed. Check the presence of files related to svg. Not only the libraries but also the cmake/qmake related ones.

yryu4526

What does "cmake/qmake related ones" mean? What exactly and where should I be looking for those files?

SGaist

cmake files in lib/cmake for exemple.

yryu4526

I was finally able to build the third-party application using both Qt 5.9.7 and 5.12.10. The problem I had above was due to the fact that I called the wrong qmake when building the third-party application.

I did, however have to use the flag -skip qtquick1 when building 5.9.7 and -skip qtwebengine when building 5.12.10.

I then decided to build the app using statically linked Qt-libraries using the flag -static for qmake but this has not been successful. The statically built app crashes with a segmentation fault. Note that in both scenarios I built in a docker container with the same software being installed in the container. The only difference is the -static flag.

I will create a new thread for this problem.