New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support OpenSSL 1.1.0 lib names in Windows non-configure builds #984

Closed
jay opened this Issue Aug 26, 2016 · 3 comments

Comments

Projects
None yet
3 participants
@jay
Member

jay commented Aug 26, 2016

I did this

winbuild, projects and probably others link to ssleay32.lib and libeay32.lib for OpenSSL. Since the release of OpenSSL 1.1.0 they have changed the library names to libssl.lib and libcrypto.lib.

I expected the following

Even though these build systems aren't dynamically generated I think we will need a way to determine what libs to link to, since any lib that is not found causes an error. I started a thread in openssl-dev about this, but I expect I'll be told to just use the new names.

Related https://curl.haxx.se/mail/lib-2016-08/0104.html cc @rodwiddowson

@gvanem

This comment has been minimized.

Show comment
Hide comment
@gvanem

gvanem Dec 17, 2016

Member

BTW if using BoringSSL (as a drop-in replacement for OpenSSL), some of it's functions have been moved to decrepit.lib. AFAICS they are BIO_set_ssl() and BIO_f_ssl(). Which complicates building on Windows even more.

Member

gvanem commented Dec 17, 2016

BTW if using BoringSSL (as a drop-in replacement for OpenSSL), some of it's functions have been moved to decrepit.lib. AFAICS they are BIO_set_ssl() and BIO_f_ssl(). Which complicates building on Windows even more.

@Mellnik

This comment has been minimized.

Show comment
Hide comment
@Mellnik

Mellnik Jan 4, 2017

Please add support for OpenSSL 1.1.0 Series

Mellnik commented Jan 4, 2017

Please add support for OpenSSL 1.1.0 Series

@stale

This comment has been minimized.

Show comment
Hide comment
@stale

stale bot Jul 3, 2017

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

stale bot commented Jul 3, 2017

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot closed this Jul 18, 2017

@lock lock bot locked as resolved and limited conversation to collaborators May 6, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.