It is left up to you, the developer, to take the compiled frameworks and embed them into your project as needed.īecause of this difference in philosophy and functionality, there should be no problem using both at the same time. ![]() ![]() Carthage simply pulls down dependancies (using Git) and builds them into embeddable binary frameworks. Unlike CocoaPods, which reaches in and modifies your project files to include the paths to your dependancies, Carthage intentionally keeps its hands out of your project files. Not knowing much about Carthage, one of the first questions that I had was whether it could be used alongside CocoaPods. ![]() ReactiveCocoa, along with many other open-source projects, has shifted to officially supporting Carthage, rather than CocoaPods, for dependency management. In my app, I wanted to try using the latest version of ReactiveCocoa, which has been recently rewritten in Swift. Having heard that it’s possible to mix the two languages within a single project, I set out to see how difficult that would be. Here are a few things I learned throughout the process. Rather than starting a completely new project using only Swift, I thought it would be an interesting challenge to start with some Objective-C and try converting a class or two to Swift. ![]() I know I’m a little late to the game, but I just recently started playing around with Swift, Apple’s new flagship language for developing apps for iOS, OS X and Apple Watch.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |