dylib paths

[Lawrence Velázquez]

On Jun 2, 2015, at 1:42 PM, Sterling Smith <smithsp at fusion.gat.com> wrote:

> I am trying to create a port for the MDSplus library.  I have beat the library’s make process into submission to make use of DESTDIR and other standard directories.  So now it creates several dylibs and executables in the proper directories, but for which otool -L yields the build directory for library dependencies instead of the installation directory.  Poking around online, it seems that  install_name_tool can rectify this situation.

install_name_tool is fine, but since you're hacking up the build system anyway, you should make the linking commands use -install_name when creating dylibs.

> Is that not something that macports does automatically?

We can't know what any particular broken build system intends to do.

vq