Open vlasov opened 4 years ago
@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 4.8.0
is still available through Cocoapods and Carthage.
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. If a release is not available, here is how you can generate a Carthage package :
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. I would like to build the pod library as a static library, so that I can get a smaller IPA file size.
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 https://github.com/asifhabib/SteviaPod
@s4cha With Xcode 13.2 SPM has broke. Also in our big project we have tried use SPM, but with VPN it started to resolve packages and unnesessary downloads, so we decided to leave only cocoapods. Please! Add cocoapods support. A lot of developers and teams use it.
@asifhabib can you please update your version in https://github.com/asifhabib/SteviaPod with last changes?
https://github.com/freshOS/Stevia/pull/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)