[Paraview] Building ParaView v5.1.2 on Linux from source with support for GPU and SWR.

[David E DeMarle]

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.albina at 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.demarle at kitware.com]
> *Sent:* Montag, 26. September 2016 15:37
> *To:* Albina, Frank
> *Cc:* paraview at 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
>
>
>
> On Mon, Sep 26, 2016 at 5:17 AM, Albina, Frank <frank.albina at 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
>
> 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
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160926/ed98fa78/attachment.html>