Installation and Deployment

@nootnoot hey, I installed the QT with the online tool in win10 ,and I faced the same problem, I found the 3D studio ,creator and build tool in a same root file ,I can not find the 3D studio runtime module

I re-downloaded the NDK 10 e and getting same error. but Kits got detected. Hope it will work fine :) [image: b199681b-3661-475c-997e-1de59b88f17b.png] [image: a9181fc8-5a1e-4c35-a2c0-331c631cdf6c.png] Thanks @SGaist

Thanx AndyS ! I just tried it with vcvars64.bat but I have the same result. I don't understand it... But above all, how can we explain that QtCreator is not able to set up automatically the Msvc and Android kits? I also updated my version of Visual Studio. Can this explain this? I put these parameters manually to define the msvc kits. Are they correct? [image: 506709a0-6fe5-45dd-840b-46114c03b1c3.jpg] Thank you!

User something like LIBS += -F /path/to/where/qwt_framework_is -framework qwt

@ichidan Hi and welcome to devnet forums The versions are determined by availability on the repository servers. Since there are a "mass" of different compiler versions around Qt libraries are only build for some selected versions. The best is to install the same version of a pre-built Qt libs as the compiler is you have installed. Especially with MSVC compiler there is almost no compatibility between subsequent versions. However, IIRC there is a compatibility between MSVC2015 and MSVC2017 versions. For sure there is no compatibility to or between previous versions. Also you cannot mix 32-bit and 64-bit versions. However, since you have a qt-enterprise version, it should mean that you have a commercial version with license, if I amnot mistaken. When you have a commercial license you are entitled to get support from the commercial hotline. This is the open source forum.

Hi, If you don't need QtWebEngine, just move the module folder out of the source tree before calling configure and it won't be built.

Yep, that's OK.

@kaochucs What do you mean by "keyboard not working"? Not working in general or in Qt apps? If in general then it is more of a Linux question, not Qt.

@SGaist Qt 5.11.1 does'nt having support for imx 25. Do you know which is the latest qt version that supports imx25?

@MikhailQt Hi and welcome to the forums I cant recommend downloading dlls from forums :) Also, there is mingw version and visual studio version. You can get it from https://www1.qt.io/offline-installers/

If you used the source archive then it’s normal, as suggested by the name, it’s the module sources. Since you have an Unbuntu machine, you should be able to install the distribution provided Qt and then build the module with it.

Hi and welcome to devnet, First thing: use matching kit in terms of architecture and compiler. The only exception currently is VS2017 which is backward compatible with VS2015 but you still have to have the same architecture. Then, did you follow the Creating Shared Libraries chapter of Qt's documentation ?

@SGaist said in Need help with masternode output list in qt wallet: You should contact the application's author. He will more likely be able to answer your question. k i just found out a guy named coolbits authored it ill try to contact him ty for the help!

the file exists but the javac doesn't seem to be redircted with the symbol link so I have to restart the whole build with a shorter path

@mkalinow I tried the above script but it did not work due to network issues. Is it possible to create docker build without connecting to internet or download offline?

@aha_1980 Thanks for quick reply. I will try that. Regards, Digvijay

This bug report indeed was helpful: https://bugreports.qt.io/browse/QTBUG-63323 Specifically, Thiago indicated to: Remove .qmake.cache, .qmake.stash and all other cache files and then try again, starting from configure. If you updated Xcode, then the path to the headers changed and qmake needs to know to search again for them. In other words, "Clean Project" or "Rebuild Project" is not enough. You need to either delete every single (hidden) file from the build directories or more easily just trash the build directories and then rebuild. You'll then get the key message: Info: creating stash file /Users/XXX/Qtprojects/build-TestCompileErrors-Desktop_Qt_5_11_1_clang_64bit-Debug/.qmake.stash And your project will run!