TARGET VS COCOAPODS: why choose one if you can have BOTH?
summary
Claims a reproducible workflow that lets modules act as both Tuist-generated targets and CocoaPods with precompiled XCFrameworks using Tuist for manifest-driven project generation and CocoaPods for packaging and xcbuild -create-xcframework to produce binaries. Demonstrates a three-step conversion (targets → local pods → precompiled frameworks) in a live demo, requires a strict sources/supporting files/resources folder layout, switches by editing the Project.swift and running tuist generate plus pod install, and works but only for full-mode switches and requires bumping pod repos for code changes.
AI-written summary · about
chapters (16)
- 0:00Intro
- 2:32Agenda
- 3:22Goal and solution
- 5:42Modularisation means
- 9:17Target
- 10:57Pods
- 12:54XC Framework
- 14:20Comparison
- 16:20What is Tuist?
- 17:32Target vs Cocoapods
- 18:38Target folder structure
- 20:07Repositories
- 21:00Steps for the configuration switch
- 22:16Solution limitation
- 23:32Practical Demostration
- 35:30Conclusion
related talks
45mSwift, Frameworks & Modules, Learnings from CocoaPods
39mScaling iOS DevX with Tuist
54mCocoaPods, the Objective-c Dependency Manager we've been Waiting for
30mFrom CocoaPods to Swift Package Manager
45mTooling in Swift - Xcode Integration & CI
26mPractical Cross-Platform Swift
37mCut costs, not corners: Master modularization with SPM
53mAutomate your whole iOS Projects & share resources with Android