Could you suggest a builder for the IOS8-SWIFT project?

Question

Cocoa

I recently got into IOS development, and after working under android \ studio / java / maven / gradle, I came across some misunderstandings with how to organize joint development through git. For example, how not to carry files of libraries Alamofire.swift, etc? Found two options CocoaPods and Carthage . But how they work - I'll never know, even based on the documentation. Or it works quite unusually. They download libraries, create frameworks (O_o!). How to work with version control under IOS+Swift? Tell me people.

Answer 1

Oh, and you have drawn up the question ... you'll understand the hell.
And if the case, then there are several approaches
1) Carry in the form of files. Cheap and cheerful, the choice of real Jedi (before, by the way, they did so)
2) Use other people's developments in the form of lib (only static in iOS) or Frameworks. For this point, the author of the library must prepare them himself.
3) Use Git submodules.
4) Use Cocoapods. In a nutshell, it looks like this: the author of the library publishes it in a special way. The programmer user writes the libraries he needs in a special file, which are automatically pulled out and put into the project by cocapod's tool. The name of the lib can be found at https://cocoapods.org or directly from the author. At the same time, you are free to update/add/remove all/selected library at any time and, which is not unimportant sometimes, you have direct access to the source code of the library. Of the minuses - the cocapods reworks the project a bit, which is sometimes unacceptable.
5) Carthage - a kind of cross between 4 and 2 options. Those. you get rid of the dirty work of generating libraries, but at the same time you will have to limit yourself to projects only under iOS 8. It uses a special technology (c) from Apple that does not work on older versions.
As for Apple's position, it suggests reusing the code using the approach from point 2 + for iOS 8 the same special technology (c). That's why these Carthage and CocoaPods look so strange - they are at least de facto the standard in the world of apple development, but at the same time, Apple has not been officially noticed YET.

Answer 2

Why didn't you like xcode?

Answer 3

I'm sorry, but are you sure you're writing code in Xcode?
There, all dependencies and libraries are pulled up.
Frameworks and libraries (not system ones) must be carried with you in source codes, because they are part of the code.
Cocoapods and Carthage are some kind of package manager for all open source frameworks.