Installation and Deployment

So, it's a bug, for me :D

It's not about having your qml files deployed it's about having them parsed so the tool can deploy the files from the related modules needed by your qml code to run properly.

Hi all, I tried to limit the error much more. It doesn't matter if I compile 5.9.2/5.9.1 with the use of nmake or jom. Next thing is that it doesn't matter if I compile 5.9.2/5.9.1 as 32bit version or 64bit version. Kind regards, Mike

And of course as soon as I finally give up and post in the forum my build works. Mind you it's been 4 solid days and be my 23rd or 24th attempt... In the end I think it was a combination of getting the right version of a static openssl build and the OPENSSL_LIBS config parameter set correctly (I also had the OPENSSL_LIBS environment variable set which seemed to conflict with the config parameter). Below are my steps (you'll need to modify the build paths as required). All builds were performed from the "Visual Studio 2017 x86 Native Tools Command Prompt". OpenSSL 1.0.2 Static Build (note needs to be version 1.0.x, Qt does not yet support 1.1.x) git clone https://github.com/openssl/openssl.git git checkout OpenSSL_1_0_2-stable perl configure VC-WIN32 no-shared enable-static-engine --prefix=f:\deps\openssl\1.0.2\vc141-x86 ms\do_nasm nmake -f ms\nt.mak (DOUBLE CHECK that you type ms\nt.mak NOT ms\ntdll.mak) nmake -f ms\nt.mak install Qt 5.9.2 Static Build git clone https://code.qt.io/qt/qt5.git (an alternative is to use the qt-everywhere-opensource-src-5.9.2.zip file) git checkout 5.9.2 cd qt5 && mkdir build && cd build ..\configure -prefix F:\deps\qt\5.9.2-git-ssl\vc141-x86\release -platform win32-msvc -release -opensource -confirm-license -strip -no-shared -static -no-static-runtime -ltcg -make libs -make tools -nomake examples -no-compile-examples -no-dbus -no-qml-debug -no-icu -no-gtk -no-opengl -no-opengles3 -no-angle -no-sql-sqlite -no-sql-odbc -no-sqlite -skip qt3d -skip qtactiveqt -skip qtandroidextras -skip qtcanvas3d -skip qtcharts -skip qtconnectivity -skip qtdatavis3d -skip qtdeclarative -skip qtdoc -skip qtgamepad -skip qtgraphicaleffects -skip qtimageformats -skip qtlocation -skip qtmacextras -skip qtmultimedia -skip qtnetworkauth -skip qtpurchasing -skip qtquickcontrols -skip qtquickcontrols2 -skip qtscript -skip qtscxml -skip qtsensors -skip qtserialbus -skip qtserialport -skip qtspeech -skip qtvirtualkeyboard -skip qtwayland -skip qtwebchannel -skip qtwebengine -skip qtwebsockets -skip qtwebview -skip qtx11extras -skip qtxmlpatterns -recheck-all -ssl -openssl-linked -IF:\deps\openssl\1.0.2\vc141-x86\include -LF:\deps\openssl\1.0.2\vc141-x86\lib OPENSSL_LIBS="-llibeay32 -lssleay32 -lgdi32 -luser32 -lwsock32 -ladvapi32" nmake nmake install Pay particular attention to the include, library and OPENSSL_LIBS paths in the configure.bat parameters. Getting those right is what eventually got my build working.

Hi, Did you thought of installing it once it was done ?

@parsa From did you get the source? AFAIK you still need to download a source version form the archives e.g. for windows the zip and for Linux the tar Note the source is almost identical, but you cannot simply use the tar on windows and vice versa. The differences are mostly in file endings IIRC. When you have downloaded and unzipped you will find the configure there.

@azaclauson said in Visual Studio 2017 unresolved external symbol struct QStaticPlugin: If I've understood correctly the default Qt downloads available at https://www1.qt.io/download-open-source/#section-2 are built with shared rather than static plugins. I believe so. In order to get Qt with static plugins I need to do a custom build with the "-static" parameter specified for configure.bat? That'd be implied if the installer provides only a shared library build. I've been unable to get very far with building Qt either from the git repo or from the above download (if anyone has a configure command that works with the Visual Studio 2017 command prompt I'd be very grateful). I suggest you open a new topic for that specifically and provide the configure command you had tried, what was the output and what didn't work.

Using a build directory underneath the root of the source directory rather than next to it solves the issue. When it's underneath the build scripts use ".." to locate source files, when it's beside they put in the full path.

No, I don't see a direct reason for that. Can you test if the same happens when building for 64 bit ? (Shouldn't make difference but who knows...) Note that you shouldn't need to pass the platform parameter.

That's why I suggest asking in the forum if in doubt. I'm not sure if there is any wiki page explaining which archive is for what. In short: Root directory contains offline Qt installers "Single" directory contains whole Qt source code (all modules) combined. Zip is for Windows, tarball for Unix, Linux, Mac "Submodules" directory is for code of single Qt repositories. Unfortunately, they do not represent Qt modules directly. As said, that is due to historical reasons Lastly, Qt code can also be cloned from git, of course. Then checking out a given Qt version is just a matter of checking out a tag with version name.

Perfect - thanks. Not sure how I missed or mis-understood that.

I made it by controller script function Controller() { installer.installationFinished.connect(function() { var isUpdate = installer.isUpdater(); if(isUpdate) { var targetDir = installer.value("TargetDir"); console.log("targetDir: " + targetDir); installer.executeDetached(targetDir+"/WebSourceManager.exe"); }else{ var result = QMessageBox.question("quit.question", "Start Program", "Do you want to start the installed application?",QMessageBox.Yes | QMessageBox.No); if( result == QMessageBox.Yes) { var targetDir = installer.value("TargetDir"); console.log("targetDir: " + targetDir); console.log("Is Updater: " + installer.isUpdater()); console.log("Is Uninstaller: " + installer.isUninstaller()); console.log("Is Package Manager: " + installer.isPackageManager()); installer.executeDetached(targetDir+"/WebSourceManager.exe"); } } }); installer.updateFinished.connect(function(){ var targetDir = installer.value("TargetDir"); console.log("targetDir: " + targetDir); installer.executeDetached(targetDir+"/WebSourceManager.exe"); }); }

You can compile Qt yourself, see this link. Source code is available from git, or here as zip/ tarball.

I was about to do that, but first I just tried deleting everything, including the source files qt and started all over again. This seems to have fixed it! It managed to build successfully now and OpenSSL is working too. Thank you for your time :)

@Allerknappe said in cant run v-play example: RCC: Error in ‘........\V-Play\mingw_32\mkspecs\common\vplay\resources_user.qrc’: Cannot find file ‘../../../../../V-Play/vplay_license.key’ Did you check if the file vplay_license.key is present and at the right location? If you can find this file, there is a problem with your path settings which are not aligned with the situation.

Hi, Please show content of the .pro file you are using with your custom compiler.

@pip010 said in Qt 5.9.1 building on windows and OpenGL support: how do the qt guys produce the official build, please post step by step instructions ... Why do you ask this here? This forum is for Qt users not for "qt guys".

I was able to solve the problem where fontconfig was not able to find libexpat by adding the following in my xplatform qmake.conf QMAKE_LINK = $HOST-g++ -lts -L/opt/qt/qt5.9.1arm/lib -Wl,-rpath -Wl,/opt/qt/qt5.9.1arm/lib QMAKE_LINK_SHLIB= $HOST-g++ -lts -L/opt/qt/qt5.9.1arm/lib -Wl,-rpath -Wl,/opt/qt/qt5.9.1arm/lib