[Paraview-developers] CMake Version

[David E DeMarle]

Is there any reason why we don't bump up the minimum cmake for VTK to keep
HDF5 happy rather than the other way around?

FYI:

Minimum cmake on the vtk dashboard right now is (from
./VTK/Utilities/Maintenance/vtk_submitter_summary.py /vtk_submitter_summary.py
| grep CMAKE_VERSION)

CMAKE_VERSION;2.8.8;;['karego-at.kitware', 'dash3.kitware',
'tarvalon.kitware']

Those do not have XDMF and thus HDF5 turned on, which is why we haven't
noticed this before now. ParaView by default turns HDF5 on, so it would be
more obvious there if.






David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909

On Thu, Jan 8, 2015 at 11:04 AM, Dan Lipsa <dan.lipsa at kitware.com> wrote:

>
> On Thu, Jan 8, 2015 at 10:03 AM, Ben Boeckel <ben.boeckel at kitware.com>
> wrote:
>
>> On Thu, Jan 08, 2015 at 12:25:47 +0530, Chiranjib Sur wrote:
>> > For building Paraview 4.2, I am using cmake-3.0.2. Although the
>> > paraview build prerequisite says it should work with cmake 2.8.8.
>>
>> Looking at VTK, the HDF5 we upgraded to now has 2.8.10 and 2.8.11
>> minimum requirements in it. This should probably be looked at to keep
>> VTK down to 2.8.8.
>>
>
> I'll look at this.
> Dan
>
>
> _______________________________________________
> Paraview-developers mailing list
> Paraview-developers at paraview.org
> http://public.kitware.com/mailman/listinfo/paraview-developers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150108/0a6cc2a9/attachment.html>