handling dependencies for iOS Framework project

Question

I\'ve created iOS Framework project using this method: https://github.com/jverkoey/iOS-Framework

Works pretty neat but I\'m a little confused on how to include libra

Answer 1

Mostly if you install third party frameworks you can install with cocoapods (which is really nice, I would definitely do that) or they offer you to download the framework and include it in your Project. If you decide to download the library and include it there is normally a list of frameworks you need in the "Getting started" guide.

Means: Offer them to install using cocoapods and to download your library but do not include anything else, give them a list what they need.

Answer 2

You should use CocoaPods. Your dependency on Facebook can be done by linking against the CocoaPod.

If you want to include that particular version of Facebook in your pod, you can put it in your repo and use the vendored_frameworks property to refer to it.

Similarly if you wanted to vendor libFlurry.a, you could do so using s.vendored_libraries.

For system libraries, you don't need to vendor them, e.g. libZ.a.

I strongly recommend creating your CocoaPod using pod lib create YourPodName. They've recently changed the mechanism for how this works and it's really nice.

You can create an Example project that shows how to use your code in context of an app.

Then one of the other neat things I just learned about, someone can do pod try YourPodName and it will automatically download, integrate and run the Xcode project.

CocoaPods is worth the trouble.

Answer 3

1. Use cocoapods , it's easy (http://cocoapods.org/)

2. Your application developers will have to include the podfile and download the dependencies.

3. While developing your SDK use a reference application/demo app on top of the SDK to simulate this.

Answer 4

For the use case you are describing, you should be linking to these external libraries from your application, NOT your own framework. It can be one or the other, but it can't be both.

If you decide that these dependancies belong as the responsibility of the application, you would remove them from "Link Binary With Libraries" and any other explicit linking configuration, and just project your framework project with the path to these frameworks and libraries so it can find the symbols (but not link against them) at compile time (i.e. the path to the libraries should be included LIBRARY_SEARCH_PATHS).

Answer 5

You shouldn't link anything when building your framework but just create a *.a binary with your framework's objects.

Also you should not include code from other libraries in your framework as client applications may be adding the same libraries directly or requiring different versions of them, thus creating conflicts.

Off course you can reference *.h header files from other libraries in your framework in order to compile your objects.

As a result the installation steps for your framework should detail other required frameworks/libraries needed, their supported versions, how to add resource files (if any), etc. Just some of the many reasons why you may want to consider Creating a CocoaPods' podspec instead.

Answer 6

Use CocoaPods dependancy manager. Here's a good guide,

7 miniute video tutorial