Re: Link (dyld) error: image not found (QuickTime.framework)
Re: Link (dyld) error: image not found (QuickTime.framework)
- Subject: Re: Link (dyld) error: image not found (QuickTime.framework)
- From: Eric Albert <email@hidden>
- Date: Fri, 16 Dec 2005 09:51:10 -0800
On Dec 16, 2005, at 1:10 AM, Jonathan del Strother wrote:
I've had a couple of users send me crash reports like the one pasted
below. Apparently my app loads fine, but later just bombs out
complaining that it can't find Quicktime. They say that Quicktime
player and everything else works fine - any suggestions what might
cause this?
Command: CoverFlow
Path: /Applications/CoverFlow.app/Contents/MacOS/CoverFlow
Parent: WindowServer [64]
Link (dyld) error:
image not found
/System/Library/Frameworks/QuickTime.framework/QuickTime
This is interesting. Typically applications link against the actual
binary file inside each framework. For example, here's what QuickTime
Player links against:
Ithilien:~> otool -L /Applications/QuickTime\
Player.app/Contents/MacOS/QuickTime\ Player | grep QuickTime
/Applications/QuickTime Player.app/Contents/MacOS/QuickTime Player:
/System/Library/Frameworks/QuickTime.framework/Versions/A/QuickTime
(compatibility version 1.0.0, current version 11.0.0)
Note that it's "QuickTime.framework/Versions/A/QuickTime". The path in
your crash log is normally a symlink to the binary in Versions/A, but
it isn't technically required. I wonder if it's missing on those
users' systems. But what I'm more curious about is how you built an
application in the first place which linked against the symlink version
instead of the actual binary.
I'd suggest running otool -L against your binary and seeing which path
you get. Assuming you get the path that you're seeing in the crash
logs, I'd suggest looking at your build process and seeing how you link
against QuickTime and whether you're running install_name_tool or
anything like that on the build product to change your link paths. And
you might want to take a look at the QuickTime framework on your build
system (or in the SDK you're using) and make sure it has a symlink
there rather than an actual binary.
Hope this helps,
Eric
_______________________________________________
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