-
-
Notifications
You must be signed in to change notification settings - Fork 214
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
Bringing back Cocoapods/Carthage support #137
Comments
@vlasov I understand your pain. You should still be able to grab the version 4.7.3 of Stevia via Cocoapods though : target 'MyApp'
pod 'SteviaLayout', '~> 4.7.3'
use_frameworks! Let me know if that works on your side :) |
@vlasov any news on your side ? Any version prior to |
We need Carthage support for 5.0.1 |
We need cocoapods support for 5.0.1 |
@norbdev Carthage support (pre-built framework) as been added to the 5.0.1 release. Clone Stevia Repo swift package generate-xcodeproj
carthage build --no-skip-current --platform iOS
carthage archive @sdyalor, I'm sorry but Cocoapods support has been purposefully dropped in favour of more lightweight solutions such as Carthage and SPM. Could you elaborate a little bit about why you'd need it? Hope this helps :) |
@s4cha :( I cant elaborate but my company works with many ipads 4th gen with just ios 10 support, there is no way to get spm on their stack xcode10 :( |
@sdyalor I understand this must me painful to support. Isn't pre-5.0.0 versions a good tradeoff though? |
Please bring back Cocoapods support back. |
For now, SPM is not good enough to deal with resource bundle, so I have to use Cocoapods. |
You can have latest stevia on pod at following link |
@asifhabib can you please update your version in https://github.com/asifhabib/SteviaPod with last changes? |
#163 has been merged and pushed to Cocoapods repo, let me know if that works for you :) |
Works ! 🎉✨ |
Please! There's not too much effort to maintain a podspec file. But using two or more package managers is really painful (in terms of resolving possible package dependencies version conflicts)
The text was updated successfully, but these errors were encountered: