dyld: Library not loaded … Reason: Image not found





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







170















When trying to run an executable I've been sent in Mac OS X, I get the following error



dyld: Library not loaded: libboost_atomic.dylib
Referenced from: /Users/"Directory my executable is in"
Reason: image not found
Trace/BPT trap:5


I have installed the boost libraries and they are located in /opt/local/lib. I think the problem has something to do with the executable only looking in the directory it is in as when I paste the 'libboost_atomic.dylib' in there, it doesn't mind about it anymore. Unfortunately then it complains it can't find the next boost library.



Is there an easy way to fix this?










share|improve this question

























  • If you still has problem use method from this topic

    – Tarik
    May 15 '17 at 9:23


















170















When trying to run an executable I've been sent in Mac OS X, I get the following error



dyld: Library not loaded: libboost_atomic.dylib
Referenced from: /Users/"Directory my executable is in"
Reason: image not found
Trace/BPT trap:5


I have installed the boost libraries and they are located in /opt/local/lib. I think the problem has something to do with the executable only looking in the directory it is in as when I paste the 'libboost_atomic.dylib' in there, it doesn't mind about it anymore. Unfortunately then it complains it can't find the next boost library.



Is there an easy way to fix this?










share|improve this question

























  • If you still has problem use method from this topic

    – Tarik
    May 15 '17 at 9:23














170












170








170


72






When trying to run an executable I've been sent in Mac OS X, I get the following error



dyld: Library not loaded: libboost_atomic.dylib
Referenced from: /Users/"Directory my executable is in"
Reason: image not found
Trace/BPT trap:5


I have installed the boost libraries and they are located in /opt/local/lib. I think the problem has something to do with the executable only looking in the directory it is in as when I paste the 'libboost_atomic.dylib' in there, it doesn't mind about it anymore. Unfortunately then it complains it can't find the next boost library.



Is there an easy way to fix this?










share|improve this question
















When trying to run an executable I've been sent in Mac OS X, I get the following error



dyld: Library not loaded: libboost_atomic.dylib
Referenced from: /Users/"Directory my executable is in"
Reason: image not found
Trace/BPT trap:5


I have installed the boost libraries and they are located in /opt/local/lib. I think the problem has something to do with the executable only looking in the directory it is in as when I paste the 'libboost_atomic.dylib' in there, it doesn't mind about it anymore. Unfortunately then it complains it can't find the next boost library.



Is there an easy way to fix this?







macos dylib dyld otool install-name-tool






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Apr 3 at 10:36









Adobels

1,91221435




1,91221435










asked Jul 17 '13 at 15:08









rwolstrwolst

3,66693555




3,66693555













  • If you still has problem use method from this topic

    – Tarik
    May 15 '17 at 9:23



















  • If you still has problem use method from this topic

    – Tarik
    May 15 '17 at 9:23

















If you still has problem use method from this topic

– Tarik
May 15 '17 at 9:23





If you still has problem use method from this topic

– Tarik
May 15 '17 at 9:23












16 Answers
16






active

oldest

votes


















133














Find all the boost libraries:



$ otool -L exefile
exefile:
@executable_path/libboost_something.dylib (compatibility version 0.7.0, current version 0.7.0)
/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 65.1.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)


and for each libboost_xxx.dylib, do:



$ install_name_tool -change @executable_path/libboost_something.dylib /opt/local/lib/libboost_something.dylib exefile


and finally verify using otool again:



$ otool -L exefile
exefile:
/opt/local/lib/libboost_something.dylib (compatibility version 0.7.0, current version 0.7.0)
/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 65.1.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)


Manpages: otool install_name_tool



EDIT A while back I wrote a python script (copy_dylibs.py) to work out all this stuff automatically when building an app. It will package up all libraries from /usr/local or /opt/local into the app bundle and fix references to those libraries to use @rpath. This means you can easily install third-party library using Homebrew and package them just as easily.



I have now made this script public on github.






share|improve this answer


























  • @RobWolstenholme Yeah the changes are permanent.

    – trojanfoe
    Jul 17 '13 at 16:11






  • 3





    @trojanfoe can you please explain here what is the exefile is it be a tool exec file path ? isnt it ?

    – VenushkaT
    Dec 2 '14 at 5:30






  • 1





    If this is my error: dyld: Library not loaded: /usr/local/homebrew/lib/libboost_system-mt.dylib Referenced from: /Users/jordann/Documents/Games/TUO_OSX/./tuo-2.4.5 Reason: image not found Trace/BPT trap: 5 Can someone help me then what to fill in after $ install_name_tool

    – Jordann Gross
    Feb 20 '15 at 13:22








  • 3





    @JordannGross Ask a new question.

    – trojanfoe
    Feb 24 '15 at 15:14






  • 5





    'exefile': No such file or directory

    – ScottyBlades
    May 29 '18 at 7:38



















71














In the target's General tab, there is an Embedded Binaries field.



add required framework and crash is resolved.



enter image description here



click on the + sign and add framework






share|improve this answer
























  • what should i add ? there's a lot of files

    – Joe Sleiman
    Jan 8 at 8:15






  • 1





    This is solved the problem.

    – showmyroutes
    Apr 4 at 21:42






  • 1





    Solved it for me

    – dcdroid
    Apr 18 at 14:21



















30














This worked for me:



brew upgrade node





