[Cmb-users] Updates to CMB for VTK's OpenGL2 backend

[Marcus D. Hanwell]

On Tue, Dec 23, 2014 at 9:16 AM, Marcus D. Hanwell
<marcus.hanwell at kitware.com> wrote:
> Hi David,
>
> On Mon, Dec 22, 2014 at 11:03 PM, David Thompson
> <david.thompson at kitware.com> wrote:
>>>>> I just pushed updates to a few repositories, and had a pull request
>>>>> merged in SMTK to make it possible to build CMBv4 with OpenGL2-based
>>>>> ParaView/VTK. ...
>>>>
>>>> I am using an older version of ParaView (SHA 55f3b0e, from around Sep 10) and get link errors building libsmtkDiscreteBridge.dylib in SMTK ("library not found for -lvtkRendering"), ...
>>>>
>>> I didn't realize people would want to use old ParaView/VTK, I added a
>>> new commit, and will make a pull request, that should address this.
>>
>>
>> I am still getting the same error message. Also, if I want to build ParaView master with the OpenGL2 backend, do I need to set anything beside VTK_RENDERING_BACKEND:STRING=OpenGL2 ? I tried that and (after turning off some PV plugins) it starts building but then dies with
>>
>> [ 74%] Undefined symbols for architecture x86_64:
>>   "vtkWebGLObject::GetId()", referenced from:
>>       vtkPVWebApplication::GetWebGLSceneMetaData(vtkSMViewProxy*) in vtkPVWebApplication.cxx.o
>>   "vtkWebGLObject::isVisible()", referenced from:
>>       vtkPVWebApplication::GetWebGLSceneMetaData(vtkSMViewProxy*) in vtkPVWebApplication.cxx.o
>>       vtkPVWebApplication::GetWebGLBinaryData(vtkSMViewProxy*, char const*, int) in vtkPVWebApplication.cxx.o
>>
> Not to get all picky but that looks like a very different error
> message ;-) Before it couldn't find the libraries, now it is just a
> few symbols. Annoyingly Linux doesn't resolve symbols upfront, and if
> they are not used never will - guessing this is from the pickier Apple
> linker.

I need to drink more coffee before replying...I thought that was the
CMB error. Maybe the code I added doesn't trickle down to all the
files then, I will try to build an old VTK pre-backend vars to figure
out what I missed. There are a few patches Utkarsh merged this morning
that should make the above go away, I am just rebuilding PV to verify,
otherwise you must disable ParaViewWeb.

Marcus