Installation and Deployment

Thanks !

The error message comes with a link to https://github.com/probonopd/linuxdeployqt/issues/340 where you get the full explanation about the message. It also talks about the -unsupported-allow-new-glibc option.

@sierdzio said in download qt is slow from Prague(Czech Republic): I think picking other mirrors is possible in online installer, too, but I can't find proper links for that now. nothing precompiled afaik, but here's the git repo from @JKSH https://github.com/JKSH/QtSdkRepoChooser

hi guys finally I got success in installing Qt on my PC Just created new folder and installed all versions of MinGW from Developer and Designer Tools and its working now.. Thanks for help :)

Hi and welcome to devnet, What version of Qt are you trying to build ? Why do you want to build Qt yourself ? What platform are you running ?

@VietThan Yes. First is the Qt version (in this case Qt 5.12.1 built using Min GW 7.3.0 64 compiler), second one (in Tools) is the compiler itself. You always have to use same compiler which was used to build Qt. The reason is that different C++ compilers are not compatible with each other.

Hi everyone and thank you all for investigating this issue. @SGaist We managed to find a Visual Studio 6 installation to run and compile on the WinXP machine. We found out that in the SDK, there was some VC++ 6 files, like *dsw. It actually does compile simple examples from the SDK. Of course, we need to understand how the whole library works. However, I do not know how to check about the MinGW compiler. I was told it could work and I am currently downloading qt-opensource-windows-x86-mingw492-5.5.1.exe @mrjj There are a lot of libraries available in the SDK. When we try to use a command to open the camera, we get an error like Dll access violation. Choosing a compiler is not something we are familiar to! I personnally code small interfaces with Visual Studio 2017 with Qt 5.6 and it is very fun. But going back more than 10 years, I feel like I missed something. @KroMignon Well that is what I wanted to know: How to build from sources? @Pablo-J-Rogina Our supervisor is not willing to test it on another machine. It is his only camera with no spare and he does not want to try, as the IT tech told him. We are thinking of doing a small local network in order to share the image to another machine, with proper tools to develop a more up-to-date application.

Hi and welcome to devnet, You don't need to do that. Your distribution already provides Qt 4.8.7. You should use that one as it will have proper OpenSSL support directly.

Okay, I did find an error in the config.log: > C:\qt-everywhere-src-5.12.1\qtwebengine\config.tests\winversion\winversion.cpp(30): fatal error C1189: #error: unsupported Visual Studio version > jom: C:\qt-build-lib\config.tests\winversion\Makefile [winversion.obj] Error 2 test config.qtwebengine_core.tests.webengine-winversion FAILED It seems odd this didn't show up in the config summary: Build type: win32-msvc (i386, CPU features: sse sse2) Compiler: msvc 191627027 Configuration: sse2 aesni sse3 ssse3 sse4_1 sse4_2 avx avx2 avx512f avx512bw avx512cd avx512dq avx512er avx512ifma avx512pf avx512vbmi avx512vl compile_examples f16c largefile precompile_header rdrnd shani x86SimdAlways shared debug_and_release release debug build_all c++11 c++14 c++1z concurrent dbus no-pkg-config release_tools stl Build options: Mode ................................... debug and release; default link: debug; optimized tools Optimize release build for size ........ no Building shared libraries .............. yes Using C standard ....................... C89 Using C++ standard ..................... C++1z Using gold linker ...................... no Using precompiled headers .............. yes Using LTCG ............................. no Target compiler supports: SSE .................................. SSE2 SSE3 SSSE3 SSE4.1 SSE4.2 AVX .................................. AVX AVX2 AVX512 ............................... F ER CD PF DQ BW VL IFMA VBMI Other x86 ............................ AES F16C RDRAND SHA Build parts ............................ libs tools App store compliance ................... no Qt modules and options: Qt Concurrent .......................... yes Qt D-Bus ............................... yes Qt D-Bus directly linked to libdbus .... no Qt Gui ................................. yes Qt Network ............................. yes Qt Sql ................................. yes Qt Testlib ............................. yes Qt Widgets ............................. yes Qt Xml ................................. yes Support enabled for: Using pkg-config ....................... no udev ................................... no Using system zlib ...................... no Qt Core: DoubleConversion ....................... yes Using system DoubleConversion ........ no GLib ................................... no iconv .................................. no ICU .................................... no Tracing backend ........................ <none> Logging backends: journald ............................. no syslog ............................... no slog2 ................................ no Using system PCRE2 ..................... no Qt Network: getifaddrs() ........................... no IPv6 ifname ............................ no libproxy ............................... no OpenSSL ................................ no Qt directly linked to OpenSSL ........ no OpenSSL 1.1 ............................ no DTLS ................................... no SCTP ................................... no Use system proxies ..................... yes Qt Gui: Accessibility .......................... yes FreeType ............................... yes Using system FreeType ................ no HarfBuzz ............................... yes Using system HarfBuzz ................ no Fontconfig ............................. no Image formats: GIF .................................. yes ICO .................................. yes JPEG ................................. yes Using system libjpeg ............... no PNG .................................. yes Using system libpng ................ no EGL .................................... yes OpenVG ................................. no OpenGL: ANGLE ................................ yes Combined ANGLE Library ............... no Desktop OpenGL ....................... no Dynamic OpenGL ....................... yes OpenGL ES 2.0 ........................ no OpenGL ES 3.0 ........................ no OpenGL ES 3.1 ........................ no OpenGL ES 3.2 ........................ no Vulkan ................................. no Session Management ..................... yes Features used by QPA backends: evdev .................................. no libinput ............................... no INTEGRITY HID .......................... no mtdev .................................. no tslib .................................. no xkbcommon .............................. no X11 specific: XLib ................................. no EGL on X11 ........................... no QPA backends: DirectFB ............................... no EGLFS .................................. no LinuxFB ................................ no VNC .................................... no Mir client ............................. no Windows: Direct 2D ............................ yes DirectWrite .......................... yes DirectWrite 2 ........................ yes Qt Sql: SQL item models ........................ yes Qt Widgets: GTK+ ................................... no Styles ................................. Fusion Windows WindowsVista Qt PrintSupport: CUPS ................................... no Qt Sql Drivers: DB2 (IBM) .............................. no InterBase .............................. no MySql .................................. no OCI (Oracle) ........................... no ODBC ................................... yes PostgreSQL ............................. no SQLite2 ................................ no SQLite ................................. yes Using system provided SQLite ......... no TDS (Sybase) ........................... no Qt Testlib: Tester for item models ................. yes Qt SerialBus: Socket CAN ............................. no Socket CAN FD .......................... no Qt QML: QML network support .................... yes QML debugging and profiling support .... yes QML sequence object .................... yes QML list model ......................... yes QML XML http request ................... yes QML Locale ............................. yes QML delegate model ..................... yes Qt Quick: Direct3D 12 ............................ yes AnimatedImage item ..................... yes Canvas item ............................ yes Support for Qt Quick Designer .......... yes Flipable item .......................... yes GridView item .......................... yes ListView item .......................... yes TableView item ......................... yes Path support ........................... yes PathView item .......................... yes Positioner items ....................... yes Repeater item .......................... yes ShaderEffect item ...................... yes Sprite item ............................ yes Qt Scxml: ECMAScript data model for QtScxml ...... yes Qt Bluetooth: BlueZ .................................. no BlueZ Low Energy ....................... no Linux Crypto API ....................... no WinRT Bluetooth API (desktop & UWP) .... yes Qt Sensors: sensorfw ............................... no Qt Positioning: Gypsy GPS Daemon ....................... no WinRT Geolocation API .................. yes Qt Location: Qt.labs.location experimental QML plugin . yes Geoservice plugins: OpenStreetMap ........................ yes HERE ................................. yes Esri ................................. yes Mapbox ............................... yes MapboxGL ............................. no Itemsoverlay ......................... yes QtXmlPatterns: XML schema support ..................... yes Qt Multimedia: ALSA ................................... no GStreamer 1.0 .......................... no GStreamer 0.10 ......................... no Video for Linux ........................ no OpenAL ................................. no PulseAudio ............................. no Resource Policy (libresourceqt5) ....... no Windows Audio Services ................. yes DirectShow ............................. yes Windows Media Foundation ............... yes Media player backend ................... DirectShow Qt Tools: QDoc ................................... no Qt WebEngine: Embedded build ......................... no Pepper Plugins ......................... yes Printing and PDF ....................... yes Proprietary Codecs ..................... no Spellchecker ........................... yes Native Spellchecker .................... no WebRTC ................................. yes Use System Ninja ....................... no Geolocation ............................ yes WebChannel support ..................... yes Use v8 snapshot ........................ yes Kerberos Authentication ................ yes I think the bit about "Embedded build: no" just means it isn't building for an embedded Linux, not for a WebEngine to embed in an app. I updated my MSVC 2017 with the latest service packs and it seems like it is working now. So it is probably a configuration bug that it doesn't report WebEngine won't be built. Just an FYI for anyone else who wants to try this Herculean task - we got a 16 core, 32bg Amazon Instance (a c5 4xlarge) and the build, using this config line: %_ROOT%\configure -prefix %_ROOT%\..\5.12.1-32-release -nomake examples -nomake tests -skip qtandroidextras -skip qtgamepad -skip qtmacextras -skip qtquickcontrols -skip qt3d -skip qtcanvas3d -skip qtx11extras -skip qtactiveqt -skip qtcharts -skip qtdatavis3d -skip qtpurchasing -skip qtquickcontrols2 -skip qtvirtualkeyboard -skip qtwayland -opensource -opengl dynamic -confirm-license -make-tool jom So you see, I'm not building a bunch of pieces that we don't use. This took 20 minutes without WebEngine and 120 minutes with WebEngine. On my older dual 3ghz Xeon machine, the one sans WebEngine took 5 hours. I'll let you do the math for how long it would probably take with it. And this is using jom! Thanks again to SGaist for all your help! Jonathan

