Note that there are some explanatory texts on larger screens.

plurals
  1. PObuild/install succeed, but at runtime: dyld image not found - why?
    text
    copied!<p>I had <a href="https://stackoverflow.com/questions/13611740/qt-mac-osx-10-8-dyld-library-not-loaded-image-not-found">this problem</a> with ICU in my app, trying to run in Qt Creator on my Mountain Lion MacBook Pro.</p> <p>Now I discovered I have a similar problem at run time with a dmg that I build on this same MacBook Pro. The build completes successfully, running the dmg and installing appears successful, but when I try to run I get:</p> <pre><code>Dyld Error Message: Library not loaded: @executable_path/../Frameworks/libicuuc.46.dylib Referenced from: /Applications/MapCreator.app/Contents/SharedLibraries/libicui18n.46.1.dylib Reason: image not found </code></pre> <p>I grabbed a previous tagged version of our app (and build script) from source control and I get the same problem when it's built on this MacBook.</p> <p>The only errors I see when I run the build script are listed below. I believe these errors have always been present in our builds on all machines, and have never been a problem, but I list them here just in case it turns out to be helpful:</p> <pre><code>ERROR: "strip: can't map file: /Users/david/dev/svn/map_creator1.0.2/build/mac/pkg-root/Applications/MapCreator.app/Contents (Invalid argument) " ERROR: "" ERROR: "install_name_tool: can't map file: /Users/david/dev/svn/map_creator1.0.2/build/mac/pkg-root/Applications/MapCreator.app/Contents/Frameworks//.. (Invalid argument) " ERROR: "" ERROR: "otool: can't map file: /Users/david/dev/svn/map_creator1.0.2/build/mac/pkg-root/Applications/MapCreator.app/Contents/Frameworks//.. (Invalid argument) " ERROR: no file at "/usr/lib/libicui18n.46.dylib" ERROR: no file at "/usr/lib/libicuuc.46.dylib" ERROR: no file at "/usr/lib/libicudata.46.dylib" </code></pre> <p>I'm not sure where to look to track this down. Can anyone point me in the right direction?</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload