I was able to get it working. I was on the right path but didn't realize my ssl library was compiled with vs2008. Sorry, haven't really done much on Windows for a long time. :-)
Compiled with 2005 and this time just added it to the platform jars. Needed to add this to qtjambi-deployment.xml: <library name="bin/libeay32.dll" load="never" /> <library name="bin/ssleay32.dll" load="never" /> And updated the cache key (or removing ~/Local Settings/Temp/*jambi* works, too). Thanks, Mike On Wed, 2009-06-17 at 14:43 -0700, Mike Johnson wrote: > Hi all, > > I have been going nuts trying to get my program working on Windows. > Everything works great on Linux. I apologize if I've missed something > obvious. I'm using 4.5.0_01. > > I've downloaded the 9k win32 binary distribution from > http://www.slproweb.com/products/Win32OpenSSL.html and created a jar > openssl-win32.jar. > > I've added a deployment file: > <qtjambi-deploy system="win32"> > <cache key="msvc2005-20090513-1349" /> > <library name="lib/libeay32.dll"/> > <library name="lib/libssl32.dll"/> > <library name="lib/ssleay32.dll"/> > </qtjambi-deploy> > > With debug on, I see the libraries are loaded: > > Checking Archive 'openssl-win32.jar' > - cache key='msvc2005-20090513-1349' > - adding 'libeay32.dll' to library map > - library: name='lib/libeay32.dll', > - adding 'libssl32.dll' to library map > - library: name='lib/libssl32.dll', > - adding 'ssleay32.dll' to library map > - library: name='lib/ssleay32.dll', > > But I still get this error trying to access a ssl url: > QSslSocket: cannot call unresolved function SSLv3_client_method > QSslSocket: cannot call unresolved function SSL_CTX_new > QSslSocket: cannot call unresolved function SSL_library_init > QSslSocket: cannot call unresolved function ERR_get_error > QSslSocket: cannot call unresolved function ERR_error_string > > These libraries do appear to include the functions: > $ grep SSLv3_client_method * > Binary file libssl32.dll matches > Binary file ssleay32.dll matches > > I've run Depends.exe on these dlls and they don't appear to depend on > anything special. > > I'm aware that I can probably install openssl to a system directory > and > avoid this altogether but unfortunately I need to deploy to some > locked > down user desktops. > > Thanks for any help, > Mike > > > > > IMPORTANT NOTICE: This message is intended only for the addressee > and may contain confidential, privileged information. If you are > not the intended recipient, you may not use, copy or disclose any > information contained in the message. If you have received this > message in error, please notify the sender by reply e-mail and > delete the message. > _______________________________________________ > Qt-jambi-interest mailing list > [email protected] > http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest > _______________________________________________ Qt-jambi-interest mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest
