Qt-solutions Archive, August 2006
RE: Visual Studio, OpenSSL QTsslSocket
Message 1 in thread
Andrew - you are the man!
Thank you. This worked (i finally got back to this today).
I can now compile and link the Qt examples.
Now to see if they'll actually work!
Charley
-----Original Message-----
From: Andrew Francis [mailto:andrew@xxxxxxxxxxxxxxx]
Sent: Sunday, July 30, 2006 8:34 PM
To: Charley Burns
Cc: qt-solutions@xxxxxxxxxxxxx
Subject: Re: Visual Studio, OpenSSL QTsslSocket
Charley Burns wrote:
> Is anyone using Visual Studio.Net 2003 and the QTsslSocket solution
and
> openssl?
>
> I cant seem to get the right version of the ssleay32.lib into the
visual
> studio folders.
>
> I tried to build the source, but had to download perl and then compile
> from the command line and the perl scripts came up with errors.
Hi,
We're doing it like this:
** Perl
Install ActivePerl 5.8 (latest MSI package from ActiveState). Make sure
it's
in the path. (Other Perls would probably work as well, but I can't say
I've
tried).
** OpenSSL debug build (for Qt built in debug mode)
Extract the OpenSSL source into c:\libs\vc71-qt33-debug\openssl. Go into
that
directory. Edit util\pl\VC-32.pl so that the "/MD" flag in $cflags
becomes
"/MDd". (Note that there is a code block to amend $cflags to use /MDd if
$debug is set, but that doesn't work with this build process).
Then run:
C:\libs\vc71-qt33-debug\openssl>perl Configure VC-WIN32
C:\libs\vc71-qt33-debug\openssl>ms\do_masm.bat
C:\libs\vc71-qt33-debug\openssl>nmake -f ms\ntdll.mak
** OpenSSL release build
Repeat the entire procedure from scratch (ie fresh extraction of the
TAR) in
c:\libs\vc71-qt33-release\openssl, but this time don't edit
util\pl\VC-32.pl.
** qtsslsocket build
Make sure that the following are in the .pri file for qtsslsocket, or
that you
otherwise enable these paths:
OPENSSL_PATH = <<<path to c:\libs\....\openssl>>>
win32 {
INCLUDEPATH += $${OPENSSL_PATH}/inc32
LIBS += -L$${OPENSSL_PATH}/out32dll libeay32.lib ssleay32.lib
}
--
[ signature omitted ]
