Installation and Deployment

@jsulm directly , all libs and headers are there

@L_Raiz I experienced similar problems which I resolved by forcing desktop mode of openGL. See https://forum.qt.io/topic/70483/how-to-setup-qopenglwindow-to-have-access-to-desirable-functionality/8

NDK version: r12b SDK version: 24 However I have been using these for a while and signing has always worked for me before. I can still sign packages manually using apksigner directly, but it fails when using androiddeployqt.exe. The only thing I can think of that has changed is that Android Studio ran a lot of automatic updates, but I don't remember what exactly has been updated.

Hi, To add to @cfdev good point, you should use QStandardPaths to retrieve a proper folder to store your database.

The chromium snapshot is outdated. There is already a fix for that! link text

@jsulm When I call nmake I now get missing headers however I think I can continue from here. Thanks.

Also note that Qt 5.4 was released before VS2015 came out, you should use at least Qt 5.6 with this compiler

AFAIK, QtWebKit static build has been disabled a long time ago.

Hi, To add to @mostefa What version of Qt ? What compiler ? What version of Windows ? What command line prompt do you try to use ?

I tried but when I run nmake or jom I get errors such int_least8_t and int_max8_t and similar errors

Here's a guide: https://wiki.qt.io/Transition_from_Qt_4.x_to_Qt5 Qt5 is in Raspbian repository so upgrading Qt itself is just a matter of calling: sudo apt install qt5-qmake

Because you had the winrt_armv7_msvc2015 package installed at some point (from your previous posts).

Thanks mrjj your answer solve my problem

Hmm no timestamp? howeever 17.11.23 I had a similar issue with this Link Error: Qt5Widgetsd.lib(Qt5Widgetsd.dll):-1: Fehler: LNK1112: Modul-Computertyp "x86" steht in Konflikt mit dem Zielcomputertyp "x64". This message Pop up when I try to compile with the following setting [image: f804b6df-a8c8-4db5-b223-e532f0c4e888.png] Even when I adjust it "more correct" to ...MSVC2015 32bit like this [image: 477e3066-040e-4610-91d5-755b2233e55a.png] The message stay the same. I think it has to do with this line from (Projekte->Build-Umgebung) C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\bin\HostX64\x64; So for me the solution was to use this Setting [image: 4c371996-4d72-4802-9bb6-f669b1ee0e86.png] I have a 64bit machine so it make sense. So my resume is do not set up 64Bit stuff inside of 32Bit?QtPlugins? And I am not able to use a 32Bit Debugger on my 64Bit machine. OR expand the Microsoft Visual Studio\2017\Community\VC\Tools to HostX86\x86.

No it's not, you can mark your thread as solved. All the same you can vote for any answer you find useful on any of the threads.

@Pablo-J.-Rogina Thanks for the suggestion and the link to the guide. I see that the benefits of using Qt Creator so far out weights the benefits of the eclipse integration, which at this time is not fully available. I have done a few days worth of searching online before creating this post. I will play around with trying to get Eclipse CDT to play nicely with Qt when I have a lull in activities.

@aha_1980 said in Building QT Creator from source problem: Unknown module(s) in QT: script.: Regarding your questions: No, you don't need to build Qt yourself to build Creator. If you have installed Qt through the online installer, then there is a separate option Qt script - deprecated. If you installed by the package manager you need to search if it provides the package. ... Hope that helped! Wow, I cannot believe that simple check box was what I was missing! I'm ashamed to say I even re-installed QT a couple of times and still didn't spot it... Anyway, upon adding the QT script (deprecated) module via the maintenance tool to my QT installation, QT Creator successfully built and ran. Thank you; I really appreciate you taking the time to point me in the right direction. Kind regards, Ben