Re: Embedded framework prevents app from debugging
Re: Embedded framework prevents app from debugging
- Subject: Re: Embedded framework prevents app from debugging
- From: Nick Zitzmann <email@hidden>
- Date: Fri, 25 Apr 2003 14:04:28 -0700
On Friday, April 25, 2003, at 08:27 AM, Brad Werth wrote:
Through experimentation, I have found that the cause is the
INSTALL_PATH of the framework, which I have set to
"@executable_path/../Frameworks". My understanding is that this
install path is necessary for embedding frameworks in my app. If I
change it back to "$(HOME)/Library/Frameworks", things work fine, but
I'm worried that the framework won't be part of the app distribution.
What is the correct way for me to embed the framework and still be
able to debug my application?
1. Set the framework's install path to "@executable_path/../Frameworks".
2. Make sure the framework is actually embedded in the application
bundle. Your target should have a "copy files" build phase that copies
the framework into the bundle.
If this phase isn't present, then that's probably your problem right
there - just adding a framework to the target doesn't bundle it into
the target; you have to do that manually.
As I understand things, when a task is launched, the dynamic linker
will first search for the framework in the install path. If it can't
find it in the install path, then it looks in ~/Library/Frameworks,
/Library/Frameworks, etc. If it can't find it in any of these places,
then the application won't run. But when you run GDB, it takes over
that function, and does things its way...
Nick Zitzmann
AIM/iChat: dragonsdontsleep
Check out my software page:
http://dreamless.home.attbi.com/
"Building the future and keeping the past alive are one and the same
thing." - Metal Gear Solid 2
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.