Deploying Third Party Frameworks
Deploying Third Party Frameworks
- Subject: Deploying Third Party Frameworks
- From: Rush Manbert <email@hidden>
- Date: Thu, 17 Dec 2009 09:17:54 -0800
We are using Qt to develop multiple applications that we deploy to multiple platforms.
On the Mac we need to deploy back to 10.4 on ppc, which requires us to build Qt as frameworks.
The end result of a Qt make is a fairly large number of frameworks and dylibs. Since our applications all use the same set of Qt frameworks, those frameworks are rather large, and we deploy the applications via download, we do not want to embed the frameworks in the apps. We want to deploy one framework set and let all of our apps use it.
We think we can do this by making a single framework that is really just a container for the Qt frameworks. That approach doesn't really seem to fit with Apple's notion of what a framework is according to the documentation, but I have examined /System/Library/Frameworks/Python.framework, which seems to essentially wrap a standard BSD-type library installation, so that looks like a model we could follow.
I have two questions:
It seems from example that there is a rather large amount of freedom in how a framework is constructed as long as the basic form is observed. Is that true, or are there subtleties that I don't grasp?
Has anyone else tackled this problem and is willing to share their solution?
- Rush
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden