Installation and Deployment

Hi and welcome to devnet, qmake can be found in /path/to/Qt/5.10.0/gcc_64/. But why install both separately ? Qt Creator comes also with both the online and offline installers. Start that version, it will be configured with the Qt versions you installed.

@JKSH I have one library which is written in both i.e., java and .net, So i just want to use that library in Qt, as that library is written in java and .net, i am little confused how to use it ! That library is HL7 library which is use to encode the data and send the messages to server.

@Ratzz said in QtIFW: Maintenance.exe does not start (no uninstall, no update): @Schenk So is the thread solved? YES!

@Opptur Just now worked for me too the below suggestion :) I Ran my first QML application "Hello World" :) chcp is an application that resides in C:\Windows\system32. I have added that directory to the PATH environment variable and everything is working again. Thank you!

@CMRO May be that is not possible with QtIFW . As suggested here it can only show version in control panel. May be you can change once you use QtIFW and use these https://www.digitalcitizen.life/how-change-metadata-stored-executable-files https://www.codeproject.com/Articles/37133/Simple-Version-Resource-Tool-for-Windows

@Schenk said in QtIF: Adding version info in windows: but the debug output do not find a start tag "rcc". So, how can i achieve this infos? I tried using .rc file format and it just worked fine . see this

Hi and welcome to devnet, Because it's complex to integrate one build system with another. What 3rd party is it ?

I have successfully build Qt 5.9 with additional argument -prefix C:\Qt5.9 while configuring and then nmake and nmake install.

@Alhasni You can give a try Workaround for Qt Installer Framework not overwriting existing installation.

Hi, I solved the problem, I used windeployqt on the executable to generate the required dependencies for deployment. It works now on Windows 10 PC as it did on Windows 7 PC.

@torpeanders said in Install to docker volume fails: Docker container using the online installer and an installer script. Hi, are you using windows docker container or linux? which version of onliner installer did you use? I tried to install QT 5.10.1 in windows docker using qt-installer-noninteractive.qs script and it did not work. I get this error while installing. I tried with proxy and without proxy as well. Network error: [ QNetworkReply::NetworkError(UnknownNetworkError) ] "Failed to connect to server. Check your network connection and try again." FROM microsoft/windowsservercore:10.0.14393.2189 COPY ["./install", "C:/tmp/qt"] RUN ["C:\\tmp\\qt\\qt-opensource-windows-x86-5.10.1.exe", "--no-proxy", "--script C:\\tmp\\qt\\qt-installer-noninteractive.qs"] ENV PATH "$PATH:C:\Qt\Qt5.10.1" ENV PATH "$PATH:C:\Program Files (x86)\Microsoft Visual Studio 15.0\VC" CMD ["vcvarsall.bat", "x86_amd64"]

use macro: Q_IMPORT_PLUGIN(QLinuxFbIntegrationPlugin);

No, the problem was (in my opinion) that Windows didn't want to work with MinGW. After I switched to MSVC everything works without problems. Thank you for your help. (can someone give me a reputation so I can respond more quickly?)

Thanks, it was because of output folder. object_with_source option makes error like when I compile without an option. so I just use object_parallel_to_source

The moc files are generated code, they should not be part of the source tree. Nuke them and rebuild with a more recent version of Qt. Qt 4 has already reached end of life for a couple of years now.

You're welcome ! You can mark the thread a solved using the "Topic Tools" button. When finding an answer that you deem interesting, you can up vote it by clicking the upward arrow beside the quote word.

@jsulm Yeah I do have internet on my Windows server 2016 VM. When I run this script on VM it installed. When I try to run the same insatller inside docker, it will get stuck and show this warning.

by renaming qbs.pro to something else it's ignored... however I had so many followup errors that I gave up. Set it to solved though.