Ok, found what happened.
For a reason that remains gloomy to me (I think this is undocumented from
POCO), POCO adds the following dependencies to the vcxproj file:
ws2_32.lib;iphlpapi.lib;libeay32.lib;ssleay32.lib;%(AdditionalDependencies)
I have removed those dependencies and it looks to be ok
In message
Sorry, I meant no reference to libeaymt64.lib or ssleaymt64.lib
On Sat, Jul 8, 2017 at 12:20 PM, Raymi Coevan
wrote:
> Hi,
>
> Indeed, the list you mentioned is exactly the one I have in my
> environment. In my MSVC project, I only statically link with
>
Hi,
Indeed, the list you mentioned is exactly the one I have in my environment.
In my MSVC project, I only statically link with libcrypto64MT.lib and
libssl64MT.lib. No reference is made to libeaymt64.lib or libssl64MT.lib,
from what I know at least. So I don't understand why I got these link
Hi,
In message
on Sat, 8 Jul 2017 11:19:57 +0200, Raymi Coevan said:
...
raymi.coevan> I have dependencies on Poco and OpenSSL (1.1.0e is currently used
on
raymi.coevan> MacOSX and Linux), and when
Dear OpenSSL experts,
I'm a junior developer so please forgive me if this is a stupid question.
I'm trying to port an existing application, currently running on MacOSX and
Linux, to Windows 64 bits platform which is not my favorite environment.
I have dependencies on Poco and OpenSSL (1.1.0e is