UPDATE: VTK-4.2.6 add install_name support

[cssdev@…]

The attached Portfile patch updates the VTK port to specify the correct install_name. This feature is only provided by the cmake-devel port, but older versions of CMake will simply ignore the new options. I don't think this warrants a variant, as the need for install_name support is not essential due to the an workaround with DYLD_FALLBACK_LIBRARY_PATH.

Because this feature is only available through the cmake-devel port at this time, it's possible to install that port before building VTK. However, I don't want to force a dependency on a devel port. Should I simply update the Portfile and provide a message that people requiring install_name support should install cmake-devel first?

See BUG #4495 and BUG #7571.

[cssdev@…]

vtk Portfile patch

[cssdev@…]

It just occurred to me that older versions of CMake will still include the incorrect path using the build directory. If cmake-devel is installed, then the VTK port should use the new features available. Otherwise, it should completely exclude rpath support.

Maybe the Portfile can parse the output from 'cmake --version' to determine the currently installed version of CMake? That gets ugly, as the alternative is to strictly depend on the cmake-devel port. Perhaps a variant could rely on cmake-devel with the updated install_names, while the default could rely on the stable version of cmake without install_names (relying instead on DLYD_LIBRARY_PATH)?

[cssdev@…]

vtk Portfile patch

[cssdev@…]

Changed bug title to reflect that this issue may now be resorted with an update to the VTK Portfile.

[cssdev]

Reassign to maintainer.

[cssdev]

Set verbose compiling and libraries' install_names

[cssdev]

CMake usually hides the compile commands, and that can make debugging with port -v build challenging. The latest patch simply sets CMake to verbose mode in addition to setting the required flags for rpath/install_name support.

[cssdev]

Fixed in r19880.