[Paraview] [solved] Library not loading due to reason "image not found".

[Samuel Crow]

A coworker helped my solve the problem by setting the ld path to ./ and selecting the plugin directly from the bundle.

--- On Tue, 7/8/08, Mike Jackson <mike.jackson at imts.us> wrote:

> From: Mike Jackson <mike.jackson at imts.us>
> Subject: Re: [Paraview] Library not loading due to reason "image not found".
> To: "ParaView" <paraview at paraview.org>, samuel_crow_work at rocketmail.com
> Date: Tuesday, July 8, 2008, 2:46 PM
> Try building ParaView with "RPATH ON" for OS X. OR
> do as Ken writes  
> and you will need to set the DYLD_LIBRARY_PATH to the
> <path omitted>/ 
> Paraview_build/bin/ directory.
> 
> <history/informatio>
>    OS X has the notion of the "install_name" for
> dylibs. OS X will  
> encode the path to the library inside the actual library
> itself so  
> when another library or application links to the library
> the  
> application/library will know where to find it thus
> obviating the  
> need for the DYLD_LIBRARY_PATH. This is good and bad. Good
> because  
> you shouldn't have to set environment variables. BAD
> because if you  
> move those libraries somewhere else then everything breaks.
> 
> There are "special" install_name prefixes that
> can be used to get  
> around all this but I think in your case you need to rerun
> ccmake and  
> set the VTK_USE_RPATH to ON.
> 
> OR you can run paraview FROM the <path
> omitted>/Paraview_build/bin/  
> directory. OS X will always look in the current directory
> for dylibs.
> 
> so from a terminal your session might look like the
> following:
> 
> $ make
> $ cd bin
> $ paraview.app/Contents/MacOS/paraview
> 
> {ParaView should now launch}.
> 
> Try all that and let's see what happens.
> 
> -- 
> Mike Jackson   Senior Research Engineer
> Innovative Management & Technology Services
> 
> 
> On Jul 8, 2008, at 10:37 AM, Moreland, Kenneth wrote:
> 
> > It sounds like the system cannot find some dependent
> dynamic  
> > libraries for
> > some reason.  You could try setting your
> LD_LIBRARY_PATH environment
> > variable to point to the libraries.  What does otool
> -L report your  
> > plugin
> > libraries need to reference?
> >
> > -Ken
> >
> >
> > On 7/7/08 1:51 PM, "Samuel Crow"
> <samuel_crow_work at rocketmail.com>  
> > wrote:
> >
> >> Hello,
> >>
> >> As a practice exercise in making readers for
> Paraview 3.2.2, I  
> >> wrote a reader
> >> that loads the specifications of a cube with
> different colors for the
> >> vertexes.
> >>
> >> When I try to load the libSMCubeReader.dylib into
> the server side  
> >> plugin
> >> manager, I get the message "Library not
> loaded:   
> >> libvtkPVFiltersCS.dylib
> >> referenced from <path
> omitted>/Paraview_build/bin/ 
> >> libSMCubeReader.dylib
> >> Reason: image not found."
> >>
> >> When loading the client side plugin I get the
> message from  
> >> QLibrary::load_sys
> >> cannot load <path
> omitted>/Paraview_build/bin/ 
> >> libGUICubeReader.dylib: "Library
> >> not loaded:  libpqComponents.dylib Referenced from
> <path
> >>
> omitted>/Paraview_build/bin/libGUICubeReader.dylib
> Reason: image  
> >> not found"
> >>
> >> I'm on a PowerBook G4 Macintosh with 2 Gb RAM,
> building ParaView from
> >> Unix-style makefiles on XCode 2.4.1 under MacOSX
> 10.4.11 using  
> >> dynamic library
> >> linkage in DEBUG mode.
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> ParaView mailing list
> >> ParaView at paraview.org
> >> http://www.paraview.org/mailman/listinfo/paraview
> >>
> >
> >
> > _______________________________________________
> > ParaView mailing list
> > ParaView at paraview.org
> > http://www.paraview.org/mailman/listinfo/paraview
> >