[Xcode 11+] The only thing to do is to add the framework to the General->Frameworks, Libraries And Embedded Content section in the General tab of your app target. Make sure you select the ‘Embed & Sign’ option. [Xcode v6 -> Xcode v10] The only thing to do is to add the framework to the Embedded … Read more
Find all the boost libraries (where exefile is the name of your executable): $ 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 … Read more
For me none of the previous solutions worked. We discovered that there is an “Always Embed Swift Standard Libraries” flag in the Build Settings that needs to be set to YES. It was NO by default! Build Settings > Always Embed Swift Standard Libraries After setting this, clean the project before building again. For keen … Read more
In the target’s General tab, there is an Embedded Binaries field. When you add the framework there the crash is resolved. Reference is here on Apple Developer Forums.