On Wed, Aug 30, 2017 at 5:02 PM, Michael Povolotskyi <mpovo...@purdue.edu>
wrote:
> I can try that, thank you.
>
> Still, why some libraries are found and some are not? Should this be
> covered when libmesh_opt.so is built?
>
This depends on the way VTK was built on your system. When I build VTK, I
use the following Cmake flags to "compile in" the installation paths to the
libraries themselves. This works on Mac, on Linux your mileage may vary...
-DCMAKE_INSTALL_RPATH:STRING="/path/to/vtk/lib"
-DCMAKE_INSTALL_RPATH_USE_LINK_PATH:BOOL=ON
-DCMAKE_INSTALL_NAME_DIR:STRING="/path/to/vtk/lib"
Additionally, the use of system modules (e.g. module load vtk) is
recommended to control the contents of environment variables like
LD_LIBRARY_PATH in a transparent way.
--
John
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Libmesh-users mailing list
Libmesh-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-users
