Re: Setting up Xcode workspace with multiple embedded frameworks that rely on each other.
Re: Setting up Xcode workspace with multiple embedded frameworks that rely on each other.
- Subject: Re: Setting up Xcode workspace with multiple embedded frameworks that rely on each other.
- From: Kyle Sluder <email@hidden>
- Date: Mon, 30 Jun 2014 14:36:48 -0500
On Sat, Jun 28, 2014, at 02:14 AM, Jens Alfke wrote:
>
> I think you’re forgetting about adding copy-files build phases to copy
> the frameworks into the app bundle, and also the fiddly steps to tell the
> app binary what path it should look for the framework at (the details of
> which I always forget until the next time I have to set it up, then I go
> back and look at earlier projects. There’s something about “@rpath”…)
FWIW, my Radar about making @rpath the default was returned as fixed in
Xcode 6, and I can confirm that the default value for
DYLIB_INSTALL_BASE_NAME is now "@rpath". No more futzing with
install_name_tool(1)!
--Kyle Sluder
_______________________________________________
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