Reputation: 4911
I've got a large project that uses Cocoapods, whose compilation time is > 60 seconds. A large amount of this compilation time goes towards compiling third party SDK's: Facebook
and Parse
. This is because they contain the most source files.
I find myself running pod install
quite often, especially when I want to refactor my application and maintain create test app targets as well as unit test targets that require third party dependencies.
Building the project after pod install
causes all the SDK's get rebuilt again, even though nothing's changed about them. When done repeatedly this wastes lots of time during a refactoring process.
How can I force Cocoapods to make use of binary frameworks of those dependencies which I've already downloaded on disk, to avoid compilation?
Upvotes: 4
Views: 2758
Reputation: 475
I've had similar problems and developed my own utility 🏈 Rugby. In the current version, Rugby can cache all (or just some of them) pods dependencies and remove their targets from the Pods project.
Also, 🏈 Rugby doesn't change Podfile. You can use pod install && rugby
for working with cache or just pod install for working with sources. It's without changes in git.
Rugby was written using Swift and I regularly support this open source project.
Best regards
Upvotes: 2
Reputation: 218
You can use CocoaPods Binary to pre-compile your Pods during pod install
.
Upvotes: 1
Reputation: 4285
You can use CocoaPods Rome to generate binary frameworks which you can install yourself manually.
Upvotes: 2