Implementing SPM — a thorny path
summary
How to adopt Swift Package Manager (SPM) into an existing iOS codebase: reasons for choosing SPM, practical step-by-step migration from Apple example projects to creating the first module and generated projects, and the current project state. Concrete problems and solutions covered include compilation errors, mixing Swift and Objective‑C, incorrect linking crashes, using CocoaPods together with SPM, and CI build issues (TeamCity).
AI-written summary · about
chapters (6)
- 0:00Start
- 13:48Why not Xcode?
- 14:47Why not CocoaPods?
- 18:59Dependency Manager
- 25:25Swift Package Manager
- 37:25Multiple commands produce framework
related talks
19mReact Native without Cocoapods
08mPërparësitë dhe mangësitë e iOS Dependency Managers
59mDependency Managers — Catch Them All
01h 00m3rd party tools and frameworks you use in your applications and why
32mSimplified Swift Multiplatform Integration
53mRefactor Your Way Forward
45mMoving from Objective-C to Swift — Is It Really That Simple?
29mWorking with C and C++ in Apple environment