add workspace with iOS and macOS projects

[jcavar]

Ok, here is the first step. Added projects for building iOS and macOS frameworks from Xcode. You can just open workspace, select appropriate scheme, build project and new binary should be copied in bin folder.

[krzyzanowskim]

...but adding sub Pod shouldn't be that many changes. Why would you want add Xcode project at all? It's unecessary

[jcavar]

Because integrating framework as is doesn't work. It doesn't contain plist and id inside binary is not properly set (see this issue x2on/OpenSSL-for-iPhone#103)

[krzyzanowskim]

How "OpenSSL-iOS" and "OpenSSL-macOS" is generated?

[krzyzanowskim]

Isn't Dynamic framework too much trouble after all (bitcode, this)? how about static framework that can be generated quite easily

[jcavar]

Yes, but that doesn't solve CocoaPods issue, right?

[jcavar]

OpenSSL-iOS and OpenSSL-macOS are Xcode projects which are manually generated mostly following Method 2 in this article

[eladav]

Hey,
So, Why was this and #26 closed? And why was this PR rejected?
I know it's an old issue/pr but it looks like a lot of iOS developers would benefit from that, as well as some major security frameworks for Apple platforms.
Edit: and from taking a quick look at the solution it looks like a good one.

[sashabaranov]

+1 for this PR, static linking is painful.

If not merged it would be helpful to instruct users how to integrate this project into their project(i.e. http://stackoverflow.com/questions/32125338/how-can-i-use-an-a-static-library-in-swift) and ignore dependencies to it in Podfile

[levigroker]

FYI, not to diminish the excellent work done here, but I have taken the liberty of creating my own fork which combines these ideas in order to create frameworks. https://github.com/levigroker/GRKOpenSSLFramework