<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" id="owaParaStyle"></style>
</head>
<body fpstyle="1" ocsi="0">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">Hi Franics,
<div><br>
</div>
<div>Thanks for getting back to me. I didn't try replacing the OpenSSL binaries directly, as I was under the impression that major version changes never match in terms of signatures (i.e. projects linked against older Libeay32.lib v0.9 would not successfully
load a 1.0.1.x libeay32.dll). At the very least it doesn't seem very safe from a stability point of view.</div>
<div><br>
</div>
<div><span style="font-size: 10pt;">I should have explained myself better in the original message sent to the mailing list....I actually did move on to take a crack at building Vortex myself. As discussed in an off-list email, I think I could ultimately get
it to work, but it is far from a trivial task for a Visual Studio developer. LibVortex has a bunch of additional dependencies, each of which have their own complexities/quirks when building on Microsoft Windows, without even getting to the issue of 64 bit
targets. These dependencies include libgsasl, libaxl, libgsasl, openssl, and libcryto. Most of them have to be built from source for Visual Studio/Windows, and it was not clear to me which versions of each dependency the current LibVortex should be built
against. </span><span style="font-size: 10pt;">LibAxl also turns out to require mingw installed, even if building from Visual Studio. </span></div>
<div><span style="font-size: 10pt;"><br>
</span></div>
<div><span style="font-size: 10pt;">For now, we've decided we will try to get everything working by not using TLS, etc. A quick experiment has shown that the basic vortex functionality is only loading libvortex/libaxl binaries, avoiding our OpenSSL conflict.
</span></div>
<div><span style="font-size: 10pt;"><br>
</span></div>
<div>Your suggestion to build ourselves is definitely valid, and we may have to revisit in the future, but with any luck we can hold out until a future Vortex binary release. </div>
<div><br>
</div>
<div>Thanks again,</div>
<div>Jeff</div>
<div><br>
</div>
<div>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div id="divRpF915219" style="direction: ltr;"><font face="Tahoma" size="2" color="#000000"><b>From:</b> Francis Brosnan Blázquez [francis@aspl.es]<br>
<b>Sent:</b> Wednesday, July 02, 2014 2:41 PM<br>
<b>To:</b> Jeff Kenneally<br>
<b>Cc:</b> vortex@lists.aspl.es<br>
<b>Subject:</b> Re: [Vortex] Vortex OpenSSL versioning<br>
</font><br>
</div>
<div></div>
<div><br>
<blockquote type="CITE">
<pre>Hello,
</pre>
</blockquote>
<pre></pre>
Hi Jeff,<br>
<br>
Sorry for the delay...<br>
<br>
<blockquote type="CITE">I'm working on an application that currently needs to be built against both 32 and 64 bit Windows targets. I was happy to get confirmation recently that the Vortex SDK is produced for both.
<br>
<br>
I've since downloaded the latest versions of both SDK's from: "<a href="https://code.google.com/p/vortexlibrary/downloads/list" target="_blank">https://code.google.com/p/vortexlibrary/downloads/list</a>"<br>
<br>
There is a slight disparity in version numbers for the current w64 build (1.1.10) vs w32 (1.1.12), which in itself is not an issue.
<br>
</blockquote>
<br>
Ok,<br>
<br>
<blockquote type="CITE">However, one battle that we can never seem to win with our product is that at least 3 third party packages we link against all use OpenSSL (ie libeay32.dll). Anytime we update any of them, it's a horrible juggling act to find up to date
versions of all these dependencies that use a similar-enough version of Libeay32.DLL to not cause conflicts at runtime. Slight differences in build numbers tend to be fine, but the larger the gap, the more chance we start seeing missing symbol errors at run-time,
or even linker errors depending on which of the various Libeay32 DLL's present actually got loaded by our process.<br>
</blockquote>
<br>
Did you try changing/upgrade libssl library to a newer version by just replacing them? Did it break after that?<br>
<br>
The OpenSSL API subset used by Vortex Library is quite common and it works with openssl versions across different platforms with those version differences....<br>
<br>
<blockquote type="CITE">One thing I've noticed between the two Vortex Windows SDK's I mention above is that the w64 SDK contains Libeay32.dll vs 1.0.0.5, while the w64 SDK (newer version number) contains an older 0.9.8.11 version. Both versions are quite a
bit behind the more recent releases (ie current GDAL binaries we are using link against Libeay32.dll v1.0.1.7).<br>
<br>
Is there any way we can get Vortex w32 and w64 SDK's that use the same version of OpenSSL, and using a more recent version, such as 1.0.1.7?<br>
</blockquote>
<br>
Ok, this is obvious, but the best way is to grab source code from SVN or latest tar.gz and have them compiled with your current compiler. That way you don't have to depend on us releasing next stable release and/or producing those SDK installer plus the fact
that debugging and binary output will match perfectly the entire product (without mentioning you'll be able to better control OpenSSL versions).<br>
<br>
Best Regards,<br>
<br>
<blockquote type="CITE">Thanks very much,<br>
Jeff
<pre>_______________________________________________
Vortex mailing list
<a href="mailto:Vortex@lists.aspl.es" target="_blank">Vortex@lists.aspl.es</a>
<a href="http://lists.aspl.es/cgi-bin/mailman/listinfo/vortex" target="_blank">http://lists.aspl.es/cgi-bin/mailman/listinfo/vortex</a>
</pre>
</blockquote>
<br>
<table cellspacing="0" cellpadding="0" width="100%">
<tbody>
<tr>
<td>
<pre>--
Francis Brosnan Blázquez <<a href="mailto:francis.brosnan@aspl.es" target="_blank">francis.brosnan@aspl.es</a>>
ASPL
91 134 14 22 - 91 134 14 45 - 91 116 07 57
AVISO LEGAL
Este mensaje se dirige exclusivamente a su destinatario. Los datos
incluidos en el presente correo son confidenciales y sometidos a secreto
profesional, se prohíbe divulgarlos, en virtud de las leyes vigentes. Si
usted no lo es y lo ha recibido por error o tiene conocimiento del mismo
por cualquier motivo, le rogamos que nos lo comunique por este medio y
proceda a destruirlo o borrarlo.
En virtud de lo dispuesto en la Ley Orgánica 15/1999, de 13 de
diciembre, de Protección de Datos de Carácter Personal, le informamos de
que sus datos de carácter personal, recogidos de fuentes accesibles al
público o datos que usted nos ha facilitado previamente, proceden de
bases de datos propiedad de Advanced Software Production Line, S.L.
(ASPL). No obstante, usted puede ejercitar sus derechos de acceso,
rectificación, cancelación y oposición dispuestos en la mencionada Ley
Orgánica, notificándolo por escrito a:
ASPL - Protección Datos, C/Antonio Suárez 10 A-102, 28802, Alcalá de
Henares (Madrid).
</pre>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
</div>
</body>
</html>