CALL C:\Qt\Qt5.12.1\5.12.1\msvc2017_64\bin\windeployqt.exe MyApp.exe --qmldir "D:\MyApp\Application\Qml" is working fine

Okay, I think the problem here is that I was doing 'jom release' when I built it and that just doesn't seem to work. If I just do 'jom', it seems to work fine.

hi, thanks for the heads up so i ended up retrieving the old macbook and installed Qt build the app on it. thanks

Yup, that's it. Turns out I can add a qt.conf file "next" to the qmake.exe with the following in it: [Paths] Prefix = f:/5.12.1-32-release And now I get: F:\5.12.1-32-release\bin>qmake --version QMake version 3.1 Using Qt version 5.12.1 in f:/5.12.1-32-release/lib And Qt Creator is very happy.

@tr1cks https://stackoverflow.com/a/44665772

@iieklund It should be 131.188.12.211 in my case. Apparently University of Erlangen However, this time behaviour has changed. The download of meta was still a bit slow. Apprently the complete list was downloaded and I have started to add qt5.12.1 since it was this time possible.

@ed00 I don't know Qt Maintenance Tool works for me.

Solution found for MacOS and iOS. It's might be working well for another platforms. I haven't tested it yet. Every library that is using by libzip should be added manually to the QT project and if it's not by default in the system you need to build it like static. If there zlib - then add it manually, if there SSL - then add it manually, etc The step-by-step guidance for building libzip published by me on Github There are couple of strange things that I found (I don't know the cause of it): In the directory where located library appeared couple of symlinks on the real shared library file when I am attaching it to QT project via symlinks it's not working, only direct original file attaching to project working well (it's mean important for attaching zlib from system folder). See the screenshot [image: 7d3eb179-2d62-4daf-bf31-b8472b35cfbd.png] The libzip library only working when you attaching it to QT Project like statical library (*.a), all of attempts of using like shared/dynamic libraray (*.dylib) have got failed, even it's installed like the operational system part. Code from that works for me *.pro file: macx { LIBS += -lz.1 LIBS += -L$$PWD/libs/libzip/ -lzipstatic INCLUDEPATH += $$PWD/libs/libzip DEPENDPATH += $$PWD/libs/libzip PRE_TARGETDEPS += $$PWD/libs/libzip/libzipstatic.a } ios { LIBS += -lz.1 LIBS += -L$$PWD/libs/libzip/ -lzipstatic INCLUDEPATH += $$PWD/libs/libzip DEPENDPATH += $$PWD/libs/libzip PRE_TARGETDEPS += $$PWD/libs/libzip/libzipstatic.a } SUPER-MEGA-HUGE (SMH) thanks to Thomas Klausner (one of authors of libzip). He has been helping me to solve this trouble.

Hi, You need to add the DYLD_LIBRARY_PATH environment variable in the Run part of the project panel and point it to the folder where that library is located.