Installation and Deployment

@Xenoshell What's the full output from the configure? Or more specifically, what is the output from the tests that are built to test for gstreamer and dbus? That will help shed some light on your install issue. It sounds like even though you installed all the *-dev packages Qt isn't finding them properly.

I've tinkered around a bit more and found that I can't even compile the modules from source. Qmake works, but when I try to do a make I get various errors. Qtbase compiles fine, though. I'm wondering if having previously installed QtCreator from the Ubuntu repositories has caused these issues.

After few researches and some help from internal, it appears that my links to libraries ain't clean enough wich leads to those random behaviours. So i'm working on making it cleaner for x32/x64 debug and release. Thanks a lot for your help ! You made my mind way sharper !

I checked the env variables - it looks a little bit strange. On the working configuration, the PATH env variable contains Qt\Tools\mingw530_32\bin and no msvc2015 related path. In Qt Creator, the Build & Run config are using the System Environment (without manually performed modifications) but the Path contains Qt\5.9.3\msvc2015_64\bin (the MinGW bin location too of course). My PC doesn't have the PATH with an item related to Qt build kit. In Qt Creator, in Build & Run I have the Qt\5.9.3\msvc2015_64\lib but I didn't found the Qt\5.9.3\msvc2015_64\bin. Of course after adding the C:\Qt\5.9.3\msvc2015_64\bin to the PATH, I'm able to run the app from Qt Creator and from the debug/release folder so looks like the problem is solved - but I still don't know how the working configuration generated an extra bin location in Build & Run.

@SGaist I'm not sure, if you look at the picture I posted, I copied, by hand, the folders qmltooling, Qt, QtGraphicalEffects, QtQML, QtQuick, QtQuick.2, and scenegraph and than it worked. So anyone of them, or all auf them?

Hi @karasho, To add to @koahnig, the Microsoft CDB debugger has to be installed separately. It is part of the Windows SDK (e.g. https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk ) Regards

@jackmack Are you also able to debug your Qt Application using VS 2017 and its Debugger?

@Stefano79 Glad you figured it out. Then please mark this thread as solved. Thanks.

@Jonathan-Levanon said in MaintenanceTool error: Well I've solved it in a stupid-but-working way, I had to install 5.10 on another computer anyway, so I took the maintenance tool from there and used it to delete the 5.10 with the buggy installation. Then reinstalled with the needed components. Clever trick :)

I have the same problem when I use a mobile phone 4G+ connection.

@Ahmed-Jmail said in Size difference in QT online and offline installations: I'm seeing a noticeable size difference in offline (11 GB approx ) and online (38 GB approx) installers. Why is that so ? Because the online installers contain PDB files for debugging, but the offline installers don't. Will I be missing some features if I use offline version. Currently, you don't have the symbols for debugging Qt libraries. They are not strictly necessary, but they can be helpful when you're trying to figure out why your code is crashing. If you want those symbols, you can download them separately: http://download.qt.io/official_releases/qt/5.10/5.10.0/qt-opensource-windows-x86-pdb-files-desktop-5.10.0.zip (2.1 GB) http://download.qt.io/official_releases/qt/5.10/5.10.0/qt-opensource-windows-x86-pdb-files-uwp-5.10.0.zip (1.4 GB) @J.Hilk said in Size difference in QT online and offline installations: @Ahmed-Jmail Have you checked that the offline and online installer actually offer the same installation options? They do now, actually! I just checked and was surprised. In the past, only 1 version of Qt was provided per offline installer (e.g. http://download.qt.io/official_releases/qt/5.8/5.8.0/ ) However, since Qt 5.9, there's one single installer for all versions (e.g. http://download.qt.io/official_releases/qt/5.9/5.9.0/ )

Hi and welcome to devnet, First thing: avoid using such an outdated version of Qt 5.1 was released almost five years ago. Please consider using the current LTS (5.9) version if not the latest (5.10 currently) Then, don't use sudo, there's no reason to develop as root. Why doesn't ROOTFS_PATH point to /home/ninad/work/4.9.41_sdk/linux-devkit/sysroots/x86_64-arago-linux/ ?

Hello, I have the same problem :(

I will come back later, on a version of FreeBSD supported because the version 12 currente is not supported it is version 11.1 which is supported! I would install QTcreator on the supported version! thank you

No need to be connected on Firefox... The button now appear on Opera even without connected

What SDK did you install exactly ? On a side note, IIRC, JDK 8 should be used rather than 9.

You're welcome ! Since you have it working now, please mark the thread as solved using the "Topic Tools" button so that other forum users may know a solution has been found :)

Because: Licensing constraints. LGLP requires that your library/application users can switch to a different version of Qt (or any other LGPL dependency you have) how they see fit. Which means that if you want to use a static build of Qt you have to provide all the object files of your library/application to whoever asks you and that for each version of your library/application you released. It's your responsibility to abide by these constrains. Human and infrastructure constraints. The CI is already under high pressure as it is running for the LTS, the current release branch and dev. The CI generates pre-built package for iOS, macOS, Android (arm and x86 IIRC), Linux 64bit, and MinGW, VS2015, VS2017 for Windows. All in debug and release versions. Each of these packages are tested by actual people. The number of possible configuration option permutations makes it impossible to test absolutely every possible combination. See number two for reasons. If you want to avoid as much trouble as possible, only build the modules that you are actually going to use. It's faster in any case. That's why I write time and again: use out of source builds. This way you just have to nuke the folder and start from scratch quickly. That is valid for all platforms.

@raven-worx Using windeployqt fixed my issue, thank you very much! :)