dyld: Library not loaded: & embedded app resources <SOLVED>
Anthony B Arthur
brianarthur at nc.rr.com
Fri Sep 21 04:23:18 PDT 2007
Thanks to all who responded. I figured out what was wrong, something =20=
I swear I had done, but somehow the setting was lost. But the simple =20=
solution was setting the build Install Directory value to =20
@executable_path/../Frameworks for every relevant framework. That =20
was it!
--Brian
On Sep 21, 2007, at 5:27 AM, Emanuele =B0 Vulcano wrote:
>
> Il giorno 21/set/07, alle ore 11:03, Anthony B Arthur ha scritto:
>
>> hmm, no I did not tamper with this part of the project. It is =20
>> unclear, from the info panel, what path these are linked to and =20
>> how to change that.
>
> When you link to a library, its install name is embedded in the =20
> executable. The install name can be fixed on a binary with =20
> install_name_tool, or, if you have the source, by changing the =20
> framework's install name in its target settings (if the Xcode =20
> project is available) or link flags (man gcc should help).
>
> At worst, you could make a copy of the framework, run =20
> install_name_tool on it, and link to that. If you need the =20
> framework to live in Library, you can make a shell script build =20
> phase that copies the framework on-the-fly.
>
> - =B0
More information about the MacOSX-dev
mailing list