<div dir="ltr">Thank you for the suggestions Chuck,<br><br>I tried the configuration: EL7-OSMesa.cmake with the edit that you suggested.<br><br>It first failed when I ran: cmake -C ../paraview-superbuild/cmake/sites/EL7-OSMesa.cmake ../paraview-superbuild/<br><br>The error was:<br><br><i>CMake Error at superbuild/cmake/SuperbuildRevisionMacros.cmake:339 (message):<br> The 5.2.0-RC4 source selection for paraview does not exist.<br>Call Stack (most recent call first):<br> versions.cmake:60 (superbuild_set_selectable_source)<br> superbuild/CMakeLists.txt:96 (include)<br><br>-- Configuring incomplete, errors occurred!<br></i><br><br>I took at a look at the EL7-OSMesa.cmake file and it looks like there is a hardcoded paraview version in there. The option: set(paraview_SOURCE_SELECTION 5.2.0-RC4 CACHE BOOL "") . I changed it from 5.2.0-RC4 to 5.2.0 and the configuration continued on until it hit another failure. I changed set(ENABLE_paraviewsdk ON CACHE "") to set(ENABLE_paraviewsdk ON CACHE BOOL "") [note the BOOL], and that seemed to fix the issue.<br><br><br>Upon doing 'make' the compilation failed in the HDF5 stage with the following error.<br><br><i>CMakeFiles/Makefile2:127: recipe for target 'src/CMakeFiles/hdf5.dir/all' failed<br>gmake[4]: *** [src/CMakeFiles/hdf5.dir/all] Error 2<br>Makefile:149: recipe for target 'all' failed<br>gmake[3]: *** [all] Error 2<br>CMake Error at /home/neal/software/ParaView_osMesa_Superbuild/build/superbuild/sb-hdf5-build.cmake:43 (message):<br> Failed with exit code 2<br><br><br>superbuild/CMakeFiles/hdf5.dir/build.make:115: recipe for target 'superbuild/hdf5/stamp/hdf5-build' failed<br>make[2]: *** [superbuild/hdf5/stamp/hdf5-build] Error 1<br>CMakeFiles/Makefile2:2399: recipe for target 'superbuild/CMakeFiles/hdf5.dir/all' failed<br>make[1]: *** [superbuild/CMakeFiles/hdf5.dir/all] Error 2<br>Makefile:127: recipe for target 'all' failed<br>make: *** [all] Error 2</i><br><br>I'm unsure about how to resolve the failure. I am using cmake-3.6. There is a version of hdf5 already installed on the system( which h5dump gives: /usr/lib64/mpi/gcc/openmpi/bin/h5dump ).<br><br>Have you ever had issues with the hdf5 compilation of the superbuild?<br><br>Thank you,</div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Dec 19, 2016 at 3:52 PM, Chuck Atkins <span dir="ltr"><<a href="mailto:chuck.atkins@kitware.com" target="_blank">chuck.atkins@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div><div><div>Hi Christopher,<br><br></div>While I haven't tested with OpenSuSE, I have been testing extensively with SLES12.2 and EL7. I usually recommend to build a CMake cache file to encode the appropriate options used that you can save off as your build's configuration file. You can see many current examples in the cmake/sites directory. Specifically, the EL7-OSMesa.cmake configuration will likely be a good place to start for you. To use it:<br><br></div><div><span style="font-family:monospace,monospace"># Clone the repo and it's submodules<br></span></div><div><span style="font-family:monospace,monospace"># The current superbuild master/ branch is pointing to the ParaView 5.2.0 release<br></span></div><div><span style="font-family:monospace,monospace">git clone https;//gitlab./<a href="http://kitware.com/paraview/paraview-superbuild.git" target="_blank">kitware.com/<wbr>paraview/paraview-superbuild.<wbr>git</a> source<br></span></div><div><span style="font-family:monospace,monospace">cd source<br></span></div><div><span style="font-family:monospace,monospace">git submodule init<br></span></div><div><span style="font-family:monospace,monospace">git submodule update<br><br></span></div><div><span style="font-family:monospace,monospace"># Setup the build location<br></span></div><div><span style="font-family:monospace,monospace">cd ..<br></span></div><div><span style="font-family:monospace,monospace">mkdir build<br></span></div><div><span style="font-family:monospace,monospace">cd build<br><br></span></div><div><span style="font-family:monospace,monospace"># Configure<br></span></div><span style="font-family:monospace,monospace">cmake -C /path/to/sb-source/cmake/</span><span style="font-family:monospace,monospace">sites<wbr>/EL7-OSMesa.cmake /path/to/sb-source<br><br></span></div><div><span style="font-family:monospace,monospace"># Build<br></span></div><span style="font-family:monospace,monospace">make<br><br></span></div><div><span style="font-family:monospace,monospace"># Install<br></span></div><span style="font-family:monospace,monospace">make install</span><br><br></div>In your case specifically, you'll want to add the following to the config file:<br><br></div><span style="font-family:monospace,monospace">set(ENABLE_paraviewsdk ON CACHE "")</span><br><br></div>This will make sure the necessary headers and CMake files get packaged for using Catalyst. This will build with OSMesa enabling both the llvmpipe and OpenSWR drivers. Also, instead of a "make install", you can run "ctest -R cpack-paraviewsdk-TGZ" which will generate a tarball that you can "install" by extracting wherever you want it to end up.<br><br></div>We're still working on getting good HowTo docs for the Superbuild, which has been challenging because many different users tend to use it in many different ways. I hope this helps give you a good place to start though.<br><div><br><div><div><div><div><div><div><div><div><br></div></div></div></div></div></div></div></div></div><div class="gmail_extra"><br clear="all"><div><div class="m_-5689166271470711857gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">----------<br>Chuck Atkins<br>Staff R&D Engineer, Scientific Computing<br>Kitware, Inc.<br><br></div></div></div></div></div></div></div>
<br><div class="gmail_quote"><div><div class="h5">On Mon, Dec 19, 2016 at 12:30 PM, Christopher Neal <span dir="ltr"><<a href="mailto:chrisneal@snumerics.com" target="_blank">chrisneal@snumerics.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">Hi all,<br>
<br>
I just saw that the paraview superbuild has be greatly refactored. I<br>
wanted to try and give another shot to something that I have been<br>
trying to do for a while now. My goal is to compile a version of<br>
paraview with osmesa enabled such that an HPC code that is<br>
instrumented with Catalyst calls can run on a computer without having<br>
to open up a window to render images.<br>
<br>
Has anyone had luck building the superbuild with osmesa on OpenSuse<br>
13.2? I'm trying to put together an appropriate configuration script<br>
that conforms to the new superbuild's style.<br>
<br>
Thank you,<br>
<br>
--<br>
Christopher Neal<br>
Research Engineer<br>
Streamline Numerics, Inc.<br></div></div>
______________________________<wbr>_________________<br>
Powered by <a href="http://www.kitware.com" rel="noreferrer" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" rel="noreferrer" target="_blank">http://www.kitware.com/opensou<wbr>rce/opensource.html</a><br>
<br>
Please keep messages on-topic and check the ParaView Wiki at: <a href="http://paraview.org/Wiki/ParaView" rel="noreferrer" target="_blank">http://paraview.org/Wiki/ParaV<wbr>iew</a><br>
<br>
Search the list archives at: <a href="http://markmail.org/search/?q=ParaView" rel="noreferrer" target="_blank">http://markmail.org/search/?q=<wbr>ParaView</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://public.kitware.com/mailman/listinfo/paraview" rel="noreferrer" target="_blank">http://public.kitware.com/mail<wbr>man/listinfo/paraview</a><br>
</blockquote></div><br></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Christopher Neal</div>Research Engineer<div>Streamline Numerics, Inc.</div></div></div>
</div>