Yeah, that's how I'd do it, add a "run script" build phase to the daemon target.
sherm-- On Fri, Apr 8, 2011 at 9:57 AM, Mr. Gecko <grmrge...@gmail.com> wrote: > So basically once I've compiled the daemon, have it run a post script that > will change the path to go back 4 directories instead of 1 if I was to place > it in Contents/Daemon/Daemon.app/Contents/MacOS/Daemon? > > Thanks for the response, > Mr. Gecko > > On Apr 8, 2011, at 8:48 AM, Sherm Pendley wrote: > >> The details will vary according to how you've structured your bundles, >> but the principle is the same. The install name of the framework is >> used at link time, and copied into any apps that link with it. At run >> time, it's the copy in the app that's used to find the framework, and >> you can use install_name_tool's -change option to modify that. >> >> install_name_tool -change >> '@executable_path/../Frameworks/Foo.framework/Foo' >> '@executable_path/../../Frameworks/Foo.framework/Foo'. >> >> sherm-- >> >> -- >> Cocoa programming in Perl: >> http://camelbones.sourceforge.net > > -- Cocoa programming in Perl: http://camelbones.sourceforge.net _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
