From: William K. <wo...@ky...> - 2007-08-27 20:52:34
|
Ah. I just build for my use and package for others. I haven't had a need for detailed debugging. Usually a crash log is enough for me to figure out problems or report a bug, and let the developers debug. But that makes sense - it probably should be the packaging step that chagnes install_names if it wants to bundle frameworks in the app. Considering my comment about the OSG-distributed binaries having exploded symlinks, I'm not too surprised that the install_names are not right. Maybe they're thinking or suggesting that the osg frameworks are meant to be bundled, and aren't expecting anyone to want to install them in system locations. On Aug 27, 2007, at 3:34 PM, jim hopper wrote: > Yes it works, but the debugger appears to be unable to find the > symbols for > the frameworks when you crash into it. It spits out a number of error > messagess and does not show you any valid stack trace. At least > that's what > I am getting today with xcode. > > Jim > > On 8/27/07 4:32 PM, "William Kyngesburye" <wo...@ky...> > wrote: > >> When a framework has @executable_path in its install_name, it still >> works in /Library/Frameworks. It certainly works now, since the osg >> frameworks are built that way, yet planet still runs. I think the >> framework loader checks the standard paths if a framework isn't found >> in the named path. ----- William Kyngesburye <kyngchaos*at*kyngchaos*dot*com> http://www.kyngchaos.com/ [Trillian] What are you supposed to do WITH a maniacally depressed robot? [Marvin] You think you have problems? What are you supposed to do if you ARE a maniacally depressed robot? No, don't try and answer, I'm 50,000 times more intelligent than you and even I don't know the answer... - HitchHiker's Guide to the Galaxy |