From: Jack J. <Jac...@or...> - 2002-01-21 21:17:02
|
On Monday, January 21, 2002, at 07:32 PM, Jim Ingham wrote: > On 1/21/02 7:54 AM, "Ashley Ward" <ash...@nt...> wrote: > >> Any hints would be appreciated! > > If you want to package Frameworks in your app, you are supposed > to put the > cookie: @executable_path in the name of the framework you are > linking to, > and dyld will resolve the reference relative to where the > executable lives > in your App bundle. Do you mean that your private frameworks aren't on the search path by default? I haven't tried this yet, but I was assuming that if you link with "-framework Foo" and you then copy this Foo framework from /Library/Frameworks/Foo.framework to /Applications/MyApp.app/Contents/Frameworks/Foo.framework it would find it automatically. I know that dyld *does* find frameworks in the current directory if you add "-Wl,-F." to your link command line. When I'm building Python I link against Python.framework. At build time this is simply a subdirectory of the current directory, and the resulting executable works fine with that. Later, when everything has been installed, the same executable runs just as fine with the framework in /Library/Frameworks/Python.framework. Hmmm, long paragraph, but what I wanted to suggest is try adding "-Wl,-F../FrameWorks" to your link line. -- - Jack Jansen <Jac...@or...> http://www.cwi.nl/~jack - - If I can't dance I don't want to be part of your revolution -- Emma Goldman - |