-
-
Notifications
You must be signed in to change notification settings - Fork 332
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
Will OpenSSL 3.1.x be the next step to have an xcframework? #167
Comments
is it the time already? |
Reading from the official site: https://www.openssl.org/blog/blog/2023/03/28/1.1.1-EOL/ So I guess from September 3.1.x will be the only supported series :) |
I was able to build for 3.1.1 by substituting darwin-common->module_ldflags from "-bundle" to "-dynamiclib" in Configurations/shared_info.pl I haven't fully tested it yet, but it does complete the build. Additionaly, had to update the header files in support/OpenSSLh.h to include the 3.1.1 headers (and remove deprecated, deleted ones) and do the same in the OpenSSL.xcproject - update the include files. |
@krzyzanowskim thank you for providing timely updates all this time (the latest one just hours ago), but I'd second @ferencIOS's request as OpenSSL 1.1.1 "will no longer be receiving publicly available security fixes" after September 11 which is in almost exactly a month from today. Are there plans to provide updates for the 3.0 or 3.1 series going forward? |
I plan to prepare update to 3.x later this month. |
That's great, thank you again. |
3.1.2 update PR is on #174 if anyone wants to give it a try. It's not tagged so you have to use the branch name. |
@krzyzanowskim Thanks for the update! OpenSSL 3.0 changed its license though (cf. https://www.openssl.org/docs/man3.0/man7/migration_guide.html#License-Change); maybe you want to reflect that? |
Hi all!
As per title: is there any idea to port openssl 3.1.x?
Thank you.
The text was updated successfully, but these errors were encountered: