Installation and Deployment

I don't remember that it is possible to deselect Qt Creator from the online installer at all. So, I highly doubt that you don't have Qt Creator installed. The default location is C:\Qt\Tools\QtCreator\bin\qtcreator.exe. However, it looks like you have changed C:\Qt to C:\Qt-framework.

Great ! Since you have it working now, please mark the thread as solved using the "Topic Tools" button or the three doted menu beside the answer you deem correct so that other forum users may know a solution has been found :-)

@jsulm Yes, i actually did a reinstall and now works just fine, but im still curious on what may have happend?

I have exactly the same problem sudo apt install qml-qt6 solved the problem for me

Note: The GPL and LGPL licenses are focussed on providing freedom for the software's users (as opposed to focussing on the software's developers). The GPL guarantees more user freedom than the LGPL.

Sorry, another update. This snippet: MediaPlayer { id: mediaplayer source: "file:///root/sample.mp4" autoPlay: true } VideoOutput { anchors.fill: parent source: mediaplayer } works fine. So it's only the Video object that does not work. I can live with MediaPlayer + VideoOutput but I'd like to understand why the first option does not work.

@mzimmers said in Windows build needs libtiff-5__.dll: Also, assuming I can find those libraries, is there a way to build them into my next static build of Qt? If source code is available then it should be possible as long as those can be built for all your target platforms. Static libs should work as long as they were built using compatible compiler.

@jeremy_k Ah, thanks. I’ll try it.

@DL5EU nice catch !

Hi, In addition to what @sierdzio wrote, you have the Yocto project which is more or less a dedicated tool to build a full system including cross-compiling Qt.

@jsulm Reset means that after 15 seconds the installation will be interrupted (the system will be restarted).

@Kuolung Post actuall error if you want to get support...

@Christian-Ehrlicher To be honest the inconsistency with DLL files is because I've struggled with this issue for a month now. I've followed many guides and threads trying to solve the problem. Some people suggested moving the DLL files to .py file folder, to Python folder, to Pyside folder or to Qt folder. So I was just testing different configurations. I put QtCore.dll in the folder because dependency-walker showed an issue with dependency of qmysql.dll on this file. Concerning the plugin, I installed it in two ways: I compiled the plugin myself to the D:/Qt_Directory/6.5.2/Src/qtbase/src/plugins/sqldrivers/plugins/sqldrivers directory, and then copied the dll files to few folders - including My_Project_Directory/sqldrivers, Python directory and PySide6 directory. When the above didn't work I also downloaded pre-compiled DLL files from this repository: https://github.com/thecodemonkey86/qt_mysql_driver and added them in the same places. I'm aware that this method is somewhat messy but I was seriously desperate. How do I compile the plugin with default architecture?

Hello. I experience the same on macos 10.15.7 using the MaintenanceTool in version 4.6.0 trying to install Qt6.5.2. Error during installation process (qt.qt6.652.clang_64): Could not find the required QmakeOutputInstallerKey(qt.qt6.652.clang_64_qmakeoutput) value on the installer object. The ConsumeOutput operation on the valid qmake needs to be called first. I also downloaded a fresh online installer (version 6.4.0) but running this complains about a missing license although I want to use the OpenSource version of Qt. This might be a different issue though.

for the time being i am instead including a non-qt zlib, and hoping that it will work for these purposes (gzip functionality) Will close once i have tested it and verified functionality.

Embarrasingly i think i've resolved it, it was an odd case sensitivity issue. took me a few hours of digging...

@Tobias-Fensch From the installation documentation you linked earlier: Installation Supported Platforms The application manager is tested regularly on multiple platforms. The following platforms are only supported for development and testing purposes. In addition these platforms only allow the application manager to work in single-process mode: Windows macOS Android (the application manager cannot be deployed directly, but only as part of an Android APK package containing the System UI) These platforms can be used for development and production and will allow you to use the full feature set of the application manager: Linux desktop and embedded in single-process and multi-process mode Note: In multi-process mode, only the Intel, AMD (open source), and VMWare graphics drivers are supported due to the varying stability levels in Wayland drivers. While other drivers may work, they require either special QtWayland versions or specific firmware blobs for the GPU driver. As for the sources, yes you can use the GitHub mirrors. Otherwise, there's https://code.qt.io

Don't know if this is still an issue but i had the same problem and i think i just solved it. I have Qtcreator version 6.5.2 and MacOS Ventura 13.5. What i did was first of all checking "Run in terminal" under "Projects". Then in Qt Creator "Preferences" -> "Build & Run" -> "Default for "Run in terminal"" selected "Enabled". Finally, also in "Preferences", "Terminal" this time, unchecked "Use internal terminal". Don't know if this is still useful, but couldn't find much on google about this topic just now.

Yeah so Wayland vs. X11 are the "backend" for drawing windows on Linux. Some Linux distributions use Wayland by default, some X11. As @JoeCFD mentioned, both can be installed in parallel and chosen at login time. But, since you are on WSL... that gets complicated. This article suggests how it can be done in terminal: https://trendoceans.com/how-to-enable-x11-and-disable-wayland-window-system/ but if it will work on WSL I have no idea. Perhaps VirtualKeyboard won't work through WSL anyway, I have never tried it.

@jsulm New joiners cannot do that :)