-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Podspec CocoaPods 1.0 compatibility #127
Comments
Solutions v1
Updated PodSpec:podspec:
Result =>podfile looks liks
Demo project is compiling fine. However, linting pod spec cause error --> Linting error (pods 1.0)
error |
I found solution for linting podspec with static library (add
Result ==>Podspec with dependency to Podspec that includes .a library can be linted :) 🎉 🎉 🎉 🎉 🎉 |
Solution v2Adding openssl dynamic framework to themis wrapper, linking podspec to the dynamic framework. Dynamic frameworksThe idea behind is to build OpenSSL as dynamic framework. The problem is that dynamic frameworks need a lot of extra work to do (like, to create separate iOS/MacOS Xcode workspaces to be able to generate frameworks). However, @jcavar has done incredible work and created PRs for this: krzyzanowskim/OpenSSL#26 I've grabbed generated dynamic frameworks and added them to themis objcwrapper sources (see pods_1.0 branch). Podspec
Build errorUnfortunately, project build causes errors Possible reasonMaybe connected with this CP bug: ResultWell, project cannot be built :) And podspec cannot be linted :) Any suggestions? Wait for CP fix? Or is it header issue? |
Last issue may be fixed by disabling modules, as described on apple forums. So, resulting wrapper contains built-in openssl frameworks and disabling modules flag. PodspecLink to frameworks.
Project is now building successfully, but you may need to use Themis via Bridging header.
LintingHowever, linting on CP 1.0 fails due to
¯_(ツ)_/¯ |
I split this discussion into two threads, see issue #128 for further dynamic frameworks discussion |
Pushed new podspec and tag 0.9.3.1 |
The given:
Creating a new iOS project, linking themis master as CocoaPod.
The problem:
If you create new project using CocoaPods v1.0.1, your podfile includes
use_frameworks!
and links to the HEAD of master branch, then Pods can't be installed.podfile:
Error log
The text was updated successfully, but these errors were encountered: