1.1.0g update + arm64 support about openssl HOT 14 CLOSED

The --openssldir config option no longer works, 'make' will put binaries in the working directory rather than /tmp

changed to --prefix in build.sh script

from openssl.

Hi, yes, OpenSSL release 1.0.2 is EOL, no longer supported since January 1st, 2020:
https://www.openssl.org/blog/blog/2019/11/07/3.0-update/
Please update it to the latest of current LTS release, 1.1.1

from openssl.

I've adapted the script to do this. The primary changes that are needed are:

1. The --openssldir config option no longer works, 'make' will put binaries in the working directory rather than /tmp
2. The sed command looks for "CFLAG=" instead of "CFLAGS="

You can also remove all the 32-bit architectures, only arm64 and x86_64 are needed these days.

from openssl.

@wyllys66 , Are able to upgrade as suggested by @rspq. If so, I do need your help to upgrade to 1.1.0

from openssl.

@satinder-singh-axway - I ended up forking and have a new repo that builds OpenSSL 1.1.1-stable for iOS. I havent tested with MacOS build.

https://github.com/wyllys66/OpenSSLFrameworkForIOS

from openssl.

Due to changes in 1.0.x support, I'll update to 1.1.x next time.
https://www.openssl.org/blog/blog/2018/05/18/new-lts/

from openssl.

There is ongoing work on 1.1.1-lts branch
https://github.com/krzyzanowskim/OpenSSL/tree/marcin/1.1.1-lts

from openssl.

Hi, would that branch have already everything needed to create the framework?

from openssl.

@jrpinteno give it a try please and let me know if you encounter problems

from openssl.

@krzyzanowskim I've tried two different approaches. For what is worth, I was using carthage 0.36 and Xcode 12
I created the framework using the script provided which went smooth. Once added to framework to my test project I could not import framework. Not sure if that's because module.modulemap is not created. I added manually one but couldn't make it work.

I have to say I'm a bit out of my depth when creating/using frameworks, I mainly use spm

Using cocoapods to fetch from the git branch straight away, module is not detected either.

from openssl.

Not sure if that's because module.modulemap is not created.

Xcode no longer produces it any longer and I have no idea why

from openssl.

@jrpinteno I did push fixes to the branch, you can try it again now. Should be better.

from openssl.

I bring partially good news. I was able to make it work via create-framework script on a laptop with Big Sur beta.
On Catalina although the framework is correctly added and autocompletes to import OpenSSL correctly, it immediately warns error and fails to compile project.

In both cases I've used Xcode 12.0.1, a brand new project is created, framework added the same way (through add files menu), then import OpenSSL and try to build.

I haven't been able to import it with cocoapods the way it's shown in #88 neither on Big Sur nor Catalina.

Here's the error log, hope it helps

from openssl.

On Catalina although the framework is correctly added and autocompletes to import OpenSSL correctly, it immediately warns error and fails to compile project.

Most likely because I built binaries on Big Sur (11 beta9 + Xcode 12.2 beta2).

from openssl.