[Paraview] Software Rendering

[Kent Eschenberg]

One more detail: before you run paraview make sure the path(s) in LD_LIBRARY_PATH point to the Mesa libraries before the libraries for OpenGL. If the shared object is not found using the paths in LD_LIBRARY_PATH your system will then look in several other places (e.g., /usr/lib) defined at the system level.

Use something like "ldd paraview" to see whether your system is using the desired libraries.

On our Redhat's Fedora Core 5 (32 bit) and Enterprise 4 (64 bit) machines the path specified at link time (in JB's example, /home/biddisco/Mesa-6.5.1/lib) is NOT recorded in the paraview executable (e.g., "paraview", "pvclient", "pvserver"); instead, only the library name (e.g., libGL.so) is recorded. The system selects WHICH libGL.so to use when the program is started.

Is all this true on all Linux/Unix/Mac/Windows systems?

Kent
Pittsburgh Supercomputing Center

--On 01/23/2007 09:24:00 AM +0100 biddisco at cscs.ch wrote:
> Jim,
>> OPENGL_INCLUDE_DIR                   /usr/include
>> OPENGL_gl_LIBRARY                       /usr/X11R6/lib64/libGL.so
>> OPENGL_glu_LIBRARY                     /usr/X11R6/lib64/libGLU.so 
>> OSMESA_INCLUDE_DIR                  /usr/include
>> OSMESA_LIBRARY                           /usr/X11R6/lib64/libOSMesa.so
> 
> Try this : point these to your Mesa build. Mine looks like this...
> 
>  OPENGL_INCLUDE_DIR               /home/biddisco/Mesa-6.5.1/include
>  OPENGL_gl_LIBRARY                /home/biddisco/Mesa-6.5.1/lib/libGL.so
>  OPENGL_glu_LIBRARY               /home/biddisco/Mesa-6.5.1/lib/libGLU.so
>  OPENGL_xmesa_INCLUDE_DIR         /home/biddisco/Mesa-6.5.1/include
>  OSMESA_INCLUDE_DIR               /home/biddisco/Mesa-6.5.1/include
>  OSMESA_LIBRARY                   /home/biddisco/Mesa-6.5.1/lib/libOSMesa.so
> 
> So that the GL is Mesa GL and not the system GL. This ought to help prevent the app picking up the wrong one.
> 
> JB