Hi Michael, On Wed, Feb 13, 2013 at 1:46 PM, Michael Jackson < mike.jack...@bluequartz.net> wrote:
> If you look at > "/Users/schmitt/paraview/opt/ParaView-3.98.1_RC1_OSX-10.7/paraview/src/paraview-build/lib/libvtkpqComponents-pv3.98.1.dylib" > what does the RPATH to HDF5 library look like? It should be something like > @executable_path/../lib/libhdf5.dylib or some such thing. If it does not > have a path at all and just the name of the library (libhdf5.dylib) then > something is not updating those libraries correctly. > > Yes -- pqComponents does not have the paths to hdf5 fixed: > otool -L /Users/schmitt/paraview/opt/ParaView-3.98.1_RC1_OSX-10.7/paraview/src/paraview-build/lib/libvtkpqComponents-pv3.98.1.dylib | grep hdf5 > libhdf5.7.3.0.dylib (compatibility version 7.3.0, current version 1.8.9) > libhdf5_hl.7.3.0.dylib (compatibility version 7.3.0, current version 1.8.9) This confuses me because I thought I did a fairly straightforward SuperBuild: 1. git clone git://paraview.org/ParaViewSuperbuild.git; I see the same behavior with ParaView GIT_TAG in versions.cmake to both "v3.98.0" and "master". 2. In an empty build directory, I use ccmake with settings described in my first post http://www.paraview.org/pipermail/paraview/2013-February/027433.html 3. gmake 4. ctest 5. cpack -G"DragNDrop" Here's additional info on my system: * OSX-10.7.5 * xcode-4.4.1 * GNU i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00) * Not sure if it matters, but GNU Fortran (MacPorts gcc47 4.7.1_2) 4.7.1
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview