On Thu, Jun 23, 2016 at 4:20 PM, Christoph Grüninger <f...@grueninger.de> wrote: > Hi Ben, > >> I think the easiest way to check this would be to set the minimum to 3.3 >> and run against 3.5 to see if any POLICY warnings are triggered for the >> way openSUSE builds ParaView. If they are, the old version is probably >> silently doing something wrong. > > I just did exactly that, no warning from CMake occurs. So we can assume > everything would be fine with CMake 3.3. Should I create an according > Github merge request?
Sure, sounds like a plan. @Utkarsh, any foreseeable problems reducing the CMake required version to 3.3? @Ben, I assume all the dashboard machines are running CMake 3.5. Do you think we should downgrade one to CMake 3.3? Thanks, Cory > > Bye > Christoph > _______________________________________________ > 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 -- Cory Quammen R&D Engineer Kitware, Inc. _______________________________________________ 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
