Then, since Qt Creator comes with the jom.exe tool build tool, I added the path to it to the PATH variable so that I can build with jom instead of nmake by simply typing jom at the command line. The directory E:\Qt-Debug is the directory where I copied the Qt source from my Qt installation (originally in the \Src subdirectory), i.e. bat path I use in my Qt Creator's MSVC2015 kit settings. Up there, I used the amd64 architecture and the same path. SET PATH=E:\Qt\Tools\QtCreator\bin %PATH% REM SET PATH=%_ROOT%\qtrepotools\bin %PATH% REM Uncomment the below line when using a git checkout of the source repository SET PATH=%_ROOT%\qtbase\bin %_ROOT%\gnuwin32\bin %PATH% The contents of my qt5vars.cmd batch file is as follows: REM Set up \Microsoft Visual Studio 2013, where is \c amd64, \c x86, etc.ĬALL "D:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" amd64 ![]() Then, this doc tells how you can statically link your Qt Build to the OpenSSL libraries you built above: If you don't want to build, the above site also provides precompiled binaries for MSVS2015 as well! It seems that before you configure and start your Qt build, you need to build OpenSSL with the instructions from here (there are even batch files provided for build with MSVS2015): This build was without the -openssl-link configure option however. I work on Windows7 with MSVS2015 Community Edition installed. ![]() The build succeeded without a single snatch, surprisingly. ![]() I just build Qt from source with the instructions found here:
0 Comments
Leave a Reply. |