OS X internal library paths wrong in installed development tree binaries
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
Using OS X (10.6.2 in my case), when PARAVIEW_INSTALL_DEVELOPMENT is turned on, and you do a "make install", the library paths in the executable binaries installed in the development tree at [install_prefix]/bin/ are incorrect.
So, when trying to do things like build a branded app against the installed development tree, I get things like:
dyld: Library not loaded: libvtkCommon.pv3.7.dylib Referenced from: /usr/local/ParaView/bin/kwProcessXML Reason: image not found
If I run "otool -L" on kwProcessXML (or on any app in that directory), the library paths don't point to the correct lib directories:
emo2:/usr/local/ParaView/bin> otool -L kwProcessXML kwProcessXML: libvtkCommon.pv3.7.dylib (compatibility version 0.0.0, current version 0.0.0) libvtksys.pv3.7.dylib (compatibility version 0.0.0, current version 0.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 123.0.0) /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.9.0)
It looks like the application installed at /Applications/ParaView 3.7.0.app/ has all of the correct paths, though, so this part is working fine.