Installation and Deployment

After the advice from @SGaist I started to experiment a bit with settings of the build steps: problem disappeared after I did these three steps one by one (after each I checked if the problem is gone - it disappeared after the last step: turning off QML debugging and profiling switch (default was "leave default", effective call showed CONFIG+=qml_debug now it is CONFIG-=) turning off QtQuick compiler (default was "leave default, effective call showed CONFIG+=qtquickcompiler now it is CONFIG-=) deleting shadow build folders (I do it routinely once a week or so anyway). Now the problem is gone, I am marking the topic as "solved".

So I finally found an answer. You simply uncheck and hit next and then update. It would be nice if there was a better confirmation message that states exactly what is about to be done. The predicted disk usage is a bit lame.

@san_qt_enthusisast I guess you should be using Java 8

FWIW, it seems to work fine in Win10 and IFW 4.0.0 these days, even when the string contains spaces (i.e. installed in c:\program files...).

@jsulm no problem, I was hoping that wouldn't be the case! Thanks again for the help.

There are a few docker for qt webassembly already around: https://github.com/Zebreus/qt-webassembly-docker https://github.com/guerinoni/qt-wasm and instructions: https://www.qt.io/blog/2019/03/05/using-docker-test-qt-webassembly

Fixed by removing kwin-lowlatency, and installing kwin. They are telling me that the official kwin now has the benefits of lowlatency too.

Hi and welcome to devnet, How many different versions of Python do you have ? It looks like you are using a custom one. Are you using a virtual env ? Conda ? Just your system Python (does not look it though) ?

"deploying" (aka file copy) debug qt libs is supported as it is a parameter of the tool, and why are you talking about MS debug runtime exactly ? I am talking about Qt binaries copied from the qt bin dir to my project bin dir ...

I'm using Qt5.15.2, compiled from source. I eventually figured out the problem. It just needed export paths for "LD_LIBRARY_PATH" and "QT_PLUGIN_PATH", then it worked Ok. export LD_LIBRARY_PATH=/opt/Qt5/lib export QT_PLUGIN_PATH=/opt/Qt5/plugins

@_2020_ Why are you building Qt for Android anyhow? I am using the pre-built Android versions on Win 10 64 bit. The only thing you have to careful is the use of the correct NDK, which is not always the latest one.

@Wycliffe You are welcome and good to know that your issue has been found. Please mark your post as solved under "Topic Tools"

@Nan-Feng said in About Qt Install Tools: Is "qt-unified-windows-x86-4.0.0-online.exe" made using "Qt Install Framework"? Yes

@McTob Eventually find the most interesting lead thanks to the last link above with the following command: /opt/Qt/Tools/Conan/conan install qt3d/6.0.1@qt/final --build=missing -s build_type=Release -g cmake_paths -g=cmake -g deploy --profile=/opt/Qt/Tools/Conan/profiles/qt-6.0.1-gcc-x86_64 EDIT2: finally changed my mind again, cmake was much faster (and I just know it better). /opt/Qt/Tools/CMake/bin/cmake -DCMAKE_INSTALL_PREFIX=/opt/Qt/6.0.1/gcc_64/ /opt/Qt/AdditionalLibraries/Qt/qt3d-6.0.1/Src/ make -j12 make install