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:<AdditionalDependencies>ws2_32.lib;iphlpapi.lib;libeay32.lib;ssleay32.lib;%(AdditionalDependencies)</AdditionalDependencies>
On Sat, Jul 8, 2017 at 12:34 PM, Richard Levitte <levitte@xxxxxxxxxxx> wrote:
In message <CANFqjkLN5DHq7uOTuxYgCCVLv9==WQLO=3j8JJM9QW2p41012Q@mail. gmail.com > on Sat, 8 Jul 2017 12:29:31 +0200, Raymi Coevan <raymi.coevan@xxxxxxxxx> said:
raymi.coevan> Sorry, I meant no reference to libeaymt64.lib or ssleaymt64.lib
raymi.coevan>
raymi.coevan> On Sat, Jul 8, 2017 at 12:20 PM, Raymi Coevan <raymi.coevan@xxxxxxxxx>
raymi.coevan> wrote:
...
raymi.coevan>
raymi.coevan> Indeed, the list you mentioned is exactly the one I have in my
raymi.coevan> environment. In my MSVC project, I only statically link with
raymi.coevan> libcrypto64MT.lib and libssl64MT.lib. No reference is made to
raymi.coevan> libeaymt64.lib or libssl64MT.lib, from what I know at least. So I
raymi.coevan> don't understand why I got these link errors...
Can't help you there, sorry.
Cheers,
Richard
--
Richard Levitte levitte@xxxxxxxxxxx
OpenSSL Project http://www.openssl.org/~levitte/
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
-- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users