Swift: Creating Framework dependencies - swift

iOS8:
I'm trying to create a Database framework (DBKit) that will be used amongst our apps. DBKit requires Couchbase (ObjC) and Alamofire (Swift) frameworks.
I'm trying to avoid using Umbrella framework as it's discouraged by Apple.
Questions:
When creating a framework, how do I tell the framework to use Couchbase and Alamofire within the Demo Project?
Is using Cocoa Pods to manage frameworks inside a framework a good idea?

Believe you should be linking to the respective external libraries from within your application and NOT your own framework.
For Couchbase, you can simply drag in the frameworks to the 'Supporting Files' folder within your iOS project.

Related

Creating a Swift Framework with OpenCV as a 3rd party framework, but not packaging OpenCV in the end framework

Im currently working on creating a Swift Framework, my framework currently includes OpenCV as a Linked Framework. I have read up on the standards for distributing frameworks, and many people say that frameworks shouldn't be compiled/packaged with other 3rd party frameworks as this can cause issues like framework collisions etc...
So I knowing this I have been trying to work out how to build my framework but without packaging OpenCV with it, so the application will have to depend on OpenCV in order to use my framework.
I've had a look into Cocoa Pods and how the dependency management there will handle this for me. The problem with Cocoa Pods is the distribution, we need to be able to carefully control who can gain access to the framework.
So in conclusion, what would be the best way to create my framework without including the 3rd party dependency? Im open to any ideas!
This is the first framework I've created and some help or pointers would be very appreciated.

Pros and cons of embedded Cocoa Touch Frameworks?

I am using Swift, Xcode 6. Is there any good reasons to separate common code between watch app and main app into a separate Cocoa Touch Framework (embedded into the project)? By code I mean core data models, maybe some helper extensions etc. I have not intension to use this framework in other projects. Instead of creating framework, I can just add files to both targets.
Also, is there any problems with swift, framework versions that I can run into when creating new releases of the app?

Implementing Cocoa XML-RPC framework for iphone

I have my drupal xml-rpc service setup, and now I want to retrieve content for my iphone app.
I'm attempting to use https://github.com/eczarny/xmlrpc, however I dont know where to begin. How do I add the project to my own project for use? I've added a static library before; is it the same process? Just drag the proj file to my project and add the xml-rpc library?
Any tips would be appreciated.
Try dragging the project file for xmlrpc framework into the code list in XCode for starters. Next make the framework target in the xmlrpc framework a build dependency. Finally add the xmlrpc.framework to your linked frameworks. Exactly how you do this depends on whether you are using XCode 3 or 4

When to use framework in Objective C development

Not many libraries such as GHUnit suggest you to use them as a Framework.
While most libraries such as Facebook iOS SDK just require you to drag the project into existing XCode project.
So when you are building a library which suppose to be re-use by other project in the future, should you use Framework or just like many current opensource projects, don't use Framework provided by XCode.
There is a reason why those opensource projects are provided as static libraries or just source code and not Framework, Frameworks are currently not supported by iOS SDK.
You can only use Frameworks provided by Apple - parts of SDK itself. Your code cannot be linked against your own or third party Frameworks.
So stick with one of those ways - I personally prefer static libraries.

iphone: cross platform references and referencing external framework resources

working on an iphone app and separate framework.
the separate framework is for an API that i'm building for use in multiple future apps.
this api now needs to reference resources (images). what i would like to do is keep the resources WITH the API framework as local set of resources.
i followed the instructions from http://www.clintharris.net/2009/iphone-app-shared-libraries/ to setup my app's project to use the headers from the separate API framework.
what i can't seem to figure out is how to automatically load the framework's resources into the app's xcode environment so they can be linked in at app compile time.
sure, i can drag the resources across from the framework into the main app's set of resources. but that seems kinda ugly and another step that possibly can be automated (??) anyone know of a better way? it would be great if any changes from the framework would be automatically available in the main app (due to the project 'link-age').
thanks for any help/tips/suggestions...
You can't make your own frameworks and have the apps made with that framework get accepted into the iTunes store... Apple doesn't allow other frameworks in the App Store.