[Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader

[Utkarsh Ayachit]

Roger that. I will have updates for you early next week (plan to work
on it as soon as I am done with the task at hand).

On Thu, Jun 2, 2016 at 12:45 PM, Angelini, Richard C (Rick) CIV USARMY
RDECOM ARL (US) <richard.c.angelini.civ at mail.mil> wrote:
> Our *immediate* concern is OSMesa - but we'll probably eventually want to address Mesa w/X support .....
>
> -----Original Message-----
> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
> Sent: Thursday, June 02, 2016 9:48 AM
> To: Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) <richard.c.angelini.civ at mail.mil>
> Cc: Chuck Atkins <chuck.atkins at kitware.com>; ParaView <paraview at paraview.org>
> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
>
> Ah okay. Give me a few days to sort it out. The end goal is indeed to have superbuild build the right versions of Mesa. Do you only  care about OSMesa or also Mesa with X support?
>
> Utkarsh
>
>
>
>
> On Thu, Jun 2, 2016 at 8:48 AM, Angelini, Richard C (Rick) CIV USARMY RDECOM ARL (US) <richard.c.angelini.civ at mail.mil> wrote:
>> Our current issues seem to be related to our osmesa build for the HPC_side
>> servers.       The Superbuild is building 7.11.2 - you are suggesting that
>> we need to *manually* build a different version of Mesa and somehow link
>> in that new version of Mesa in to the Superbuild?     We rely exclusively
>> on the Superbuild for compiling ParaView across 20 different HPC
>> systems - so stepping outside of the super build paradigm isn’t necessarily obvious
>> to me!    8-)
>>
>>
>>
>>
>>
>> ________________________________
>> Rick Angelini
>> USArmy Research Laboratory
>> CISD/HPC Architectures Team
>> Phone:  410-278-6266
>>
>>
>>
>>
>> -----Original Message-----
>> From: Utkarsh Ayachit <utkarsh.ayachit at kitware.com>
>> Date: Thursday, June 2, 2016 at 8:37 AM
>> To: Rick Angelini <Richard.C.Angelini.CIV at mail.mil>
>> Cc: Chuck Atkins <chuck.atkins at kitware.com>, ParaView
>> <paraview at paraview.org>
>> Subject: Re: [Paraview] [Non-DoD Source] Re: 5.0.1/Exodus Reader
>>
>> All active links contained in this email were disabled.  Please verify
>> the identity of the sender, and confirm the authenticity of all links
>> contained within the message prior to copying and pasting the address
>> to a Web browser.
>>
>>
>>
>>
>> ----
>>
>>> So there is much more to be done than adding
>>> -DPARAVIEW_RENDERING_BACKEND:STRING=OpenGL2
>>> -DVTK_RENDERING_BACKEND:STRING="OpenGL2"
>>> to the cmake flags?
>>
>> As far as ParaView is concerned, no there's not much more to it.
>> However if your OpenGL implementation doesn't support OpenGL 3.2
>> (released in 2009), then alas there's more work to get ParaView
>> working which could include building a newer version of Mesa. Not sure
>> if you have seen this blog [1], but that talks about how I got Mesa to
>> build with appropriate OpenGL renderer enabled. Things have gotten a
>> little better since then and the Docker script encapsulates that. The
>> moral of the story is get latest Mesa version and build it with
>> LLVM/Gallum support.
>>
>> Utkarsh
>>
>> [1]
>> Caution-https://blog.kitware.com/messing-with-mesa-for-paraview-5-0vtk
>> -7-0/
>>