Thank you!
That is clear.
вт, 01 ноя 2016 г., 12:47 Kim Gräsman :
> Hi Ernst,
>
> On Tue, Nov 1, 2016 at 10:25 AM, Ernst Maurer
> wrote:
> > Thank you for the reply,
> > I've tried to build dynamic version (import lib + dll) so I see the libs
> > like:
> > openssl.lib
> > libcrypto.lib
> > capi.
I'd recommend using the official releases rather than the
work-in-progress code at the head of git. Whoever looks after the
library which needs OpenSSL should be able to tell you what version it
needs, but from those names it's the 1.0.2 branch or earlier. 1.0.2 will
be supported until the end
Hi Ernst,
On Tue, Nov 1, 2016 at 10:25 AM, Ernst Maurer wrote:
> Thank you for the reply,
> I've tried to build dynamic version (import lib + dll) so I see the libs
> like:
> openssl.lib
> libcrypto.lib
> capi.lib
> and some other ones,
>
> so do you mean that libeay32 and ssleay32 some depricate
Thank you for the reply,
I've tried to build dynamic version (import lib + dll) so I see the libs
like:
openssl.lib
libcrypto.lib
capi.lib
and some other ones,
so do you mean that libeay32 and ssleay32 some depricated version ? and
recommend me to go throu the git history for a looking for? (of co
I think this depends on what version of OpenSSL you're using and whether
you're using static or dynamic libraries, none of which you mention.
There were changes in library names in recent releases. Try reviewing
the various NOTES, INSTALL, and README files for whichever version of
OpenSSL you a
