Re: "Best" ways to install frameworks?
Re: "Best" ways to install frameworks?
- Subject: Re: "Best" ways to install frameworks?
- From: Jonathan Hess <email@hidden>
- Date: Thu, 22 Nov 2007 02:15:54 -0800
On Nov 21, 2007, at 6:39 AM, Rick Hoge wrote:
A problem I just worked through getting IB plugins to load raised a
number of questions relating to where and how frameworks should be
installed in Xcode projects:
1) the default install path specified for framework target seems
to be /Library/Frameworks/. However as far as I can tell, none of
the framework templates in Xcode includes a build phase to actually
copy the framework into this location. I know this is easy to do
using a "copy files" build phase, but why don't any of the templates
include this? I suppose it could be that, for actually shipping an
app, your installer would do this since the ultimate objective is
not to run the app out of Xcode (also it's probably good that by
default Xcode never modifies anything outside of the project). Is
there any other reason why the templates don't actually install the
framework?
Hey Rick -
The templates actually can install frameworks, but the build action in
Xcode.app doesn't do that. Installing your built product typically
wouldn't be what you wanted when you were just building and debugging.
When you're actually ready to build a project for install, you can use
"sudo xcodebuild install" from the terminal after setting the
"DSTROOT" environment variable. For customers though, you'll probably
want to use an installer package or app relative/embedded frameworks
so that you can support drag installs.
Jon Hess
2) an app we currently distribute has it's frameworks located
inside the app bundle, making the app drag-and-drop installable and
relocatable. If we want to make some of the frameworks available to
3d party developers, the frameworks should probably be in /Library/
Frameworks/. Do I have to choose one or the other? I am wondering
what strategies work well for allowing both flexible installation
and exposure of frameworks to developers. Having two sets of the
framework seems like it could lead to confusion or problems.
Thanks for any suggestions,
Rick
_______________________________________________
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
_______________________________________________
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