Installation and Deployment

Hi @QtNewComer, Linux applies a limit on the number of files open for each user, so its possible (indeed, very likely) that you have files open from other processes using up most of your user limit - not necessarily Qt Creator. Have a look at the output of: ulimit -n - this shows you how many files your user is allowed to have open. Then try lsof which will show you what files are currently open - look through that list, and see which application(s) is using up your limit. You can try a command like: lsof | cut -d' ' -f1 | sort | uniq -c | sort -n to get a quick list of which processes have how many files open. Cheers.

Hi, You'll likely have to use the MariaDB package to be able to build the plugin for RPi. Hope it helps

@troste Reinstalling Windows to have a clean Qt setup?! Sounds heavy... If your problem is that the installer cannot download stuff from the repository then use https://github.com/JKSH/QtSdkRepoChooser to select another repository.

Ok many thanks all ! solved

@Andrej-Debenjak it's not solution even in the slightest sense.

@Rohith if your issue is solved, please don't forget to mark your post as such. Thanks.

Hi, There might be something to do with qt.conf. Hope it helps

Additional information I forgot to post: I did find a way to remove the "Porter" tool from the 4.6.2 build and complete it successfully (although there were other problems). After the imbedded install us untared, go into the <untar dir>/tools/tools.pro and remove the "porting " line from the SUDIRS variable. then remove the <untar dir>/tools/porting directory. Continue with the ./configure step on the build process, and porting will not be built or referenced.

Figured the problem. If you call configure script with "-icu" option then pkg-config isn't taking effect. This is counter-intuitive. Also "LD_LIBRARY_PATH=<icudir>" is required during make because what seems to be a bug in some webkit subdirectory which doesnt respect PKG_CONFIG_PATH. Once "-no-icu", PKG_CONFIG_PATH in configure script and PKG_CONFIG_PATH, LD_LIBRARY_PATH in make are specified it works fine.

Hi, No I didn't know this tool and it worked perfectly. Thank you SGaist !

So the solution to this is to download and install: Visual Studio 2017 Qt 5.6.3 sources Perl 5.12 Python 2.7 Ruby 1.9 Win-Flex/Bison Start the VS2017 x86 command line prompt, then step into qt\5.6.3\src and configure and build f.ex. like this: configure -prefix path\to\qt\5.6.3\vs2017-xp32-static -release -static -static-runtime -target xp -strip -mp nmake nmake install You should now have a new kit called "vs2017-xp32-static" that will produce binaries compatible with WinXP 32-bit, which are stand-alone without dependencies. If you only need basic Core and GUI functionality, then step into src\qtbase and build from there instead. Good luck

In my case it was more complex. The antivirus client was tripping up over all the reg query calls in some of the bat files and delaying things sufficiently such that Qt got an incomplete environment. Seems Qt times out when calling vcvarsall. The delays were substantial. Minutes. Observed Qt creating temp bat files to call vcvarsall.bat over and over and over again. The solution I arrived at is to cache the resulting environment in another .bat file that simply sets the environment variables with the determined values. This is updated 1x day and the result is that I can open in Qt and have a working environment. It simply sets the saved environment and skips all the reg query calls. Note that vcvars64 or vcvars32 both make a reg query call for VS140COMNTOOLS. This seems enough of a delay to result in an incomplete path and hence cl.exe missing. I setup the caching within the vcvars64/32 files. If the cache file exists for the day then it's simply loaded, otherwise the reg query process is done to populate the values in case the environment changes and then those variables are written to the cache cmd file. The other bit of fun is that the order of reg query calls isn't optimized for current systems, meaning it tries several failing paths first, also adding to delay. And most every line in called bat files is prepended with @ (echo off) making debugging harder. That and the subroutines called have > null 2>&1 which also turns off output. So if you need to debug you need to deal with all that. Noticed 2017 bats have two branches of code to allow for debugging.

Thanks @sierdzio

Looks like something didn't work properly... Anyway, yes, you can do that.

Just thought of something: the usual way to prepare your application before packaging it is to follow the deployment procedure (usually using windeployqt) and then use that to create the installer. That way you ensure that your application is ready to run.

@jsulm Hello jsulm, Hello pramod-jadhav , We follow the steps to install the sqlcipher for qt on Ubuntu 16.04LTS, http://gssivasankari.blogspot.in/2015/11/building-qt-sqlcipher-driver-plugin.html. -- In this link we don't know where to copy. ################################################### File 3: sqlcipher.json { "Keys": [ "QSQLCIPHER" ] } 2. Copy directory \Qt5.3.1\5.3\Src\qtbase\src\sql\drivers\sqlite to -----? (Where to copy) Customize file The content of the file shall be like: ####################################################

