My framework will utilise other frameworks, but I'd like this to be transparent to the end-user
- by d11wtq
I'm building a framework, which aims to provide a new development environment for the user, but I need to use things like RegexKit and almost certainly some other established frameworks in order to do this. Any functionality exposed from such frameworks would be abstracted through classes and methods in my own framework for maintenance reasons (allowing me to change my mind on which dependencies I want).
In an ideal world I just want to ship a single .framework. However I'm aware that unlike with standard bundles and applications it is not possibile to embed a framework inside the framework bundle. Do I have any other option other than to tell the end user that they must also install RegexKit and any other dependencies? I have a feeling this lessens the appeal value of the easy to use embedded framework I'd envisaged building.
Right now I'm feeling like I have some limited options:
Force the user to install the dependencies.
Write my own classes that provide the same functionality -- ugh!
If at all possible, try to statically link the third party frameworks (is this possible??)
My end-product is ideally a single .framework bundle that uses @rpath and so can be installed in the system or simply bundled with the app that uses it.
