Skip to content

Installation and Deployment

Your Qt just doesn't want to build? Your compiler can't find the libs? Here's where you find comfort and understanding. And help.
9.8k Topics 51.2k Posts
  • Qt license for older version like 4 ?

    Unsolved
    2
    0 Votes
    2 Posts
    456 Views
    sierdzioS
    Get in touch with Qt Company. They still offer paid support for Qt 4, as far as I've heard.
  • Link errors when building with qmake outside of Creator

    Solved
    4
    0 Votes
    4 Posts
    2k Views
    CentralScrutinizerC
    Thanks for the helpful answers. It turned out to be my environment. For some reason I had an extra path in my PATH variable that pointed to another make (mingw64-make in my MSYS installation). I have no Idea why that affected my ability to build at the command line (esp. since I use full absolute paths for all of the commands used in the build) but removing it seemed to do the trick. I also don't understand why the mingw paths are needed on the PATH at all when using absolute paths. Or why it worked inside creator. Oh well I don't have time to investigate any further so i'll just have to be satisfied with it working now. Thanks again
  • I can not install Qt 5.10 on Debian 9.3 because of SSL problem?!

    Unsolved
    10
    0 Votes
    10 Posts
    3k Views
    MucipM
    .Hi, Yes. I remove openssl 1.1 and install openssl 1.0 as said. Now I started to install Qt 9.10... Thanks... Regards, Mucip:)
  • Install QT Online Installer Unified as Invoker? (Non-Admin)

    Unsolved
    6
    0 Votes
    6 Posts
    1k Views
    SGaistS
    Once you can confirm you came to an arrangement with your school's IT people.
  • Qt 5.9.4 For ARM

    Unsolved
    7
    0 Votes
    7 Posts
    2k Views
    A
    No problem, feel free to post back here if you get stuck on something. :) Oh and this may make things easier: https://github.com/probonopd/linuxdeployqt
  • Customizing maintenance tool

    Unsolved
    5
    0 Votes
    5 Posts
    1k Views
    D
    @sierdzio Thanks.
  • Building my own Embedded Linux Image for Apalis-IMX6

    Unsolved
    2
    0 Votes
    2 Posts
    548 Views
    L
    You can try to rebuild icu-native: bitbake -c cleansstate icu-native && bitbake -c icu-native
  • Qt 5.9.2 build error (Mac)

    Unsolved
    5
    0 Votes
    5 Posts
    1k Views
    C
    @SGaist said in Qt 5.9.2 build error (Mac): @ChristopherL said in Qt 5.9.2 build error (Mac): I'd love to be able to just 86 the whole locale/timezone code but it seems to break more stuff. What do you mean by that ? I mean that I can get Qt 5.8 to build just fine because it doesn't have that bug I mentioned that's stopping me from building 5.9. @ChristopherL said in Qt 5.9.2 build error (Mac): And by the way these OS and XCode upgrade requirements are really annoying. Tell that to Apple, they officially support the 3 last versions of their OS. If you need support for older versions, then you should consider the 5.6 series. Thanks. I'll take a look at 5.6 next..
  • QT Source code compile Error

    Unsolved
    3
    0 Votes
    3 Posts
    2k Views
    JKSHJ
    @vivekyuvan said in QT Source code compile Error: mainwindow.cpp:972:25: error: ‘class QwtDial’ has no member named ‘setRange’ ... #include </usr/local/qwt-6.1.0/include/qwt_dial.h> QwtDial::setRange() was removed in Qwt 6.1. Your project needs Qwt 6.0. It is not compatible with Qwt 6.1
  • Qt source build with -qtlibinfix, and -framework

    Unsolved
    3
    0 Votes
    3 Posts
    974 Views
    J
    Thanks! It looks like the behaviour that I'm seeing is due to the bug that you've linked. I'll build without frameworks.
  • Could not initialize GLX

    Unsolved
    2
    0 Votes
    2 Posts
    6k Views
    sierdzioS
    Normally Qt requires OpenGL and a screen to work. So you're getting issues when you launch apps through the terminal because screen is missing. Try running your app like so: ./myApplication -platform minimal # OR ./myApplication -platform offscreen
  • qt design tab is disabled

    Solved
    4
    0 Votes
    4 Posts
    1k Views
    J
    @aha_1980 said in qt design tab is disabled: a virtua I already solve this issue. What I did is I runMaintenanceTool from C:\Qt\MaintenanceTool.exe I only install one version of mingw . in my case mingw48_32 then also install msvc2010 and msvc2012_64. then it works.
  • Raspberry: Deploy application once cross build finished

    Solved
    10
    0 Votes
    10 Posts
    2k Views
    A
    @sneubert It worls also the call in crontab so now after boot the application starts automatically! Good. Thanks
  • Qt Application crashes on startup

    Solved
    4
    0 Votes
    4 Posts
    2k Views
    DenjasD
    I tried re-installing MSVC 2017 completely as SGaist said and it seems to have fixed the problem, now I can run applications in debug mode again :) Thanks for the help both of you!
  • Qt 5.9.2 cross-compiled: host errors

    Solved
    4
    0 Votes
    4 Posts
    4k Views
    W
    @AlTro Was there any resolution to your problem? I found a Qt-Bug that very likely seems to be related, but it was issued and already "resolved" in 5.9 and I'm cross-compiling with 5.10, so this specific bug should be solved. https://bugreports.qt.io/browse/QTBUG-62434 Any clue?
  • How to install qt in static link mode with qt-opensource-linux-x64-5.10.1.run

    Unsolved
    3
    0 Votes
    3 Posts
    839 Views
    E
    @JKSH thanks. There are always kinds of problems when compiling source code, so i tried the installer. I don't like that.
  • Testing "customwidgetplug" under Windows (Mingw)

    Unsolved
    2
    0 Votes
    2 Posts
    465 Views
    raven-worxR
    @Luis-Felipe IIRC the designer isn't built with mingw, thus it can*t load mingw dlls. Check the Info window in the designer, there should be the used compiler specified. I believe its some msvc variant.
  • Could not start process "mingw32-make.exe" qmake_all

    Unsolved
    4
    0 Votes
    4 Posts
    5k Views
    R
    @robrob said in Could not start process "mingw32-make.exe" qmake_all: My first installation issue is resolved. After 03 or 04 clean installation, now I can compile and run Hello Word project in the Qt Creator 4.5.1 which is good. But the headache start again with the second part of the exercise. Now the more important part is to open the project and add more functionalities. It has a graphical Interface and I wanted to add one button. I manage to open the project but when I build the project, I had this error. Does anyone have the slight idea how to resolve this issue? Your help would be very appreciated ! 18:58:12: Running steps for project SA430Gui... 18:58:12: Starting: "C:\Qt\5.10.1\mingw53_32\bin\qmake.exe" "C:\Users\rabmerab\Documents\Qt projects\SA430.Gui\V2.0\Src\SA430Gui.pro" -spec win32-g++ "CONFIG+=debug" "CONFIG+=qml_debug" Info: creating stash file C:\Users\rabmerab\Documents\Qt projects\SA430.Gui\V2.0\build-SA430Gui-Desktop_Qt_5_10_1_MinGW_32bit-Debug.qmake.stash 18:58:18: The process "C:\Qt\5.10.1\mingw53_32\bin\qmake.exe" exited normally. 18:58:19: Starting: "C:\Qt\Tools\mingw530_32\bin\mingw32-make.exe" qmake_all mingw32-make: Nothing to be done for 'qmake_all'. 18:58:22: The process "C:\Qt\Tools\mingw530_32\bin\mingw32-make.exe" exited normally. 18:58:22: Starting: "C:\Qt\Tools\mingw530_32\bin\mingw32-make.exe" C:/Qt/Tools/mingw530_32/bin/mingw32-make -f Makefile.Debug mingw32-make[1]: Entering directory 'C:/Users/rabmerab/Documents/Qt projects/SA430.Gui/V2.0/build-SA430Gui-Desktop_Qt_5_10_1_MinGW_32bit-Debug' C:\Qt\5.10.1\mingw53_32\bin\uic.exe ..\Src\mainwindow.ui -o ui_mainwindow.h C:\Qt\5.10.1\mingw53_32\bin\uic.exe ..\Src\appFwUpdater.ui -o ui_appFwUpdater.h g++ -c -fno-keep-inline-dllexport -g -std=gnu++11 -Wall -W -Wextra -fexceptions -mthreads -DUNICODE -D_UNICODE -DWIN32 -DQT_QML_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_XML_LIB -DQT_CORE_LIB -DQT_NEEDS_QMAIN -I..\Src -I. -IC:/QtSDK/qwt-6.0.0/src -I../sa430 -IC:\Qt\5.10.1\mingw53_32\include -IC:\Qt\5.10.1\mingw53_32\include\QtWidgets -IC:\Qt\5.10.1\mingw53_32\include\QtGui -IC:\Qt\5.10.1\mingw53_32\include\QtANGLE -IC:\Qt\5.10.1\mingw53_32\include\QtXml -IC:\Qt\5.10.1\mingw53_32\include\QtCore -Idebug -I. -IC:\Qt\5.10.1\mingw53_32\mkspecs\win32-g++ -o debug\main.o ..\Src\main.cpp g++ -c -fno-keep-inline-dllexport -g -std=gnu++11 -Wall -W -Wextra -fexceptions -mthreads -DUNICODE -D_UNICODE -DWIN32 -DQT_QML_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_XML_LIB -DQT_CORE_LIB -DQT_NEEDS_QMAIN -I..\Src -I. -IC:/QtSDK/qwt-6.0.0/src -I../sa430 -IC:\Qt\5.10.1\mingw53_32\include -IC:\Qt\5.10.1\mingw53_32\include\QtWidgets -IC:\Qt\5.10.1\mingw53_32\include\QtGui -IC:\Qt\5.10.1\mingw53_32\include\QtANGLE -IC:\Qt\5.10.1\mingw53_32\include\QtXml -IC:\Qt\5.10.1\mingw53_32\include\QtCore -Idebug -I. -IC:\Qt\5.10.1\mingw53_32\mkspecs\win32-g++ -o debug\mainwindow.o ..\Src\mainwindow.cpp Makefile.Debug:1350: recipe for target 'debug/mainwindow.o' failed mingw32-make[1]: Leaving directory 'C:/Users/rabmerab/Documents/Qt projects/SA430.Gui/V2.0/build-SA430Gui-Desktop_Qt_5_10_1_MinGW_32bit-Debug' mingw32-make[1]: *** [debug/mainwindow.o] Error 1 Makefile:36: recipe for target 'debug' failed mingw32-make: *** [debug] Error 2 18:58:46: The process "C:\Qt\Tools\mingw530_32\bin\mingw32-make.exe" exited with code 2. Error while building/deploying project SA430Gui (kit: Desktop Qt 5.10.1 MinGW 32bit) When executing step "Make" 18:58:46: Elapsed time: 00:34. I will create new thread for this as it is new topic.
  • windeployqt.exe for exe QT dependencies

    Unsolved
    2
    0 Votes
    2 Posts
    530 Views
    SGaistS
    Hi, AFAIK, you only need to run it against your application. Note that's typically something that is faster tested than waiting for an answer on the forum.
  • 0 Votes
    9 Posts
    4k Views
    QjayQ
    @aha_1980 i cleaned my old project build tried it again. The build is successful but when i try to run same error as mentioned above. any changes : just uninstalled Qt5.9.1 .other than that nothing much. this is my compiler tab if it helps any !! [image: f0224abb-fb05-4190-8409-4c859082c261.PNG] p.. i have downloaded windows 10 SDK too now there is no triangle on msvc 32bit one but the problem still remains :/ .