David, I could manage to get Paraview 5.1.2 compiled using the ParaView superbuild on my Linux desktop running OpenSuSE 12.3.
In this regard, I would like to point out a few things I have found while performing the build process on the aforementioned Linux distribution. Note that my incentive is to help improve the ParaView software suite as well as helping others to be able to build and use the software. 1. I found it this page quite useful for having at least a starting point for building ParaView v5.1.2 on Linux: https://cmake.org/Wiki/ParaView/Binaries 2. You definitely need cmake at least cmake v3.5 (and not v3.3) to compile ParaView from SuperBuild. 3. You need a GNU compiler v4.8.0 or above to build. My Linux distribution comes with gcc v4.7.2. Fortunately, I had gcc v4.9.2 installed with which I could perform a successful build. 4. Dependencies such libsz, libxml, libbzip2 are built and stored in the <build>/install/lib64 directory on my platform. This creates linking issues which I could partly resolve by pushing the missing libraries into the <build>/install/lib directory. This is not ideal but could be solved by forcing the lib directory to <build>/install/lib using the --libdir option. 5. The vistrails plugin cannot be built. After 3 attempts, the git clone from https://kwgitlab.kitware.com/paraview/vistrails.git fails. Either the link is wrong or the server is unreachable. 6. The mesa libraries are pre-compiled and downloaded to <buils>/mesa-downloads. They are unpacked and moved into the ParaView installation directory when performing “make install”. These libraries are dating from May 3rd, hence prior to the release of Mesa 12.0 which embeds OpenSWR as a build option. Is there a way to build new libGL.so and libOSMesa.so libraries based on Mesa3D v12.0 and replace the currently pre-compiled binaries? If so,what are the typical configuration options used in this case? Any feedback/comments are most welcome. Regards, Frank. From: Albina, Frank Sent: Montag, 26. September 2016 15:51 To: 'David E DeMarle' Cc: paraview@paraview.org; Del Citto, Francesco Subject: RE: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR. Perfect! Thanks. Frank. From: David E DeMarle [mailto:dave.dema...@kitware.com] Sent: Montag, 26. September 2016 15:49 To: Albina, Frank Cc: paraview@paraview.org<mailto:paraview@paraview.org>; Del Citto, Francesco Subject: Re: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR. 3.3 David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Mon, Sep 26, 2016 at 9:42 AM, Albina, Frank <frank.alb...@sauber-motorsport.com<mailto:frank.alb...@sauber-motorsport.com>> wrote: Hi David! Thanks for the swift feedback. As I have been compiling ParaView from source for at least the last 6 years, it never came to my mind trying out the super-build. £ I’ll try it out and report if I find myself stuck. By the way, which CMake version do you recommend for building ParaView v5.1.2 from the git repository? Best regards, Frank. From: David E DeMarle [mailto:dave.dema...@kitware.com<mailto:dave.dema...@kitware.com>] Sent: Montag, 26. September 2016 15:37 To: Albina, Frank Cc: paraview@paraview.org<mailto:paraview@paraview.org>; Del Citto, Francesco Subject: Re: [Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR. I recommend the ParaView superbuild. All of the incantations that we use to setup and build paraview, mesa and the rest of our dependencies are written down and maintained there. https://gitlab.kitware.com/paraview/paraview-superbuild We've used it for our Desktop binaries for years, and more and more often we use it for our HPC installs as well. David E DeMarle Kitware, Inc. R&D Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909<tel:518-881-4909> On Mon, Sep 26, 2016 at 5:17 AM, Albina, Frank <frank.alb...@sauber-motorsport.com<mailto:frank.alb...@sauber-motorsport.com>> wrote: Dear all, after having downloaded last week the latest ParaView release (v5.1.2) for Linux, I have found out that the binary version has the following folder structure in lib/paraview-5.1: mesa-llvm |-- libGL.so -> libGL.so.1 |-- libGL.so.1 -> libGL.so.1.5 |-- libGL.so.1.5 |-- libOSMesa.so -> libOSMesa.so.8 |-- libOSMesa.so.8 -> libOSMesa.so.8.0.0 `-- libOSMesa.so.8.0.0 mesa-swr-avx |-- libGL.so -> libGL.so.1 |-- libGL.so.1 -> libGL.so.1.5 |-- libGL.so.1.5 |-- libOSMesa.so -> libOSMesa.so.8 |-- libOSMesa.so.8 -> libOSMesa.so.8.0.0 `-- libOSMesa.so.8.0.0 mesa-swr-avx2 |-- libGL.so -> libGL.so.1 |-- libGL.so.1 -> libGL.so.1.5 |-- libGL.so.1.5 |-- libOSMesa.so -> libOSMesa.so.8 |-- libOSMesa.so.8 -> libOSMesa.so.8.0.0 `-- libOSMesa.so.8.0.0 Which is an elegant way of providing a binary package for GPU and non-GPU architectures at the same time. Hence my question: How do I build ParaView v5.1.2 from source to have the same folder structure so that I have one version for GPU and software rendering? I understand that swr-avx(2) should be also available from Mesa v12.x. Is there anything I’d need to consider / take care of before building the different OSMesa libraries with LLVM / OpenSWR? Frank Albina _______________________________________________ Powered by www.kitware.com<http://www.kitware.com> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
