MantisBT - ParaView
View Issue Details
0012639ParaView(No Category)public2011-10-10 17:042016-08-12 09:58
Robert Maynard 
Kitware Robot 
highminorhave not tried
closedmoved 
3.12 
 
Sandia
incorrect functionality
0012639: Configuration with MESA enabled is a nightmare
Currently you have to set the following flags to properly build with OSMesa.

VTK_OPENGL_HAS_OSMESA is enabled.
OPENGL_INCLUDE_DIR set to OSMesa library
OPENGL_gl_LIBRARY is empty if you want offscreen rendering
OPENGL_glu_LIBRARY set the to library built by OSMesa
VTK_USE_X is turned off

Ontop of that VTK_USE_X doesn't properly clear itself once it is toggled on, so if that happens you need to blow away the entire build directory.

We really should have a single non advanced option which is ENABLE_OSMESA which does everything for the end user.
No tags attached.
Issue History
2011-10-10 17:04Robert MaynardNew Issue
2011-10-10 17:08Alan ScottNote Added: 0027561
2011-10-10 17:11Alan ScottNote Added: 0027562
2016-08-12 09:58Kitware RobotNote Added: 0038081
2016-08-12 09:58Kitware RobotStatusbacklog => closed
2016-08-12 09:58Kitware RobotResolutionopen => moved
2016-08-12 09:58Kitware RobotAssigned To => Kitware Robot

Notes
(0027561)
Alan Scott   
2011-10-10 17:08   
Furthermore, if Mesa is turned on, if a user turns on an incompatible switch, at least a warning message should be printed out.
(0027562)
Alan Scott   
2011-10-10 17:11   
OK, I just checked, and VTK_USE_X is turned on by default, and must explicitly be turned off. This is nuts.
(0038081)
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.