RE: Deploying Third Party Frameworks
RE: Deploying Third Party Frameworks
- Subject: RE: Deploying Third Party Frameworks
- From: Yan Shapochnik <email@hidden>
- Date: Thu, 17 Dec 2009 12:35:29 -0500
- Acceptlanguage: en-US
- Thread-topic: Deploying Third Party Frameworks
Qt only requires the building of frameworks for 10.5 and newer and only if you build the Qt Cocoa version. Qt Carbon can be built as libraries for 10.4 and newer and can be built for ppc and i386 as a universal binary (but no x86_64). See this link for additional information:
http://doc.trolltech.com/4.5/developing-on-mac.html#carbon-or-cocoa
Therefore, you are not required to use Qt Frameworks. With that said, as far as deployment is concerned, you can deploy any way you want. You can make 1 huge container-like framework if you wish and then copy the necessary binaries from other frameworks into this one. All that really matters is updating your framework dependencies with install_name_tool for the application you are installing. However, I think the best policy is to deploy each framework separately, similar to what Apple and Nokia do and then place them in a location of your choice somewhere on the machine.
Download Nokia's binary Qt 4.5/4.6 packages and see what they do.
- Yan -
-----Original Message-----
From: xcode-users-bounces+shapochniky=email@hidden [mailto:xcode-users-bounces+shapochniky=email@hidden] On Behalf Of Rush Manbert
Sent: Thursday, December 17, 2009 12:18 PM
To: XCode Users
Subject: Deploying Third Party Frameworks
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
_______________________________________________
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