[Paraview-developers] cmake trouble with origin/next (3.98 ish)

[Utkarsh Ayachit]

I think the odd part is that it wasn't enabled by default. It should
be. That's what leads me to believe that something is awry in the
initial stages itself.

On Fri, Nov 23, 2012 at 11:22 AM, Moreland, Kenneth <kmorel at sandia.gov> wrote:
> You are rendering with Mesa, and Mesa is a compliant OpenGL implementation,
> so enabling IceTUSE_OPENGL doesn't seem odd to me at all.
>
> -Ken
>
> Sent from my iPad so blame autocorrect.
>
> On Nov 23, 2012, at 7:28 AM, "Biddiscombe, John A." <biddisco at cscs.ch>
> wrote:
>
> Well after about 100 cmake configures, I finally have 100% built
>
> Had to enable virtually everything that didn’t have Qt/SQL or python in the
> title. Got the usual link errors for netcdf and system hdf5 but managed to
> work around those. Finally, rendering wanted IceTGL libs so I had to enable
> IceTUSE_OPENGL which seems odd, but it picked up mesa and all is built. (Bet
> it doesn’t work when I test it now).
>
>
>
> <sigh J >
>
>
>
>
>
>
>
> From: Biddiscombe, John A.
> Sent: 23 November 2012 14:14
> To: Biddiscombe, John A.; paraview-developers at paraview.org
> Subject: RE: cmake trouble with origin/next (3.98 ish)
>
>
>
> I manually turn on Module_vtklibxml2 and then it tells me vtkTestingCore is
> missing. Turn that on (I have testing disabled anyway) and now it wants
> vtkCosmo, this could become annoying …. I wonder how many I’ll have to
> enable by hand.
>
>
>
> Module_vtkFiltersCosmo
>
> Module_vtkFiltersFlowPaths
>
> Module_vtkImagingFourier
>
> Module_vtkalglib
>
> And on we go …..
>
>
>
>
>
> From: paraview-developers-bounces at paraview.org
> [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Biddiscombe,
> John A.
> Sent: 23 November 2012 13:29
> To: paraview-developers at paraview.org
> Subject: [Paraview-developers] cmake trouble with origin/next (3.98 ish)
>
>
>
> Building on the cray, I am getting a problem and I’m not quite sure what it
> means. (NB. I commented out some IceTGL which told me it was an exported
> target that wasn’t being built … using mesa obviously, hopefully this is
> unrelated)
>
>
>
> If anyone can tell me how to make this go away before I fix it myself,
> please tell.
>
>
>
> Ta
>
>
>
> JB
>
>
>
> VTK will be built with OSMesa support!
>
>
>
> CMake Error at VTK/CMake/vtkModuleAPI.cmake:90 (message):
>
>    Requested modules not available:
>
>
>
>      vtklibxml2
>
> Call Stack (most recent call first):
>
>    VTK/CMake/vtkModuleAPI.cmake:48 (vtk_module_config)
>
>    CMake/vtkClientServerWrapping.cmake:19 (vtk_module_dep_includes)
>
>    Wrapping/ClientServer/CMakeLists.txt:9 (vtk_add_cs_wrapping)
>
>
>
>
>
>
>
>
>
> --
>
> John Biddiscombe,                        email:biddisco @.at.@ cscs.ch
>
> http://www.cscs.ch/
>
> CSCS, Swiss National Supercomputing Centre  | Tel:  +41 (91) 610.82.07
>
> Via Trevano 131, 6900 Lugano, Switzerland   | Fax:  +41 (91) 610.82.82
>
>
>
> _______________________________________________
>
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
>
>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
>