{"id":1230,"date":"2015-02-28T11:55:42","date_gmt":"2015-02-28T17:55:42","guid":{"rendered":"http:\/\/dev.iachieved.it\/iachievedit\/?p=1230"},"modified":"2015-02-28T20:57:13","modified_gmt":"2015-03-01T02:57:13","slug":"using-carthage-with-alamofire","status":"publish","type":"post","link":"https:\/\/dev.iachieved.it\/iachievedit\/using-carthage-with-alamofire\/","title":{"rendered":"Using Carthage with Alamofire"},"content":{"rendered":"

I have never been a fan of CocoaPods<\/a> due to its intrusiveness in the build process and insistence on creating Xcode project workspaces. Unfortunately managing dependencies through the use of Git submodules<\/a> is no better. How many times have you told yourself, “Okay, I understand submodules now” only to be met with fatal: reference is not a tree:<\/code> when trying to do a git submodule update<\/code>? Perhaps I’m dense, but I shouldn’t have to turn to Google every time I check out a project which uses submodules.<\/p>\n

In the tutorial HTTP JSON Request with Swift and Alamofire<\/a> we used the git submodule approach to add the Alamofire framework as a dependency to our Xcode project. Let’s now look at a new approach to managing framework dependencies with Carthage.<\/p>\n

Carthage<\/a> was developed to make framework dependency management in your Xcode projects just a bit easier. Luckily for us, Alamofire now supports using Carthage, and we can leverage that support in our project to get rid of the git submodule approach.<\/p>\n

To get started with Carthage, you’ll first need to install Homebrew<\/a>. If you have never used Homebrew<\/a> before, you’re in for a real treat. To install Homebrew open a terminal and paste:<\/p>\n

\r\nruby -e \"$(curl -fsSL https:\/\/raw.githubusercontent.com\/Homebrew\/install\/master\/install)\"\r\n<\/pre>\n
Follow the prompts and once Homebrew is properly installed then you can install carthage with brew install carthage<\/code>.
\n
\n==> Downloading https:\/\/downloads.sf.net\/project\/machomebrew\/Bottles\/carthage-0.5.2.yosemite.bottle.tar.gz
\nAlready downloaded: \/Library\/Caches\/Homebrew\/carthage-0.5.2.yosemite.bottle.tar.gz
\n==> Pouring carthage-0.5.2.yosemite.bottle.tar.gz
\n[emoji beer mug] \/usr\/local\/Cellar\/carthage\/0.5.2: 157 files, 34M
\n<\/code><\/p>\n
Now, let’s look at how to add Alamofire to our project using Carthage. The first step is to create a Cartfile<\/code> in our project folder. The Cartfile<\/code> is what you might expect: a list of dependencies (and where to fetch them from) for our project. Our Cartfile<\/code> will contain a single dependency on Alamofire.<\/p>\n
\r\ngithub \"Alamofire\/Alamofire\" >= 1.1\r\n<\/pre>\n
Run carthage update<\/code>. Carthage will now check out and build<\/i> Alamofire.
\n
\n% carthage update
\n*** Fetching Alamofire
\n*** Checking out Alamofire at \"2f39b8634ab85cd6b3a55bbcfdec8cbb6463a6ee\"
\n*** xcodebuild output can be found in \/var\/folders\/yn\/ljzrn5hd4g3fxsj4klwkhbkm0000gp\/T\/carthage-xcodebuild.wAPiQR.log
\n*** Building scheme \"Alamofire iOS\" in Alamofire.xcworkspace
\n*** Building scheme \"Alamofire OSX\" in Alamofire.xcworkspace
\n<\/code><\/p>\n
Once completed you should see a new file and new folder in your project directory: Cartfile.resolved<\/code> and Carthage<\/code>, respectively.<\/p>\n
You are going to want to check in both Cartfile<\/code> and Cartfile.resolved<\/code>, so add them to your repository.
\n
\ngit add Cartfile
\ngit add Cartfile.resolved
\n<\/code><\/p>\n
You do not<\/i> need to add the Carthage<\/code> folder, so you can add it to your .gitignore<\/code> file if you like.<\/p>\n
Now, let’s add the build output from Carthage to our project. First, go to your project’s General<\/b> tab and locate the section Linked Frameworks and Libraries<\/b>. You can either drag-and-drop the built framework from the Finder, or use the +<\/b> button and navigate to the folder in Xcode. <\/p>\n
\"Add_Alamofire\"<\/a><\/p>\n
You should see the framework added to the list:<\/p>\n
\"Alamofire_added\"<\/a><\/p>\n
Now, go to Build Phases and create a new Run Script<\/b> phase. The script contents will be:<\/p>\n
\r\n\/usr\/local\/bin\/carthage copy-frameworks\r\n<\/pre>\n
Then add an Input File<\/b> as the framework you want to copy, i.e., Alamofire.framework<\/code>.
\n\"Carthage_RunScript\"<\/a><\/p>\n
That’s it!  With your Xcode project set up to pull in the built framework that Carthage created, you’re ready to build and run!  Much easier than using than CocoaPods or git submodules.<\/p>\n
Gotchas<\/h2>\n
If you are iOS developer that likes to stay on the bleeding edge you undoubtedly have both the release and beta versions of Xcode installed on your Mac. If you build your projects solely within Xcode there’s typically no conflict between the two, but since Carthage builds your frameworks from the command-line, the version of Xcode selected by xcodebuild<\/code> matters. For example, if your xcodebuild<\/code> is set to use the release version of Xcode and you run carthage update<\/code> and then include that framework in an Xcode beta project, you will likely get the error Module file was created by an older version<\/code>. To resolve this use xcode-select<\/code> to switch xcodebuild<\/code> to use the beta version of Xcode:<\/p>\n
\r\nsudo xcode-select -s \/Applications\/Xcode-Beta.app\r\n<\/pre>\n
As of February 28, 2015, the Alamofire main branch hasn’t been updated to support Xcode 6.3 (and by extension, Swift 1.2).  To continue working with Alamofire in your Xcode 6.3 projects, update your Cartfile<\/code> to specify a branch dependency<\/i>:<\/p>\n
\r\ngithub \"Alamofire\/Alamofire\" \"xcode-6.3\"\r\n<\/pre>\n
Run carthage update<\/code> and Carthage will checkout the xcode-6.3<\/code> branch of Alamofire and compile it.  If you get a build failure make sure you’re using the right xcodebuild<\/code>!
\n
\n% xcodebuild -version
\nXcode 6.3
\nBuild version 6D520o
\n<\/code><\/p>\n
Get the Code<\/h2>\n
You can check out our example application (for details on the application, see our post here<\/a>)of using Alamofire and Carthage on Bitbucket.  There are two branches, carthage<\/code> and carthage-xcode-6.3<\/code>. <\/p>\n
If you’re using Xcode 6.1 then you will want to use the carthage<\/code> branch:<\/p>\n
\r\ngit clone git@bitbucket.org:joeiachievedit\/alamofire-translator translator\r\ncd translator\r\ngit checkout carthage\r\nsudo xcode-select -s \/Applications\/Xcode.app\r\ncarthage update\r\n<\/pre>\n
If you’re using Xcode 6.3 (which is beta at the time of this writing):<\/p>\n
\r\ngit clone git@bitbucket.org:joeiachievedit\/alamofire-translator translator\r\ncd translator\r\ngit checkout carthage-xcode-6.3\r\nsudo xcode-select -s \/Applications\/Xcode-Beta.app\r\ncarthage update\r\n<\/pre>\n
Note!<\/b>  If you open the translator project and try to build and are met with No such module 'Alamofire'<\/code> you didn’t build Alamofire with carthage update<\/code> first!<\/p>\n","protected":false},"excerpt":{"rendered":"
I have never been a fan of CocoaPods due to its intrusiveness in the build process and insistence on creating Xcode project workspaces. Unfortunately managing dependencies through the use of Git submodules is no better. How many times have you told yourself, “Okay, I understand submodules now” only to be met with fatal: reference is […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11,2],"tags":[],"class_list":["post-1230","post","type-post","status-publish","format-standard","hentry","category-apple","category-xcodetips"],"_links":{"self":[{"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/posts\/1230"}],"collection":[{"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/comments?post=1230"}],"version-history":[{"count":42,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/posts\/1230\/revisions"}],"predecessor-version":[{"id":1979,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/posts\/1230\/revisions\/1979"}],"wp:attachment":[{"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/media?parent=1230"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/categories?post=1230"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dev.iachieved.it\/iachievedit\/wp-json\/wp\/v2\/tags?post=1230"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}