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.
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
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.
@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
Not sure if this is helpful, but I found I got this error if my Google account was paused. As soon as I logged into Google account, the install resumed with no errors. (Assuming of course that you have downloaded Qt via Google browser)
@ununez try this https://sysprogs.com/w/fixing-rpath-link-issues-with-cross-compilers/. I had the same problem. Don't use gold linker. This is my configure: /opt/qt5pi/qt-everywhere-src-5.11.3/configure -opengl es2 -device buildroot -device-option CROSS_COMPILE=/opt/qt5pi/gcc-linaro-7.5.0-2019.12-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf- -sysroot /opt/qt5pi/sysroot -prefix /usr/local/qt5pi -confirm-license -opensource -skip qtscript -skip wayland -skip qtwebengine -skip qtdatavis3d -nomake examples -make libs -pkg-config -no-use-gold-linker -v. Creat a folder called etc in sysroot(for expamle, /opt/qt5pi/sysroot/etc/ld.so.conf ). My ld.so.conf: /usr/local/lib/arm-linux-gnueabihf
/lib/arm-linux-gnueabihf
/usr/lib/arm-linux-gnueabihf
/usr/local/lib
Just see the site the above
My target device is Armbian Buster with Linux 5.3.9-sunxi and host computer ubuntu(Distributor ID: Ubuntu
Description: Ubuntu 16.04.7 LTS
Release: 16.04
Codename: xenial
)
Speaking about the missing mkspec:
@SGaist said in Building Qt for QNX:
You have to copy it over from an actual version to possibly use it there. There might be additional work to be done though.
I installed LLVM and added an environment variable called, "LLVM_INSTALL_DIR" with location '<path>\LLVM\bin directory ". Then I added this variable to the path variable, reconfigured and rebuilt the project. Problem solved.
Yes . I'm getting translations based on System Language. For Eg: If My system language is German than installer will be translated to German language.
What I need is :
-listing some languages after the Introduction page.
-Based on the language I select than installer must change to that particular
language for the subsequent pages.
-Is it possible with Qt installer framework ?? If yes than how to apply in the
installscript.
Thanks for your response though..!
Qt Creator is a tool, it's not Qt (the library). I haven't seen this dialog, but you should look for the directory where Qt was installed (usually that's where you have qmake and moc, at least most auto-detect tools look for qmake).
These are device settings, I was asking for Kit settings for the kit you are using. Since you don't want to compile/ run on Android, you can ignore Devices->Android and you can ignore those auto-generated Android kits. They are irrelevant here.
We need to investigate why Qt Creator is trying to compile for Android when you select a Desktop kit (you do that right?).