@SGaist It seems I solved this problem! windeployqt got me files in this form c:\PAZI100\audio c:\PAZI100\bearer c:\PAZI100\config.ini c:\PAZI100\D3Dcompiler_47.dll c:\PAZI100\hello_speak.exe c:\PAZI100\iconengines c:\PAZI100\imageformats c:\PAZI100\libEGL.dll c:\PAZI100\libgcc_s_dw2-1.dll c:\PAZI100\libGLESV2.dll c:\PAZI100\libstdc++-6.dll c:\PAZI100\libwinpthread-1.dll c:\PAZI100\mediaservice c:\PAZI100\opengl32sw.dll c:\PAZI100\Pazi100.exe c:\PAZI100\platforms c:\PAZI100\playlistformats c:\PAZI100\printsupport c:\PAZI100\Qt5Core.dll c:\PAZI100\Qt5Gui.dll c:\PAZI100\Qt5Multimedia.dll c:\PAZI100\Qt5Network.dll c:\PAZI100\Qt5PrintSupport.dll c:\PAZI100\Qt5SerialPort.dll c:\PAZI100\Qt5Svg.dll c:\PAZI100\Qt5TextToSpeech.dll c:\PAZI100\Qt5Widgets.dll c:\PAZI100\texttospeech c:\PAZI100\translations c:\PAZI100\audio\qtaudio_windows.dll c:\PAZI100\bearer\qgenericbearer.dll c:\PAZI100\bearer\qnativewifibearer.dll c:\PAZI100\iconengines\qsvgicon.dll c:\PAZI100\imageformats\qgif.dll c:\PAZI100\imageformats\qicns.dll ... c:\PAZI100\mediaservice\dsengine.dll c:\PAZI100\mediaservice\qtmedia_audioengine.dll c:\PAZI100\platforms\qwindows.dll c:\PAZI100\playlistformats\qtmultimedia_m3u.dll c:\PAZI100\printsupport\windowsprintersupport.dll >>> Wrong: c:\PAZI100\texttospeech\qtexttospeech_sapi.dll c:\PAZI100\translations\qt_bg.qm ... I added a folder and voices appeared. c:\PAZI100>dir /s /b c:\PAZI100\audio c:\PAZI100\bearer c:\PAZI100\config.ini c:\PAZI100\D3Dcompiler_47.dll c:\PAZI100\hello_speak.exe c:\PAZI100\iconengines c:\PAZI100\imageformats c:\PAZI100\libEGL.dll c:\PAZI100\libgcc_s_dw2-1.dll c:\PAZI100\libGLESV2.dll c:\PAZI100\libstdc++-6.dll c:\PAZI100\libwinpthread-1.dll c:\PAZI100\mediaservice c:\PAZI100\opengl32sw.dll c:\PAZI100\Pazi100.exe c:\PAZI100\platforms c:\PAZI100\playlistformats c:\PAZI100\plugins c:\PAZI100\Qt5Core.dll c:\PAZI100\Qt5Gui.dll c:\PAZI100\Qt5Multimedia.dll c:\PAZI100\Qt5Network.dll c:\PAZI100\Qt5PrintSupport.dll c:\PAZI100\Qt5SerialPort.dll c:\PAZI100\Qt5Svg.dll c:\PAZI100\Qt5TextToSpeech.dll c:\PAZI100\Qt5Widgets.dll c:\PAZI100\translations c:\PAZI100\audio\qtaudio_windows.dll c:\PAZI100\bearer\qgenericbearer.dll c:\PAZI100\bearer\qnativewifibearer.dll c:\PAZI100\iconengines\qsvgicon.dll c:\PAZI100\imageformats\qgif.dll ... c:\PAZI100\mediaservice\dsengine.dll c:\PAZI100\mediaservice\qtmedia_audioengine.dll c:\PAZI100\platforms\qwindows.dll c:\PAZI100\playlistformats\qtmultimedia_m3u.dll c:\PAZI100\plugins\printsupport c:\PAZI100\plugins\texttospeech c:\PAZI100\plugins\printsupport\windowsprintersupport.dll >>> Right: c:\PAZI100\plugins\texttospeech\qtexttospeech_sapi.dll c:\PAZI100\translations\qt_bg.qm ... After replacing the folders, the program hello_speak.exe still worked. It's strange that two programs behave differently. Thanks a lot for your help!

Get in touch with Qt Company. They still offer paid support for Qt 4, as far as I've heard.