Installation and Deployment

@Buttink If anyone comes across this problem. Apparently, the QLoggingCategory or the stderr/windows debugger are SUPER slow on windows. To fix this I used qInstallMessageHandler and wrote my own handler to not send to the terminal for windows. Now, my application runs just fine.

I was hoping someone might verify/refute as some of my initial problems building from source were user error. However, thank you, I'll submit a bug report.

@mcosta Thanks mcosta Yes, indeed I can show website over https with WebEngine, even though it still show those warning messages. As documented here, Web Kit will be deprecated in Qt version 5.5+, so I'll switch to use WebEngine then. For those who feel annoyed with the warning messages, you could suppress them by calling following method in your main() QLoggingCategory::setFilterRules("qt.network.ssl.w arning=false"); or by setting environment variable QT_LOGGING_RULES=qt.network.ssl.warning=false

Hi and welcome to devnet, Boot to Qt is an commercial feature, if you are having trouble with it you should contact The Qt Company directly through your profile Support Center link

@adebruyn thank you very much for this tips, this is well working :) But how to rebind the framebuffer driver once the QT application has been closed ? Is a command like this could do the trick ? echo 0 > /sys/class/vtconsole/vtcon1/bind ; \ myQtApplication -platform eglfs ; \ echo 1 > /sys/class/vtconsole/vtcon1/bind Because I need to get the console back when the application close. Also, do you know if we get the same problem with the console (flashing in background) if the application is lunch from init.d ? Best regards.

@SGaist thanks , I have actually compiled without the script no errors thought while compiling, but I'm not sure if the errors will popup when i start using the build, but it would be really useful for future builds also I'm compiling OpenCV , so here is my installation paths : DirectX SDK : C:\Program Files\Microsoft DirectX SDK (June 2010) Microsoft SDK : C:\Program Files\Microsoft SDKs MSVC : C:\Program Files\Microsoft Visual Studio 12.0 .NET : C:\Program Files\Microsoft.NET OpenSSL : C:\OpenSSL-Win32 Qt source : C:\Qt\5.4.1 thanks again for your time

Hi, I'm having a similar problem with the auto installer for Linux 64. The installer gets about half way and then stops with the error message: Error during installation process (qt.54.gcc_64): File '/qt/5.4/gcc_64/bin/qmake' does not exist or is not an executable binary. Checked the files and sure enough qmake is not executable by any user and only read write by root, I tried chmod but can't make the file executable. I don't really understand why its not working I have a working tool-chain and executing the run file as root. I haven’t tried building it from source yet, just hoping some one might know what’s happening?

PySide is a dead project for many years, basically since Nokia switched from Meego and Qt to Windows Phone. If you want to use Python with Qt, the only option is PyQt.

Just wanted to say, I finally figured how to set RPATH when building the project. This way it's much easier and no need for install_name_tool #set RPATH (place to look for .dylib & framework by default) QMAKE_RPATHDIR += @executable_path/../Frameworks QMAKE_RPATHDIR += @executable_path/lib Thank you for your help!

I figured out, that QSslSocket::supportsSsl() returns false due to lack of the OpenSSL installation. Adding OpenSSL dlls to the installer dir solved this problem and starts another: How to distribute the installer, which depends on OpenSSL dlls?

Hi, @eldiener said: Is there a way to deploy the exe so that qt creator automatically adds any needed dlls to the output directory of the exe. See @Leonardo's link for automatic deployment. However, not that the tool is still not perfect, because it can't always know which plugins your app needs. Was qt supposed to add its own dlls to the path when I installed qt ? No. Adding DLLs to the PATH can cause DLL Hell -- programs can crash. I see the same qt dlls in the /bin directory of each of my kits as well as some of them in the /tools/qtcreator/bin directory. is the same-named dll the exact same dll each time ? They are not the same. You must not use the DLLs in /tools/qtcreator/bin. These are for Qt Creator only, not for your apps. (Qt Creator is also an .exe that is built with Qt, so it needs Qt DLLs to run)