Sorry to follow up - but didn't want the thread to die off here. Thanks!
On Mon, Sep 13, 2010 at 4:58 PM, Dan Lussier <[email protected]> wrote: > Here is the result: > > % otool -L /opt/local/libexec/qt4-mac/lib/QtGui.framework/Versions/4/QtGui > > /opt/local/libexec/qt4-mac/lib/QtGui.framework/Versions/4/QtGui: > /opt/local/libexec/qt4-mac/lib/QtGui.framework/Versions/4/QtGui > (compatibility version 4.6.0, current version 4.6.3) > /opt/local/libexec/qt4-mac/lib/QtCore.framework/Versions/4/QtCore > (compatibility version 4.6.0, current version 4.6.3) > /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon > (compatibility version 2.0.0, current version 152.0.0) > /opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current > version 1.2.5) > /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit > (compatibility version 45.0.0, current version 1038.29.0) > /opt/local/lib/libpng12.0.dylib (compatibility version 45.0.0, > current version 45.0.0) > /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current > version 7.9.0) > /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current > version 103.0.0) > /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current > version 125.0.1) > /usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version > 227.0.0) > > /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices > (compatibility version 1.0.0, current version 44.0.0) > > /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation > (compatibility version 150.0.0, current version 550.19.0) > > /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices > (compatibility version 1.0.0, current version 38.0.0) > /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation > (compatibility version 300.0.0, current version 751.21.0) > > This Qt library (in /opt) is from MacPorts, while I built the other > one (/Code/qt-pv/...) from source. I used the one built from source > for building PV. Here is the same otool command against that library: > > % otool -L ~/Code/qt-pv/lib/QtGui.framework/Versions/4/QtGui > /Users/<user-id>/Code/qt-pv/lib/QtGui.framework/Versions/4/QtGui: > /Users/<user-id>/Code/qt-pv/lib/QtGui.framework/Versions/4/QtGui > (compatibility version 4.6.0, current version 4.6.3) > /Users/<user-id>/Code/qt-pv/lib/QtCore.framework/Versions/4/QtCore > (compatibility version 4.6.0, current version 4.6.3) > /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon > (compatibility version 2.0.0, current version 152.0.0) > /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version > 1.2.3) > /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit > (compatibility version 45.0.0, current version 1038.32.0) > /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current > version 7.9.0) > /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current > version 103.0.0) > /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current > version 125.2.0) > /usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version > 227.0.0) > > /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices > (compatibility version 1.0.0, current version 44.0.0) > > /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation > (compatibility version 150.0.0, current version 550.29.0) > > /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices > (compatibility version 1.0.0, current version 38.0.0) > /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation > (compatibility version 300.0.0, current version 751.29.0) > > Thanks. > > On Mon, Sep 13, 2010 at 4:10 PM, Michael Jackson > <[email protected]> wrote: >> That will most likely cause "problems" running paraview. You really want to >> make sure you consistently build and load against the same set of Qt >> Libraries. It looks like your Qt installations do NOT have an "install_name" >> that contains the absolute path to the Qt frameworks so setting something >> like DYLD_LIBRARY_PATH may be necessary. And the same for frameworks. >> >> run "otool -L >> /opt/local/libexec/qt4-mac/lib/QtGui.framework/Versions/4/QtGui" >> and post the output. >> >> ___________________________________________________________ >> Mike Jackson www.bluequartz.net >> Principal Software Engineer [email protected] >> BlueQuartz Software Dayton, Ohio >> >> >> >> On Sep 13, 2010, at 3:28 PM, Dan Lussier wrote: >> >>> When I import the paraview Python module from a regular Python >>> interpreter, I get a slew of warning messages like: >>> >>> >>> objc[31181]: Class QNSImageView is implemented in both >>> /opt/local/libexec/qt4-mac/lib/QtGui.framework/Versions/4/QtGui and >>> /.. other directories ... >>> /Code/qt-pv/lib/QtGui.framework/Versions/4/QtGui. One of the two will >>> be used. Which one is undefined. >>> >>> Is this likely to cause a problem in running PV? What is the best way >>> to fix this issue? I was thinking about setting the LD_LIBRARY_PATH >>> to point at the qt library that I used to build PV. >>> >>> Thanks. >>> _______________________________________________ >>> 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 >> >> > _______________________________________________ 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
