Linking problems in MSVC++

Don Payette payettedon at gmail.com
Thu Aug 24 20:42:25 UTC 2023


I would imagine all of the Microsoft stuff comes in.
Wouldn't the BIO_ stuff be in one of the OpenSSL libs?

Don Payette
(cell) 479-216-6320 <(479)%20216-6320>


On Thu, Aug 24, 2023 at 3:11 PM Floodeen, Tom <thomas.floodeenjr at siemens.com>
wrote:

> It’s part of the SDK and should be found by Visual Studio.
>
>
>
> *From:* Don Payette <payettedon at gmail.com>
> *Sent:* Thursday, August 24, 2023 2:10 PM
> *To:* Floodeen, Tom (DI SW EBS ENG PHY PL1) <thomas.floodeenjr at siemens.com
> >
> *Cc:* openssl-users at openssl.org
> *Subject:* Re: Linking problems in MSVC++
>
>
>
> Where would I find that file?
>
>
>
> Don Payette
>
> (cell) 479-216-6320 <(479)%20216-6320>
>
>
>
>
>
> On Thu, Aug 24, 2023 at 2:45 PM Floodeen, Tom <
> thomas.floodeenjr at siemens.com> wrote:
>
> Are you linking with ws2_32.lib?
>
>
>
> *From:* openssl-users <openssl-users-bounces at openssl.org> *On Behalf Of *Don
> Payette
> *Sent:* Thursday, August 24, 2023 1:33 PM
> *To:* openssl-users at openssl.org
> *Subject:* Linking problems in MSVC++
>
>
>
> When I do a build in MSVC++ I get link errors, here is the one for
> _BIO_ctrl.
>
>
>
> Severity Code   Description
> Error LNK2019  unresolved external symbol _BIO_ctrl referenced in function
> "public: void __thiscall CSocket::Connect(class CDFDSSocket *,char
> *,unsigned short)" (?Connect at CSocket@@QAEXPAVCDFDSSocket@@PADG at Z)
>
>
> I get the same for  _BIO_free_all, _BIO_new_ssl_connect and more.
>
>
>
> I installed the OpenSSL Win64 pre-compiled binaries and pointed
> to C:\Program Files\OpenSSL-Win64\lib in Library Directories.
>
>
>
> What am I missing?
>
>
>
> Don Payette
>
> (cell) 479-216-6320 <(479)%20216-6320>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mta.openssl.org/pipermail/openssl-users/attachments/20230824/62292272/attachment-0001.htm>


More information about the openssl-users mailing list