MantisBT - ParaView
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0010377ParaViewBugpublic2010-03-05 15:312016-08-12 09:58
ReporterEric Monson 
Assigned ToDavid Partyka 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionmoved 
PlatformOSOS Version
Product VersionDevelopment 
Target VersionFixed in Version 
Project
Topic Name
Type
Summary0010377: OS X internal library paths wrong in installed development tree binaries
DescriptionUsing 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.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-03-05 15:31Eric MonsonNew Issue
2010-03-05 15:44Utkarsh AyachitStatusbacklog => tabled
2010-03-05 15:44Utkarsh AyachitAssigned To => David Partyka
2010-03-17 09:41David PartykaNote Added: 0019926
2010-03-17 09:51Eric MonsonNote Added: 0019927
2010-03-17 15:19Eric MonsonNote Added: 0019943
2016-08-12 09:58Kitware RobotNote Added: 0037794
2016-08-12 09:58Kitware RobotStatusexpired => closed
2016-08-12 09:58Kitware RobotResolutionopen => moved

Notes
(0019926)
David Partyka   
2010-03-17 09:41   
If you run make install I don't think the fixup bundle utilities get run that will run install_name_tool on everything and get rid of the absolute local paths. If you run cpack instead and create say a tar.gz is everything fixed up correctly?

http://www.paraview.org/Wiki/ParaView:Build_And_Install#Install_ParaView [^]
(0019927)
Eric Monson   
2010-03-17 09:51   
I don't have time to try it again this minute, but when I was trying it in January, #3 on this email describes the problems I was having with the TGZ packages.

http://www.mail-archive.com/paraview@paraview.org/msg06204.html [^]

I can try it later this afternoon after I'm back from some meetings.
(0019943)
Eric Monson   
2010-03-17 15:19   
No, if I run cpack to make a tar.gz package, none of the libraries are fixed up -- they are just like the ones mentioned above. The executable in the .app package doesn't have the @executable_path stuff in it (when you look at it with otool -L) and neither do the libraries.

As a caveat, I'm compiling ParaView on my Mac with VTK_USE_RPATH: ON since I still have trouble getting it to build with rpath OFF, if that makes a difference here.
(0037794)
Kitware Robot   
2016-08-12 09:58   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current ParaView Issues page linked in the banner at the top of this page.