handling of @rpath? about macdylibbundler HOT 3 CLOSED

One of the main reasons why dylibbundler never handled rpath is because rpath libraries already are "bundleable", it means the author of that library already handled bundling, and dylibbundler trying working on top of that would be redundent (and in some cases might break some setups that rely on rpath). I don't remember the exact syntax by heart, but you can just add some compiler flag while building your application to tell where to look for rpath libs, that should solve your issue

from macdylibbundler.

The linker flag is:

 -rpath path
             Add path to the runpath search path list for image being created.  At
             runtime, dyld uses the runpath when searching for dylibs whose load
             path begins with @rpath/.

To pass it via clang, you need to escape it, e.g.:

-Wl,-rpath,@executable_path/../Frameworks

@executable_path is relative to the main executable. @loader_path is relative to a library.

That embeds an LC_RPATH load command into the binary. use otool -l to verify it. e.g.:

Load command 42
      cmd LC_RPATH
  cmdsize 48
     path @executable_path/../Frameworks (offset 12)

from macdylibbundler.

Sweet!

from macdylibbundler.