Skip to content
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

[poco] ssl/https support on windows failed #7555

Closed
debugfan opened this issue Aug 5, 2019 · 4 comments
Closed

[poco] ssl/https support on windows failed #7555

debugfan opened this issue Aug 5, 2019 · 4 comments
Labels
category:port-bug The issue is with a library, which is something the port should already support

Comments

@debugfan
Copy link

debugfan commented Aug 5, 2019

Describe the bug
vcpkg uses the develop branch of poco, but its ssl/https support on Windows is malfunction in this version.

Reason & Workaround
Poco current develop branch enables both NetSSL_OpenSSL and NetSSL_Win options when build on Windows. and Its header files are mixed and overwritten after installed by vcpkg,
but NetSSL_OpenSSL and NetSSL_Win used to support ssl/https with different implements, shouldn't be mixed.
It seems only its current develop branch has this problem. A simplest workaround is using a stable or master version of poco as port instead.

Environment

  • OS: Windows

To Reproduce
Steps to reproduce the behavior:

  1. ./vcpkg install poco
  2. Create a project, copy sample codes under NetSSL_OpenSSL or NetSSL_Win
  3. Just run it simply, program will crash.
@cbezault cbezault added the category:port-bug The issue is with a library, which is something the port should already support label Aug 8, 2019
@cbezault
Copy link
Contributor

cbezault commented Aug 8, 2019

Thanks for reporting this, is there an issue in the upstream we can track?

@debugfan
Copy link
Author

debugfan commented Aug 9, 2019

Thanks for reporting this, is there an issue in the upstream we can track?

Someone has recently opened a relative issue in the upstream: pocoproject/poco#2760
But this issue seems to exist a long time, and only occur while installed by vcpkg.
People who use master or stable branch or install manually will maybe ignore this issue,
so it will be probably a long time to wait developers in the upstream to notice and fix it.

@JackBoosY
Copy link
Contributor

Hi @debugfan, does #7698 fixed this issue?

@debugfan
Copy link
Author

Hi @debugfan, does #7698 fixed this issue?

Yes, it fixed. Nice work!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:port-bug The issue is with a library, which is something the port should already support
Projects
None yet
Development

No branches or pull requests

3 participants