[Development] openssl-linked include paths in Qt 5.8

Thiago A. CorrĂȘa thiago.correa at gmail.com
Wed Apr 19 05:03:18 CEST 2017

I have struggled with this in 5.5 and there was closed bug (no
feedback) that dates back from 5.5 as well. From what I can tell nmake
distclean misses something. I was able to work around this with both
of these options:

    - Erase all source code and download/extract new fresh source tree
    - Edit .qmake.super and add: INCLUDEPATH += -I c:\path...\include
and LIBS += -L c:\path...\lib

I suppose after configure qmake -recursive could also work. Most of
the time it looks like previously generated Makefiles get stale.

Kind Regards,
      Thiago A. Correa

On Tue, Apr 18, 2017 at 10:26 PM, Kuba Ober <kuba at mareimbrium.org> wrote:
> When I build 5.8 configured with -static -openssl-linked -I c:\path\to\openssl\include -L c:\path...\lib etc., the OpenSSL configure test passes, but building the network code fails since the include path never makes it to the Makefile (for nmake). Adding QMAKE_INCDIR+=c:\path...\include doesn't help. Am I missing something, or is this a bug? OPENSSL_PATH also seems to be a no-op.
> Thanks, Kuba Ober
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development

More information about the Development mailing list