Re: Problem having a framework working in one of my targets (a screensaver)
Re: Problem having a framework working in one of my targets (a screensaver)
- Subject: Re: Problem having a framework working in one of my targets (a screensaver)
- From: Kevin Meaney <email@hidden>
- Date: Fri, 03 Jul 2015 10:29:10 +0100
I’m not sure either of those will work.
On 3 Jul 2015, at 10:07, Roland King <email@hidden> wrote:
>
> There’s two other options
>
> 1) Use install_name_tool to change the name in the library to the one you want. If it’s shorter, and it should be as the install name in that library seems rather long, you can do that
I don’t think modifying the Installation Directory will work. I’ve checked my framework using otool as Juanjo mentioned he did. Building my Framework I’ve set Installation Directory to @rpath but the name I see using otool still says @executable_path/… etc. so there is some information set elsewhere which informs the linker. So I don’t think editing the path using install_name_tool will help.
> 2) Craft the way you package your final product so the library IS in that path relative to the executable.
Except in this case the executable in question will be the screen saver process that loads Juanjo’s screensaver plugin.
There is possibly one solution. Modify the name using install_name_tool to /Library/Frameworks and install the Framework to /Library/Frameworks.
I still think going to the developers of the framework is the best approach.
Kevin
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden