Building Qt5 with OpenSSL support using VS 2015

  • I'm looking for some guidance on building Qt5 with OpenSSL support using VS 2015
    I've read through a number of older posting on this forum and elsewhere. I am looking for a more recently shared experience(s).

    older posts:

  • Hi,
    I just build Qt from source with the instructions found here:
    The build succeeded without a single snatch, surprisingly... I work on Windows7 with MSVS2015 Community Edition installed. This build was without the -openssl-link configure option however.

    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):
    If you don't want to build, the above site also provides precompiled binaries for MSVS2015 as well!

    Then, this doc tells how you can statically link your Qt Build to the OpenSSL libraries you built above:

    The instructions seem clear. What have you tried so far?

    PS. The contents of my qt5vars.cmd batch file is as follows:

    REM Set up \Microsoft Visual Studio 2013, where <arch> is \c amd64, \c x86, etc.
    CALL "D:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" amd64
    SET _ROOT=E:\Qt-Debug
    SET PATH=%_ROOT%\qtbase\bin;%_ROOT%\gnuwin32\bin;%PATH%
    REM Uncomment the below line when using a git checkout of the source repository
    REM SET PATH=%_ROOT%\qtrepotools\bin;%PATH%
    SET PATH=E:\Qt\Tools\QtCreator\bin;%PATH%
    SET _ROOT=

    Up there, I used the amd64 architecture and the same path .bat path I use in my Qt Creator's MSVC2015 kit settings.

    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. the path of the configure script.

    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.

Log in to reply

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.