I did as suggested If I type paraview in my bin directory without turning on the VTK_USE_RPATH flag - it complains that it can't find qt libs. As you suggested, if I turn on the RPATH flag then I can run Paraview OK from
/home/rakesh/Downloads/Kitware/ParaView-3.4.0/linux/bin when I do make install, my libs are built under /home/rakesh/MyLibraries/Kitware/Paraview/3.4.0 and then go into bin directory and run paraview, I get the following error error while loading shared libraries: libpqComponents.so: cannot open shared object file: No such file or directory Can some one please tell me what I am missing here? I know I can add the LD_LIBRARY_PATH - but for all sorts of reasons and conflicts with other system libs, I would prefer not to take this route. Thanks, Rakesh 2008/11/11 Utkarsh Ayachit <[EMAIL PROTECTED]> > Set the cmake option VTK_USE_RPATH to ON and then rebuild ParaView. > > Utkarsh > > > Dominik Szczerba wrote: > >> yes, it is possible, there should be a cmake option, I dont recall >> exactly, something with RPATH in name. >> >> Dominik >> >> Rakesh Hammond wrote: >> >>> Dear users, >>> >>> Can we some how get around having to specify LD_LIBRARY_PATH for Qt, once >>> we have built paraview to get it up and running? >>> I remember vaguely being able to use -WI -rpath in make files to do some >>> thing similar, is there anyway to specify this within CMake when we build >>> Paraview? >>> >>> Rakesh >>> >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> ParaView mailing list >>> [email protected] >>> http://www.paraview.org/mailman/listinfo/paraview >>> >> >>
_______________________________________________ ParaView mailing list [email protected] http://www.paraview.org/mailman/listinfo/paraview
