Re[4]: Custom embedded framework not working [Solved]
Re[4]: Custom embedded framework not working [Solved]
- Subject: Re[4]: Custom embedded framework not working [Solved]
- From: Peter Mulholland <email@hidden>
- Date: Sun, 29 Jul 2007 01:28:34 +0100
Hello Ken,
Saturday, July 28, 2007, 9:41:55 PM, you wrote:
> The @executable_path hack is actually rather nice once you understand
> it (and find it, as it's not documented) but I was thinking more
> along the lines of : Say I find some freeware framework that was
> compiled to install in the /Library/Frameworks folder. If I want to
> embed that framework in my app I'm clean out of luck. Without the
> source there's no way I can set the deploy location so there's no way
> to embed it. (At least with my current understanding of the embedding
> process) There should be a way to embed framework as "black boxes"
> without having to set anything inside them.
You can do this using install_name_tool, but yes, it shouldn't be
neccesary.
Example, to change it for Blah.framework:
install_name_tool -id
@executable_path/../Frameworks/Blah.framework/Versions/A/Blah Blah.framework/Versions/A/Blah
To be honest, i'm not 100% sold on Frameworks.. for a start, Xcode
should have an option during the Copy phase, to strip out the headers
- this is something I currently do manually. It should also strip out
any alternate versions of the framework that aren't linked to by the
app. They are good for developers to have the headers etc in a neat
little bundle, but for embedding into an app bundle, they are just
bloat.
--
Best regards,
Peter mailto: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