<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<blockquote type="cite">- one build for the front end with GUI: it
has no GPU but a windowing system (this is the blocking point at
this time)
</blockquote>
OK. to accomplish this, first do a Mesa build configured as
follows(glx+software rendering)<br>
<blockquote><tt>../mesa-17.0.6/configure --enable-texture-float
--enable-glx --disable-dri --disable-egl --disable-gles1
--disable-gles2 --disable-gbm --disable-driglx-direct
--disable-xvmc --with-gallium-drivers=swrast,swr
--prefix=/work/apps/mesa/17.0.6-x11-swr<br>
</tt></blockquote>
make sure ParaView can find it, and configure ParaView as follows<br>
<blockquote><tt>export
LD_LIBRARY_PATH=/work/apps/mesa/17.0.6-x11-swr/lib/:$LD_LIBRARY_PATH<br>
cmake
-DOPENGL_INCLUDE_DIR=/work/apps/mesa/17.0.6-x11-swr/include
-DOPENGL_gl_LIBRARY=/work/apps/mesa/17.0.6-x11-swr/lib/libGL.so
~/work/ParaView/<br>
</tt></blockquote>
when you run ParaView the "help/about" dialog should report VMWare
Mesa 17.0.6 Gallium on llvmpipe.<br>
<br>
<div class="moz-cite-prefix">On 05/16/2017 11:18 PM, Patrick Begou
wrote:<br>
</div>
<blockquote
cite="mid:71fe5007-fc1b-874d-81dc-0685b2354c44@legi.grenoble-inp.fr"
type="cite">Yes Burlen, this is exactly what I try to do:
<br>
- one build for the nodes whitout GUI as they have no windowing
system nor GPU (I build this using the wiki documentation)
<br>
- one build for the front end with GUI: it has no GPU but a
windowing system (this is the blocking point at this time)
<br>
- one build on the users workstations where a GPU and a windowing
system are available (this is working too thanks to the wiki
documentation)
<br>
<br>
On the front-end I have a system libGL but too old for Paraview 5
and it is requested by other commercial softwares. This is why I
try to build a new mesa from sources for Paraview. I use the
module environment then to set the LD_LIBRARY_PATH and PATH order
to reach the right libraries and, as strace show, it seams to work
fine. So I suppose it is a mesa configuration mistake in my build.
<br>
<br>
May be should I post on the Mesa forum ?
<br>
<br>
Patrick
<br>
<br>
<br>
Burlen Loring wrote:
<br>
<blockquote type="cite">that's the point. this allows you to run
without the windowing system or GPU on the cluster. Most cluster
have neither. If you wanted to provide the GUI then I would
suggest you have two installs of both ParaView and Mesa. One
based on OSMesa, the other based on some X11 enabled OpenGL.
Alternatively you could install only the OSMesa capable pvserver
as suggested in previous email and direct your users to the
ParaView GUI enabled binaries that Kitware provides on their web
site. The latter is what I have been doing.
<br>
<br>
As an aside, it gets messy when you have two libGL in the same
build. One need to be very careful about library dependencies.
It is possible to do this if one is very careful during link
time. However as far as I know this has not been supported for
quite a long time in VTK/ParaView, and I think it would require
some reorganization of VTK OpernGL classes.
<br>
<br>
Burlen
<br>
<br>
On 05/16/2017 08:38 AM, Patrick Begou wrote:
<br>
<blockquote type="cite">Burlen Loring wrote:
<br>
<blockquote type="cite">../mesa-17.0.2/configure
--enable-texture-float --disable-glx --disable-dri
--disable-egl --disable-gles1 --disable-gles2 --disable-gbm
--disable-driglx-direct --disable-xvmc
--enable-gallium-osmesa --with-gallium-drivers=swrast,swr
--prefix=/usr/common/software/ParaView/mesa/17.0.2/
<br>
</blockquote>
<br>
Hi Burlen,
<br>
<br>
this Mesa setup does not provide libGL requested to build
paraview with GUI enabled :-(
<br>
It is OK for the cluster nodes but not for the frontend where
I need this GUI even with no GPU installed.
<br>
<br>
Patrick
<br>
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
</body>
</html>