标签:
If you prefer not to use either of the aforementioned dependency managers, you can integrate Alamofire into your project manually.
cd
into your top-level project directory, and run the following command "if" your project is not initialized as a git repository:$ git init
$ git submodule add https://github.com/Alamofire/Alamofire.git
Open the new Alamofire
folder, and drag the Alamofire.xcodeproj
into the Project Navigator of your application‘s Xcode project.
It should appear nested underneath your application‘s blue project icon. Whether it is above or below all the other Xcode groups does not matter.
Select the Alamofire.xcodeproj
in the Project Navigator and verify the deployment target matches that of your application target.
+
button under the "Embedded Binaries" section.You will see two different Alamofire.xcodeproj
folders each with two different versions of the Alamofire.framework
nested inside a Products
folder.
It does not matter which
Products
folder you choose from, but it does matter whether you choose the top or bottomAlamofire.framework
.
Select the top Alamofire.framework
for iOS and the bottom one for OS X.
You can verify which one you selected by inspecting the build log for your project. The build target for
Alamofire
will be listed as eitherAlamofire iOS
orAlamofire OSX
.
And that‘s it!
The
Alamofire.framework
is automagically added as a target dependency, linked framework and embedded framework in a copy files build phase which is all you need to build on the simulator and a device.
标签:
原文地址:http://www.cnblogs.com/baaingSheep/p/4857049.html