share|improve this answer































    28














    For some, this could be as easy as setting the system path for dynamic libraries. On OS X, this is as simple as setting the DYLD_LIBRARY_PATH environment variable. See:



    Is it OK to use DYLD_LIBRARY_PATH on Mac OS X? And, what's the dynamic library search algorithm with it?






    share|improve this answer





















    • 2





      This answer is the most generic and gets to the point: if you have custom/user libs, then this is the way to go.

      – Kei-ven
      Jul 4 '16 at 1:47











    • It may seem stupid, but I wonder what value should I set DYLD_LIBRARY_PATH to?

      – Caesar
      Mar 21 '17 at 1:13








    • 1





      @Caesar Set it to the directory of wherever the dylibs you're trying to link are located.

      – markshiz
      May 2 '17 at 14:01






    • 1





      This should be accepted as the answer. The other one with higher votes are meaningless.

      – SmallChess
      Nov 27 '17 at 23:59











    • You cannot expect your users to change DYLD_LIBRARY_PATH. The correct solution is to include non-standard libraries with the .app and the user won't have to do anything. The developer, however, may still have to hack the loader path as per my answer.

      – trojanfoe
      Feb 4 at 8:00





















    13














    I got this error when I tried to install ruby 2.3.1 using rvm. It first told me to run brew update, which I did, and then when I tried running rvm install ruby-2.3.1, I received the error in this SO question.



    The fix was to first run brew upgrade, apparently according to this superuser.com question you need to do both brew update && brew upgrade. Once that was done, I could finally install ruby 2.3.1.






    share|improve this answer

































      5














      You can use the otool command with the -L option for the executable, which will display where the executable is expecting those libraries to be.



      If the path to those need changing, use the install_name_tool command, which allows you to set the path to the libraries.






      share|improve this answer































        4














        I got here trying to run a program I just compiled using CMake. When I try to run it, it complains saying:



        dyld: Library not loaded: libboost_system.dylib
        Referenced from: /Users/path/to/my/executable
        Reason: image not found


        I circumvented the problem telling CMake to use the static version of Boost, instead of letting it use the dynamic one:



        set(Boost_USE_STATIC_LIBS ON)





        share|improve this answer

































          4














          After upgrade Mac OS to Mojave. I tried to install npm modules via yarn command I got error:



          dyld: Library not loaded: /usr/local/opt/icu4c/lib/libicui18n.60.dylib
          Referenced from: /usr/local/bin/node
          Reason: image not found
          Abort trap: 6


          Was fix with:



          brew update
          brew upgrade





          share|improve this answer































            2














            I fix it by brew install libpng






            share|improve this answer































              1














              You can use sudo install_name_tool -change change dylib path
              And
              sudo install_name_tool -id change dylib name






              share|improve this answer































                0














                For anyone coming to this page because they got this error trying to link a third party framework to their project using Xcode 6.3.1, the problem I ran into was because the library was being created with an older version of the compiler using a different version of swift. The only way to fix this for me was to re-build the framework.



                Another reason you might get this is stated in an Apple technical doc..




                If you are building an app that does not use Swift but embeds content such as a framework that does, Xcode will not include these libraries in your app. As a result, your app will crash upon launching with an error message looking as follows:




                set the Embedded Content Contains Swift Code (EMBEDDED_CONTENT_CONTAINS_SWIFT) build setting to YES in your app



                Here is the link to the full Apple doc that explains it here






                share|improve this answer


























                • but how do you solve this?

                  – Klemen Zagar
                  Apr 17 '16 at 8:32



















                0














                I faced the app crash issue quoting SIGABRT error in thread.Overview of the crash is dyld library not loaded and image not found something like that.



                This was seen in xcode 9.3 version.The reason i found out was xcode is not picking up libraries dynamically so i had to do it manually which solved my crash issue.



                Follow the below steps:
                Step 1: Go to Build Phases
                Step 2: Hit the '+' button at the top and select "New Copy File Phase"
                Step 3 : Select Destination as Frameworks and Hit the '+' button below to add files.
                Step 4 : Select Add Other at below, click CMD+SHIFT+G and paste the below path,
                /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphoneos



                Now you will be able to see some swift dylibs, Select all the swift libraries with .dylib extension and click on open.



                These will get added to the embedded binaries in the general tab of app.



                Create a new group in project folder and add all these libraries.



                Now run your app.



                Happy Coding






                share|improve this answer































                  0














                  For anyone experiencing the same thing with a different library or package, @user3835452 is on the right track. I found this message while trying to run composer:



                  dyld: Library not loaded: /usr/local/opt/openldap/lib/libldap-2.4.2.dylib
                  Referenced from: /usr/local/opt/php@7.1/bin/php
                  Reason: image not found
                  Abort trap: 6


                  After trying a lot of different ways I just ran brew install openldap and it fixed it. Note that I had already ran brew update and brew upgrade but only after I manually installed openldap did it actually work.






                  share|improve this answer































                    0














                    Maybe someone need this:



                    if you use cmake, add DYLIB_INSTALL_NAME_BASE "@rpath" to target properties:



                    set_target_properties(target_dyLib PROPERTIES
                    # # for FRAMEWORK begin
                    # FRAMEWORK TRUE
                    # FRAMEWORK_VERSION C
                    # MACOSX_FRAMEWORK_IDENTIFIER com.cmake.targetname
                    # MACOSX_FRAMEWORK_INFO_PLIST ./Info.plist
                    # PUBLIC_HEADER targetname.h
                    # # for FRAMEWORK end
                    IPHONEOS_DEPLOYMENT_TARGET "8.0"
                    DYLIB_INSTALL_NAME_BASE "@rpath" # this is the key point
                    XCODE_ATTRIBUTE_CODE_SIGN_IDENTITY "iPhone Developer"
                    DEVELOPMENT_TEAM "${DEVELOPMENT_TEAM}"
                    )


                    or in xcode dynamic library project Target -> Build Setting set Dynamic Library Install Name Base to @rpath






                    share|improve this answer
























                    • I create a cocoa framework dynamic library project, it works, and compared with my bad cmake generated project find this different, and fixed it, it works on iOS.

                      – cn00
                      Feb 27 at 6:54





















                    0














                    I fixed this by reinstalling Homebrew



                    Uninstall



                    ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/uninstall)"



                    Install



                    /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"






                    share|improve this answer

































                      0














                      I fixed this issue by simply pressing Command + Shift + K, which makes a new clean build, really odd.






                      share|improve this answer
























                        Your Answer






                        StackExchange.ifUsing("editor", function () {
                        StackExchange.using("externalEditor", function () {
                        StackExchange.using("snippets", function () {
                        StackExchange.snippets.init();
                        });
                        });
                        }, "code-snippets");

                        StackExchange.ready(function() {
                        var channelOptions = {
                        tags: "".split(" "),
                        id: "1"
                        };
                        initTagRenderer("".split(" "), "".split(" "), channelOptions);

                        StackExchange.using("externalEditor", function() {
                        // Have to fire editor after snippets, if snippets enabled
                        if (StackExchange.settings.snippets.snippetsEnabled) {
                        StackExchange.using("snippets", function() {
                        createEditor();
                        });
                        }
                        else {
                        createEditor();
                        }
                        });

                        function createEditor() {
                        StackExchange.prepareEditor({
                        heartbeatType: 'answer',
                        autoActivateHeartbeat: false,
                        convertImagesToLinks: true,
                        noModals: true,
                        showLowRepImageUploadWarning: true,
                        reputationToPostImages: 10,
                        bindNavPrevention: true,
                        postfix: "",
                        imageUploader: {
                        brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
                        contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
                        allowUrls: true
                        },
                        onDemand: true,
                        discardSelector: ".discard-answer"
                        ,immediatelyShowMarkdownHelp:true
                        });


                        }
                        });














                        draft saved

                        draft discarded


















                        StackExchange.ready(
                        function () {
                        StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f17703510%2fdyld-library-not-loaded-reason-image-not-found%23new-answer', 'question_page');
                        }
                        );

                        Post as a guest















                        Required, but never shown

























                        16 Answers
                        16






                        active

                        oldest

                        votes








                        16 Answers
                        16






                        active

                        oldest

                        votes









                        active

                        oldest

                        votes






                        active

                        oldest

                        votes









                        133














                        Find all the boost libraries:



                        $ otool -L exefile
                        exefile:
                        @executable_path/libboost_something.dylib (compatibility version 0.7.0, current version 0.7.0)
                        /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 65.1.0)
                        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)


                        and for each libboost_xxx.dylib, do:



                        $ install_name_tool -change @executable_path/libboost_something.dylib /opt/local/lib/libboost_something.dylib exefile


                        and finally verify using otool again:



                        $ otool -L exefile
                        exefile:
                        /opt/local/lib/libboost_something.dylib (compatibility version 0.7.0, current version 0.7.0)
                        /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 65.1.0)
                        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)


                        Manpages: otool install_name_tool



                        EDIT A while back I wrote a python script (copy_dylibs.py) to work out all this stuff automatically when building an app. It will package up all libraries from /usr/local or /opt/local into the app bundle and fix references to those libraries to use @rpath. This means you can easily install third-party library using Homebrew and package them just as easily.



                        I have now made this script public on github.






                        share|improve this answer


























                        • @RobWolstenholme Yeah the changes are permanent.

                          – trojanfoe
                          Jul 17 '13 at 16:11






                        • 3





                          @trojanfoe can you please explain here what is the exefile is it be a tool exec file path ? isnt it ?

                          – VenushkaT
                          Dec 2 '14 at 5:30






                        • 1





                          If this is my error: dyld: Library not loaded: /usr/local/homebrew/lib/libboost_system-mt.dylib Referenced from: /Users/jordann/Documents/Games/TUO_OSX/./tuo-2.4.5 Reason: image not found Trace/BPT trap: 5 Can someone help me then what to fill in after $ install_name_tool

                          – Jordann Gross
                          Feb 20 '15 at 13:22








                        • 3





                          @JordannGross Ask a new question.

                          – trojanfoe
                          Feb 24 '15 at 15:14






                        • 5





                          'exefile': No such file or directory

                          – ScottyBlades
                          May 29 '18 at 7:38
















                        133














                        Find all the boost libraries:



                        $ otool -L exefile
                        exefile:
                        @executable_path/libboost_something.dylib (compatibility version 0.7.0, current version 0.7.0)
                        /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 65.1.0)
                        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)


                        and for each libboost_xxx.dylib, do:



                        $ install_name_tool -change @executable_path/libboost_something.dylib /opt/local/lib/libboost_something.dylib exefile


                        and finally verify using otool again:



                        $ otool -L exefile
                        exefile:
                        /opt/local/lib/libboost_something.dylib (compatibility version 0.7.0, current version 0.7.0)
                        /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 65.1.0)
                        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)


                        Manpages: otool install_name_tool



                        EDIT A while back I wrote a python script (copy_dylibs.py) to work out all this stuff automatically when building an app. It will package up all libraries from /usr/local or /opt/local into the app bundle and fix references to those libraries to use @rpath. This means you can easily install third-party library using Homebrew and package them just as easily.



                        I have now made this script public on github.






                        share|improve this answer


























                        • @RobWolstenholme Yeah the changes are permanent.

                          – trojanfoe
                          Jul 17 '13 at 16:11






                        • 3





                          @trojanfoe can you please explain here what is the exefile is it be a tool exec file path ? isnt it ?

                          – VenushkaT
                          Dec 2 '14 at 5:30






                        • 1





                          If this is my error: dyld: Library not loaded: /usr/local/homebrew/lib/libboost_system-mt.dylib Referenced from: /Users/jordann/Documents/Games/TUO_OSX/./tuo-2.4.5 Reason: image not found Trace/BPT trap: 5 Can someone help me then what to fill in after $ install_name_tool

                          – Jordann Gross
                          Feb 20 '15 at 13:22








                        • 3





                          @JordannGross Ask a new question.

                          – trojanfoe
                          Feb 24 '15 at 15:14






                        • 5





                          'exefile': No such file or directory

                          – ScottyBlades
                          May 29 '18 at 7:38














                        133












                        133








                        133







                        Find all the boost libraries:



                        $ otool -L exefile
                        exefile:
                        @executable_path/libboost_something.dylib (compatibility version 0.7.0, current version 0.7.0)
                        /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 65.1.0)
                        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)


                        and for each libboost_xxx.dylib, do:



                        $ install_name_tool -change @executable_path/libboost_something.dylib /opt/local/lib/libboost_something.dylib exefile


                        and finally verify using otool again:



                        $ otool -L exefile
                        exefile:
                        /opt/local/lib/libboost_something.dylib (compatibility version 0.7.0, current version 0.7.0)
                        /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 65.1.0)
                        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)


                        Manpages: otool install_name_tool



                        EDIT A while back I wrote a python script (copy_dylibs.py) to work out all this stuff automatically when building an app. It will package up all libraries from /usr/local or /opt/local into the app bundle and fix references to those libraries to use @rpath. This means you can easily install third-party library using Homebrew and package them just as easily.



                        I have now made this script public on github.






                        share|improve this answer















                        Find all the boost libraries:



                        $ otool -L exefile
                        exefile:
                        @executable_path/libboost_something.dylib (compatibility version 0.7.0, current version 0.7.0)
                        /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 65.1.0)
                        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)


                        and for each libboost_xxx.dylib, do:



                        $ install_name_tool -change @executable_path/libboost_something.dylib /opt/local/lib/libboost_something.dylib exefile


                        and finally verify using otool again:



                        $ otool -L exefile
                        exefile:
                        /opt/local/lib/libboost_something.dylib (compatibility version 0.7.0, current version 0.7.0)
                        /usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 65.1.0)
                        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)


                        Manpages: otool install_name_tool



                        EDIT A while back I wrote a python script (copy_dylibs.py) to work out all this stuff automatically when building an app. It will package up all libraries from /usr/local or /opt/local into the app bundle and fix references to those libraries to use @rpath. This means you can easily install third-party library using Homebrew and package them just as easily.



                        I have now made this script public on github.







                        share|improve this answer














                        share|improve this answer



                        share|improve this answer








                        edited Feb 27 at 12:36

























                        answered Jul 17 '13 at 15:40









                        trojanfoetrojanfoe

                        106k15173210




                        106k15173210













                        • @RobWolstenholme Yeah the changes are permanent.

                          – trojanfoe
                          Jul 17 '13 at 16:11






                        • 3





                          @trojanfoe can you please explain here what is the exefile is it be a tool exec file path ? isnt it ?

                          – VenushkaT
                          Dec 2 '14 at 5:30






                        • 1





                          If this is my error: dyld: Library not loaded: /usr/local/homebrew/lib/libboost_system-mt.dylib Referenced from: /Users/jordann/Documents/Games/TUO_OSX/./tuo-2.4.5 Reason: image not found Trace/BPT trap: 5 Can someone help me then what to fill in after $ install_name_tool

                          – Jordann Gross
                          Feb 20 '15 at 13:22








                        • 3





                          @JordannGross Ask a new question.

                          – trojanfoe
                          Feb 24 '15 at 15:14






                        • 5





                          'exefile': No such file or directory

                          – ScottyBlades
                          May 29 '18 at 7:38



















                        • @RobWolstenholme Yeah the changes are permanent.

                          – trojanfoe
                          Jul 17 '13 at 16:11






                        • 3





                          @trojanfoe can you please explain here what is the exefile is it be a tool exec file path ? isnt it ?

                          – VenushkaT
                          Dec 2 '14 at 5:30






                        • 1





                          If this is my error: dyld: Library not loaded: /usr/local/homebrew/lib/libboost_system-mt.dylib Referenced from: /Users/jordann/Documents/Games/TUO_OSX/./tuo-2.4.5 Reason: image not found Trace/BPT trap: 5 Can someone help me then what to fill in after $ install_name_tool

                          – Jordann Gross
                          Feb 20 '15 at 13:22








                        • 3





                          @JordannGross Ask a new question.

                          – trojanfoe
                          Feb 24 '15 at 15:14






                        • 5





                          'exefile': No such file or directory

                          – ScottyBlades
                          May 29 '18 at 7:38

















                        @RobWolstenholme Yeah the changes are permanent.

                        – trojanfoe
                        Jul 17 '13 at 16:11





                        @RobWolstenholme Yeah the changes are permanent.

                        – trojanfoe
                        Jul 17 '13 at 16:11




                        3




                        3





                        @trojanfoe can you please explain here what is the exefile is it be a tool exec file path ? isnt it ?

                        – VenushkaT
                        Dec 2 '14 at 5:30





                        @trojanfoe can you please explain here what is the exefile is it be a tool exec file path ? isnt it ?

                        – VenushkaT
                        Dec 2 '14 at 5:30




                        1




                        1





                        If this is my error: dyld: Library not loaded: /usr/local/homebrew/lib/libboost_system-mt.dylib Referenced from: /Users/jordann/Documents/Games/TUO_OSX/./tuo-2.4.5 Reason: image not found Trace/BPT trap: 5 Can someone help me then what to fill in after $ install_name_tool

                        – Jordann Gross
                        Feb 20 '15 at 13:22







                        If this is my error: dyld: Library not loaded: /usr/local/homebrew/lib/libboost_system-mt.dylib Referenced from: /Users/jordann/Documents/Games/TUO_OSX/./tuo-2.4.5 Reason: image not found Trace/BPT trap: 5 Can someone help me then what to fill in after $ install_name_tool

                        – Jordann Gross
                        Feb 20 '15 at 13:22






                        3




                        3





                        @JordannGross Ask a new question.

                        – trojanfoe
                        Feb 24 '15 at 15:14





                        @JordannGross Ask a new question.

                        – trojanfoe
                        Feb 24 '15 at 15:14




                        5




                        5





                        'exefile': No such file or directory

                        – ScottyBlades
                        May 29 '18 at 7:38





                        'exefile': No such file or directory

                        – ScottyBlades
                        May 29 '18 at 7:38













                        71














                        In the target's General tab, there is an Embedded Binaries field.



                        add required framework and crash is resolved.



                        enter image description here



                        click on the + sign and add framework






                        share|improve this answer
























                        • what should i add ? there's a lot of files

                          – Joe Sleiman
                          Jan 8 at 8:15






                        • 1





                          This is solved the problem.

                          – showmyroutes
                          Apr 4 at 21:42






                        • 1





                          Solved it for me

                          – dcdroid
                          Apr 18 at 14:21
















                        71














                        In the target's General tab, there is an Embedded Binaries field.



                        add required framework and crash is resolved.



                        enter image description here



                        click on the + sign and add framework






                        share|improve this answer
























                        • what should i add ? there's a lot of files

                          – Joe Sleiman
                          Jan 8 at 8:15






                        • 1





                          This is solved the problem.

                          – showmyroutes
                          Apr 4 at 21:42






                        • 1





                          Solved it for me

                          – dcdroid
                          Apr 18 at 14:21














                        71












                        71








                        71







                        In the target's General tab, there is an Embedded Binaries field.



                        add required framework and crash is resolved.



                        enter image description here



                        click on the + sign and add framework






                        share|improve this answer













                        In the target's General tab, there is an Embedded Binaries field.



                        add required framework and crash is resolved.



                        enter image description here



                        click on the + sign and add framework







                        share|improve this answer












                        share|improve this answer



                        share|improve this answer










                        answered May 10 '16 at 7:22









                        Himanshu padiaHimanshu padia

                        4,6653539




                        4,6653539













                        • what should i add ? there's a lot of files

                          – Joe Sleiman
                          Jan 8 at 8:15






                        • 1





                          This is solved the problem.

                          – showmyroutes
                          Apr 4 at 21:42






                        • 1





                          Solved it for me

                          – dcdroid
                          Apr 18 at 14:21



















                        • what should i add ? there's a lot of files

                          – Joe Sleiman
                          Jan 8 at 8:15






                        • 1





                          This is solved the problem.

                          – showmyroutes
                          Apr 4 at 21:42






                        • 1





                          Solved it for me

                          – dcdroid
                          Apr 18 at 14:21

















                        what should i add ? there's a lot of files

                        – Joe Sleiman
                        Jan 8 at 8:15





                        what should i add ? there's a lot of files

                        – Joe Sleiman
                        Jan 8 at 8:15




                        1




                        1





                        This is solved the problem.

                        – showmyroutes
                        Apr 4 at 21:42





                        This is solved the problem.

                        – showmyroutes
                        Apr 4 at 21:42




                        1




                        1





                        Solved it for me

                        – dcdroid
                        Apr 18 at 14:21





                        Solved it for me

                        – dcdroid
                        Apr 18 at 14:21











                        30














                        This worked for me:



                        brew upgrade node





                        share|improve this answer




























                          30














                          This worked for me:



                          brew upgrade node





                          share|improve this answer


























                            30












                            30








                            30







                            This worked for me:



                            brew upgrade node





                            share|improve this answer













                            This worked for me:



                            brew upgrade node






                            share|improve this answer












                            share|improve this answer



                            share|improve this answer










                            answered May 9 '18 at 20:14









                            oshaikenoshaiken

                            891919




                            891919























                                28














                                For some, this could be as easy as setting the system path for dynamic libraries. On OS X, this is as simple as setting the DYLD_LIBRARY_PATH environment variable. See:



                                Is it OK to use DYLD_LIBRARY_PATH on Mac OS X? And, what's the dynamic library search algorithm with it?






                                share|improve this answer





















                                • 2





                                  This answer is the most generic and gets to the point: if you have custom/user libs, then this is the way to go.

                                  – Kei-ven
                                  Jul 4 '16 at 1:47











                                • It may seem stupid, but I wonder what value should I set DYLD_LIBRARY_PATH to?

                                  – Caesar
                                  Mar 21 '17 at 1:13








                                • 1





                                  @Caesar Set it to the directory of wherever the dylibs you're trying to link are located.

                                  – markshiz
                                  May 2 '17 at 14:01






                                • 1





                                  This should be accepted as the answer. The other one with higher votes are meaningless.

                                  – SmallChess
                                  Nov 27 '17 at 23:59











                                • You cannot expect your users to change DYLD_LIBRARY_PATH. The correct solution is to include non-standard libraries with the .app and the user won't have to do anything. The developer, however, may still have to hack the loader path as per my answer.

                                  – trojanfoe
                                  Feb 4 at 8:00


















                                28














                                For some, this could be as easy as setting the system path for dynamic libraries. On OS X, this is as simple as setting the DYLD_LIBRARY_PATH environment variable. See:



                                Is it OK to use DYLD_LIBRARY_PATH on Mac OS X? And, what's the dynamic library search algorithm with it?






                                share|improve this answer





















                                • 2





                                  This answer is the most generic and gets to the point: if you have custom/user libs, then this is the way to go.

                                  – Kei-ven
                                  Jul 4 '16 at 1:47











                                • It may seem stupid, but I wonder what value should I set DYLD_LIBRARY_PATH to?

                                  – Caesar
                                  Mar 21 '17 at 1:13








                                • 1





                                  @Caesar Set it to the directory of wherever the dylibs you're trying to link are located.

                                  – markshiz
                                  May 2 '17 at 14:01






                                • 1





                                  This should be accepted as the answer. The other one with higher votes are meaningless.

                                  – SmallChess
                                  Nov 27 '17 at 23:59











                                • You cannot expect your users to change DYLD_LIBRARY_PATH. The correct solution is to include non-standard libraries with the .app and the user won't have to do anything. The developer, however, may still have to hack the loader path as per my answer.

                                  – trojanfoe
                                  Feb 4 at 8:00
















                                28












                                28








                                28







                                For some, this could be as easy as setting the system path for dynamic libraries. On OS X, this is as simple as setting the DYLD_LIBRARY_PATH environment variable. See:



                                Is it OK to use DYLD_LIBRARY_PATH on Mac OS X? And, what's the dynamic library search algorithm with it?






                                share|improve this answer















                                For some, this could be as easy as setting the system path for dynamic libraries. On OS X, this is as simple as setting the DYLD_LIBRARY_PATH environment variable. See:



                                Is it OK to use DYLD_LIBRARY_PATH on Mac OS X? And, what's the dynamic library search algorithm with it?







                                share|improve this answer














                                share|improve this answer



                                share|improve this answer








                                edited May 23 '17 at 11:55









                                Community

                                11




                                11










                                answered Jan 27 '16 at 1:04









                                markshizmarkshiz

                                1,9841422




                                1,9841422








                                • 2





                                  This answer is the most generic and gets to the point: if you have custom/user libs, then this is the way to go.

                                  – Kei-ven
                                  Jul 4 '16 at 1:47











                                • It may seem stupid, but I wonder what value should I set DYLD_LIBRARY_PATH to?

                                  – Caesar
                                  Mar 21 '17 at 1:13








                                • 1





                                  @Caesar Set it to the directory of wherever the dylibs you're trying to link are located.

                                  – markshiz
                                  May 2 '17 at 14:01






                                • 1





                                  This should be accepted as the answer. The other one with higher votes are meaningless.

                                  – SmallChess
                                  Nov 27 '17 at 23:59











                                • You cannot expect your users to change DYLD_LIBRARY_PATH. The correct solution is to include non-standard libraries with the .app and the user won't have to do anything. The developer, however, may still have to hack the loader path as per my answer.

                                  – trojanfoe
                                  Feb 4 at 8:00
















                                • 2





                                  This answer is the most generic and gets to the point: if you have custom/user libs, then this is the way to go.

                                  – Kei-ven
                                  Jul 4 '16 at 1:47











                                • It may seem stupid, but I wonder what value should I set DYLD_LIBRARY_PATH to?

                                  – Caesar
                                  Mar 21 '17 at 1:13








                                • 1





                                  @Caesar Set it to the directory of wherever the dylibs you're trying to link are located.

                                  – markshiz
                                  May 2 '17 at 14:01






                                • 1





                                  This should be accepted as the answer. The other one with higher votes are meaningless.

                                  – SmallChess
                                  Nov 27 '17 at 23:59











                                • You cannot expect your users to change DYLD_LIBRARY_PATH. The correct solution is to include non-standard libraries with the .app and the user won't have to do anything. The developer, however, may still have to hack the loader path as per my answer.

                                  – trojanfoe
                                  Feb 4 at 8:00










                                2




                                2





                                This answer is the most generic and gets to the point: if you have custom/user libs, then this is the way to go.

                                – Kei-ven
                                Jul 4 '16 at 1:47





                                This answer is the most generic and gets to the point: if you have custom/user libs, then this is the way to go.

                                – Kei-ven
                                Jul 4 '16 at 1:47













                                It may seem stupid, but I wonder what value should I set DYLD_LIBRARY_PATH to?

                                – Caesar
                                Mar 21 '17 at 1:13







                                It may seem stupid, but I wonder what value should I set DYLD_LIBRARY_PATH to?

                                – Caesar
                                Mar 21 '17 at 1:13






                                1




                                1





                                @Caesar Set it to the directory of wherever the dylibs you're trying to link are located.

                                – markshiz
                                May 2 '17 at 14:01





                                @Caesar Set it to the directory of wherever the dylibs you're trying to link are located.

                                – markshiz
                                May 2 '17 at 14:01




                                1




                                1





                                This should be accepted as the answer. The other one with higher votes are meaningless.

                                – SmallChess
                                Nov 27 '17 at 23:59





                                This should be accepted as the answer. The other one with higher votes are meaningless.

                                – SmallChess
                                Nov 27 '17 at 23:59













                                You cannot expect your users to change DYLD_LIBRARY_PATH. The correct solution is to include non-standard libraries with the .app and the user won't have to do anything. The developer, however, may still have to hack the loader path as per my answer.

                                – trojanfoe
                                Feb 4 at 8:00







                                You cannot expect your users to change DYLD_LIBRARY_PATH. The correct solution is to include non-standard libraries with the .app and the user won't have to do anything. The developer, however, may still have to hack the loader path as per my answer.

                                – trojanfoe
                                Feb 4 at 8:00













                                13














                                I got this error when I tried to install ruby 2.3.1 using rvm. It first told me to run brew update, which I did, and then when I tried running rvm install ruby-2.3.1, I received the error in this SO question.



                                The fix was to first run brew upgrade, apparently according to this superuser.com question you need to do both brew update && brew upgrade. Once that was done, I could finally install ruby 2.3.1.






                                share|improve this answer






























                                  13














                                  I got this error when I tried to install ruby 2.3.1 using rvm. It first told me to run brew update, which I did, and then when I tried running rvm install ruby-2.3.1, I received the error in this SO question.



                                  The fix was to first run brew upgrade, apparently according to this superuser.com question you need to do both brew update && brew upgrade. Once that was done, I could finally install ruby 2.3.1.






                                  share|improve this answer




























                                    13












                                    13








                                    13







                                    I got this error when I tried to install ruby 2.3.1 using rvm. It first told me to run brew update, which I did, and then when I tried running rvm install ruby-2.3.1, I received the error in this SO question.



                                    The fix was to first run brew upgrade, apparently according to this superuser.com question you need to do both brew update && brew upgrade. Once that was done, I could finally install ruby 2.3.1.






                                    share|improve this answer















                                    I got this error when I tried to install ruby 2.3.1 using rvm. It first told me to run brew update, which I did, and then when I tried running rvm install ruby-2.3.1, I received the error in this SO question.



                                    The fix was to first run brew upgrade, apparently according to this superuser.com question you need to do both brew update && brew upgrade. Once that was done, I could finally install ruby 2.3.1.







                                    share|improve this answer














                                    share|improve this answer



                                    share|improve this answer








                                    edited Mar 20 '17 at 10:18









                                    Community

                                    11




                                    11










                                    answered Oct 21 '16 at 11:41









                                    IonicBurgerIonicBurger

                                    2,61412139




                                    2,61412139























                                        5














                                        You can use the otool command with the -L option for the executable, which will display where the executable is expecting those libraries to be.



                                        If the path to those need changing, use the install_name_tool command, which allows you to set the path to the libraries.






                                        share|improve this answer




























                                          5














                                          You can use the otool command with the -L option for the executable, which will display where the executable is expecting those libraries to be.



                                          If the path to those need changing, use the install_name_tool command, which allows you to set the path to the libraries.






                                          share|improve this answer


























                                            5












                                            5








                                            5







                                            You can use the otool command with the -L option for the executable, which will display where the executable is expecting those libraries to be.



                                            If the path to those need changing, use the install_name_tool command, which allows you to set the path to the libraries.






                                            share|improve this answer













                                            You can use the otool command with the -L option for the executable, which will display where the executable is expecting those libraries to be.



                                            If the path to those need changing, use the install_name_tool command, which allows you to set the path to the libraries.







                                            share|improve this answer












                                            share|improve this answer



                                            share|improve this answer










                                            answered Jul 17 '13 at 15:26









                                            TheDarkKnightTheDarkKnight

                                            22k43666




                                            22k43666























                                                4














                                                I got here trying to run a program I just compiled using CMake. When I try to run it, it complains saying:



                                                dyld: Library not loaded: libboost_system.dylib
                                                Referenced from: /Users/path/to/my/executable
                                                Reason: image not found


                                                I circumvented the problem telling CMake to use the static version of Boost, instead of letting it use the dynamic one:



                                                set(Boost_USE_STATIC_LIBS ON)





                                                share|improve this answer






























                                                  4














                                                  I got here trying to run a program I just compiled using CMake. When I try to run it, it complains saying:



                                                  dyld: Library not loaded: libboost_system.dylib
                                                  Referenced from: /Users/path/to/my/executable
                                                  Reason: image not found


                                                  I circumvented the problem telling CMake to use the static version of Boost, instead of letting it use the dynamic one:



                                                  set(Boost_USE_STATIC_LIBS ON)





                                                  share|improve this answer




























                                                    4












                                                    4








                                                    4







                                                    I got here trying to run a program I just compiled using CMake. When I try to run it, it complains saying:



                                                    dyld: Library not loaded: libboost_system.dylib
                                                    Referenced from: /Users/path/to/my/executable
                                                    Reason: image not found


                                                    I circumvented the problem telling CMake to use the static version of Boost, instead of letting it use the dynamic one:



                                                    set(Boost_USE_STATIC_LIBS ON)





                                                    share|improve this answer















                                                    I got here trying to run a program I just compiled using CMake. When I try to run it, it complains saying:



                                                    dyld: Library not loaded: libboost_system.dylib
                                                    Referenced from: /Users/path/to/my/executable
                                                    Reason: image not found


                                                    I circumvented the problem telling CMake to use the static version of Boost, instead of letting it use the dynamic one:



                                                    set(Boost_USE_STATIC_LIBS ON)






                                                    share|improve this answer














                                                    share|improve this answer



                                                    share|improve this answer








                                                    edited Jun 30 '15 at 21:38

























                                                    answered Jun 30 '15 at 2:35









                                                    Lucio PaivaLucio Paiva

                                                    7,11523959




                                                    7,11523959























                                                        4














                                                        After upgrade Mac OS to Mojave. I tried to install npm modules via yarn command I got error:



                                                        dyld: Library not loaded: /usr/local/opt/icu4c/lib/libicui18n.60.dylib
                                                        Referenced from: /usr/local/bin/node
                                                        Reason: image not found
                                                        Abort trap: 6


                                                        Was fix with:



                                                        brew update
                                                        brew upgrade





                                                        share|improve this answer




























                                                          4














                                                          After upgrade Mac OS to Mojave. I tried to install npm modules via yarn command I got error:



                                                          dyld: Library not loaded: /usr/local/opt/icu4c/lib/libicui18n.60.dylib
                                                          Referenced from: /usr/local/bin/node
                                                          Reason: image not found
                                                          Abort trap: 6


                                                          Was fix with:



                                                          brew update
                                                          brew upgrade





                                                          share|improve this answer


























                                                            4












                                                            4








                                                            4







                                                            After upgrade Mac OS to Mojave. I tried to install npm modules via yarn command I got error:



                                                            dyld: Library not loaded: /usr/local/opt/icu4c/lib/libicui18n.60.dylib
                                                            Referenced from: /usr/local/bin/node
                                                            Reason: image not found
                                                            Abort trap: 6


                                                            Was fix with:



                                                            brew update
                                                            brew upgrade





                                                            share|improve this answer













                                                            After upgrade Mac OS to Mojave. I tried to install npm modules via yarn command I got error:



                                                            dyld: Library not loaded: /usr/local/opt/icu4c/lib/libicui18n.60.dylib
                                                            Referenced from: /usr/local/bin/node
                                                            Reason: image not found
                                                            Abort trap: 6


                                                            Was fix with:



                                                            brew update
                                                            brew upgrade






                                                            share|improve this answer












                                                            share|improve this answer



                                                            share|improve this answer










                                                            answered Jan 7 at 10:39









                                                            Michael KlishevichMichael Klishevich

                                                            344513




                                                            344513























                                                                2














                                                                I fix it by brew install libpng






                                                                share|improve this answer




























                                                                  2














                                                                  I fix it by brew install libpng






                                                                  share|improve this answer


























                                                                    2












                                                                    2








                                                                    2







                                                                    I fix it by brew install libpng






                                                                    share|improve this answer













                                                                    I fix it by brew install libpng







                                                                    share|improve this answer












                                                                    share|improve this answer



                                                                    share|improve this answer










                                                                    answered Mar 16 '18 at 5:49









                                                                    user3835452user3835452

                                                                    412




                                                                    412























                                                                        1














                                                                        You can use sudo install_name_tool -change change dylib path
                                                                        And
                                                                        sudo install_name_tool -id change dylib name






                                                                        share|improve this answer




























                                                                          1














                                                                          You can use sudo install_name_tool -change change dylib path
                                                                          And
                                                                          sudo install_name_tool -id change dylib name






                                                                          share|improve this answer


























                                                                            1












                                                                            1








                                                                            1







                                                                            You can use sudo install_name_tool -change change dylib path
                                                                            And
                                                                            sudo install_name_tool -id change dylib name






                                                                            share|improve this answer













                                                                            You can use sudo install_name_tool -change change dylib path
                                                                            And
                                                                            sudo install_name_tool -id change dylib name







                                                                            share|improve this answer












                                                                            share|improve this answer



                                                                            share|improve this answer










                                                                            answered Dec 12 '16 at 6:39









                                                                            hailuodevhailuodev

                                                                            59649




                                                                            59649























                                                                                0














                                                                                For anyone coming to this page because they got this error trying to link a third party framework to their project using Xcode 6.3.1, the problem I ran into was because the library was being created with an older version of the compiler using a different version of swift. The only way to fix this for me was to re-build the framework.



                                                                                Another reason you might get this is stated in an Apple technical doc..




                                                                                If you are building an app that does not use Swift but embeds content such as a framework that does, Xcode will not include these libraries in your app. As a result, your app will crash upon launching with an error message looking as follows:




                                                                                set the Embedded Content Contains Swift Code (EMBEDDED_CONTENT_CONTAINS_SWIFT) build setting to YES in your app



                                                                                Here is the link to the full Apple doc that explains it here






                                                                                share|improve this answer


























                                                                                • but how do you solve this?

                                                                                  – Klemen Zagar
                                                                                  Apr 17 '16 at 8:32
















                                                                                0














                                                                                For anyone coming to this page because they got this error trying to link a third party framework to their project using Xcode 6.3.1, the problem I ran into was because the library was being created with an older version of the compiler using a different version of swift. The only way to fix this for me was to re-build the framework.



                                                                                Another reason you might get this is stated in an Apple technical doc..




                                                                                If you are building an app that does not use Swift but embeds content such as a framework that does, Xcode will not include these libraries in your app. As a result, your app will crash upon launching with an error message looking as follows:




                                                                                set the Embedded Content Contains Swift Code (EMBEDDED_CONTENT_CONTAINS_SWIFT) build setting to YES in your app



                                                                                Here is the link to the full Apple doc that explains it here






                                                                                share|improve this answer


























                                                                                • but how do you solve this?

                                                                                  – Klemen Zagar
                                                                                  Apr 17 '16 at 8:32














                                                                                0












                                                                                0








                                                                                0







                                                                                For anyone coming to this page because they got this error trying to link a third party framework to their project using Xcode 6.3.1, the problem I ran into was because the library was being created with an older version of the compiler using a different version of swift. The only way to fix this for me was to re-build the framework.



                                                                                Another reason you might get this is stated in an Apple technical doc..




                                                                                If you are building an app that does not use Swift but embeds content such as a framework that does, Xcode will not include these libraries in your app. As a result, your app will crash upon launching with an error message looking as follows:




                                                                                set the Embedded Content Contains Swift Code (EMBEDDED_CONTENT_CONTAINS_SWIFT) build setting to YES in your app



                                                                                Here is the link to the full Apple doc that explains it here






                                                                                share|improve this answer















                                                                                For anyone coming to this page because they got this error trying to link a third party framework to their project using Xcode 6.3.1, the problem I ran into was because the library was being created with an older version of the compiler using a different version of swift. The only way to fix this for me was to re-build the framework.



                                                                                Another reason you might get this is stated in an Apple technical doc..




                                                                                If you are building an app that does not use Swift but embeds content such as a framework that does, Xcode will not include these libraries in your app. As a result, your app will crash upon launching with an error message looking as follows:




                                                                                set the Embedded Content Contains Swift Code (EMBEDDED_CONTENT_CONTAINS_SWIFT) build setting to YES in your app



                                                                                Here is the link to the full Apple doc that explains it here







                                                                                share|improve this answer














                                                                                share|improve this answer



                                                                                share|improve this answer








                                                                                edited Apr 17 '16 at 11:30

























                                                                                answered Apr 28 '15 at 1:22









                                                                                bolnadbolnad

                                                                                3,32232237




                                                                                3,32232237













                                                                                • but how do you solve this?

                                                                                  – Klemen Zagar
                                                                                  Apr 17 '16 at 8:32



















                                                                                • but how do you solve this?

                                                                                  – Klemen Zagar
                                                                                  Apr 17 '16 at 8:32

















                                                                                but how do you solve this?

                                                                                – Klemen Zagar
                                                                                Apr 17 '16 at 8:32





                                                                                but how do you solve this?

                                                                                – Klemen Zagar
                                                                                Apr 17 '16 at 8:32











                                                                                0














                                                                                I faced the app crash issue quoting SIGABRT error in thread.Overview of the crash is dyld library not loaded and image not found something like that.



                                                                                This was seen in xcode 9.3 version.The reason i found out was xcode is not picking up libraries dynamically so i had to do it manually which solved my crash issue.



                                                                                Follow the below steps:
                                                                                Step 1: Go to Build Phases
                                                                                Step 2: Hit the '+' button at the top and select "New Copy File Phase"
                                                                                Step 3 : Select Destination as Frameworks and Hit the '+' button below to add files.
                                                                                Step 4 : Select Add Other at below, click CMD+SHIFT+G and paste the below path,
                                                                                /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphoneos



                                                                                Now you will be able to see some swift dylibs, Select all the swift libraries with .dylib extension and click on open.



                                                                                These will get added to the embedded binaries in the general tab of app.



                                                                                Create a new group in project folder and add all these libraries.



                                                                                Now run your app.



                                                                                Happy Coding






                                                                                share|improve this answer




























                                                                                  0














                                                                                  I faced the app crash issue quoting SIGABRT error in thread.Overview of the crash is dyld library not loaded and image not found something like that.



                                                                                  This was seen in xcode 9.3 version.The reason i found out was xcode is not picking up libraries dynamically so i had to do it manually which solved my crash issue.



                                                                                  Follow the below steps:
                                                                                  Step 1: Go to Build Phases
                                                                                  Step 2: Hit the '+' button at the top and select "New Copy File Phase"
                                                                                  Step 3 : Select Destination as Frameworks and Hit the '+' button below to add files.
                                                                                  Step 4 : Select Add Other at below, click CMD+SHIFT+G and paste the below path,
                                                                                  /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphoneos



                                                                                  Now you will be able to see some swift dylibs, Select all the swift libraries with .dylib extension and click on open.



                                                                                  These will get added to the embedded binaries in the general tab of app.



                                                                                  Create a new group in project folder and add all these libraries.



                                                                                  Now run your app.



                                                                                  Happy Coding






                                                                                  share|improve this answer


























                                                                                    0












                                                                                    0








                                                                                    0







                                                                                    I faced the app crash issue quoting SIGABRT error in thread.Overview of the crash is dyld library not loaded and image not found something like that.



                                                                                    This was seen in xcode 9.3 version.The reason i found out was xcode is not picking up libraries dynamically so i had to do it manually which solved my crash issue.



                                                                                    Follow the below steps:
                                                                                    Step 1: Go to Build Phases
                                                                                    Step 2: Hit the '+' button at the top and select "New Copy File Phase"
                                                                                    Step 3 : Select Destination as Frameworks and Hit the '+' button below to add files.
                                                                                    Step 4 : Select Add Other at below, click CMD+SHIFT+G and paste the below path,
                                                                                    /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphoneos



                                                                                    Now you will be able to see some swift dylibs, Select all the swift libraries with .dylib extension and click on open.



                                                                                    These will get added to the embedded binaries in the general tab of app.



                                                                                    Create a new group in project folder and add all these libraries.



                                                                                    Now run your app.



                                                                                    Happy Coding






                                                                                    share|improve this answer













                                                                                    I faced the app crash issue quoting SIGABRT error in thread.Overview of the crash is dyld library not loaded and image not found something like that.



                                                                                    This was seen in xcode 9.3 version.The reason i found out was xcode is not picking up libraries dynamically so i had to do it manually which solved my crash issue.



                                                                                    Follow the below steps:
                                                                                    Step 1: Go to Build Phases
                                                                                    Step 2: Hit the '+' button at the top and select "New Copy File Phase"
                                                                                    Step 3 : Select Destination as Frameworks and Hit the '+' button below to add files.
                                                                                    Step 4 : Select Add Other at below, click CMD+SHIFT+G and paste the below path,
                                                                                    /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphoneos



                                                                                    Now you will be able to see some swift dylibs, Select all the swift libraries with .dylib extension and click on open.



                                                                                    These will get added to the embedded binaries in the general tab of app.



                                                                                    Create a new group in project folder and add all these libraries.



                                                                                    Now run your app.



                                                                                    Happy Coding







                                                                                    share|improve this answer












                                                                                    share|improve this answer



                                                                                    share|improve this answer










                                                                                    answered May 18 '18 at 7:24









                                                                                    Miya MirzaMiya Mirza

                                                                                    1




                                                                                    1























                                                                                        0














                                                                                        For anyone experiencing the same thing with a different library or package, @user3835452 is on the right track. I found this message while trying to run composer:



                                                                                        dyld: Library not loaded: /usr/local/opt/openldap/lib/libldap-2.4.2.dylib
                                                                                        Referenced from: /usr/local/opt/php@7.1/bin/php
                                                                                        Reason: image not found
                                                                                        Abort trap: 6


                                                                                        After trying a lot of different ways I just ran brew install openldap and it fixed it. Note that I had already ran brew update and brew upgrade but only after I manually installed openldap did it actually work.






                                                                                        share|improve this answer




























                                                                                          0














                                                                                          For anyone experiencing the same thing with a different library or package, @user3835452 is on the right track. I found this message while trying to run composer:



                                                                                          dyld: Library not loaded: /usr/local/opt/openldap/lib/libldap-2.4.2.dylib
                                                                                          Referenced from: /usr/local/opt/php@7.1/bin/php
                                                                                          Reason: image not found
                                                                                          Abort trap: 6


                                                                                          After trying a lot of different ways I just ran brew install openldap and it fixed it. Note that I had already ran brew update and brew upgrade but only after I manually installed openldap did it actually work.






                                                                                          share|improve this answer


























                                                                                            0












                                                                                            0








                                                                                            0







                                                                                            For anyone experiencing the same thing with a different library or package, @user3835452 is on the right track. I found this message while trying to run composer:



                                                                                            dyld: Library not loaded: /usr/local/opt/openldap/lib/libldap-2.4.2.dylib
                                                                                            Referenced from: /usr/local/opt/php@7.1/bin/php
                                                                                            Reason: image not found
                                                                                            Abort trap: 6


                                                                                            After trying a lot of different ways I just ran brew install openldap and it fixed it. Note that I had already ran brew update and brew upgrade but only after I manually installed openldap did it actually work.






                                                                                            share|improve this answer













                                                                                            For anyone experiencing the same thing with a different library or package, @user3835452 is on the right track. I found this message while trying to run composer:



                                                                                            dyld: Library not loaded: /usr/local/opt/openldap/lib/libldap-2.4.2.dylib
                                                                                            Referenced from: /usr/local/opt/php@7.1/bin/php
                                                                                            Reason: image not found
                                                                                            Abort trap: 6


                                                                                            After trying a lot of different ways I just ran brew install openldap and it fixed it. Note that I had already ran brew update and brew upgrade but only after I manually installed openldap did it actually work.







                                                                                            share|improve this answer












                                                                                            share|improve this answer



                                                                                            share|improve this answer










                                                                                            answered Nov 25 '18 at 6:42









                                                                                            brunounobrunouno

                                                                                            327414




                                                                                            327414























                                                                                                0














                                                                                                Maybe someone need this:



                                                                                                if you use cmake, add DYLIB_INSTALL_NAME_BASE "@rpath" to target properties:



                                                                                                set_target_properties(target_dyLib PROPERTIES
                                                                                                # # for FRAMEWORK begin
                                                                                                # FRAMEWORK TRUE
                                                                                                # FRAMEWORK_VERSION C
                                                                                                # MACOSX_FRAMEWORK_IDENTIFIER com.cmake.targetname
                                                                                                # MACOSX_FRAMEWORK_INFO_PLIST ./Info.plist
                                                                                                # PUBLIC_HEADER targetname.h
                                                                                                # # for FRAMEWORK end
                                                                                                IPHONEOS_DEPLOYMENT_TARGET "8.0"
                                                                                                DYLIB_INSTALL_NAME_BASE "@rpath" # this is the key point
                                                                                                XCODE_ATTRIBUTE_CODE_SIGN_IDENTITY "iPhone Developer"
                                                                                                DEVELOPMENT_TEAM "${DEVELOPMENT_TEAM}"
                                                                                                )


                                                                                                or in xcode dynamic library project Target -> Build Setting set Dynamic Library Install Name Base to @rpath






                                                                                                share|improve this answer
























                                                                                                • I create a cocoa framework dynamic library project, it works, and compared with my bad cmake generated project find this different, and fixed it, it works on iOS.

                                                                                                  – cn00
                                                                                                  Feb 27 at 6:54


















                                                                                                0














                                                                                                Maybe someone need this:



                                                                                                if you use cmake, add DYLIB_INSTALL_NAME_BASE "@rpath" to target properties:



                                                                                                set_target_properties(target_dyLib PROPERTIES
                                                                                                # # for FRAMEWORK begin
                                                                                                # FRAMEWORK TRUE
                                                                                                # FRAMEWORK_VERSION C
                                                                                                # MACOSX_FRAMEWORK_IDENTIFIER com.cmake.targetname
                                                                                                # MACOSX_FRAMEWORK_INFO_PLIST ./Info.plist
                                                                                                # PUBLIC_HEADER targetname.h
                                                                                                # # for FRAMEWORK end
                                                                                                IPHONEOS_DEPLOYMENT_TARGET "8.0"
                                                                                                DYLIB_INSTALL_NAME_BASE "@rpath" # this is the key point
                                                                                                XCODE_ATTRIBUTE_CODE_SIGN_IDENTITY "iPhone Developer"
                                                                                                DEVELOPMENT_TEAM "${DEVELOPMENT_TEAM}"
                                                                                                )


                                                                                                or in xcode dynamic library project Target -> Build Setting set Dynamic Library Install Name Base to @rpath






                                                                                                share|improve this answer
























                                                                                                • I create a cocoa framework dynamic library project, it works, and compared with my bad cmake generated project find this different, and fixed it, it works on iOS.

                                                                                                  – cn00
                                                                                                  Feb 27 at 6:54
















                                                                                                0












                                                                                                0








                                                                                                0







                                                                                                Maybe someone need this:



                                                                                                if you use cmake, add DYLIB_INSTALL_NAME_BASE "@rpath" to target properties:



                                                                                                set_target_properties(target_dyLib PROPERTIES
                                                                                                # # for FRAMEWORK begin
                                                                                                # FRAMEWORK TRUE
                                                                                                # FRAMEWORK_VERSION C
                                                                                                # MACOSX_FRAMEWORK_IDENTIFIER com.cmake.targetname
                                                                                                # MACOSX_FRAMEWORK_INFO_PLIST ./Info.plist
                                                                                                # PUBLIC_HEADER targetname.h
                                                                                                # # for FRAMEWORK end
                                                                                                IPHONEOS_DEPLOYMENT_TARGET "8.0"
                                                                                                DYLIB_INSTALL_NAME_BASE "@rpath" # this is the key point
                                                                                                XCODE_ATTRIBUTE_CODE_SIGN_IDENTITY "iPhone Developer"
                                                                                                DEVELOPMENT_TEAM "${DEVELOPMENT_TEAM}"
                                                                                                )


                                                                                                or in xcode dynamic library project Target -> Build Setting set Dynamic Library Install Name Base to @rpath






                                                                                                share|improve this answer













                                                                                                Maybe someone need this:



                                                                                                if you use cmake, add DYLIB_INSTALL_NAME_BASE "@rpath" to target properties:



                                                                                                set_target_properties(target_dyLib PROPERTIES
                                                                                                # # for FRAMEWORK begin
                                                                                                # FRAMEWORK TRUE
                                                                                                # FRAMEWORK_VERSION C
                                                                                                # MACOSX_FRAMEWORK_IDENTIFIER com.cmake.targetname
                                                                                                # MACOSX_FRAMEWORK_INFO_PLIST ./Info.plist
                                                                                                # PUBLIC_HEADER targetname.h
                                                                                                # # for FRAMEWORK end
                                                                                                IPHONEOS_DEPLOYMENT_TARGET "8.0"
                                                                                                DYLIB_INSTALL_NAME_BASE "@rpath" # this is the key point
                                                                                                XCODE_ATTRIBUTE_CODE_SIGN_IDENTITY "iPhone Developer"
                                                                                                DEVELOPMENT_TEAM "${DEVELOPMENT_TEAM}"
                                                                                                )


                                                                                                or in xcode dynamic library project Target -> Build Setting set Dynamic Library Install Name Base to @rpath







                                                                                                share|improve this answer












                                                                                                share|improve this answer



                                                                                                share|improve this answer










                                                                                                answered Feb 27 at 6:48









                                                                                                cn00cn00

                                                                                                13




                                                                                                13













                                                                                                • I create a cocoa framework dynamic library project, it works, and compared with my bad cmake generated project find this different, and fixed it, it works on iOS.

                                                                                                  – cn00
                                                                                                  Feb 27 at 6:54





















                                                                                                • I create a cocoa framework dynamic library project, it works, and compared with my bad cmake generated project find this different, and fixed it, it works on iOS.

                                                                                                  – cn00
                                                                                                  Feb 27 at 6:54



















                                                                                                I create a cocoa framework dynamic library project, it works, and compared with my bad cmake generated project find this different, and fixed it, it works on iOS.

                                                                                                – cn00
                                                                                                Feb 27 at 6:54







                                                                                                I create a cocoa framework dynamic library project, it works, and compared with my bad cmake generated project find this different, and fixed it, it works on iOS.

                                                                                                – cn00
                                                                                                Feb 27 at 6:54













                                                                                                0














                                                                                                I fixed this by reinstalling Homebrew



                                                                                                Uninstall



                                                                                                ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/uninstall)"



                                                                                                Install



                                                                                                /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"






                                                                                                share|improve this answer






























                                                                                                  0














                                                                                                  I fixed this by reinstalling Homebrew



                                                                                                  Uninstall



                                                                                                  ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/uninstall)"



                                                                                                  Install



                                                                                                  /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"






                                                                                                  share|improve this answer




























                                                                                                    0












                                                                                                    0








                                                                                                    0







                                                                                                    I fixed this by reinstalling Homebrew



                                                                                                    Uninstall



                                                                                                    ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/uninstall)"



                                                                                                    Install



                                                                                                    /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"






                                                                                                    share|improve this answer















                                                                                                    I fixed this by reinstalling Homebrew



                                                                                                    Uninstall



                                                                                                    ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/uninstall)"



                                                                                                    Install



                                                                                                    /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"







                                                                                                    share|improve this answer














                                                                                                    share|improve this answer



                                                                                                    share|improve this answer








                                                                                                    edited Mar 14 at 15:11

























                                                                                                    answered Mar 14 at 15:02









                                                                                                    sidonaldsonsidonaldson

                                                                                                    14.3k73749




                                                                                                    14.3k73749























                                                                                                        0














                                                                                                        I fixed this issue by simply pressing Command + Shift + K, which makes a new clean build, really odd.






                                                                                                        share|improve this answer




























                                                                                                          0














                                                                                                          I fixed this issue by simply pressing Command + Shift + K, which makes a new clean build, really odd.






                                                                                                          share|improve this answer


























                                                                                                            0












                                                                                                            0








                                                                                                            0







                                                                                                            I fixed this issue by simply pressing Command + Shift + K, which makes a new clean build, really odd.






                                                                                                            share|improve this answer













                                                                                                            I fixed this issue by simply pressing Command + Shift + K, which makes a new clean build, really odd.







                                                                                                            share|improve this answer












                                                                                                            share|improve this answer



                                                                                                            share|improve this answer










                                                                                                            answered Mar 21 at 5:27









                                                                                                            Douglas PfeiferDouglas Pfeifer

                                                                                                            2816




                                                                                                            2816






























                                                                                                                draft saved

                                                                                                                draft discarded




















































                                                                                                                Thanks for contributing an answer to Stack Overflow!


                                                                                                                • Please be sure to answer the question. Provide details and share your research!

                                                                                                                But avoid



                                                                                                                • Asking for help, clarification, or responding to other answers.

                                                                                                                • Making statements based on opinion; back them up with references or personal experience.


                                                                                                                To learn more, see our tips on writing great answers.




                                                                                                                draft saved


                                                                                                                draft discarded














                                                                                                                StackExchange.ready(
                                                                                                                function () {
                                                                                                                StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f17703510%2fdyld-library-not-loaded-reason-image-not-found%23new-answer', 'question_page');
                                                                                                                }
                                                                                                                );

                                                                                                                Post as a guest















                                                                                                                Required, but never shown





















































                                                                                                                Required, but never shown














                                                                                                                Required, but never shown












                                                                                                                Required, but never shown







                                                                                                                Required, but never shown

































                                                                                                                Required, but never shown














                                                                                                                Required, but never shown












                                                                                                                Required, but never shown







                                                                                                                Required, but never shown







                                                                                                                這個網誌中的熱門文章

                                                                                                                Xamarin.form Move up view when keyboard appear

                                                                                                                Post-Redirect-Get with Spring WebFlux and Thymeleaf

                                                                                                                Anylogic : not able to use stopDelay()